linux-kernel - Re: Change in register

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]

Date:   Wed, 31 Jan 2018 15:24:03 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Srivatsa S. Bhat" <srivatsa@...il.mit.edu>
Cc:     logang@...tatee.com, axboe@...nel.dk, jlayton@...chiereds.net,
        bfields@...ldses.org, linux-kernel@...r.kernel.org
Subject: Re: Change in register_blkdev() behavior

On Tue, Jan 30, 2018 at 04:56:32PM -0800, Srivatsa S. Bhat wrote:
> 
> Hi,
> 
> Before commit 133d55cdb2f "block: order /proc/devices by major number",
> if register_blkdev() was called with major = [1..UINT_MAX], it used to
> succeed (provided the requested major number was actually free).

How was LTP calling register_blkdev() with such crazy numbers?

Anyway, I agree with Logan, this sounds like something to be resolved in
LTP, as allowing block devices with numbers greater than the number we
really allow seems like an odd requirement :)

thanks,

greg k-h