From: ebiederm@xmission.com (Eric W. Biederman)
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@mail.by>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kobject_set_name_vargs memory leak
Date: Sun, 28 Jun 2009 06:13:56 -0700 [thread overview]
Message-ID: <m1tz20zejv.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <ac3eb2510906280602j1812d7e7qce874d2e9775e29e@mail.gmail.com> (Kay Sievers's message of "Sun\, 28 Jun 2009 15\:02\:46 +0200")
Kay Sievers <kay.sievers@vrfy.org> writes:
> On Sun, Jun 28, 2009 at 14:07, Eric W. Biederman<ebiederm@xmission.com> wrote:
>
>> But setting a kobject's name several times in a row is a bug. You
>> need to call kobject_rename if you are going to change the name.
>
> Sure, we can define in that way.
>
>> So how about we fix the driver core not to do that. Stop treating fmt
>> as a flag, and make it clear kobject_add should not be passed a name.
>
> Sounds fine to me. You did not try to compile your patch, right? :)
Only the lib/kobject bits...
> block/blk-sysfs.c: In function ‘blk_register_queue’:
> block/blk-sysfs.c:436: error: implicit declaration of function ‘kobj_set_name’
>
> drivers/base/driver.c: In function ‘driver_add_kobj’:
> drivers/base/driver.c:149: error: too many arguments to function ‘kobject_add’
Ugh I totally missed that one.
> Documentation/kobject.txt would also need an update then.
As for the rules it already seems correct.
But getting the prototype and mentioning kobject_set_name wouldn't
hurt.
Eric
next prev parent reply other threads:[~2009-06-28 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 14:36 [PATCH] kobject_set_name_vargs memory leak Sergey Senozhatsky
2009-06-26 14:49 ` Greg KH
2009-06-26 22:29 ` Sergey Senozhatsky
2009-06-26 23:00 ` Eric W. Biederman
2009-06-26 23:14 ` Sergey Senozhatsky
2009-06-26 23:23 ` Sergey Senozhatsky
2009-06-27 2:10 ` Eric W. Biederman
2009-06-27 9:33 ` Sergey Senozhatsky
2009-06-27 9:39 ` Sergey Senozhatsky
2009-06-27 23:56 ` Kay Sievers
2009-06-28 12:07 ` Eric W. Biederman
2009-06-28 13:02 ` Kay Sievers
2009-06-28 13:13 ` Eric W. Biederman [this message]
2009-06-28 13:40 ` Sergey Senozhatsky
2009-06-29 9:53 ` Dave Young
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=m1tz20zejv.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@mail.by \
/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