From: Yuta sugiura <ysugiura@miraclelinux.com>
To: netdev@vger.kernel.org
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Andreas Schwab <schwab@linux-m68k.org>,
David Miller <davem@davemloft.net>,
brian.haley@hp.com
Subject: Re: [IPV6]: ROUTE:read ifname in rt6_info_route()
Date: Fri, 17 Apr 2009 12:44:13 +0900 [thread overview]
Message-ID: <49E7FB0D.3040100@miraclelinux.com> (raw)
In-Reply-To: <20090416102731.459f9558@nehalam>
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
Thank you for respons to my e-mail.
I read net-snmp's patch as reference.
How about this method?
Stephen Hemminger wrote:
> On Thu, 16 Apr 2009 18:47:04 +0200
> Andreas Schwab <schwab@linux-m68k.org> wrote:
>
>
>> Stephen Hemminger <shemminger@vyatta.com> writes:
>>
>>
>>> On Thu, 16 Apr 2009 04:38:00 -0700 (PDT)
>>> David Miller <davem@davemloft.net> wrote:
>>>
>>>
>>>> From: Yuta sugiura <ysugiura@miraclelinux.com>
>>>> Date: Thu, 16 Apr 2009 20:05:05 +0900
>>>>
>>>>
>>>>> Hi,
>>>>> I have a suggestion about /proc/net/IPv6_route format.
>>>>> In rt6_info_route(), interface name is treated as a maximum 8
>>>>> characters.
>>>>> But the type of (struct rt6_inf *)->u.dst.dev->name is char[IFNAMESIZ=
>>>>> 16]
>>>>> so, I think that it should change "%8s" to "%16s".
>>>>>
>>>> Isn't there a way to pass the field length as a paramenter
>>>> to formatting functions? Then we can just pass in
>>>> IFNAMESIZE as that parameter.
>>>>
>>> seq_printf(m, " %08x %08x %08x %08x %*s\n"
>>> rt->rt6i_metric, atomic_read(&rt->u.dst.__refcnt),
>>> rt->u.dst.__use, rt->rt6i_flags,
>>> IFNAMESIZE,
>>> rt->rt6i_dev ? rt->rt6i_dev->name : "")
>>>
>> Actually since it is the last item on the line a field width does not
>> make much sense, and omitting it would print the name left justified.
>>
>> (And RT6_INFO_LEN is not used any more.)
>>
>> Andreas.
>>
>>
>
> The issue is what happens if name is not null terminated. in this case
> I bet the kernel already handles that.
>
>
[-- Attachment #2: ipv6_route_ifnamesiz2.patch --]
[-- Type: text/plain, Size: 824 bytes --]
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index 1394ddb..a532dda 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -2434,7 +2434,8 @@ static int ip6_route_dev_notify(struct notifier_block *this,
#ifdef CONFIG_PROC_FS
-#define RT6_INFO_LEN (32 + 4 + 32 + 4 + 32 + 40 + 5 + 1)
+#define RT6_INFO_LEN (32 + 4 + 32 + 4 + 32 + 48 + 5 + 1)
+#define RT6_VAL_TO_STR(s) #s
struct rt6_proc_arg
{
@@ -2462,7 +2463,8 @@ static int rt6_info_route(struct rt6_info *rt, void *p_arg)
} else {
seq_puts(m, "00000000000000000000000000000000");
}
- seq_printf(m, " %08x %08x %08x %08x %8s\n",
+ seq_printf(m, " %08x %08x %08x %08x %"
+ RT6_VAL_TO_STR(IFNAMSIZ) "s\n",
rt->rt6i_metric, atomic_read(&rt->u.dst.__refcnt),
rt->u.dst.__use, rt->rt6i_flags,
rt->rt6i_dev ? rt->rt6i_dev->name : "");
next prev parent reply other threads:[~2009-04-17 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 11:05 [IPV6]: ROUTE:read ifname in rt6_info_route() Yuta sugiura
2009-04-16 11:38 ` David Miller
2009-04-16 15:30 ` Stephen Hemminger
2009-04-16 16:17 ` Brian Haley
2009-04-16 16:47 ` Andreas Schwab
2009-04-16 17:27 ` Stephen Hemminger
2009-04-17 3:44 ` Yuta sugiura [this message]
2009-04-17 10:24 ` Andreas Schwab
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=49E7FB0D.3040100@miraclelinux.com \
--to=ysugiura@miraclelinux.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.