netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Savola <pekkas@netcore.fi>
To: netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 7817] New: commit edfe21a29b1dca9ce5a938317868066d2e21c385 breaks IPv6 address autoconfiguration
Date: Mon, 15 Jan 2007 06:47:50 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701150646250.4252@netcore.fi> (raw)
In-Reply-To: <20070113134506.6021cf79.akpm@osdl.org>

On Sat, 13 Jan 2007, Andrew Morton wrote:
>> On Sat, 13 Jan 2007 05:44:39 -0800 bugme-daemon@bugzilla.kernel.org wrote:
>> http://bugzilla.kernel.org/show_bug.cgi?id=7817
>>
>>            Summary: commit edfe21a29b1dca9ce5a938317868066d2e21c385 breaks
>>                     IPv6 address autoconfiguration
>>     Kernel Version: 2.6.19.2
>>             Status: NEW
>>           Severity: high
>>              Owner: yoshfuji@linux-ipv6.org
>>          Submitter: gernoth@informatik.uni-erlangen.de
>>
>>
>> Most recent kernel where this bug did *NOT* occur: 2.6.19.1
>> Distribution: Debian Testing
>> Hardware Environment: About 100 different x86 boxes
>> Software Environment: no special software involved, just the kernel. No modules are loaded on the
>> affected machines (everything needed is built into the kernel)
>>

I got hit by this as well.  2.6.20rc4-git4 is also affected.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

      parent reply	other threads:[~2007-01-15  4:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200701131344.l0DDidDq007345@fire-2.osdl.org>
2007-01-13 21:45 ` [Bugme-new] [Bug 7817] New: commit edfe21a29b1dca9ce5a938317868066d2e21c385 breaks IPv6 address autoconfiguration Andrew Morton
2007-01-14 18:56   ` [PATCH] [IPV6] MCAST: Fix joining all-node multicast group on device initialization YOSHIFUJI Hideaki / 吉藤英明
2007-01-15  4:47   ` Pekka Savola [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=Pine.LNX.4.64.0701150646250.4252@netcore.fi \
    --to=pekkas@netcore.fi \
    --cc=netdev@vger.kernel.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).