Skip to contentSkip to conversation

why CURRENT->sector is zero??

DISCUSSION mohanlal jangir 2 participants 2 messages Mar 17, 2005

lore
Share & tools
lore
#0 lore raw

I downloaded sbull.c (for LDD 2nd Edition) from http://examples.oreilly.com/linuxdrive/. After compiling and inserting (registering as block device), I tried to mount different file systems (Although there is no valid file system there; my goal is to observe value of req->sector in sbull_transfer function). The observations are as follows:
File System req->sector
msdos 0
vfat 0
ext2 2
ext3 2
iso9000 72

I don't know about other file systems, but I believe the value of req->sector for msdos/vfat is wrong. Because when I mount a CF card having FAT file system on my Linux box (using USB mass storage driver), the first read request contains sector 0x20. Does someone have any clue, why sbull gets this value as 0 rather then 0x20? Basically this means why CURRENT->sector is 0?
I am working on 2.4.18; a little old :(

Regards
Mohanlal

#1 lore raw

Hello.

Quoted 1 line

I downloaded sbull.c (for LDD 2nd Edition) from

Please note that sbull is a block device not hosting partitions.

Quoted 7 lines

of req->sector in sbull_transfer function). The observations are as follows:
File System req->sector
msdos 0
vfat 0
ext2 2
ext3 2
iso9000 72

If there is no filesystem in the device, you just get the probe transfers. Not very interesting, indeed. Some filesystems have their magic number in the first sector, and some have it later in the device.

Quoted 4 lines

I don't know about other file systems, but I believe the value of req->sector for msdos/vfat is wrong. Because when I mount a CF card having FAT file system on my Linux box (using USB mass storage driver), the first read request contains sector 0x20.

Before you state it's wrong you should see some effect. In your case there is no effect at all. If you make a filesystem on the device you'll see it works. So if this concerns you, you should look for an explanation rather than saying it is wrong.

Quoted 1 line

Does someone have any clue, why sbull gets this value as 0 rather then 0x20?

I suspect because the device is not partitioned, while the other one is, so every transfer just is done inside the partition (while the low-level access uses absolute sector number of the device).

/alessandro