Date: Thu, 17 Mar 2005 14:42:45 +0530
From: mohanlal jangir <mohanlal@samsung.com>
Subject: why CURRENT->sector is zero??
To: Linux Kernel <linux-kernel@vger.kernel.org>,
       Linux Newbies <kernelnewbies@nl.linux.org>
Cc: rubini@gnu.org, rubini@fsfeurope.org, rubini@prosa.it, rubini@gnudd.com,
       rubini@linux.it
Message-id: <01ae01c52ad1$83e79190$3d476c6b@sisodomain.com>
MIME-version: 1.0
Content-type: text/plain; reply-type=original; charset=iso-8859-1; format=flowed
Content-transfer-encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1148
Lines: 29


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 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/