netdev - Re: SOCK_MEMALLOC vs loopback

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: <20150304200427.GQ3087@suse.de>
Date:	Wed, 4 Mar 2015 20:04:27 +0000
From:	Mel Gorman <mgorman@...e.de>
To:	Ilya Dryomov <idryomov@...il.com>
Cc:	ceph-devel@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>,
	Sage Weil <sage@...hat.com>,
	Mike Christie <mchristi@...hat.com>, NeilBrown <neilb@...e.de>,
	netdev@...r.kernel.org
Subject: Re: SOCK_MEMALLOC vs loopback

On Wed, Mar 04, 2015 at 09:38:48PM +0300, Ilya Dryomov wrote:
> Hello,
> 
> A short while ago Mike added a patch to libceph to set SOCK_MEMALLOC on
> libceph sockets and PF_MEMALLOC around send/receive paths (commit
> 89baaa570ab0, "libceph: use memalloc flags for net IO").  rbd is much
> like nbd and is succeptible to all the same memory allocation
> deadlocks, so it seemed like a step in the right direction.
> 

The contract for SOCK_MEMALLOC is that it would only be used for temporary
allocations that were necessary for the system to make forward progress. In
the case of swap-over-NFS, it would only be used for transmitting
buffers that were necessary to write data to swap when there were no
other options. If that contract is not met then using it can deadlock the
system. It's the same for PF_MEMALLOC -- activating that is a recipe for
deadlock due to memory exhaustion.

-- 
Mel Gorman
SUSE Labs
--
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