From: Mark Lord <lkml@rtr.ca>
To: Greg KH <gregkh@suse.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-usb-devel@lists.sourceforge.net,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] [PATCH] base/class.c: prevent ooops due to insert/remove race (v3)
Date: Thu, 29 Nov 2007 15:46:42 -0500 [thread overview]
Message-ID: <474F2532.5090708@rtr.ca> (raw)
In-Reply-To: <20071129203225.GA5383@suse.de>
Greg KH wrote:
> On Thu, Nov 29, 2007 at 03:25:04PM -0500, Mark Lord wrote:
>> (resending .. somebody trimmed the CC: list earlier)
>>
>> Greg KH wrote:
>>>>>> Mark Lord wrote:
>>>>>>> ..
>>>>>>>
>>>>>>> While doing insert/remove (quickly) tests on USB,
>>>>>>> I managed to trigger an Oops on 2.6.23.8 on a call
>>>>>>> to strlen() in make_class_name().
>> ...
>>
>>> I'll hold off on adding this patch for now.
>> ..
>>
>> Why?
>>
>> Bugs that result in Oops in core code (class.c) can bite
>> just about any subsystem that does hotplug, and should get
>> prompt attention. Or so one might think.
>
> And they have, the 2.6.24 kernel should have the correct fix for this
> problem, right? The fact that you oopsed out in this function enabled
> people to find and fix the problem already. Adding a BUG_ON() does the
> same exact thing :)
..
Well, actually BUG_ON() allows the system to continue running
while still not masking the issue. But close enough.
> So again, the problem is in the higher up scsi layer, and that is where
> the problem should already be fixed.
..
Ahhh.. so you figure the Oops should also have been fixed
as part of the 2.6.24 SCSI fixes ? That's what I was missing here.
Thanks.
next prev parent reply other threads:[~2007-11-29 20:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 4:00 [PATCH] base/class.c: prevent ooops due to insert/remove race Mark Lord
2007-11-29 4:33 ` Greg KH
2007-11-29 15:41 ` Mark Lord
2007-11-29 16:27 ` Greg KH
2007-11-29 17:45 ` Mark Lord
2007-11-29 17:48 ` Mark Lord
2007-11-29 17:50 ` Mark Lord
2007-11-29 18:09 ` [PATCH] base/class.c: prevent ooops due to insert/remove race (v3) Mark Lord
2007-11-29 18:12 ` Mark Lord
2007-11-29 19:20 ` [linux-usb-devel] " Alan Stern
2007-11-29 20:01 ` Mark Lord
2007-11-29 20:12 ` Greg KH
[not found] ` <474F1DB3.4030900@rtr.ca>
2007-11-29 20:25 ` Mark Lord
2007-11-29 20:32 ` Greg KH
2007-11-29 20:46 ` Mark Lord [this message]
2007-11-29 21:17 ` Greg KH
2007-11-29 22:07 ` Alan Stern
2007-11-29 22:11 ` Greg KH
2007-11-29 22:28 ` Mark Lord
2007-11-29 22:43 ` Alan Stern
2007-11-29 23:09 ` Linus Torvalds
2007-11-30 2:58 ` Alan Stern
2007-11-29 20:13 ` Alan Stern
2007-11-29 20:17 ` Mark Lord
2007-11-29 20:20 ` Mark Lord
2007-11-29 21:59 ` Alan Stern
2007-11-29 15:59 ` [PATCH] base/class.c: prevent ooops due to insert/remove race (v2) Mark Lord
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=474F2532.5090708@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.org \
/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.