NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Shiyang Ruan <ruansy.fnst@fujitsu.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev
Subject: Re: [PATCH] xfs: drop experimental warning for FSDAX
Date: Thu, 5 Oct 2023 16:53:12 +0800	[thread overview]
Message-ID: <ce9ef1dc-d62b-466d-882f-d7bf4350582d@fujitsu.com> (raw)
In-Reply-To: <20231005000809.GN21298@frogsfrogsfrogs>



在 2023/10/5 8:08, Darrick J. Wong 写道:
>>>
>>> Sorry, I sent the list below to Chandan, didn't cc the maillist
>>> because it's just a rough list rather than a PR:
>>>
>>>
>>> 1. subject: [v3]  xfs: correct calculation for agend and blockcount
>>>     url:
>>>     https://lore.kernel.org/linux-xfs/20230913102942.601271-1-ruansy.fnst@fujitsu.com/
>>>     note:    This one is a fix patch for commit: 5cf32f63b0f4 ("xfs:
>>>     fix the calculation for "end" and "length"").
>>>              It can solve the fail of xfs/55[0-2]: the programs
>>>              accessing the DAX file may not be notified as expected,
>>>             because the length always 1 block less than actual.  Then
>>>            this patch fixes this.
>>>
>>>
>>> 2. subject: [v15] mm, pmem, xfs: Introduce MF_MEM_PRE_REMOVE for unbind
>>>     url:
>>>     https://lore.kernel.org/linux-xfs/20230928103227.250550-1-ruansy.fnst@fujitsu.com/T/#u
>>>     note:    This is a feature patch.  It handles the pre-remove event
>>>     of DAX device, by notifying kernel/user space before actually
>>>    removing.
>>>              It has been picked by Andrew in his
>>>              mm-hotfixes-unstable. I am not sure whether you or he will
>>>             merge this one.
>>>
>>>
>>> 3. subject: [v1]  xfs: drop experimental warning for FSDAX
>>>     url:
>>>     https://lore.kernel.org/linux-xfs/20230915063854.1784918-1-ruansy.fnst@fujitsu.com/
>>>     note:    With the patches mentioned above, I did a lot of tests,
>>>     including xfstests and blackbox tests, the FSDAX function looks
>>>    good now.  So I think the experimental warning could be dropped.
>>
>> Darrick/Dave, Could you please review the above patch and let us know if you
>> have any objections?
> 
> The first two patches are ok.  The third one ... well I was about to say
> ok but then this happened with generic/269 on a 6.6-rc4 kernel and those
> two patches applied:

Hi Darrick,

Thanks for testing.  I just tested this case (generic/269) on v6.6-rc4 
with my 3 patches again, but it didn't fail.  Such WARNING message 
didn't show in dmesg too.

My local.config is shown as below:
[nodax_reflink]
export FSTYP=xfs
export TEST_DEV=/dev/pmem0
export TEST_DIR=/mnt/test
export SCRATCH_DEV=/dev/pmem1
export SCRATCH_MNT=/mnt/scratch
export MKFS_OPTIONS="-m reflink=1,rmapbt=1"

[dax_reflink]
export FSTYP=xfs
export TEST_DEV=/dev/pmem0
export TEST_DIR=/mnt/test
export SCRATCH_DEV=/dev/pmem1
export SCRATCH_MNT=/mnt/scratch
export MKFS_OPTIONS="-m reflink=1,rmapbt=1"
export MOUNT_OPTIONS="-o dax"
export TEST_FS_MOUNT_OPTS="-o dax"

And tools version are:
  - xfstests (v2023.09.03)
  - xfsprogs (v6.4.0)


Could you show me more info (such as kernel config, local.config) ?  So 
that I can find out what exactly is going wrong.


--
Thanks,
Ruan.

  reply	other threads:[~2023-10-05  8:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  6:38 [PATCH] xfs: drop experimental warning for FSDAX Shiyang Ruan
2023-09-21  8:33 ` Shiyang Ruan
2023-09-26 14:55   ` Darrick J. Wong
2023-09-27  1:18     ` Dave Chinner
2023-09-27  1:46       ` Darrick J. Wong
2023-09-27  3:38         ` Chandan Babu R
2023-09-27  5:17           ` Shiyang Ruan
2023-09-27  6:38             ` Shiyang Ruan
2023-09-27  7:31               ` Chandan Babu R
2023-09-27 15:30                 ` Andrew Morton
2023-09-28  8:44                   ` Shiyang Ruan
2023-09-28 16:20                     ` Andrew Morton
2023-09-28 17:13                       ` Darrick J. Wong
2023-09-29 11:56                         ` Shiyang Ruan
2023-09-29 18:34                           ` Dan Williams
2023-10-02 12:15                             ` Shiyang Ruan
2023-10-02 12:39                               ` Chandan Babu R
2023-10-05  0:08                                 ` Darrick J. Wong
2023-10-05  8:53                                   ` Shiyang Ruan [this message]
2023-10-05 16:05                                     ` Darrick J. Wong
2023-10-09 14:14                                       ` Shiyang Ruan
2023-10-09 16:47                                         ` Darrick J. Wong
2023-10-10  3:53                                           ` Shiyang Ruan
2023-10-10 17:51                                             ` Darrick J. Wong
2023-09-29 14:17                       ` Chandan Babu R
2023-09-29 14:35                         ` Eric Sandeen
2023-09-29 15:27                           ` Chandan Babu R
2023-09-29 18:28                           ` Dan Williams
2023-10-04 17:50                             ` Darrick J. Wong
2024-01-11 16:59 ` Bill O'Donnell
2024-01-12  2:21   ` Darrick J. Wong
2024-02-23  7:28     ` Shiyang Ruan
2024-02-26 16:58       ` Dan Williams
2024-02-27  9:50         ` Shiyang Ruan
2024-02-23 17:32 ` Darrick J. Wong

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=ce9ef1dc-d62b-466d-882f-d7bf4350582d@fujitsu.com \
    --to=ruansy.fnst@fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=chandanbabu@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    /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