From: Carlos Maiolino <cmaiolino@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] quota: allow users to truncate group and project quota files
Date: Thu, 29 Jul 2021 13:23:00 +0200 [thread overview]
Message-ID: <20210729112300.libgmkmog5d6knou@omega.lan> (raw)
In-Reply-To: <20210728211535.GI3601443@magnolia>
On Wed, Jul 28, 2021 at 02:15:35PM -0700, Darrick J. Wong wrote:
> Eric asked me to resend all the pending patches for 5.13, so I might as
> well NAK this and tell everyone to watch for the imminent patchbomb.
oh, I'll read the whole thread before reviewing next time, but well, feel free
to carry my reviewed-by.
Cheers
>
> --D
>
> On Wed, Jul 28, 2021 at 01:02:08PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > In commit 79ac1ae4, I /think/ xfsprogs gained the ability to deal with
> > project or group quotas. For some reason, the quota remove command was
> > structured so that if the user passes both -g and -p, it will only ask
> > the kernel truncate the group quota file. This is a strange behavior
> > since -ug results in truncation requests for both user and group quota
> > files, and the kernel is smart enough to return 0 if asked to truncate a
> > quota file that doesn't exist.
> >
> > In other words, this is a seemingly arbitrary limitation of the command.
> > It's an unexpected behavior since we don't do any sort of parameter
> > validation to warn users when -p is silently ignored. Modern V5
> > filesystems support both group and project quotas, so it's all the more
> > surprising that you can't do group and project all at once. Remove this
> > pointless restriction.
> >
> > Found while triaging xfs/007 regressions.
> >
> > Fixes: 79ac1ae4 ("Fix xfs_quota disable, enable, off and remove commands Merge of master-melb:xfs-cmds:29395a by kenmcd.")
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > quota/state.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/quota/state.c b/quota/state.c
> > index 3ffb2c88..43fb700f 100644
> > --- a/quota/state.c
> > +++ b/quota/state.c
> > @@ -463,7 +463,8 @@ remove_extents(
> > if (type & XFS_GROUP_QUOTA) {
> > if (remove_qtype_extents(dir, XFS_GROUP_QUOTA) < 0)
> > return;
> > - } else if (type & XFS_PROJ_QUOTA) {
> > + }
> > + if (type & XFS_PROJ_QUOTA) {
> > if (remove_qtype_extents(dir, XFS_PROJ_QUOTA) < 0)
> > return;
> > }
>
--
Carlos
next prev parent reply other threads:[~2021-07-29 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 20:02 [PATCH] quota: allow users to truncate group and project quota files Darrick J. Wong
2021-07-28 21:15 ` Darrick J. Wong
2021-07-29 11:23 ` Carlos Maiolino [this message]
2021-07-29 11:21 ` Carlos Maiolino
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=20210729112300.libgmkmog5d6knou@omega.lan \
--to=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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