From: Greg KH <greg@kroah.com>
To: Johan Hovold <jhovold@gmail.com>
Cc: "Tobias Winter" <tobias@linuxdingsda.de>,
"Bjørn Mork" <bjorn@mork.no>, "Rob Landley" <rob@landley.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] raise the maximum number of usb-serial devices to 512
Date: Tue, 4 Jun 2013 09:31:48 -0700 [thread overview]
Message-ID: <20130604163148.GA31202@kroah.com> (raw)
In-Reply-To: <20130604110401.GA2566@localhost>
On Tue, Jun 04, 2013 at 01:04:01PM +0200, Johan Hovold wrote:
> On Mon, Jun 03, 2013 at 07:49:59PM -0700, Greg KH wrote:
> > On Mon, May 27, 2013 at 02:28:51PM +0200, Bjørn Mork wrote:
> > > But, IMHO, a nicer approach would be to make the allocation completely
> > > dynamic, using e.g. the idr subsystem. Static tables are always feel
> > > like straight jackets to me, no matter how big they are :)
> >
> > You are right, I didn't change the code to use idr (it predates idr by
> > about a decade or so), because I thought we needed the "rage" logic that
> > the usb-serial minor reservation does.
> >
> > But I'm not so sure anymore, so here's a patch to change to use the idr
> > code, and should remove all minor number limitations (well 65k is the
> > limit the tty core should be setting I think.)
> >
> > Tobias, can you test this patch out? Note, I only compiled it, did not
> > get the chance to actually run it, so it might not work at all.
>
> I'm afraid this won't work in it's current form. Several drivers and
> parts of usb-serial core still depend on the minor numbers being
> consecutive for multi-port devices.
You are right, let me go fix up the "port->number" assumption first,
which will let this become easier. That should have been fixed a long
time ago.
> There are also still references to SERIAL_TTY_NO_MINOR (255) as well
> as SERIAL_TTY_MINORS that need to be addressed.
Yeah, I knew it was too good to be true that a simple 45 line patch
would solve this properly :)
> > + port = idr_find(&serial_minors, index);
> > mutex_unlock(&table_lock);
> > + if (!port)
> > + return NULL;
> > +
> > + serial = port->serial;
> > + kref_get(&serial->kref);
> > return serial;
> > }
>
> We would still need to handle disconnect, and make sure to return with
> the disc_mutex held unless disconnected.
Alan noticed this as well, I've now fixed that, thanks.
> > + dev_dbg(&serial->interface->dev, "%s %d\n", __func__, num_ports);
> > +
> > + *minor = 0xffffffff;
> > + for (i = 0; i < num_ports; ++i) {
> > + x = get_free_port(serial->port[i]);
> > + if (x < 0)
> > + goto error;
> > + if (*minor == 0xffffffff)
> > + *minor = x;
> > }
> > - mutex_unlock(&table_lock);
> > - return NULL;
> > + return 0;
> > +error:
> > + // FIXME unwind the already allocated minors
> > + return -ENODEV;
> > }
>
> As mentioned above, usb-serial core and several drivers currently depend
> on us returning the first minor in a consecutive range. It's mostly used
> to determine the per device port index, so storing that index in the port
> structure could possibly be sufficient.
Yes, I'll go fix that up first, before making these changes, as it's
independant.
> > @@ -1233,9 +1226,6 @@ static int __init usb_serial_init(void)
> > return -ENOMEM;
> >
> > /* Initialize our global data */
>
> You could remove the above comment as well.
>
> > - for (i = 0; i < SERIAL_TTY_MINORS; ++i)
> > - serial_table[i] = NULL;
> > -
> > result = bus_register(&usb_serial_bus_type);
I thought about it, but we also register the bus variables, and some
other things here as well, so I left it in.
thanks for the review.
greg k-h
next prev parent reply other threads:[~2013-06-04 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <519F7195.8090306@linuxdingsda.de>
[not found] ` <20130524172354.GA1402@kroah.com>
2013-05-27 9:30 ` [PATCH] Raise the maximum number of usb-serial devices to 256 Tobias Winter
2013-05-28 6:17 ` Rob Landley
[not found] ` <87obbwbo8s.fsf@nemi.mork.no>
[not found] ` <51A332E2.1090403@linuxdingsda.de>
2013-06-04 2:49 ` [RFC] raise the maximum number of usb-serial devices to 512 Greg KH
2013-06-04 2:59 ` Dave Jones
2013-06-04 16:12 ` Greg KH
2013-06-04 11:04 ` Johan Hovold
2013-06-04 16:31 ` Greg KH [this message]
2013-06-04 14:13 ` Alan Stern
2013-06-04 16:17 ` Greg KH
2013-06-04 17:27 ` Tobias Winter
2013-06-04 17:53 ` Greg KH
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=20130604163148.GA31202@kroah.com \
--to=greg@kroah.com \
--cc=bjorn@mork.no \
--cc=jhovold@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rob@landley.net \
--cc=tobias@linuxdingsda.de \
/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