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]

Date:	Mon, 21 Jul 2008 13:20:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mingo@...e.hu
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	stefanr@...6.in-berlin.de
Subject: Re: [crash] kernel BUG at net/core/dev.c:1328!

From: Ingo Molnar <mingo@...e.hu>
Date: Mon, 21 Jul 2008 21:44:14 +0200

> 
> * David Miller <davem@...emloft.net> wrote:
> 
> > From: Linus Torvalds <torvalds@...ux-foundation.org>
> > Date: Mon, 21 Jul 2008 11:35:21 -0700 (PDT)
> > 
> > > 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.
> > > 
> > > I personally suspect the latter, since it seems to happen with just
> > > about _any_ random network driver, including the common and
> > > well-maintained ones (ie the Gods only help us for the truly
> > > odd/random cases)
> > 
> > Yes, we'll see how this plays out.
> > 
> > Ian Schram just posted a patch for the NULL pointer derfer in wireless 
> > Ingo reported, so we'll see if that bug will be fixed now as well.
> 
> Yes, the fix from Ian below solved the CONFIG_MAC80211_HWSIM=y crash i 
> was getting. I have no other pending issues other than a few low-prio 
> ne2000 build failures.
> 
> Thanks guys,

Thanks everyone, applied.
--
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/