Re: [Bug #13950] Oops when USB Serial disconnected while in use

From: Rafael J. Wysocki
Date: Fri Oct 02 2009 - 17:25:14 EST


On Friday 02 October 2009, Bruno PrÃmont wrote:
> On Thu, 01 October 2009 "Rafael J. Wysocki" <rjw@xxxxxxx> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.30 and 2.6.31.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31. Please verify if it still
> > should be listed and let me know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13950
> > Subject : Oops when USB Serial disconnected while in
> > use Submitter : Bruno PrÃmont <bonbons@xxxxxxxxxxxxxxxxx>
> > Date : 2009-08-08 17:47 (55 days old)
> > References : http://marc.info/?l=linux-kernel&m=124975432900466&w=4
> > Handled-By : Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
>
> This has been adressed with following commits:
> 41bd34ddd7aa46dbc03b5bb33896e0fa8100fe7b
> usb-serial: change referencing of port and serial structures
>
> f5b0953a89fa3407fb293cc54ead7d8feec489e4
> usb-serial: put subroutines in logical order
>
> 8bc2c1b2daf95029658868cb1427baea2da87139
> usb-serial: change logic of serial lookups
>
> cc56cd0157753c04a987888a2f793803df661a40
> usb-serial: acquire references when a new tty is installed
>
> 7e29bb4b779f4f35385e6f21994758845bf14d23
> usb-serial: fix termios initialization logic
>
> 74556123e034c8337b69a3ebac2f3a5fc0a97032
> usb-serial: rename subroutines
>
> ff8324df1187b7280e507c976777df76c73a1ef1
> usb-serial: add missing tests and debug lines
>
> 320348c8d5c9b591282633ddb8959b42f7fc7a1c
> usb-serial: straighten out serial_open
>
> They went into 2.6.32-rc1 and are probably queued for 2.6.31.2 stable.

Thanks a lot for the detailed info, bug closed.

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/