From: Greg KH <greg@kroah.com>
To: Milan Broz <mbroz@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: dm: sysfs add empty release function to avoid debug warning
Date: Wed, 16 Dec 2009 05:45:38 -0800 [thread overview]
Message-ID: <20091216134538.GA20857@kroah.com> (raw)
In-Reply-To: <4B28AC09.2000302@redhat.com>
On Wed, Dec 16, 2009 at 10:44:41AM +0100, Milan Broz wrote:
> On 12/16/2009 01:47 AM, Greg KH wrote:
> > On Tue, Dec 15, 2009 at 05:35:08PM +0000, James Bottomley wrote:
> >> commit: d2bb7df8cac647b92f51fb84ae735771e7adbfa7
> >> From: Milan Broz <mbroz@redhat.com>
> >> Date: Thu, 10 Dec 2009 23:51:53 +0000
> >> Subject: [PATCH] dm: sysfs add empty release function to avoid debug warning
> >>
> >> This patch just removes an unnecessary warning:
> >> kobject: 'dm': does not have a release() function,
> >> it is broken and must be fixed.
> >>
> >> The kobject is embedded in mapped device struct, so
> >> code does not need to release memory explicitly here.
> >
>
> > Please, this is totally and completly wrong. And if you feel that it is
> > needed, then your design is wrong and it needs to be fixed.
>
> There are several places in kernel, where kobject have not defined release
> method. Yes, something is wrong here.
Where are those instances, becides the use of static kobjects, which is
being worked on?
That still does not make this change acceptable, it is incorrect.
> So quietly ignoring warning is ok? Why is not there BUG_ON(!release) then?
I was trying to be nice and not crash your machine and give you the
opportunity to fix it easily.
> The sysfs attributes here just represents attributes of block device object,
> this device is always removed before release here is called.
Then why use a kobject at all? Your reference counting will be all
wrong if you use it incorrectly like this.
> So if there is preferred to do another alloc/free, no problem.
Please do.
Also, with the addition of this patch, your comments for the kobject are
now incorrect as well.
thanks,
greg k-h
next prev parent reply other threads:[~2009-12-16 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200912151735.nBFHZ8XP018683@hera.kernel.org>
2009-12-16 0:47 ` dm: sysfs add empty release function to avoid debug warning Greg KH
2009-12-16 9:44 ` Milan Broz
2009-12-16 13:45 ` Greg KH [this message]
2009-12-16 16:32 ` [dm-devel] " Zdenek Kabelac
2009-12-16 17:46 ` Greg KH
2009-12-16 18:40 ` Milan Broz
2009-12-17 0:30 ` Greg KH
2009-12-17 15:43 ` Milan Broz
2009-12-22 5:31 ` Greg KH
2009-12-16 23:25 ` Zdenek Kabelac
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=20091216134538.GA20857@kroah.com \
--to=greg@kroah.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
/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