From: Ben Hutchings <ben@decadent.org.uk>
To: Noah Meyerhans <noahm@debian.org>
Cc: 625914@bugs.debian.org, bridge@lists.linux-foundation.org,
netdev <netdev@vger.kernel.org>
Subject: Re: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
Date: Tue, 10 May 2011 13:42:49 +0100 [thread overview]
Message-ID: <1305031369.4065.259.camel@localhost> (raw)
In-Reply-To: <20110510043833.GG6397@morgul.net>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Mon, 2011-05-09 at 21:38 -0700, Noah Meyerhans wrote:
> On Tue, May 10, 2011 at 03:38:44AM +0100, Ben Hutchings wrote:
> > This is pretty weird. Debian version 2.6.38-3 has a few bridging
> > changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
> > would cause this.
>
> I have apparently filed the bug against the wrong version of Debian's
> kernel. 2.6.38-3 is not affected, and works as expected. The change
> was introduced in -4. That may have been clear from the report itself,
> but the report was filed against -3. I've fixed that in the BTS.
I gathered that, and then made the same mistake in writing the above!
The version with the regression, 2.6.38-4, includes the changes from
stable 2.6.38.3 and 2.6.38.4
Ben.
> I've also confirmed that -5 is affected, to no great surprise.
>
> I'll investigate further.
>
> noah
>
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Ben Hutchings <ben@decadent.org.uk>
To: Noah Meyerhans <noahm@debian.org>
Cc: 625914@bugs.debian.org, netdev <netdev@vger.kernel.org>,
bridge@lists.linux-foundation.org
Subject: Re: Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
Date: Tue, 10 May 2011 13:42:49 +0100 [thread overview]
Message-ID: <1305031369.4065.259.camel@localhost> (raw)
In-Reply-To: <20110510043833.GG6397@morgul.net>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Mon, 2011-05-09 at 21:38 -0700, Noah Meyerhans wrote:
> On Tue, May 10, 2011 at 03:38:44AM +0100, Ben Hutchings wrote:
> > This is pretty weird. Debian version 2.6.38-3 has a few bridging
> > changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
> > would cause this.
>
> I have apparently filed the bug against the wrong version of Debian's
> kernel. 2.6.38-3 is not affected, and works as expected. The change
> was introduced in -4. That may have been clear from the report itself,
> but the report was filed against -3. I've fixed that in the BTS.
I gathered that, and then made the same mistake in writing the above!
The version with the regression, 2.6.38-4, includes the changes from
stable 2.6.38.3 and 2.6.38.4
Ben.
> I've also confirmed that -5 is affected, to no great surprise.
>
> I'll investigate further.
>
> noah
>
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-05-10 12:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110506201234.6297.70279.reportbug@ip6-localhost>
2011-05-10 2:38 ` [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4 Ben Hutchings
2011-05-10 2:38 ` Ben Hutchings
2011-05-10 3:15 ` [Bridge] " Stephen Hemminger
2011-05-10 3:15 ` Stephen Hemminger
2011-05-10 4:38 ` [Bridge] " Noah Meyerhans
2011-05-10 4:38 ` Noah Meyerhans
2011-05-10 12:42 ` Ben Hutchings [this message]
2011-05-10 12:42 ` Ben Hutchings
2011-05-10 12:55 ` Yann Dupont
2011-05-10 18:05 ` [Bridge] " Noah Meyerhans
2011-05-10 18:05 ` Noah Meyerhans
2011-05-10 22:11 ` [Bridge] " Stephen Hemminger
2011-05-10 22:11 ` Stephen Hemminger
2011-05-10 23:35 ` Noah Meyerhans
2011-05-10 23:35 ` Noah Meyerhans
2011-05-12 22:59 ` David Miller
2011-05-12 22:59 ` David Miller
2011-05-12 23:28 ` Stephen Hemminger
2011-05-12 23:28 ` Stephen Hemminger
2011-05-12 23:43 ` Stephen Hemminger
2011-05-12 23:43 ` Stephen Hemminger
2011-05-13 5:03 ` Noah Meyerhans
2011-05-13 5:03 ` Noah Meyerhans
2011-05-13 18:03 ` Stephen Hemminger
2011-05-13 18:03 ` Stephen Hemminger
2011-05-13 19:53 ` [Bridge] [PATCH] bridge: fix forwarding of IPv6 Stephen Hemminger
2011-05-13 19:53 ` Stephen Hemminger
2011-05-13 20:00 ` [Bridge] " Eric Dumazet
2011-05-13 20:00 ` Eric Dumazet
2011-05-13 20:02 ` [Bridge] " David Miller
2011-05-13 20:02 ` David Miller
2011-05-13 20:05 ` [Bridge] " Eric Dumazet
2011-05-13 20:05 ` Eric Dumazet
2011-05-13 20:24 ` [Bridge] " Stephen Hemminger
2011-05-13 20:03 ` David Miller
2011-05-13 20:03 ` David Miller
2011-05-13 21:00 ` [Bridge] " Noah Meyerhans
2011-05-13 21:00 ` Noah Meyerhans
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=1305031369.4065.259.camel@localhost \
--to=ben@decadent.org.uk \
--cc=625914@bugs.debian.org \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=noahm@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.