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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Oct 2021 11:16:08 -0600
From:   Jens Axboe <>
To:     Christoph Hellwig <>
Cc:     Coly Li <>, Mike Snitzer <>,
        Song Liu <>, David Sterba <>,
        Josef Bacik <>,
        Theodore Ts'o <>,
        OGAWA Hirofumi <>,
        Dave Kleikamp <>,
        Ryusuke Konishi <>,
        Anton Altaparmakov <>,
        Konstantin Komarov <>,
        Kees Cook <>,
        Phillip Lougher <>,
        Jan Kara <>,,,,,,,,,,,,,,,,,
Subject: Re: don't use ->bd_inode to access the block device size v3

On 10/18/21 4:11 AM, Christoph Hellwig wrote:
> Hi Jens,
> various drivers currently poke directy at the block device inode, which
> is a bit of a mess.  This series cleans up the places that read the
> block device size to use the proper helpers.  I have separate patches
> for many of the other bd_inode uses, but this series is already big
> enough as-is,

This looks good to me. Followup question, as it's related - I've got a
hacky patch that caches the inode size in the bdev:

so we don't have to dip into the inode itself for the fast path. While
it's obviously not something being proposed for inclusion right now, is
there a world in which we can make something like that work?

Jens Axboe

Powered by blists - more mailing lists