Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device

[PATCH 00/10] fsdax: introduce fs query to support reflink · Shiyang Ruan <hidden> · 2020-12-30
[PATCH 01/10] pagemap: Introduce ->memory_failure() · Shiyang Ruan <hidden> · 2020-12-30
[PATCH 03/10] fs: Introduce ->corrupted_range() for superblock · Shiyang Ruan <hidden> · 2020-12-30
Re: [PATCH 03/10] fs: Introduce ->corrupted_range() for superblock · Christoph Hellwig <hch@lst.de> · 2021-01-08
[PATCH 02/10] blk: Introduce ->corrupted_range() for block device · Shiyang Ruan <hidden> · 2020-12-30
Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device · Christoph Hellwig <hch@lst.de> · 2021-01-08
Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device · Darrick J. Wong <hidden> · 2021-01-08
[PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · Shiyang Ruan <hidden> · 2020-12-30
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · Jan Kara <jack@suse.cz> · 2021-01-06
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · Ruan Shiyang <hidden> · 2021-01-12
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · zhong jiang <hidden> · 2021-01-13
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · Ruan Shiyang <hidden> · 2021-01-14
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · zhong jiang <hidden> · 2021-01-14
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · Ruan Shiyang <hidden> · 2021-01-14
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · zhong jiang <hidden> · 2021-01-14
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · "Darrick J. Wong" <djwong@kernel.org> · 2021-01-14
Re: [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping · Dan Williams <hidden> · 2021-01-14
[PATCH 05/10] mm, pmem: Implement ->memory_failure() in pmem driver · Shiyang Ruan <hidden> · 2020-12-30
Re: [PATCH 05/10] mm, pmem: Implement ->memory_failure() in pmem driver · Jan Kara <jack@suse.cz> · 2021-01-06
[PATCH 06/10] pmem: Implement ->corrupted_range() for pmem driver · Shiyang Ruan <hidden> · 2020-12-30
[PATCH 07/10] dm: Introduce ->rmap() to find bdev offset · Shiyang Ruan <hidden> · 2020-12-30
[PATCH 08/10] md: Implement ->corrupted_range() · Shiyang Ruan <hidden> · 2020-12-30
Re: [PATCH 08/10] md: Implement ->corrupted_range() · Jan Kara <jack@suse.cz> · 2021-01-06
Re: [PATCH 08/10] md: Implement ->corrupted_range() · Ruan Shiyang <hidden> · 2021-01-12
[PATCH 10/10] fs/dax: remove useless functions · Shiyang Ruan <hidden> · 2020-12-30
[PATCH 09/10] xfs: Implement ->corrupted_range() for XFS · Shiyang Ruan <hidden> · 2020-12-30
Re: [PATCH 09/10] xfs: Implement ->corrupted_range() for XFS · Darrick J. Wong <hidden> · 2021-01-04

From: Christoph Hellwig <hch@lst.de>
Date: 2021-01-08 09:56:15
Also in: linux-fsdevel, linux-raid, linux-xfs, lkml, nvdimm

It happens on a dax_device.  We should not interwind dax and block_device
even more after a lot of good work has happened to detangle them.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help