From: Linda Xie <lxiep@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Linda Xie <lxiep@us.ibm.com>,
linux-kernel@vger.kernel.org, scheel@us.ibm.com,
wortman@us.ibm.com
Subject: Re: PATCPATCH -- add unlimited name lengths support to sysfs
Date: Wed, 17 Dec 2003 14:27:57 -0600 [thread overview]
Message-ID: <3FE0BC4D.8080605@us.ltcfwd.linux.ibm.com> (raw)
In-Reply-To: 20031216231447.GA4781@kroah.com
Greg KH wrote:
> On Tue, Dec 16, 2003 at 05:07:22PM -0600, Linda Xie wrote:
>
>>diff -Nru a/fs/sysfs/symlink.c b/fs/sysfs/symlink.c
>>--- a/fs/sysfs/symlink.c Sun Dec 14 21:19:29 2003
>>+++ b/fs/sysfs/symlink.c Sun Dec 14 21:19:29 2003
>>@@ -42,7 +42,10 @@
>> struct kobject * p = kobj;
>> int length = 1;
>> do {
>>- length += strlen(p->name) + 1;
>>+ if (p->k_name)
>>+ length += strlen(p->k_name) + 1;
>>+ else
>>+ length += strlen(p->name) + 1;
>
>
> Shouldn't this just be:
> length += strlen(kobject_name(p)) + 1;
>
That is correct. But here is my concern: Some of the callers of
sysfs_create_link()
set p->name instead of p->k_name. So for them, the length calculated
using kobject_name(p) will be incorrect. Correct me if I am wrong.
Thanks,
Linda
>
>>@@ -54,11 +57,20 @@
>>
>> --length;
>> for (p = kobj; p; p = p->parent) {
>>- int cur = strlen(p->name);
>>-
>>+ int cur;
>>+ char *name;
>>+
>>+ if (p->k_name) {
>>+ cur = strlen(p->k_name);
>>+ name = p->k_name;
>>+ }
>>+ else {
>>+ cur = strlen(p->name);
>>+ name = p->name;
>>+ }
>
>
> Same here, just use kobject_name() to get the proper pointer.
>
> thanks,
>
> greg k-h
Thanks,
Linda
next prev parent reply other threads:[~2003-12-17 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 23:07 PATCPATCH -- add unlimited name lengths support to sysfs Linda Xie
2003-12-16 23:14 ` Greg KH
2003-12-17 20:27 ` Linda Xie [this message]
2003-12-17 20:41 ` Greg KH
2003-12-18 2:23 ` Linda Xie
2004-02-02 23:26 ` Greg KH
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=3FE0BC4D.8080605@us.ltcfwd.linux.ibm.com \
--to=lxiep@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scheel@us.ibm.com \
--cc=wortman@us.ibm.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