netdev - Re: [1/3] 2.6.21-rc6: known regressions

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: <Pine.LNX.4.64.0704131821020.28042@woody.linux-foundation.org>
Date:	Fri, 13 Apr 2007 18:34:23 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Adrian Bunk <bunk@...sta.de>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Jeff Garzik <jgarzik@...ox.com>, netdev@...r.kernel.org,
	e1000-devel@...ts.sourceforge.net, Ingo Molnar <mingo@...e.hu>,
	Ayaz Abdulla <aabdulla@...dia.com>,
	Dave Jones <davej@...hat.com>,
	"David S. Miller" <davem@...emloft.net>, Greg KH <greg@...ah.com>
Subject: Re: [1/3] 2.6.21-rc6: known regressions

Note: Ingo also reports what looks like a memory corruption due to 
the 6b6b6b6b pattern on presumably the same box.

The 6b6b6b6b pattern is POISON_FREE, implying some kind of slab misuse, 
most likely a use-after-free, although possibly just due to overrunning a 
slab into the next one or something like that.

What I'm leading up to is that I'm wondering if these mysterious network 
driver bugs aren't due to the network drivers themselves, but due to some 
higher-level problem. I think the hangs that Ingo sees with forcedeth were 
preceded by mysterious and "impossible" NULL pointer oopses. Ingo?

Davem - have there been network infrastructure changes that migt be 
suspect? Jeff and/or Greg - anything in the generic network driver/device 
driver level? We had some trouble earlier with the transition to the 
driver core, and kref miscounting. Related? The last Oops Ingo saw was a 
module refcounting one, iirc.

It does seem networking related somehow. Yeah, it could be obviously be a 
combination of independent bugs both in e1000/ and forcedeth drivers, but 
maybe there is something in common here...

I'll make an -rc7, but I'm a bit worried about the fact that I haven't 
actually gotten anything that looks like it might address any of this 
(unless some of the network patches I just pulled do, but that sounds 
unlikely). It's been very quiet. I don't like that. I don't get the 
feeling that we're making progress here, unlike the timer-related 
regressions which seem to all be slowly working themselves out..

So please people, give it a look. Comments?

		Linus

On Sat, 14 Apr 2007, Adrian Bunk wrote:
> 
> Subject    : laptops with e1000: lockups
> References : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229603
> Submitter  : Dave Jones <davej@...hat.com>
> Handled-By : Jesse Brandeburg <jesse.brandeburg@...el.com>
> Status     : problem is being debugged
> 
> Subject    : forcedeth: interface hangs under load
> References : http://lkml.org/lkml/2007/4/3/39
> Submitter  : Ingo Molnar <mingo@...e.hu>
> Handled-By : Ingo Molnar <mingo@...e.hu>
>              Ayaz Abdulla <aabdulla@...dia.com>
> Status     : problem is being debugged

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html