From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, rdenis@simphalempin.com
Subject: Re: [Bugme-new] [Bug 9349] New: RTNLGRP_ND_USEROPT does not report ifindex
Date: Sun, 11 Nov 2007 11:59:03 -0800 [thread overview]
Message-ID: <20071111115903.90f0fdc0.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9349-10286@http.bugzilla.kernel.org/>
On Sun, 11 Nov 2007 10:52:41 -0800 (PST) bugme-daemon@bugzilla.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@linux-ipv6.org
> ReportedBy: rdenis@simphalempin.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??
>
next parent reply other threads:[~2007-11-11 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9349-10286@http.bugzilla.kernel.org/>
2007-11-11 19:59 ` Andrew Morton [this message]
2007-11-12 23:44 ` [Bugme-new] [Bug 9349] New: RTNLGRP_ND_USEROPT does not report ifindex Pierre Ynard
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=20071111115903.90f0fdc0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdenis@simphalempin.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;
as well as URLs for NNTP newsgroup(s).