From: Patrick McHardy <kaber@trash.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Natalie Protasevich <protasnb@gmail.com>,
Linux Netdev List <netdev@vger.kernel.org>,
andy@greyhouse.net, Pavel Emelyanov <xemul@openvz.org>
Subject: Re: 2.6.25-rc9: Reported regressions from 2.6.24
Date: Sun, 13 Apr 2008 21:45:45 +0200 [thread overview]
Message-ID: <480262E9.4030500@trash.net> (raw)
In-Reply-To: <RR4Oy_oXY2J.A.b0H.A3lAIB@albercik>
Rafael J. Wysocki wrote:
> This message contains a list of some regressions from 2.6.24, for which there
> are no fixes in the mainline I know of. If any of them have been fixed already,
> please let me know.
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=10323
> Subject : panic using bridging on linus kernel 2.6.25-rc6
> Submitter : Andy Gospodarek <andy@greyhouse.net>
> Date : 2008-03-25 11:40 (20 days old)
This looks like another network-namespace regression.
icmp_send() does:
net = rt->u.dst.dev->nd_net;
The bridge netfilter code attaches a fake dst_entry to the
skb which has dev == NULL when passing it to IPv4 netfilter.
Pavel, do you have a better ideas for fixing this than
instantiating a dst_entry in br_netfilter.c for every
device (or at least for every namespace)?
next parent reply other threads:[~2008-04-13 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RR4Oy_oXY2J.A.b0H.A3lAIB@albercik>
2008-04-13 19:45 ` Patrick McHardy [this message]
2008-04-13 20:06 ` 2.6.25-rc9: Reported regressions from 2.6.24 Patrick McHardy
2008-04-13 20:18 ` Patrick McHardy
2008-04-14 7:46 ` David Miller
2008-04-14 20:31 ` Andy Gospodarek
2008-04-15 13:14 ` Andy Gospodarek
2008-04-15 13:16 ` Patrick McHardy
2008-04-14 8:39 ` Pavel Emelyanov
2008-04-14 8:50 ` Patrick McHardy
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=480262E9.4030500@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=andy@greyhouse.net \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=xemul@openvz.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).