From: "Darrick J. Wong" <djwong@kernel.org>
To: "ruansy.fnst@fujitsu.com" <ruansy.fnst@fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"david@fromorbit.com" <david@fromorbit.com>,
"hch@infradead.org" <hch@infradead.org>
Subject: Re: [PATCH] xfs: fail dax mount if reflink is enabled on a partition
Date: Thu, 21 Jul 2022 09:16:08 -0700 [thread overview]
Message-ID: <Ytl7yJJL1fdC006S@magnolia> (raw)
In-Reply-To: <74b0a034-8c77-5136-3fbd-4affb841edcb@fujitsu.com>
On Thu, Jul 21, 2022 at 02:06:10PM +0000, ruansy.fnst@fujitsu.com wrote:
> 在 2022/7/1 8:31, Darrick J. Wong 写道:
> > On Thu, Jun 09, 2022 at 10:34:35PM +0800, Shiyang Ruan wrote:
> >> Failure notification is not supported on partitions. So, when we mount
> >> a reflink enabled xfs on a partition with dax option, let it fail with
> >> -EINVAL code.
> >>
> >> Signed-off-by: Shiyang Ruan <ruansy.fnst@fujitsu.com>
> >
> > Looks good to me, though I think this patch applies to ... wherever all
> > those rmap+reflink+dax patches went. I think that's akpm's tree, right?
> >
> > Ideally this would go in through there to keep the pieces together, but
> > I don't mind tossing this in at the end of the 5.20 merge window if akpm
> > is unwilling.
>
> BTW, since these patches (dax&reflink&rmap + THIS + pmem-unbind) are
> waiting to be merged, is it time to think about "removing the
> experimental tag" again? :)
It's probably time to take up that question again.
Yesterday I tried running generic/470 (aka the MAP_SYNC test) and it
didn't succeed because it sets up dmlogwrites atop dmthinp atop pmem,
and at least one of those dm layers no longer allows fsdax pass-through,
so XFS silently turned mount -o dax into -o dax=never. :(
I'm not sure how to fix that...
--D
>
> --
> Thanks,
> Ruan.
>
> >
> > Reviewed-by: Darrick J. Wong <djwong@kernel.org>
> >
> > --D
> >
> >> ---
> >> fs/xfs/xfs_super.c | 6 ++++--
> >> 1 file changed, 4 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> >> index 8495ef076ffc..a3c221841fa6 100644
> >> --- a/fs/xfs/xfs_super.c
> >> +++ b/fs/xfs/xfs_super.c
> >> @@ -348,8 +348,10 @@ xfs_setup_dax_always(
> >> goto disable_dax;
> >> }
> >>
> >> - if (xfs_has_reflink(mp)) {
> >> - xfs_alert(mp, "DAX and reflink cannot be used together!");
> >> + if (xfs_has_reflink(mp) &&
> >> + bdev_is_partition(mp->m_ddev_targp->bt_bdev)) {
> >> + xfs_alert(mp,
> >> + "DAX and reflink cannot work with multi-partitions!");
> >> return -EINVAL;
> >> }
> >>
> >> --
> >> 2.36.1
> >>
> >>
> >>
next prev parent reply other threads:[~2022-07-21 16:17 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 14:34 [PATCH] xfs: fail dax mount if reflink is enabled on a partition Shiyang Ruan
2022-06-10 5:46 ` Christoph Hellwig
2022-07-01 0:31 ` Darrick J. Wong
2022-07-01 5:14 ` Shiyang Ruan
2022-07-21 12:43 ` ruansy.fnst
2022-07-21 14:06 ` ruansy.fnst
2022-07-21 16:16 ` Darrick J. Wong [this message]
2022-07-29 3:55 ` ruansy.fnst
2022-07-29 4:54 ` Darrick J. Wong
2022-08-03 6:47 ` ruansy.fnst
2022-08-04 0:51 ` Darrick J. Wong
2022-08-04 1:36 ` Shiyang Ruan
2022-09-08 13:46 ` Shiyang Ruan
2022-09-09 13:01 ` Brian Foster
2022-09-14 6:44 ` Yang, Xiao/杨 晓
2022-09-14 9:38 ` Yang, Xiao/杨 晓
2022-09-14 12:34 ` Brian Foster
2022-09-14 16:28 ` Darrick J. Wong
2022-09-15 10:14 ` Yang, Xiao/杨 晓
2022-09-16 2:04 ` Yang, Xiao/杨 晓
2022-09-20 2:38 ` Yang, Xiao/杨 晓
2022-09-30 0:56 ` [dm-devel] " Gotou, Yasunori/五島 康文
2022-09-30 0:56 ` Gotou, Yasunori/五島 康文
2022-10-04 0:12 ` [dm-devel] " Darrick J. Wong
2022-10-04 0:12 ` Darrick J. Wong
2022-10-04 4:12 ` [dm-devel] " Gotou, Yasunori/五島 康文
2022-10-04 4:12 ` Gotou, Yasunori/五島 康文
2022-10-04 18:26 ` [dm-devel] " Darrick J. Wong
2022-10-04 18:26 ` Darrick J. Wong
2022-10-20 14:17 ` [dm-devel] " Yang, Xiao/杨 晓
2022-10-20 14:17 ` Yang, Xiao/杨 晓
2022-10-22 2:11 ` [dm-devel] " Darrick J. Wong
2022-10-22 2:11 ` Darrick J. Wong
[not found] ` <09f522cd-e846-12ee-d662-14f34a2977c4@fujitsu.com>
2022-10-23 7:04 ` [dm-devel] " yangx.jy
2022-10-23 7:04 ` yangx.jy
2022-10-23 22:00 ` [dm-devel] " Dave Chinner
2022-10-23 22:00 ` Dave Chinner
2022-10-24 3:17 ` [dm-devel] " ruansy.fnst
2022-10-24 3:17 ` ruansy.fnst
2022-10-24 4:05 ` [dm-devel] " Darrick J. Wong
2022-10-24 4:05 ` Darrick J. Wong
2022-10-24 5:31 ` [dm-devel] " Dave Chinner
2022-10-24 5:31 ` Dave Chinner
2022-10-25 14:26 ` [dm-devel] " ruansy.fnst
2022-10-25 14:26 ` ruansy.fnst
2022-10-25 17:56 ` [dm-devel] " Darrick J. Wong
2022-10-25 17:56 ` Darrick J. Wong
2022-10-27 21:08 ` [dm-devel] " Darrick J. Wong
2022-10-27 21:08 ` Darrick J. Wong
2022-10-28 1:37 ` [dm-devel] " Dan Williams
2022-10-28 1:37 ` Dan Williams
2022-10-30 9:31 ` [dm-devel] " Shiyang Ruan
2022-10-30 9:31 ` Shiyang Ruan
2022-11-02 0:45 ` [dm-devel] " Darrick J. Wong
2022-11-02 0:45 ` Darrick J. Wong
2022-11-02 5:17 ` [dm-devel] " ruansy.fnst
2022-11-02 5:17 ` ruansy.fnst
2022-11-03 2:32 ` [dm-devel] " Dave Chinner
2022-11-03 2:32 ` Dave Chinner
2022-10-24 17:12 ` [dm-devel] " Dan Williams
2022-10-24 17:12 ` Dan Williams
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=Ytl7yJJL1fdC006S@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=ruansy.fnst@fujitsu.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.