[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <480267C0.6020402@trash.net>
Date: Sun, 13 Apr 2008 22:06:24 +0200
From: Patrick McHardy <kaber@...sh.net>
To: Pavel Emelyanov <xemul@...nvz.org>
CC: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Natalie Protasevich <protasnb@...il.com>,
Linux Netdev List <netdev@...r.kernel.org>,
andy@...yhouse.net
Subject: Re: 2.6.25-rc9: Reported regressions from 2.6.24
[CC list trimmed slightly]
Patrick McHardy wrote:
> 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@...yhouse.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)?
The description of the problem was not entirely correct, the
bridge-netfilter dst_entry does have a proper device pointer,
it points to a dummy net_device structure however that doesn't
have a namespace associated with it. This blows up in
__ip_route_output_key.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists