From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Greg KH" <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The use of KOBJ_NAME_LEN
Date: Tue, 4 Dec 2007 15:53:15 +0800 [thread overview]
Message-ID: <a8e1da0712032353m1a705ec6ged4d503818ad8f58@mail.gmail.com> (raw)
In-Reply-To: <20071204074612.GA25316@suse.de>
On Dec 4, 2007 3:46 PM, Greg KH <gregkh@suse.de> wrote:
> On Tue, Dec 04, 2007 at 02:45:47PM +0800, Dave Young wrote:
> > Hi,
> > Does the KOBJ_NAME_LEN really means the limit of kobject name length? seems
> > not . And if it's true, is the KOBJ_NAME_LEN of 20 enough to use?
>
> No, not anymore, the kobject name is totally dynamic.
Eh, Why does this macro still exist? If KOBJ_NAME_LEN is really
needed, maybe it should be renamed to something else to avoid
misleading.
>
> > In the kobject_set_name, the limit is 1024. Looks like either the comment or
> > the code should be updated.
>
> Here's a patch below for the comment updating it.
Thanks
>
> I also have a patch in my -mm series that takes away the 1024 character
> limit, but for 2.6.24 we'll have to live with it :)
>
> thanks,
>
> greg k-h
>
>
> ---
> lib/kobject.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> --- a/lib/kobject.c
> +++ b/lib/kobject.c
> @@ -234,13 +234,13 @@ int kobject_register(struct kobject * ko
>
>
> /**
> - * kobject_set_name - Set the name of an object
> - * @kobj: object.
> - * @fmt: format string used to build the name
> + * kobject_set_name - Set the name of a kobject
> + * @kobj: kobject to name
> + * @fmt: format string used to build the name
> *
> - * If strlen(name) >= KOBJ_NAME_LEN, then use a dynamically allocated
> - * string that @kobj->k_name points to. Otherwise, use the static
> - * @kobj->name array.
> + * This sets the name of the kobject. If you have already added the
> + * kobject to the system, you must call kobject_rename() in order to
> + * change the name of the kobject.
> */
> int kobject_set_name(struct kobject * kobj, const char * fmt, ...)
> {
>
next prev parent reply other threads:[~2007-12-04 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 6:45 Dave Young
2007-12-04 6:50 ` Robert P. J. Day
2007-12-04 7:17 ` Dave Young
2007-12-04 7:46 ` Greg KH
2007-12-04 8:02 ` Robert P. J. Day
2007-12-04 7:46 ` Greg KH
2007-12-04 7:53 ` Dave Young [this message]
2007-12-04 8:20 ` Greg KH
2007-12-04 8:22 ` 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=a8e1da0712032353m1a705ec6ged4d503818ad8f58@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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®