linux-kernel - Re: [GIT]: Networking

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: <20080614023916.431a868d@infradead.org>
Date:	Sat, 14 Jun 2008 02:39:16 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	David Miller <davem@...emloft.net>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, rjw@...k.pl
Subject: Re: [GIT]: Networking

On Sat, 14 Jun 2008 10:16:56 +0200
Ingo Molnar <mingo@...e.hu> wrote:

> 
> ok, should we then remove that warning, if it's spurious?
> kerneloops.org has picked up a few other instances of this warning as
> well:
> 
>   http://www.kerneloops.org/searchfile.php?search=net%2Fsched%2Fsch_generic.c&btnG=Filename+Search

the interesting thing is that there is a clear bias on which drivers
are tripping this (r8169 is top when I counted yesterday, with sis900
second and then a long tail of nothing) that I think the WARN_ON() is
useful in addition to the always-there printk. Eg it does help in seeing
which driver is most likely to trigger this.
(Andrew also thought this would trigger a *LOT*, so far it's only a
rather modest amount, but it's waiting for Fedora or others to ship a
kernel with this in to be sure)

-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/