From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Greg KH <greg@kroah.com>,
akpm@osdl.org, Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Re: [PATCH 1/9] uml: avoid sysfs warning on hot-unplug
Date: Wed, 18 Jan 2006 12:53:54 +0100 [thread overview]
Message-ID: <200601181253.54942.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060118011200.GA28086@kroah.com>
On Wednesday 18 January 2006 02:12, Greg KH wrote:
> > From: Jeff Dike <jdike@addtoit.com>, Paolo 'Blaisorblade' Giarrusso
> > <blaisorblade@yahoo.it>
> >
> > Define a release method for the ubd and network driver so that sysfs
> > doesn't complain when one is removed via:
> What? No. The kernel is complaining for a reason, don't try to
> out-smart it.
I'm not trying to ignore the warning.
> > host $ uml_mconsole <umid> remove <dev>
> > Done by Jeff around January for ubd only, later lost, then restored in
> > his tree - however I'm merging it now since there's no reason to leave
> > this here.
> > We don't need to do any cleanup in the new added method, because when
> > hot-unplug is done by uml_mconsole we already handle cleanup in mconsole
> > infrastructure, i.e. mc_device->remove (net_remove/ubd_remove), which is
> > also the calling method.
> Huh? You have 2 different release functions for the same object?
Not sure which ones you refer. net_remove and ubd_remove are for different
devices; mc_device->remove and the sysfs release are in different layers and
for different things.
> And
> how do you know which one is correct? That does not sound right at all.
No, but since we don't have plugs, we get configuration requests to remove
devices.
And currently, since this existed in already 2.4, the handler of the
configuration request(mc_device->remove) does all the work to shutdown the
interface, and then calls into the kobject stuff (with
platform_device_unregister()); and this complains for the missing ->remove.
If it's better, we may try to move things inside the sysfs ->remove event,
with care because different stuff has been done.
However, there are a lot of things to look at here... is there anything in
ubd_remove() smelling awful? Because we have a crash which is caused by us
harming sysfs data structures, which triggers on ubd_remove().
Bug report:
http://marc.theaimsgroup.com/?l=user-mode-linux-devel&m=113537479514679&w=2
investigations:
http://marc.theaimsgroup.com/?l=user-mode-linux-devel&m=113538805406552&w=2
> Please fix this correctly.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-01-18 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 1:12 [uml-devel] Re: [PATCH 1/9] uml: avoid sysfs warning on hot-unplug Greg KH
2006-01-18 11:53 ` Blaisorblade [this message]
2006-01-18 17:02 ` Greg KH
2006-01-18 18:36 ` Blaisorblade
[not found] <20060117235659.14622.18544.stgit@zion.home.lan>
2006-01-18 0:19 ` [uml-devel] " Paolo 'Blaisorblade' Giarrusso
2006-01-18 2:53 ` [uml-devel] " Jeff Dike
2006-01-18 11:11 ` Blaisorblade
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=200601181253.54942.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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