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: <8f8f8f78-fcd4-4e71-8dd5-bae03a627a34@oracle.com>
Date: Fri, 28 Jun 2024 15:30:00 +0100
From: John Garry <john.g.garry@...cle.com>
To: Christoph Hellwig <hch@...radead.org>, Keith Busch <kbusch@...nel.org>
Cc: Andreas Hindborg <nmi@...aspace.dk>, Jens Axboe <axboe@...nel.dk>,
        Andreas Hindborg <a.hindborg@...sung.com>,
        Bart Van Assche <bvanassche@....org>,
        Damien Le Moal <dlemoal@...nel.org>, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] null_blk: fix validation of block size

On 04/06/2024 05:46, Christoph Hellwig wrote:
>> It also looks like a good idea if this check was just done in
>> blk_validate_limits() so that each driver doesn't have to do their own
>> checks. That block function is kind of recent though.
> Yes.  We already discussed this in another thread a few days ago.
Has anyone taken this work? I was going to unless someone else wants to. 
4 or 5 drivers directly reference blk_validate_block_size() now.

Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ