From: Tejun Heo <htejun@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Chris Rankin <rankincj@yahoo.com>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Bug creating USB endpoints in 2.6.20.x (kernel bug 8198)
Date: Wed, 09 May 2007 17:01:25 +0200 [thread overview]
Message-ID: <4641E245.7040603@gmail.com> (raw)
In-Reply-To: <20070509145747.GA27259@kroah.com>
Greg KH wrote:
> On Wed, May 09, 2007 at 03:30:41PM +0200, Tejun Heo wrote:
>> Chris Rankin wrote:
>>> --- Tejun Heo <htejun@gmail.com> wrote:
>>>> So, we can fix the problem Chris is seeing by breaking module unload (by
>>>> allowing it to unload too early). It doesn't sound too hot but module
>>>> unloading race is much less likely than sysfs node deletion/open race.
>>> Yikes! Just temporary breakage, I hope :-)!! The only modules I unload on a regular basis these
>>> days are things like "microcode", which the init scripts take care of as part of the boot-up
>>> process.
>> Okay, here's a half-assed fix. With this patch applied, if you try to
>> unload a module while you're opening it's dev attribute, kernel will
>> oops later when the file is accessed or closed later but it should fix
>> the bug winecfg triggers. I really dunno how to fix this the right way
>> in the stable kernel. Better ideas? Anyone?
>
> This looks like the correct fix, the only reason I made this dynamic was
> to properly set up the module owner. And now that you have removed that
> link in your sysfs rework, it can go and become static again.
>
> Oh, and this isn't a "device node", it's just a text file that contains
> the major:minor number for a device node to be created from.
>
> So, care to fix up the class code too and send a patch with a
> signed-off-by:?
I think the proper fix for -stable is to free the structure in
device_release(). I asked Chris to test it. After he confirms, I'll
send a proper patch with S-O-B.
For -mm, yeap, we can simply make the whole thing static. I'll send
patch for that soon.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-05-09 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <963898.10047.qm@web52906.mail.re2.yahoo.com>
2007-05-09 9:40 ` [linux-usb-devel] Bug creating USB endpoints in 2.6.20.x (kernel bug 8198) Tejun Heo
2007-05-09 12:24 ` Chris Rankin
2007-05-09 13:30 ` Tejun Heo
2007-05-09 13:56 ` Chris Rankin
2007-05-09 14:11 ` Tejun Heo
2007-05-09 14:35 ` Dmitry Torokhov
2007-05-09 14:58 ` Tejun Heo
2007-05-09 21:09 ` Chris Rankin
2007-05-09 14:57 ` Greg KH
2007-05-09 15:01 ` Tejun Heo [this message]
2007-05-09 15:40 ` Greg KH
2007-05-10 14:45 ` [PATCH] driver-core: don't free devt_attr till the device is released Tejun Heo
2007-05-10 15:05 ` Greg KH
2007-05-10 15:13 ` Tejun Heo
2007-05-10 15:17 ` Greg KH
2007-05-10 15:33 ` Kay Sievers
2007-05-10 15:41 ` Tejun Heo
2007-05-10 15:52 ` Alan Stern
2007-05-10 16:18 ` Tejun Heo
2007-05-10 14:25 ` [PATCH 2.6.21-mm2] driver-core: make devt_attr and uevent_attr static Tejun Heo
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=4641E245.7040603@gmail.com \
--to=htejun@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rankincj@yahoo.com \
--cc=stern@rowland.harvard.edu \
/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