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: <20120120190545.GA18688@quack.suse.cz>
Date:	Fri, 20 Jan 2012 20:05:45 +0100
From:	Jan Kara <jack@...e.cz>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Jan Kara <jack@...e.cz>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PULL REQUEST] Ext3 & ext2 fix, quota improvement

On Fri 20-01-12 11:44:00, Christoph Hellwig wrote:
> On Fri, Jan 20, 2012 at 05:39:10PM +0100, Jan Kara wrote:
> >       quota: Pass information that quota is stored in system file to userspace
> 
> Was that patch posted somewhere?  How does it apply to e.g. xfs, gfs2
> and ocfs2 that have always stored quota data internally?
  It was posted back in November (but I forgot it in a topic branch thus
I'm merging it only now), looking at the post I sent it to linux-ext4 only
which was probably a bit unlucky.

Regarding other filesystems - ocfs2 and gfs2 set DQUOT_QUOTA_SYS_FILE flag
so this will now be passed properly to userspace to inform userspace
programs (but quota-tools anyway use the flag only for ext4, for other
filesystems they know quota is handled internally just by looking at
filesystem type). XFS doesn't set the flag. It does not matter in practice
as XFS doesn't use VFS quota code which cares about the flag
(dquot_quota_sync, dquot_disable) and userspace tools know XFS handles
quota internally. But maybe we could make XFS set it just for consistency?

								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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ