netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: chrisw@sous-sol.org, davem@davemloft.net, netdev@vger.kernel.org,
	stable@kernel.org
Subject: Re: [stable] [PATCH 2.6.21-stable] [IPV6]: Restore semantics of Routing Header processing.
Date: Wed, 16 May 2007 18:46:00 -0700	[thread overview]
Message-ID: <20070517014600.GE3429@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070512.012820.126195303.yoshfuji@linux-ipv6.org>

* YOSHIFUJI Hideaki / 吉藤英明 (yoshfuji@linux-ipv6.org) wrote:
> In article <20070511162243.GC3516@sequoia.sous-sol.org> (at Fri, 11 May 2007 09:22:43 -0700), Chris Wright <chrisw@sous-sol.org> says:
> > * YOSHIFUJI Hideaki / 吉藤英明 (yoshfuji@linux-ipv6.org) wrote:
> > > The "fix" for emerging security threats was overkill and it broke
> > > basic semantic of IPv6 routing header processing.  We should assume
> > > RT0 (or even RT2, depends on configuration) as "unknown" RH type so
> > > that we
> > > - silently ignore the routing header if segleft == 0
> > > - or, send ICMPv6 Parameter Problem message back to the sender,
> > >   otherwise.
> > 
> > Does that mean this one has received testing and is good for -stable
> > now, or does it need some bake time?
> 
> Chris, I think it is okay, but
> please wait for Dave's approval.

Any update on this one?

thanks,
-chris

  parent reply	other threads:[~2007-05-17  1:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 16:17 [PATCH 2.6.21-stable] [IPV6]: Restore semantics of Routing Header processing YOSHIFUJI Hideaki / 吉藤英明
2007-05-11 16:22 ` [stable] " Chris Wright
2007-05-11 16:28   ` YOSHIFUJI Hideaki / 吉藤英明
2007-05-11 16:29     ` Chris Wright
2007-05-17  1:46     ` Chris Wright [this message]
     [not found]       ` <20070516.191013.102573773.davem@davemloft.net>
2007-05-17  2:12         ` Chris Wright

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=20070517014600.GE3429@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=stable@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).