netdev - RE: order:1 failure in ipoib_cm_alloc_rx

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: <063D6719AE5E284EB5DD2968C1650D6D1747EEE3@AcuExch.aculab.com>
Date:	Fri, 22 Aug 2014 09:00:50 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Venkat Venkatsubra' <venkat.x.venkatsubra@...cle.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: order:1 failure in ipoib_cm_alloc_rx_skb

From: Venkat Venkatsubra
> Hello All,
> 
> Many of our customers have hit this order:1 failure in ipoib_cm_alloc_rx_skb causing softlockup:
> ....
>         skb = dev_alloc_skb(IPOIB_CM_HEAD_SIZE + 12);
> ....

Notwithstanding any other problems, that allocation could fail even if the size were
small enough that the entire skb would fit in one page.
So the driver needs changing so that the allocation failure doesn't cause a deadlock.

OTOH if you can't allocate 8k of contiguous address space and memory the system
is unlikely to be working very well at all.

	David

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