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: <20170616062736.GD29049@kroah.com>
Date:   Fri, 16 Jun 2017 08:27:36 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Logan Gunthorpe <logang@...tatee.com>
Cc:     linux-kernel@...r.kernel.org, Bjorn Helgaas <helgaas@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Alan Cox <alan@...ux.intel.com>, Arnd Bergmann <arnd@...db.de>,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 2/2] char_dev: order /proc/devices by major number

On Thu, Jun 15, 2017 at 02:05:21PM -0600, Logan Gunthorpe wrote:
> Presently, the order of the char devices listed in /proc/devices is not
> entirely sequential. If a char device has a major number greater than
> CHRDEV_MAJOR_HASH_SIZE (255), it will be ordered as if its major were
> module 255. For example, 511 appears after 1.

Hey, nice fix, that was annoying!

Also looks like block devices have the same issue in this file, care to
fix that up too while you are there?  :)

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ