From: Chandan Babu R <chandanbabu@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Shiyang Ruan <ruansy.fnst@fujitsu.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev,
dan.j.williams@intel.com
Subject: Re: [PATCH] xfs: drop experimental warning for FSDAX
Date: Fri, 29 Sep 2023 19:47:07 +0530 [thread overview]
Message-ID: <87msx5f4a8.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20230928092052.9775e59262c102dc382513ef@linux-foundation.org>
On Thu, Sep 28, 2023 at 09:20:52 AM -0700, Andrew Morton wrote:
> On Thu, 28 Sep 2023 16:44:00 +0800 Shiyang Ruan <ruansy.fnst@fujitsu.com> wrote:
>
>> But please pick the following patch[1] as well, which fixes failures of
>> xfs55[0-2] cases.
>>
>> [1]
>> https://lore.kernel.org/linux-xfs/20230913102942.601271-1-ruansy.fnst@fujitsu.com
>
> I guess I can take that xfs patch, as it fixes a DAX patch. I hope the xfs team
> are watching.
>
> But
>
> a) I'm not subscribed to linux-xfs and
>
> b) the changelog fails to describe the userspace-visible effects of
> the bug, so I (and others) are unable to determine which kernel
> versions should be patched.
>
> Please update that changelog and resend?
I will apply "xfs: correct calculation for agend and blockcount" patch to
xfs-linux Git tree and include it for the next v6.6 pull request to Linus.
At the outset, It looks like I can pick "mm, pmem, xfs: Introduce
MF_MEM_PRE_REMOVE for unbind"
(i.e. https://lore.kernel.org/linux-xfs/20230928103227.250550-1-ruansy.fnst@fujitsu.com/T/#u)
patch for v6.7 as well. But that will require your Ack. Please let me know
your opinion.
Also, I will pick "xfs: drop experimental warning for FSDAX" patch for v6.7.
--
Chandan
next prev parent reply other threads:[~2023-09-29 14:22 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
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 [this message]
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=87msx5f4a8.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=akpm@linux-foundation.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 \
--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.