linux-kernel - Re: iwlagn: order 2 page allocation failures

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:	Tue, 08 Sep 2009 09:59:05 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	"John W. Linville" <linville@...driver.com>
CC:	Pekka Enberg <penberg@...helsinki.fi>, Mel Gorman <mel@....ul.ie>,
	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
	linux-wireless@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net,
	Andrew Morton <akpm@...ux-foundation.org>,
	cl@...ux-foundation.org
Subject: Re: iwlagn: order 2 page allocation failures

John W. Linville wrote:
> On Tue, Sep 08, 2009 at 02:11:35PM +0300, Pekka Enberg wrote:
>> On Tue, Sep 8, 2009 at 1:54 PM, Mel Gorman<mel@....ul.ie> wrote:
>>> My feeling is also that a number of these page allocation failures have
>>> been related to wireless drivers. Is that accurate? If so, have there
>>> been changes made to the wireless stack in this cycle that would have
>>> increased the order of pages allocated?
>> That's my general feeling as well. We have linux-wireless CC'd so
>> maybe this rings a bell for them.
> 
> AFAIK, this is only the second separate report.  The other related
> to ipw2200, which actually shares no code with the iwlagn driver and
> is not based on the mac80211 stack.

A previous issue concerned the interaction between wireless and SLUB
debugging that caused O(0) allocations to get bumped to O(1), but that
was not relevant to this case either. I'm not aware of any other page
allocation problems with wireless.

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