From: Brian Haley <brian.haley@hp.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
netdev-owner@vger.kernel.org,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [IPv6] Fix ICMPv6 redirect handling with target multicast address
Date: Tue, 02 Oct 2007 17:06:08 -0400 [thread overview]
Message-ID: <4702B2C0.2070004@hp.com> (raw)
In-Reply-To: <OF939F3A2D.96830882-ON88257368.007068EA-88257368.007161DC@us.ibm.com>
Hi David,
David Stevens wrote:
> ipv6_addr_type() returns a mask, so checking for equality will
> fail to
> match if any other (irrelevant) attributes are set. How about using
> bitwise
> operators for that?
ipv6_addr_type() does return a mask, but there's a lot of code that just
checks for equality since some things are mutually-exclusive - this code
is actually identical to what ip6_route_add() does. I don't
particularly like this duality, but it's there - I'd gladly volunteer to
clean this up everywhere if I didn't think there might be some
performance reason it was done like that.
> Also, the error message is no longer descriptive of the
> failure if it's a link-local multicast, but you could make it "target
> address is not
> link-local unicast.\n" (in both places).
I can do that, thanks.
-Brian
next prev parent reply other threads:[~2007-10-02 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 16:26 [IPV6] Fix ICMPv6 redirect handling with target multicast address Brian Haley
2007-09-29 0:50 ` David Stevens
2007-09-29 1:04 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-01 3:27 ` Brian Haley
2007-10-01 11:49 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-01 17:36 ` Brian Haley
2007-10-02 19:18 ` [IPv6] " Brian Haley
2007-10-02 20:39 ` David Stevens
2007-10-02 21:06 ` Brian Haley [this message]
2007-10-02 22:41 ` David Stevens
2007-10-03 14:44 ` [IPv6] Fix ICMPv6 redirect handling with target multicast address, try 3 Brian Haley
2007-10-08 7:12 ` David Miller
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=4702B2C0.2070004@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).