linux-kernel - Re: [crash] kernel BUG at net/core/dev.c:1328!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080721184616.GA8442@elte.hu>
Date:	Mon, 21 Jul 2008 20:46:16 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	David Miller <davem@...emloft.net>, akpm@...ux-foundation.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Stefan Richter <stefanr@...6.in-berlin.de>
Subject: Re: [crash] kernel BUG at net/core/dev.c:1328!


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Mon, 21 Jul 2008, Ingo Molnar wrote:
> >
> > [   24.434799] kernel BUG at net/core/dev.c:1328!
> 
> Ok, it is now a WARN_ON_ONCE() in my tree (which I _just_ pushed out). 
> 
> So it's going to cause irritating messages (once), but the machine should 
> hopefully work.
> 
> > Should i spend time on bisecting this, or is this known already?
> 
> It's going to bisect down to the same commit you already bisected 
> once, it's the networking code that changed some of the rules, so 
> various network drivers that didn't follow the expected rules are now 
> unhappy.
> 
> Maybe the network drivers are few enough that it will get fixed, or 
> maybe the WARN_ON_ONCE() will just be removed and the rule not 
> reinforced.

ok, have updated the testboxes to your latest push.

Btw., otherwise the big networking pull held up pretty well on a healthy 
range of testboxes i have, it looked a lot scarier to me in the morning 
than it turned out to be during the day. A couple of hundred tests 
passed already and no indication of any runtime fragility so far. Boot 
crashes/warnings can be annoying and hard to get a proper log of but 
once the log is available they are normally quite easy for developers to 
act upon.

	Ingo
--
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/