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] [day] [month] [year] [list]
Date:	Thu, 8 Jan 2009 07:44:31 +0300
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	Maurice Volaski <mvolaski@...om.yu.edu>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: swapper: page allocation failure. order:2, mode:0x4020 in 2.6.27

Hi.

On Thu, Jan 08, 2009 at 10:19:23AM +0900, KOSAKI Motohiro (kosaki.motohiro@...fujitsu.com) wrote:
> if stack dump has tg3_alloc_rx_skb(), that isn't bug. (maybe)
> tg3 network card often reqire non order-0 pages under irq/softirq context.
> 
> but linux memory manager can't drop any cache under irq/softirq context.
> therefore the allocation failure is relatively typical.
> 
> the allocation failure in packet receive (tg3_alloc_rx_skb) cause
> packet dropping and network peer resend the same packet.
> it decrease network performance a bit. but it doesn't cause any serious problem.
> 
> last problem is, why we should look this false-positive warning repeatedly.
> 
> 
> net-guys, if I say false thing, please fix.

You are right. You repeatedly get that message likely because of jumbo
frames enabled and fragmented ram which does not allow to allocate more
than order-0 pages.

-- 
	Evgeniy Polyakov
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ