[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sun, 11 Nov 2007 11:59:03 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: netdev@...r.kernel.org
Cc: bugme-daemon@...zilla.kernel.org, rdenis@...phalempin.com
Subject: Re: [Bugme-new] [Bug 9349] New: RTNLGRP_ND_USEROPT does not report
ifindex
On Sun, 11 Nov 2007 10:52:41 -0800 (PST) bugme-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9349
>
> Summary: RTNLGRP_ND_USEROPT does not report ifindex
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.24-rc
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV6
> AssignedTo: yoshfuji@...ux-ipv6.org
> ReportedBy: rdenis@...phalempin.com
>
>
> Most recent kernel where this bug did not occur: none
> Distribution: N/A
> Hardware Environment: any
> Software Environment: any
> Problem Description:
> The RTNLGRP_ND_USEROPT NetLink message introduced in 2.6.24 does not seem to
> include any information as to which netif the user options come from:
>
> struct nduseroptmsg
> {
> unsigned char nduseropt_family;
> unsigned char nduseropt_pad1;
> unsigned short nduseropt_opts_len; /* Total length of options */
> __u8 nduseropt_icmp_type;
> __u8 nduseropt_icmp_code;
> unsigned short nduseropt_pad2;
> /* Followed by one or more ND options */
> };
>
> Considering this is meant to carry data that is heavily link-layer involved,
> this seems like a feature bug. Could an ifindex field be added there??
>
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists