From: Greg KH <greg@kroah.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
John Levon <levon@movementarian.org>
Subject: Re: [PATCH][2.6][CFT] rmmod floppy kills box fixes + default_device_remove
Date: Tue, 9 Sep 2003 10:13:54 -0700 [thread overview]
Message-ID: <20030909171354.GC5928@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0309091142550.14426@montezuma.fsmlabs.com>
On Tue, Sep 09, 2003 at 12:38:51PM -0400, Zwane Mwaikambo wrote:
> On Tue, 9 Sep 2003, Zwane Mwaikambo wrote:
>
> > > So an empty release() function is the wrong thing to do in 99.99% of the
> > > situations in the kernel (the one exception seems to be the mca release
> > > function that recently got added for use when the bus is doing probing
> > > logic.)
> > >
> > > Does this help out?
> >
> > Yes thanks, i was confused over which memory references had to be
> > maintained.
>
> Ok i had another look and i can see why you need a seperate release
> function, as we don't always do the kobject_cleanup immediately.
>
> John and myself had a look and now we have the following race on
> ->release() function exit.
>
> my_release_fn()
> {
> complete(&my_completion);
> <== [1] stall anywhere here, e.g. preempt/schedule
> }
Ugh. Sure, point out the theoretical :)
Any thoughts on how to solve this?
thanks,
greg k-h
next prev parent reply other threads:[~2003-09-09 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 2:53 [PATCH][2.6][CFT] rmmod floppy kills box fixes + default_device_remove Zwane Mwaikambo
2003-09-08 15:50 ` Greg KH
2003-09-08 21:27 ` Zwane Mwaikambo
2003-09-08 23:08 ` Greg KH
2003-09-09 11:50 ` Zwane Mwaikambo
2003-09-09 16:38 ` Zwane Mwaikambo
2003-09-09 17:13 ` Greg KH [this message]
2003-09-09 19:18 ` Zwane Mwaikambo
2003-09-09 19:45 ` John Levon
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=20030909171354.GC5928@kroah.com \
--to=greg@kroah.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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