From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: shanwei@cn.fujitsu.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: fix the bug of address check
Date: Mon, 17 May 2010 22:27:41 -0700 (PDT) [thread overview]
Message-ID: <20100517.222741.108775428.davem@davemloft.net> (raw)
In-Reply-To: <20100517180221.3a90ffcf@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Mon, 17 May 2010 18:02:21 -0700
> The duplicate address check code got broken in the conversion
> to hlist (2.6.35). The earlier patch did not fix the case where
> two addresses match same hash value. Use two exit paths,
> rather than depending on state of loop variables (from macro).
>
> Based on earlier fix by Shan Wei.
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> Reviewed-by: Shan Wei <shanwei@cn.fujitsu.com>
Applied, thanks everyone.
prev parent reply other threads:[~2010-05-18 5:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 12:23 [PATCH BUGFIX ] ipv6: fix the bug of address check Shan Wei
2010-05-17 17:31 ` Stephen Hemminger
2010-05-18 0:50 ` Shan Wei
2010-05-18 1:02 ` [PATCH net-next] " Stephen Hemminger
2010-05-18 5:27 ` David Miller [this message]
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=20100517.222741.108775428.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shanwei@cn.fujitsu.com \
--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 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).