From: Andrew Morton <akpm@linux-foundation.org>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Cc: <linux-fsdevel@vger.kernel.org>, <nvdimm@lists.linux.dev>,
<linux-xfs@vger.kernel.org>, <dan.j.williams@intel.com>,
<willy@infradead.org>, <jack@suse.cz>, <djwong@kernel.org>
Subject: Re: [PATCH] fsdax: force clear dirty mark if CoW
Date: Fri, 24 Mar 2023 12:42:42 -0700 [thread overview]
Message-ID: <20230324124242.c881cf384ab8a37716850413@linux-foundation.org> (raw)
In-Reply-To: <1679653680-2-1-git-send-email-ruansy.fnst@fujitsu.com>
On Fri, 24 Mar 2023 10:28:00 +0000 Shiyang Ruan <ruansy.fnst@fujitsu.com> wrote:
> XFS allows CoW on non-shared extents to combat fragmentation[1]. The
> old non-shared extent could be mwrited before, its dax entry is marked
> dirty. To be able to delete this entry, clear its dirty mark before
> invalidate_inode_pages2_range().
What are the user-visible runtime effects of this flaw?
Are we able to identify a Fixes: target for this? Perhaps
f80e1668888f3 ("fsdax: invalidate pages when CoW")?
next prev parent reply other threads:[~2023-03-24 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:28 [PATCH] fsdax: force clear dirty mark if CoW Shiyang Ruan
2023-03-24 19:42 ` Andrew Morton [this message]
2023-03-27 3:19 ` Shiyang Ruan
2023-03-27 20:24 ` Andrew Morton
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=20230324124242.c881cf384ab8a37716850413@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=ruansy.fnst@fujitsu.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).