[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210108095500.GA5647@lst.de>
Date: Fri, 8 Jan 2021 10:55:00 +0100
From: Christoph Hellwig <hch@....de>
To: Shiyang Ruan <ruansy.fnst@...fujitsu.com>
Cc: linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-raid@...r.kernel.org,
darrick.wong@...cle.com, dan.j.williams@...el.com,
david@...morbit.com, hch@....de, song@...nel.org, rgoldwyn@...e.de,
qi.fuli@...itsu.com, y-goto@...itsu.com
Subject: Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block
device
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.
Powered by blists - more mailing lists