linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Christian Lamparter <chunkeey@web.de>,
	linux-wireless@vger.kernel.org,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH v2] p54usb: rewriting rx/tx routines to make use of usb_anchor's facilities
Date: Tue, 09 Dec 2008 16:03:05 +0100	[thread overview]
Message-ID: <1228834985.1029.2.camel@johannes.berg> (raw)
In-Reply-To: <20081209145439.GB3653@tuxdriver.com>

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

On Tue, 2008-12-09 at 09:54 -0500, John W. Linville wrote:
> On Tue, Dec 09, 2008 at 03:46:39PM +0100, Johannes Berg wrote:
> > On Tue, 2008-12-09 at 09:35 -0500, John W. Linville wrote:
> > > On Tue, Dec 09, 2008 at 03:14:37PM +0100, Christian Lamparter wrote:
> > > > Alan Stern found several flaws in p54usb's implementation and annotated: 
> > > > "usb_kill_urb() and similar routines do not expect an URB's completion
> > > > routine to deallocate it.  This is almost obvious -- if the URB is deallocated
> > > > before the completion routine returns then there's no way for usb_kill_urb
> > > > to detect when the URB actually is complete."
> > > > 
> > > > This patch addresses all known limitations in the old implementation and fixes
> > > > khub's "use-after-freed" hang, when SLUB debug's poisoning option is enabled.
> > > > 
> > > > Signed-off-by: Christian Lamparter <chunkeey@web.de>
> > > > Cc: stable@kernel.org
> > > 
> > > That's a big patch for so late in the cycle.  Is there a bugzilla open for it?
> > 
> > No, but we can open one ;) It's strange, but nobody but me apparently
> > found the bug so far, even though it has been in there forever. Might be
> > due to slub debugging being disabled by default even if you enable
> > SLUB_DEBUG in Kconfig (you also need to enable SLUB_DEBUG_ON)
> 
> It might be helpful to have open a bug that includes a backtrace or something.

There's no backtrace in that sense, it just hangs. I dumped it with
sysrq-w but that wasn't too helpful...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2008-12-09 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 14:14 [PATCH v2] p54usb: rewriting rx/tx routines to make use of usb_anchor's facilities Christian Lamparter
2008-12-09 14:35 ` John W. Linville
2008-12-09 14:46   ` Johannes Berg
2008-12-09 14:54     ` John W. Linville
2008-12-09 15:03       ` Johannes Berg [this message]
2008-12-09 15:16         ` Larry Finger
2008-12-09 15:07   ` Larry Finger
2008-12-09 15:45 ` Larry Finger
2008-12-09 16:11   ` Larry Finger

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=1228834985.1029.2.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).