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: <YlUTt4ABuzb0iOjb@infradead.org>
Date:   Mon, 11 Apr 2022 22:52:55 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Mikulas Patocka <mpatocka@...hat.com>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH] stat: don't fail if the major number is >= 256

On Mon, Apr 11, 2022 at 07:47:44PM -1000, Linus Torvalds wrote:
> Considering that BLOCK_EXT_MAJOR has been 259 since 2008, and this is
> the first time anybody has hit this, I don't think there's much reason
> to change that major number when the whole error case seems to have
> been largely a mistake to begin with.

Yeah.  If Mikulas still has a problem he could just patch
BLOCK_EXT_MAJOR locally.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ