From: "Darrick J. Wong" <djwong@kernel.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>,
Roman Anufriev <dotdot@yandex-team.ru>,
linux-ext4 <linux-ext4@vger.kernel.org>, Jan Kara <jack@suse.cz>,
Wang Shilong <wangshilong1991@gmail.com>,
Dmitry Monakhov <dmtrmonakhov@yandex-team.ru>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH] ext4: compare inode's i_projid with EXT4_DEF_PROJID rather than check EXT4_INODE_PROJINHERIT flag
Date: Fri, 10 Dec 2021 16:49:29 -0800 [thread overview]
Message-ID: <20211211004929.GB69182@magnolia> (raw)
In-Reply-To: <F12B316D-D695-4B38-ABEA-D5F558696E9A@dilger.ca>
On Thu, Dec 09, 2021 at 03:53:55PM -0700, Andreas Dilger wrote:
> On Dec 7, 2021, at 12:34 PM, Theodore Y. Ts'o <tytso@MIT.EDU> wrote:
> >
> > On Tue, Dec 07, 2021 at 05:05:19PM +0300, Roman Anufriev wrote:
> >>> Commit 7ddf79a10395 ("ext4: only set project inherit bit for directory")
> >>> removes EXT4_INODE_PROJINHERIT flag from regular files. This makes
> >>> ext4_statfs() output incorrect (function does not apply quota limits
> >>> on used/available space, etc) when called on dentry of regular file
> >>> with project quota enabled.
> >
> > Under what circumstance is userspace trying to call statfs on a file
> > descriptor?
>
> Who knows what users do? Calling statfs() on a regular file works fine
> (returns stats for the filesystem), so I don't see why it wouldn't be
> consistent when calling statfs() on a file with projid set?
>
> Darrick, how does XFS handle this case? I think it makes sense to be
> consistent with that implementation, since that was the main reason to
> remove PROJINHERIT from regular files in the first place.
As far as I can tell, the existing ext4 implementation handles this
exactly the same that XFS does. I would leave this alone on the grounds
that we don't really want inconsistent behavior.
--D
>
> > Removing the test for EXT4_INODE_PROJINHERIT will cause
> > incorrect/misleading results being returned in the case where we have
> > a directory where a directory hierarchy is using project id's, but
> > which is *not* using PROJINHERIT.
>
> One alternative would be to check the PROJINHERIT status of the parent
> directory after calling statfs() on the regular file? That should
> keep the semantics for PROJINHERIT the same, but avoid inconsistent
> results if called on a regular file:
>
> #ifdef CONFIG_QUOTA
> - if (ext4_test_inode_flag(dentry->d_inode, EXT4_INODE_PROJINHERIT) &&
> + if (ext4_test_inode_flag(S_ISDIR(dentry->d_inode) ? dentry->d_inode :
> + dentry->d_parent->d_inode, EXT4_INODE_PROJINHERIT) &&
> sb_has_quota_limits_enabled(sb, PRJQUOTA))
> ext4_statfs_project(sb, EXT4_I(dentry->d_inode)->i_projid, buf);
> #endif
>
> Roman, does that work for you?
>
> Cheers, Andreas
>
>
>
>
>
next prev parent reply other threads:[~2021-12-11 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 13:18 [PATCH] ext4: compare inode's i_projid with EXT4_DEF_PROJID rather than check EXT4_INODE_PROJINHERIT flag Roman Anufriev
2021-12-07 14:05 ` Roman Anufriev
2021-12-07 19:34 ` Theodore Y. Ts'o
2021-12-09 22:53 ` Andreas Dilger
2021-12-09 23:30 ` Dave Chinner
2021-12-10 19:53 ` Roman Anufriev
2021-12-10 19:53 ` Roman Anufriev
2021-12-11 0:49 ` Darrick J. Wong [this message]
2021-12-10 19:55 ` Roman Anufriev
2021-12-14 5:06 ` Dave Chinner
2021-12-17 0:17 ` Andreas Dilger
2021-12-17 2:39 ` Dave Chinner
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=20211211004929.GB69182@magnolia \
--to=djwong@kernel.org \
--cc=adilger@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=dotdot@yandex-team.ru \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@MIT.EDU \
--cc=wangshilong1991@gmail.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