From: Greg KH <greg@kroah.com>
To: Disconnect <lkml@sigkill.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG][USB] 2.4.22-pre2
Date: Wed, 9 Jul 2003 11:49:44 -0700 [thread overview]
Message-ID: <20030709184943.GC18240@kroah.com> (raw)
In-Reply-To: <1057776185.8464.66.camel@slappy>
On Wed, Jul 09, 2003 at 02:43:06PM -0400, Disconnect wrote:
> On Wed, 2003-07-09 at 13:38, Greg KH wrote:
> > On Wed, Jul 09, 2003 at 12:57:06PM -0400, Disconnect wrote:
> > > Its dead simple to reproduce - plug a pl2303 in, open /dev/ttyUSB0 with
> > > (eg) minicom or pppd, close it, check logs.
> >
> > Known bug, search the archives :)
> >
> > It's fixed in 2.5.
> >
> > Someone needs to backport the 2.5 changes to 2.4 to fix this issue, as
> > I'm getting tired of repeating myself...
>
> Most of the archives seem to be unrelated issues ~2.4.20-pre; I found a
> couple of places where you got to repeat yourself, but I'm not finding
> info on whats actually triggering it and which changes in 2.5 need
> backporting. (I'm quite interested in getting this working, so I'm
> perfectly willing to give the backport a shot.)
I've said it before on this list, and on the linux-usb-devel list, but
here it is again for people to refer to in the future.
The locking and reference counting logic changes in the usb-serial
drivers needs to be backported to the 2.4 kernel to fix this problem.
The changes were spread out over a wide range of time during the 2.5
development process, so I can't point to a single changeset, sorry. It
also requires changing all usb-serial drivers to do this properly.
If you do a diff of the two trees, you should see the major changes.
Good luck,
greg k-h
prev parent reply other threads:[~2003-07-09 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 16:57 [BUG][USB] 2.4.22-pre2 Disconnect
2003-07-09 17:38 ` Greg KH
[not found] ` <1057776185.8464.66.camel@slappy>
2003-07-09 18:49 ` Greg KH [this message]
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=20030709184943.GC18240@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@sigkill.net \
/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