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: <76987E49-8B2B-4272-AABE-7CCE2905709D@gmx.com>
Date:   Fri, 27 Apr 2018 09:22:05 +0800
From:   "cgxu519@....com" <cgxu519@....com>
To:     "Theodore Y. Ts'o" <tytso@....edu>
Cc:     "cgxu519@....com" <cgxu519@....com>,
        Liu Bo <obuil.liubo@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: generic quota vs xfs quota


> 在 2018年4月27日,上午1:22,Theodore Y. Ts'o <tytso@....edu> 写道:
> 
> On Thu, Apr 26, 2018 at 04:16:08PM +0800, Liu Bo wrote:
>> 
>> and ext4 ->statfs() only displays dqb_curspace while xfs ->statfs()
>> displays both,
> 
> I'm not sure what you are asking.  statfs(2) has nothing to do with
> quota support.

I think statfs will do some adjustment if target dentry is in project quota
directory. So I just guess the question is why don’t we count dqb_rsvspace
as used in ext4_statfs_project().

Thanks,
Chengguang.




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ