Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750878AbWEVOnk (ORCPT ); Mon, 22 May 2006 10:43:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750880AbWEVOnj (ORCPT ); Mon, 22 May 2006 10:43:39 -0400 Received: from stinky.trash.net ([213.144.137.162]:12979 "EHLO stinky.trash.net") by vger.kernel.org with ESMTP id S1750877AbWEVOnj (ORCPT ); Mon, 22 May 2006 10:43:39 -0400 Message-ID: <4471CE19.5070802@trash.net> Date: Mon, 22 May 2006 16:43:37 +0200 From: Patrick McHardy User-Agent: Debian Thunderbird 1.0.7 (X11/20051019) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Ayres CC: James Morris , "xen-devel@lists.xensource.com" , Netfilter Development Mailinglist , Linux Kernel Mailing List Subject: Re: [Xen-devel] Re: Panic in ipt_do_table with 2.6.16.13-xen References: <4468BE70.7030802@tektonic.net> <4468D613.20309@trash.net> <44691669.4080903@tektonic.net> <4469D84F.8080709@tektonic.net> <446D0A0D.5090608@tektonic.net> <446D0E6D.2080600@tektonic.net> <446D151D.6030307@tektonic.net> <4470A6CD.5010501@trash.net> <4471CB54.401@tektonic.net> In-Reply-To: <4471CB54.401@tektonic.net> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1810 Lines: 43 Matt Ayres wrote: > > > Patrick McHardy wrote: > >> Matt Ayres wrote: >> >>> I think I confirmed the NIC is not the source of the problem. A few of >>> my servers have e100/tulip NIC's due to a bug with the chipset of the >>> on-board TG3 cards firmware and TSO. These servers that use the >>> e100/tulip drivers also experience the ipt_do_table bug. >> >> >> There is an identical report in the netfilter bugzilla, also crashes >> (on x86_64) in ipt_do_table with Xen. I haven't heard anything of >> similar crashes without Xen, so I doubt that the bug is in the >> netfilter code. >> >> https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=478 > > > Yep... too coincidental. I'd say it has _something_ to do with Xen. > I've been doing different things on my side to try to reduce the > severity of the problem, but I'd really like to hear what the Xen guys > have to say about this now.. Maybe this helps: there is not too much the Xen code could be doing wrong here. If I read your crash correctly it happend in the FORWARD chain, which could mean that the outgoing device (probably the Xen virtual network driver) has some bugs, but iptables really only cares about the names at this point, which practically can't be bogus. The only other thing I can imagine is that something is wrong with the per-CPU copy of the ruleset, i.e. either smp_processor_id is returning garbage or for_each_possible_cpu misses a CPU during initialization. I have no idea if Xen really does touch this code, but other than that I don't really see what it could break. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/