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: <E794C3E7-985B-4A6F-B763-C7BBB14061FE@dilger.ca>
Date:	Tue, 21 Jun 2011 13:24:57 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: can we simplify the quota matrix in ext4?

On 2011-06-21, at 12:45 PM, Eric Sandeen wrote:
> I was looking at 
> 
> 62d2b5f2dcd3707b070efb16bbfdf6947c38c194 ext4: Always journal quota file modifications
> 
> and was thinking - if we always journal, why do we still have all the mount options etc for journaled quota?
> 
> I guess without -o usrjquota=foo we don't journal right from mount time, and there are a few other paths that get skipped, but those seem like details...
> 
> It seems that ideally - and perhaps this is hindsight - ext4 should have defaulted to journaled, QFMT_VFS_V1 quotas only... is there any reason not to?

This would be the ideal situation for Lustre as well.  The remaining issue,
AFAIK, is that e2fsck needs to do quota accounting internally so that there
is never a need to run a quotacheck on the filesystem.

Since e2fsck is already traversing all of the inodes, this is no extra effort
to keep a handful of bytes (inode count, blocks count) for each user.  I
believe there was someone at Google working on this?  Haven't seen any output
so far, however.

> I'm still not very well versed in vfs quota, but does it seem possible to
> move in this direction?  It seems odd that we should still be supporting
> unjournaled, vfsold-format quotas in ext4 these days.  What's the point?

I totally agree.

> If it seems possible to move in this direction within the exiting quota
> framework I'd be interested in trying to get it done.
> 
> Thanks,
> -Eric
> --
> 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


Cheers, Andreas





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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ