linux-kernel - Re: [PATCH v4] pipe: limit the per-user amount of pages allocated in pipes

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: <20160120001144.GW17997@ZenIV.linux.org.uk>
Date:	Wed, 20 Jan 2016 00:11:44 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Willy Tarreau <w@....eu>,
	Марк Коренберг 
	<socketpair@...il.com>,
	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	lkp@...el.com
Subject: Re: [PATCH v4] pipe: limit the per-user amount of pages allocated in
 pipes

On Tue, Jan 19, 2016 at 04:07:15PM -0800, Linus Torvalds wrote:
> On Mon, Jan 18, 2016 at 7:36 AM, Willy Tarreau <w@....eu> wrote:
> > On no-so-small systems, it is possible for a single process to cause an
> > OOM condition by filling large pipes with data that are never read. A
> > typical process filling 4000 pipes with 1 MB of data will use 4 GB of
> > memory. On small systems it may be tricky to set the pipe max size to
> > prevent this from happening.
> >
> > This patch makes it possible to enforce a per-user soft limit above
> > which new pipes will be limited to a single page, effectively limiting
> > them to 4 kB each, as well as a hard limit above which no new pipes may
> > be created for this user. T
> 
> Al, should I take this directly, or is it coming through your tree?

I'll pick it.