linux-kernel - Re: [RFC] shmem: Add eventfd notification on utlilization level

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]

Date:	Tue, 10 Mar 2015 15:22:37 +0100
From:	Jan Kara <jack@...e.cz>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Kyungmin Park <kmpark@...radead.org>,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Hugh Dickins <hughd@...gle.com>, linux-mm <linux-mm@...ck.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Linux Filesystem Mailing List <linux-fsdevel@...r.kernel.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Jan Kara <jack@...e.cz>
Subject: Re: [RFC] shmem: Add eventfd notification on utlilization level

On Tue 10-03-15 06:03:23, Christoph Hellwig wrote:
> On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
> > Any updates?
> 
> Please just add disk quota support to tmpfs so thast the standard quota
> netlink notifications can be used.
  If I understand the problem at hand, they are really interested in
notification when running out of free space. Using quota for that doesn't
seem ideal since that tracks used space per user, not free space on fs as a
whole.

But if I remember right there were discussions about ENOSPC notification
from filesystem for thin provisioning usecases. It would be good to make
this consistent with those but I'm not sure if it went anywhere.

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/