Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/6] mkfs: PQUOTA shouldn't conflict with GQNOENFORCE
Date: Tue, 30 Jun 2026 09:27:12 -0700	[thread overview]
Message-ID: <20260630162712.GC6526@frogsfrogsfrogs> (raw)
In-Reply-To: <20260630054122.GE21007@lst.de>

On Tue, Jun 30, 2026 at 07:41:22AM +0200, Christoph Hellwig wrote:
> On Mon, Jun 29, 2026 at 06:03:57PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > Codex points out that project quota isn't incompatible with
> > non-enforcing group quota in the kernel, so those shouldn't be
> > incompatible in mkfs either.
> 
> For file systems with XFS_SB_VERSION_QUOTABIT there is no incompatibility
> at all, enforcing or not.
> 
> > 
> > Cc: <linux-xfs@vger.kernel.org> # v6.13.0
> > Fixes: 525f826429a868 ("mkfs: add quota flags when setting up filesystem")
> > Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> > ---
> >  mkfs/xfs_mkfs.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > 
> > diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> > index 3da11c664255b1..a4864c37a8821b 100644
> > --- a/mkfs/xfs_mkfs.c
> > +++ b/mkfs/xfs_mkfs.c
> > @@ -976,7 +976,7 @@ static struct opt_params mopts = {
> >  		  .defaultval = 1,
> >  		},
> >  		{ .index = M_PQUOTA,
> > -		  .conflicts = { { &mopts, M_GQNOENFORCE },
> > +		  .conflicts = { { &mopts, M_PQNOENFORCE },
> >  				 { NULL, LAST_CONFLICT } },
> 
> But I think this is just fat-fingering anyway, as it wants to
> conflict the pquota vs pquota no enforce options.  So I think
> the commit log could use some rewording for clarify, but the
> change looks good.

Ok, how about:

"Codex points out that project quota isn't incompatible with
non-enforcing group quota in the kernel, so those shouldn't be
incompatible in mkfs either.

"Furthermore, project and group quotas are never incompatible on
QUOTABIT and V5 filesystems, so this is clearly a fat-finger error."

--D

  reply	other threads:[~2026-06-30 16:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  1:02 [PATCHSET 2/4] mkfs.xfs: codex-inspired bug fixes Darrick J. Wong
2026-06-30  1:02 ` [PATCH 1/6] mkfs: don't redefine DIRT for protofiles Darrick J. Wong
2026-06-30  5:31   ` Christoph Hellwig
2026-06-30  1:03 ` [PATCH 2/6] mkfs: fix PATH_MAX check Darrick J. Wong
2026-06-30  5:31   ` Christoph Hellwig
2026-06-30  1:03 ` [PATCH 3/6] mkfs: fix symlink target length check in create_nondir_inode Darrick J. Wong
2026-06-30  5:34   ` Christoph Hellwig
2026-06-30  1:03 ` [PATCH 4/6] mkfs: fix hardlink detection in directory import code Darrick J. Wong
2026-06-30  5:38   ` Christoph Hellwig
2026-06-30 16:28     ` Darrick J. Wong
2026-06-30  1:03 ` [PATCH 5/6] mkfs: PQUOTA shouldn't conflict with GQNOENFORCE Darrick J. Wong
2026-06-30  5:41   ` Christoph Hellwig
2026-06-30 16:27     ` Darrick J. Wong [this message]
2026-06-30  1:04 ` [PATCH 6/6] xfs_protofile: make nondirectory arguments actually work Darrick J. Wong
2026-06-30  5:45   ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260630162712.GC6526@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox