[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210305061008.GA15141@lst.de>
Date: Fri, 5 Mar 2021 07:10:08 +0100
From: Christoph Hellwig <hch@....de>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Christoph Hellwig <hch@....de>,
Shiyang Ruan <ruansy.fnst@...fujitsu.com>,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, dm-devel@...hat.com,
darrick.wong@...cle.com, dan.j.williams@...el.com,
david@...morbit.com, agk@...hat.com, snitzer@...hat.com,
rgoldwyn@...e.de, qi.fuli@...itsu.com, y-goto@...itsu.com
Subject: Re: [PATCH v3 02/11] blk: Introduce ->corrupted_range() for block
device
On Thu, Mar 04, 2021 at 02:42:50PM -0800, Darrick J. Wong wrote:
> My vision here, however, is to establish upcalls for /both/ types of
> stroage.
I already have patches for doing these kinds of callbacks properly
for the block layer. They will be posted shortly.
Powered by blists - more mailing lists