From: Tejun Heo <htejun@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, Chris Rankin <rankincj@yahoo.com>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: [PATCH] driver-core: don't free devt_attr till the device is released
Date: Thu, 10 May 2007 18:18:36 +0200 [thread overview]
Message-ID: <464345DC.4000105@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0705101150100.3498-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Thu, 10 May 2007, Tejun Heo wrote:
>
>> Currently, devt_attr for the "dev" file is freed immediately on device
>> removal, but if the "dev" sysfs file is open when a device is removed,
>> sysfs will access its attribute structure for further access including
>> close resulting in jumping to garbled address. Fix it by postponing
>> freeing devt_attr to device release time.
>>
>> Note that devt_attr for class_device is already freed on release.
>>
>> This bug is reported by Chris Rankin as bugzilla bug#8198.
>>
>> Signed-off-by: Tejun Heo <htejun@gmail.com>
>> Cc: Chris Rankin <rankincj@yahoo.com>
>> ---
>> Applies well to 2.6.20 and 21. As sysfs-immediate-disconnect doesn't
>> seem to be included in 2.6.22, this should be included in linus#master
>> too (applies well there as well).
>
> Although sysfs-immediate-disconnect may not be included in 2.6.22, the old
> attribute-orphan code by Oliver Neukum is present there and also in
> 2.6.21. Shouldn't that suffice?
sysfs_release() still needs to deference attr->owner to put it, so I
think there's the same problem even with attribute-orphan. We end up
calling module_put() on garbage.
--
tejun
next prev parent reply other threads:[~2007-05-10 16:18 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
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 [this message]
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=464345DC.4000105@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=stable@kernel.org \
--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