linux-kernel - Re: kernel 3.1.1 message: <IRQ> warn_alloc

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]

Message-ID: <20111209095014.14a647cd@nehalam.linuxnetplumber.net>
Date:	Fri, 9 Dec 2011 09:50:14 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	starlight@...nacle.cx, Sony Chacko <sony.chacko@...gic.com>,
	Rajesh Borundia <rajesh.borundia@...gic.com>
Cc:	linux-kernel@...r.kernel.org, netdev <netdev@...r.kernel.org>
Subject: Re: kernel 3.1.1 message:  <IRQ> warn_alloc_failed

On Thu, 08 Dec 2011 21:10:02 -0500
starlight@...nacle.cx wrote:

> Hello.
> 
> FYI saw several of these when running
> multiple 'rcp' commands copying multi-gigabyte
> files to/from system.
> 
> 'rcp' target files were all on an encrypted
> mirrored USB3-attached pair of 3TB hard
> drives.
> 
> One outgoing 'rcp' was to a system with
> a much slower disk (due to a USB2 attachment)
> and that transfer was putting back-pressure
> on the connection.
> 
> Kernel is running on a CentOS 6.0
> distribution.
> 
> Not subscribing to the lists, so please
> CC me with any queries.  Please note that
> email originating from most non-US MTAs
> will bounce, but I will check the list
> archives if I see any.
> 
> Can't spend a lot of time on this but am
> willing to answer a few questions.  Hopefully
> the call stack will tell the story well
> enough.

You are seeing memory allocation failures because device
is allocating a 16K (order 2) size socket buffer. You are using
netxen device, and it looks like the problem.

>From reading the netxen driver source. The LRO buffers in this device
are very large (8060+skb overhead).
Until the driver is fixed to use fragmented page size memory,
I recommend turning off LRO.
--
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/