linux-kernel - Re: [RFC PATCH] tmpfs: support user quotas

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: <20111107135823.3a7cdc53@lxorguk.ukuu.org.uk>
Date:	Mon, 7 Nov 2011 13:58:23 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Davidlohr Bueso <dave@....org>
Cc:	Lennart Poettering <mzxreary@...inter.de>,
	Christoph Hellwig <hch@...radead.org>,
	Hugh Dickins <hughd@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
	Kay Sievers <kay.sievers@...y.org>
Subject: Re: [RFC PATCH] tmpfs: support user quotas

> Right, rlimit approach guarantees a simple way of dealing with users
> across all tmpfs instances.

Which is almost certainly not what you want to happen. Think about direct
rendering.

For simple stuff tmpfs already supports size/nr_blocks/nr_inodes mount
options so you can mount private resource constrained tmpfs objects
already without kernel changes. No rlimit hacks needed - and rlimit is
the wrong API anyway.

Alan

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