linux-kernel - Re: fs/bio.c - Hardcoded sector size ?

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: <20060929113814.db87b8d5.rdunlap@xenotime.net>
Date:	Fri, 29 Sep 2006 11:38:14 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Roger Gammans <roger@...puter-surgery.co.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: fs/bio.c - Hardcoded sector size ?

On Thu, 28 Sep 2006 19:22:38 +0100 Roger Gammans wrote:

> Hi
> 
> In bio_endio()  there is the follow line:- 
> 
> 	bio->bi_sector += (bytes_done >> 9);
> 
> and there is a similiar line assuming a 512byte sector in 
> __bio_add_page() .
> 
> Is this a bug as the the actual  block size  should be available
> from bio->bi_bdev->bd_block_size surely - or is some clever code
> where all block devices have to translate back to 512 byte sectors
> for bio s.

Does this answer it for you?

http://marc.theaimsgroup.com/?l=linux-kernel&m=115542872706154&w=2

---
~Randy
-
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/