From: Jane Chu <jane.chu@oracle.com>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
darrick.wong@oracle.com, david@fromorbit.com, hch@lst.de,
song@kernel.org, rgoldwyn@suse.de, qi.fuli@fujitsu.com,
y-goto@fujitsu.com
Subject: Re: [RFC PATCH v2 0/6] fsdax: introduce fs query to support reflink
Date: Mon, 14 Dec 2020 12:58:32 -0800 [thread overview]
Message-ID: <89ab4ec4-e4f0-7c17-6982-4f55bb40f574@oracle.com> (raw)
In-Reply-To: <20201123004116.2453-1-ruansy.fnst@cn.fujitsu.com>
Hi, Shiyang,
On 11/22/2020 4:41 PM, Shiyang Ruan wrote:
> This patchset is a try to resolve the problem of tracking shared page
> for fsdax.
>
> Change from v1:
> - Intorduce ->block_lost() for block device
> - Support mapped device
> - Add 'not available' warning for realtime device in XFS
> - Rebased to v5.10-rc1
>
> This patchset moves owner tracking from dax_assocaite_entry() to pmem
> device, by introducing an interface ->memory_failure() of struct
> pagemap. The interface is called by memory_failure() in mm, and
> implemented by pmem device. Then pmem device calls its ->block_lost()
> to find the filesystem which the damaged page located in, and call
> ->storage_lost() to track files or metadata assocaited with this page.
> Finally we are able to try to fix the damaged data in filesystem and do
Does that mean clearing poison? if so, would you mind to elaborate
specifically which change does that?
Thanks!
-jane
> other necessary processing, such as killing processes who are using the
> files affected.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Jane Chu <jane.chu@oracle.com>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
darrick.wong@oracle.com, dan.j.williams@intel.com,
david@fromorbit.com, hch@lst.de, song@kernel.org,
rgoldwyn@suse.de, qi.fuli@fujitsu.com, y-goto@fujitsu.com
Subject: Re: [RFC PATCH v2 0/6] fsdax: introduce fs query to support reflink
Date: Mon, 14 Dec 2020 12:58:32 -0800 [thread overview]
Message-ID: <89ab4ec4-e4f0-7c17-6982-4f55bb40f574@oracle.com> (raw)
In-Reply-To: <20201123004116.2453-1-ruansy.fnst@cn.fujitsu.com>
Hi, Shiyang,
On 11/22/2020 4:41 PM, Shiyang Ruan wrote:
> This patchset is a try to resolve the problem of tracking shared page
> for fsdax.
>
> Change from v1:
> - Intorduce ->block_lost() for block device
> - Support mapped device
> - Add 'not available' warning for realtime device in XFS
> - Rebased to v5.10-rc1
>
> This patchset moves owner tracking from dax_assocaite_entry() to pmem
> device, by introducing an interface ->memory_failure() of struct
> pagemap. The interface is called by memory_failure() in mm, and
> implemented by pmem device. Then pmem device calls its ->block_lost()
> to find the filesystem which the damaged page located in, and call
> ->storage_lost() to track files or metadata assocaited with this page.
> Finally we are able to try to fix the damaged data in filesystem and do
Does that mean clearing poison? if so, would you mind to elaborate
specifically which change does that?
Thanks!
-jane
> other necessary processing, such as killing processes who are using the
> files affected.
next prev parent reply other threads:[~2020-12-14 21:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 0:41 [RFC PATCH v2 0/6] fsdax: introduce fs query to support reflink Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-23 0:41 ` [RFC PATCH v2 1/6] fs: introduce ->storage_lost() for memory-failure Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-23 0:41 ` [RFC PATCH v2 2/6] blk: introduce ->block_lost() to handle memory-failure Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-23 0:41 ` [RFC PATCH v2 3/6] md: implement ->block_lost() for memory-failure Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-23 0:41 ` [RFC PATCH v2 4/6] pagemap: introduce ->memory_failure() Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-23 0:41 ` [RFC PATCH v2 5/6] mm, fsdax: refactor dax handler in memory-failure Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-23 0:41 ` [RFC PATCH v2 6/6] fsdax: remove useless (dis)associate functions Shiyang Ruan
2020-11-23 0:41 ` Shiyang Ruan
2020-11-29 22:47 ` [RFC PATCH v2 0/6] fsdax: introduce fs query to support reflink Dave Chinner
2020-11-29 22:47 ` Dave Chinner
2020-12-02 7:12 ` Ruan Shiyang
2020-12-02 7:12 ` Ruan Shiyang
2020-12-06 22:55 ` Dave Chinner
2020-12-06 22:55 ` Dave Chinner
2020-12-14 20:58 ` Jane Chu [this message]
2020-12-14 20:58 ` Jane Chu
2020-12-15 11:58 ` Ruan Shiyang
2020-12-15 11:58 ` Ruan Shiyang
2020-12-15 19:05 ` Jane Chu
2020-12-15 19:05 ` Jane Chu
2020-12-15 23:10 ` Dave Chinner
2020-12-15 23:10 ` Dave Chinner
2020-12-16 2:46 ` Darrick J. Wong
2020-12-16 2:46 ` 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=89ab4ec4-e4f0-7c17-6982-4f55bb40f574@oracle.com \
--to=jane.chu@oracle.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=qi.fuli@fujitsu.com \
--cc=rgoldwyn@suse.de \
--cc=ruansy.fnst@cn.fujitsu.com \
--cc=song@kernel.org \
--cc=y-goto@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.