linux-kernel - Re: Disk geometry from /sys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <480F0278.1080007@bfh.ch>
Date:	Wed, 23 Apr 2008 11:33:44 +0200
From:	Seewer Philippe <philippe.seewer@....ch>
To:	Francis Moreau <francis.moro@...il.com>
CC:	Mark Lord <lkml@....ca>, linux-kernel@...r.kernel.org
Subject: Re: Disk geometry from /sys


Francis Moreau wrote:
[snip]
> If I'd like to take a look in the kernel code to see where the kernel
> translates an offset
> provided by sys_read into a LBA or CHS address, where should I go ?
> drivers/block ?
No just /block

from Documentation/block/biodoc.txt

[quote]
Drivers no longer have to map a {partition, sector offset} into the
correct absolute location anymore, this is done by the block layer, so
where a driver received a request ala this before:

         rq->rq_dev = mk_kdev(3, 5);     /* /dev/hda5 */
         rq->sector = 0;                 /* first sector on hda5 */

   it will now see

         rq->rq_dev = mk_kdev(3, 0);     /* /dev/hda */
         rq->sector = 123128;            /* offset from start of disk */
[/quote]


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