From: Greg KH <greg@kroah.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, 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 09:02:12 -0800 [thread overview]
Message-ID: <20060118170212.GB12757@kroah.com> (raw)
In-Reply-To: <200601181253.54942.blaisorblade@yahoo.it>
On Wed, Jan 18, 2006 at 12:53:54PM +0100, Blaisorblade wrote:
> 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.
By providing a release function that does nothing, all you are doing is
shutting the kernel up. You are not doing anything to "fix" the real
problem at all.
> > > 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.
Ok, but you are still adding 2 empty release functions.
Please do not do that, if you think you need this, your code logic is
wrong.
As for your specific bug report, sorry, I really don't know.
good luck,
greg k-h
-------------------------------------------------------
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
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, 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 09:02:12 -0800 [thread overview]
Message-ID: <20060118170212.GB12757@kroah.com> (raw)
In-Reply-To: <200601181253.54942.blaisorblade@yahoo.it>
On Wed, Jan 18, 2006 at 12:53:54PM +0100, Blaisorblade wrote:
> 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.
By providing a release function that does nothing, all you are doing is
shutting the kernel up. You are not doing anything to "fix" the real
problem at all.
> > > 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.
Ok, but you are still adding 2 empty release functions.
Please do not do that, if you think you need this, your code logic is
wrong.
As for your specific bug report, sorry, I really don't know.
good luck,
greg k-h
next prev parent reply other threads:[~2006-01-18 17:03 UTC|newest]
Thread overview: 10+ 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 1:12 ` Greg KH
2006-01-18 11:53 ` [uml-devel] " Blaisorblade
2006-01-18 11:53 ` Blaisorblade
2006-01-18 17:02 ` Greg KH [this message]
2006-01-18 17:02 ` Greg KH
2006-01-18 18:36 ` Blaisorblade
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=20060118170212.GB12757@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--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 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.