From: "Darrick J. Wong" <djwong@kernel.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Chandan Babu R <chandanbabu@kernel.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: conditionally allow FS_XFLAG_REALTIME changes if S_DAX is set
Date: Sat, 10 Aug 2024 09:41:54 -0700 [thread overview]
Message-ID: <20240810164154.GF6082@frogsfrogsfrogs> (raw)
In-Reply-To: <CAFqt6zbwgNsD5Cti3bQ8Fu=8mDSedb7B9iY1zDq10qMcuJmorw@mail.gmail.com>
On Sat, Aug 10, 2024 at 08:18:16PM +0530, Souptick Joarder wrote:
> On Tue, Aug 6, 2024 at 12:16 AM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > If a file has the S_DAX flag (aka fsdax access mode) set, we cannot
> > allow users to change the realtime flag unless the datadev and rtdev
> > both support fsdax access modes. Even if there are no extents allocated
> > to the file, the setattr thread could be racing with another thread
> > that has already started down the write code paths.
> >
> > Fixes: ba23cba9b3bdc ("fs: allow per-device dax status checking for filesystems")
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > fs/xfs/xfs_ioctl.c | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> > index 4e933db75b12..6b13666d4e96 100644
> > --- a/fs/xfs/xfs_ioctl.c
> > +++ b/fs/xfs/xfs_ioctl.c
> > @@ -483,6 +483,17 @@ xfs_ioctl_setattr_xflags(
> > /* Can't change realtime flag if any extents are allocated. */
> > if (ip->i_df.if_nextents || ip->i_delayed_blks)
> > return -EINVAL;
> > +
> > + /*
> > + * If S_DAX is enabled on this file, we can only switch the
> > + * device if both support fsdax. We can't update S_DAX because
> > + * there might be other threads walking down the access paths.
> > + */
> > + if (IS_DAX(VFS_I(ip)) &&
> > + (mp->m_ddev_targp->bt_daxdev == NULL ||
> > + (mp->m_rtdev_targp &&
> > + mp->m_rtdev_targp->bt_daxdev == NULL)))
> > + return -EINVAL;
> Any chance of mp->m_ddev_targp == NULL ?
No, m_ddev_targp is the device you give to mount. e.g. if you do
# mount /dev/sda /mnt
then m_ddev_targp is the block_device /dev/sda.
--D
> > }
> >
> > if (rtflag) {
> >
prev parent reply other threads:[~2024-08-10 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 18:46 [PATCH] xfs: conditionally allow FS_XFLAG_REALTIME changes if S_DAX is set Darrick J. Wong
2024-08-06 13:07 ` Christoph Hellwig
2024-08-10 14:48 ` Souptick Joarder
2024-08-10 16:41 ` 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=20240810164154.GF6082@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=jrdr.linux@gmail.com \
--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 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.