From: "Cong WANG" <xiyou.wangcong@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [-mm3 patch]Warning fix: check the return value of kobject_add etc.
Date: Sun, 1 Apr 2007 14:20:46 +0800 [thread overview]
Message-ID: <2375c9f90703312320m3e895bbap735c2d49da9d5ff9@mail.gmail.com> (raw)
In-Reply-To: <20070331223136.6019d98f.akpm@linux-foundation.org>
2007/4/1, Andrew Morton <akpm@linux-foundation.org>:
> On Sat, 31 Mar 2007 10:30:31 +0800 "Cong WANG" <xiyou.wangcong@gmail.com> wrote:
>
> > Since kobject_add, sysfs_create_link and sysfs_create_file are marked
> > as '__must_check', so we must always check their return values, or gcc
> > will give us warnings.
> >
> > Signed-off-by: Cong WANG <xiyou.wangcong@gmail.com>
> >
> > ---
> > --- fs/partitions/check.c.orig 2007-03-30 21:35:45.000000000 +0800
> > +++ fs/partitions/check.c 2007-03-30 21:49:53.000000000 +0800
> > @@ -385,10 +385,16 @@ void add_partition(struct gendisk *disk,
> > p->kobj.parent = &disk->kobj;
> > p->kobj.ktype = &ktype_part;
> > kobject_init(&p->kobj);
> > - kobject_add(&p->kobj);
> > + if (kobject_add(&p->kobj)) {
> > + kfree(p);
> > + return;
> > + }
> > if (!disk->part_uevent_suppress)
> > kobject_uevent(&p->kobj, KOBJ_ADD);
> > - sysfs_create_link(&p->kobj, &block_subsys.kset.kobj, "subsystem");
> > + if (sysfs_create_link(&p->kobj, &block_subsys.kset.kobj, "subsystem")) {
> > + kfree(p);
> > + return;
> > + }
> > if (flags & ADDPART_FLAG_WHOLEDISK) {
> > static struct attribute addpartattr = {
> > .name = "whole_disk",
> > @@ -396,7 +402,10 @@ void add_partition(struct gendisk *disk,
> > .owner = THIS_MODULE,
> > };
> >
> > - sysfs_create_file(&p->kobj, &addpartattr);
> > + if (sysfs_create_file(&p->kobj, &addpartattr)) {
> > + kfree(p);
> > + return;
> > + }
> > }
> > partition_sysfs_add_subdir(p);
> > disk->part[part-1] = p;
>
> Well yes, but the point here it to fix kernel bugs, not to just make the
> warnings go away.
>
> The bugs here are that the effects of the kobject_add() and the
> sysfs_create_link() are not undone on the error path.
Thanks for your point.
>
> Also, please always prepare patches in `patch -p1' form, as per
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt, thanks.
>
>
Sorry. I am confused with this. Does that mean I should make patches
_upon_ the root kernel source directory or first make a copy of the
original source code and then diff against the two dirs? But I was
told that "patches should be based _in_ the root kernel source
directory" and when only one file was modified just to diff it with
the original single file. (See Documentation/SubmittingPatches.)
Can you help out? And should I remake this patch? Thanks again!
next prev parent reply other threads:[~2007-04-01 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 2:30 Cong WANG
2007-04-01 5:31 ` Andrew Morton
2007-04-01 6:20 ` Cong WANG [this message]
2007-04-01 6:34 ` Andrew Morton
2007-04-01 6:46 ` Cong WANG
[not found] ` <20070411062349.GA5843@mail.ustc.edu.cn>
2007-04-11 6:23 ` Fengguang Wu
2007-04-11 6:48 ` WANG Cong
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=2375c9f90703312320m3e895bbap735c2d49da9d5ff9@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®