From: Milan Broz <gmazyland@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: ejt@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: dm: remove pointless comparison
Date: Tue, 07 Jan 2014 18:28:15 +0100 [thread overview]
Message-ID: <52CC392F.1070804@gmail.com> (raw)
In-Reply-To: <20140107155252.GB7983@redhat.com>
On 01/07/2014 04:52 PM, Mike Snitzer wrote:
> On Tue, Jan 07 2014 at 5:39am -0500,
> Joe Thornber <thornber@redhat.com> wrote:
>
>> On Mon, Jan 06, 2014 at 10:53:28PM -0500, Mikulas Patocka wrote:
>>> Remove pointless comparison in dm_get_from_kobject. The comparison is
>>> always true and the compiler optimizes it out anyway.
>>>gmane.linux.kernel.device-mapper.devel
>>> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>>>
>>> ---
>>> drivers/md/dm.c | 2 --
>>> 1 file changed, 2 deletions(-)
>>>
>>> Index: linux-3.13-rc7/drivers/md/dm.c
>>> ===================================================================
>>> --- linux-3.13-rc7.orig/drivers/md/dm.c 2014-01-07 01:28:27.000000000 +0100
>>> +++ linux-3.13-rc7/drivers/md/dm.c 2014-01-07 01:28:39.000000000 +0100
>>> @@ -2922,8 +2922,6 @@ struct mapped_device *dm_get_from_kobjec
>>> struct mapped_device *md;
>>>
>>> md = container_of(kobj, struct mapped_device, kobj);
>>> - if (&md->kobj != kobj)
>>> - return NULL;
>>
>> What were they trying to check? The compiler?
>>
>
> Milan's commit 784aae735d, and the current dm.c code, offers this
> comment above dm_get_from_kobject:
>
> /*
> * struct mapped_device should not be exported outside of dm.c
> * so use this check to verify that kobj is part of md structure
> */
>
> I'm lacking the vision to _know_ why the kobject would suddenly be
> outside of the mapped_device without us knowing via code change..
>
> The check does seem overly cautious/useless (if we remove it the above
> comment should be removed too).
Yes, please remove both :) The check doesn't make sense.
I think it is just relict of some experiments before I committed this simple
embedded sysfs kobj handling (there were always problems like the missing .release
function you are just solving in other thread).
Milan
next prev parent reply other threads:[~2014-01-07 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 3:53 [PATCH] dm: remove pointless comparison Mikulas Patocka
2014-01-07 10:39 ` Joe Thornber
2014-01-07 15:52 ` Mike Snitzer
2014-01-07 17:28 ` Milan Broz [this message]
2014-01-07 18:17 ` Mike Snitzer
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=52CC392F.1070804@gmail.com \
--to=gmazyland@gmail.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@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