linux-kernel - Re: sky2 panic in 2.6.32.1 under load

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: <200912241128.57599.dhazelton@enter.net>
Date:	Thu, 24 Dec 2009 11:28:57 -0500
From:	Daniel Hazelton <dhazelton@...er.net>
To:	Berck Nash <flyboy@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org, Stephen Hemminger <shemminger@...tta.com>
Subject: Re: sky2 panic in 2.6.32.1 under load

On Thursday 24 December 2009 11:03:56 am Berck Nash wrote:
> Andrew Morton wrote:
> > On Mon, 21 Dec 2009 16:52:10 -0700 "Berck E. Nash" <flyboy@...il.com> 
wrote:
> >> Since 2.6.32, I've been getting kernel panics under heavy network load
> >> (bittorrent usage).
> >
> > Let's cc the right list and developer.
> >
> > This is a 2.6.31->2.6.32 regression?
> 
> I believe so.  Since it's intermittent and difficult to reproduce, it's
> possible (but unlikely) that I simply never triggered it under 2.6.31.

This is far from new. I have seen this under 2.6.27 when at least one botnet 
has been pointed at a server of mine and told to gain access. It has happened 
four times in the last six to eight months - and I have no easy way to capture 
the logs. But the oops that was posted looks very, very similar to what I've 
seen.

It's always an allocation error in the transmit path that leads to the panic. 
Because this is a production machine that I do not have a way to take down and 
do testing with I've not reported the problem before.

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