public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
	linux-kernel@vger.kernel.org, rubini@gnudd.com
Subject: Re: [PATCH 3/3] misc: use a proper range for minor number dynamic allocation
Date: Tue, 15 Dec 2009 14:56:30 -0800	[thread overview]
Message-ID: <20091215225630.GA12918@suse.de> (raw)
In-Reply-To: <4B2810D6.9030309@zytor.com>

On Tue, Dec 15, 2009 at 02:42:30PM -0800, H. Peter Anvin wrote:
> On 12/15/2009 02:34 PM, Andrew Morton wrote:
> >>>>
> >>>> The proposed solution uses the not yet reserved range from 64 to 127. If
> >>>> more devices are needed, we may push 64 to 16.
> >>>>
> >>>
> >>> Again, why not push these up above 256?
> >>>
> >>
> >> I merged this patch, but made a note-to-self that there are remaining
> >> open issues..
> > 
> > And nothing else happened.  Can we revisit this please?
> > 
> 
> There seem to be people still worried about breaking userspace with
> majors/minors >= 256.  I'm starting to think it is time to actually
> break userspace, and dynamic majors/minors seem as good as any place to
> start, especially since they by definition has to be managed by
> something like udev.  We have had large dev_t for something like six
> years now, and most pieces of software isn't affected at all -- only the
> stuff that manages /dev.

No objection from me, as long as the patch actually works.

But you might want to provide a config option so that loons that still
are running Fedora 3 PPC machines who keep insisting on updating to the
latest kernel version still keep their machines limping along
successfully :)

thanks,

greg k-h

  reply	other threads:[~2009-12-15 23:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10  0:30 [PATCH 1/3] misc: clear allocation bit in minor bitmap when device register fails Thadeu Lima de Souza Cascardo
2009-11-10  0:30 ` [PATCH 2/3] misc: use bitmap/bitops functions for dynamic minor number allocation Thadeu Lima de Souza Cascardo
2009-11-10  0:30   ` [PATCH 3/3] misc: use a proper range for minor number dynamic allocation Thadeu Lima de Souza Cascardo
2009-11-10  0:34     ` H. Peter Anvin
2009-11-10 10:19       ` Alan Cox
2009-11-10 16:45       ` Thadeu Lima de Souza Cascardo
2009-11-11 23:36       ` Andrew Morton
2009-12-15 22:34         ` Andrew Morton
2009-12-15 22:42           ` H. Peter Anvin
2009-12-15 22:56             ` Greg KH [this message]
2009-12-15 23:56               ` Alan Cox
2009-12-16 23:14                 ` cascardo
2009-12-16 22:51             ` cascardo
2009-12-15 23:37           ` Alan Cox
2009-12-15 23:41             ` Andrew Morton
2009-12-16 18:01             ` David Teigland
2009-12-16 17:10               ` H. Peter Anvin
2009-12-16 23:21               ` cascardo
2009-12-16 23:05             ` cascardo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091215225630.GA12918@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=cascardo@holoscopio.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rubini@gnudd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox