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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 14 Oct 2021 16:35:49 +0100 From: Wol <antlists@...ngman.org.uk> To: Kees Cook <keescook@...omium.org>, Dave Kleikamp <dave.kleikamp@...cle.com> Cc: "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>, "dm-devel@...hat.com" <dm-devel@...hat.com>, "drbd-dev@...ts.linbit.com" <drbd-dev@...ts.linbit.com>, "linux-bcache@...r.kernel.org" <linux-bcache@...r.kernel.org>, "linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>, "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>, "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>, "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>, "target-devel@...r.kernel.org" <target-devel@...r.kernel.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, "linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "jfs-discussion@...ts.sourceforge.net" <jfs-discussion@...ts.sourceforge.net>, "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>, "linux-nilfs@...r.kernel.org" <linux-nilfs@...r.kernel.org>, "linux-ntfs-dev@...ts.sourceforge.net" <linux-ntfs-dev@...ts.sourceforge.net>, "ntfs3@...ts.linux.dev" <ntfs3@...ts.linux.dev>, "reiserfs-devel@...r.kernel.org" <reiserfs-devel@...r.kernel.org> Subject: Re: don't use ->bd_inode to access the block device size On 14/10/2021 16:14, Kees Cook wrote: >> I don't really mind bdev_size since it's analogous to i_size, but >> bdev_nr_bytes seems good to me. > I much prefer bdev_nr_bytes(), as "size" has no units. Does it mean size IN bytes, or size OF A byte? :-) Cheers, Wol
Powered by blists - more mailing lists