netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: sri@us.ibm.com, netdev@vger.kernel.org, CHINEN@jp.ibm.com
Subject: Re: ping6 to own link-local address
Date: Wed, 28 Mar 2007 01:45:33 -0700 (PDT)	[thread overview]
Message-ID: <20070328.014533.112621902.davem@davemloft.net> (raw)
In-Reply-To: <20070328.165748.48153731.yoshfuji@linux-ipv6.org>

From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Wed, 28 Mar 2007 16:57:48 +0900 (JST)

> In article <20070321.002609.58216683.yoshfuji@linux-ipv6.org> (at Wed, 21 Mar 2007 00:26:09 +0100 (CET)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> says:
> 
> > In article <1174429000.3255.3.camel@w-sridhar2.beaverton.ibm.com> (at Tue, 20 Mar 2007 15:16:40 -0700), Sridhar Samudrala <sri@us.ibm.com> says:
> > 
> > > The following patch seems to be the cause for this regression.
> > > 
> > > [IPV6] ROUTE: Do not route packets to link-local address on other device.
> > > 
> > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a0d78ebf3a0e33a1aeacf2fc518ad9273d6a1c2f
> > 
> > Right.  Hmm...
> 
> Well, 2.6.21 is coming.  I think it is better to revert it for now.
> Current situation is more critical than the original.
> 
> Dave?

I will look into this and make some kind of decision on how
to proceed tomorrow.

  reply	other threads:[~2007-03-28  8:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20  9:19 ping6 to own link-local address YOSHIFUJI Hideaki / 吉藤英明
2007-03-20 22:16 ` Sridhar Samudrala
2007-03-20 23:26   ` YOSHIFUJI Hideaki / 吉藤英明
2007-03-28  7:57     ` YOSHIFUJI Hideaki / 吉藤英明
2007-03-28  8:45       ` David Miller [this message]
2007-04-06  7:35         ` YOSHIFUJI Hideaki / 吉藤英明
2007-04-06  8:02           ` David Miller
2007-04-06 18:43             ` 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=20070328.014533.112621902.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=CHINEN@jp.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sri@us.ibm.com \
    --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).