From: Larry Finger <Larry.Finger@lwfinger.net>
To: Greg KH <gregkh@suse.de>
Cc: Christian Lamparter <chunkeey@web.de>,
linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
John W Linville <linville@tuxdriver.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] p54usb: fix usb_kill_urb hang with slub_debug=P
Date: Fri, 05 Dec 2008 17:18:07 -0600 [thread overview]
Message-ID: <4939B6AF.2060901@lwfinger.net> (raw)
In-Reply-To: <20081205155356.GC28030@suse.de>
Greg KH wrote:
> On Fri, Dec 05, 2008 at 03:47:45PM +0100, Christian Lamparter wrote:
>> This patch fixes a problem identified by Johannes Berg.
>
> No, it only papers over the real problem here, let's work on a correct
> patch please.
I can contribute a little info. If SLUB debugging is enabled, and the boot
command includes 'slub_debug=P', I get a GPF in kref_get(), which is called from
kobject_get() with the following code:
if (kobj)
kref_get(&kobj->kref);
>From the dump, &kobj->kref is 0x6b6b6b6b6b6b6dbb, a poisoned value.
Somewhere, the "struct urb" has been freed, but kobj has not been set to NULL.
As everything I've found is a symptom, I'm still looking for the real cause.
Larry
next prev parent reply other threads:[~2008-12-05 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:47 [PATCH] p54usb: fix usb_kill_urb hang with slub_debug=P Christian Lamparter
2008-12-05 15:14 ` Larry Finger
2008-12-05 15:58 ` Christian Lamparter
2008-12-05 15:53 ` Greg KH
2008-12-05 23:18 ` Larry Finger [this message]
2008-12-05 23:23 ` Greg KH
2008-12-06 20:09 ` [RFC][PATCH] p54usb: rewriting rx/tx routines to make use of usb_anchor's facilities Christian Lamparter
2008-12-06 21:47 ` Larry Finger
2008-12-07 4:15 ` Alan Stern
2008-12-08 14:06 ` [RFC][PATCH v2] " Christian Lamparter
2008-12-08 14:06 ` Christian Lamparter
2008-12-05 23:28 ` [PATCH] p54usb: fix usb_kill_urb hang with slub_debug=P Christian Lamparter
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=4939B6AF.2060901@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=gregkh@suse.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.