linux-ext4 - Re: [PATCH 1/3] [RFC] vfs: add generic reserved space management interface

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: <877hswql6s.fsf@openvz.org>
Date:	Wed, 09 Dec 2009 17:24:59 +0300
From:	Dmitry Monakhov <dmonakhov@...nvz.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	linux-ext4@...r.kernel.org, aneesh.kumar@...ux.vnet.ibm.com,
	jack@...e.cz, cmm@...ibm.com, linux-fsdevel@...r.kernel.org,
	Al Viro <viro@...IV.linux.org.uk>
Subject: Re: [PATCH 1/3] [RFC] vfs: add generic reserved space management
 interface

Christoph Hellwig <hch@...radead.org> writes:

> On Wed, Dec 09, 2009 at 05:11:24AM +0300, Dmitry Monakhov wrote:
>> Add new field "i_rsv_blocks" to generic inode. This value is
>> managed similar to i_blocks, i_bytes fileds (protected by i_lock).
>> This generic interface will be used by generic quota code similar
>> to i_blocks.
>
> Please don't bloat the VFS inode for this information.
But almost all recent file systems using extends and delayed allocation.
This means that we have to think about generic space reservation
management quota interface. Otherwise each fs will invent it's own 
callbacks. What do you think about hide it with CONFIG_QUOTA option?
May be introduce new CONFIG_QUOTA_RESERVATION?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html