From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Achilles Gaikwad <agaikwad@redhat.com>
Cc: linux-xfs@vger.kernel.org, sandeen@sandeen.net, sgardner@redhat.com
Subject: Re: [PATCH v2] xfs_quota: fix false error reporting of project inheritance flag is not set
Date: Sun, 6 Jan 2019 10:10:18 -0800 [thread overview]
Message-ID: <20190106181018.GI12689@magnolia> (raw)
In-Reply-To: <20190106102745.GA7347@nevermore.lan>
On Sun, Jan 06, 2019 at 03:58:07PM +0530, Achilles Gaikwad wrote:
> After kernel commit:
>
> 9336e3a7 "xfs: project id inheritance is a directory only flag"
>
> xfs stopped setting the project inheritance flag on regular files, but
> userspace quota code still checks for it and will now issue the error:
>
> "project inheritance flag is not set"
>
> for every regular file during quotacheck. Fix this by only checking
> for the flag on directories.
>
> Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1663502
> Reported-by: Steven Gardner <sgardner@redhat.com>
> Signed-off-by: Achilles Gaikwad <agaikwad@redhat.com>
Looks ok to me...
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> quota/project.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/quota/project.c b/quota/project.c
> index e4e7a012..11f3be04 100644
> --- a/quota/project.c
> +++ b/quota/project.c
> @@ -126,7 +126,7 @@ check_project(
> printf(_("%s - project identifier is not set"
> " (inode=%u, tree=%u)\n"),
> path, fsx.fsx_projid, (unsigned int)prid);
> - if (!(fsx.fsx_xflags & FS_XFLAG_PROJINHERIT))
> + if (!(fsx.fsx_xflags & FS_XFLAG_PROJINHERIT) && S_ISDIR(stat->st_mode))
> printf(_("%s - project inheritance flag is not set\n"),
> path);
> }
> --
> 2.20.1
>
prev parent reply other threads:[~2019-01-06 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 10:28 [PATCH v2] xfs_quota: fix false error reporting of project inheritance flag is not set Achilles Gaikwad
2019-01-06 18:10 ` Darrick J. Wong [this message]
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=20190106181018.GI12689@magnolia \
--to=darrick.wong@oracle.com \
--cc=agaikwad@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=sgardner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.