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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Shiyang Ruan <ruansy.fnst@xxxxxxxxxxxxxx>
Subject: Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 8 Jan 2021 10:55:00 +0100
Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, linux-nvdimm@xxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, darrick.wong@xxxxxxxxxx, dan.j.williams@xxxxxxxxx, david@xxxxxxxxxxxxx, hch@xxxxxx, song@xxxxxxxxxx, rgoldwyn@xxxxxxx, qi.fuli@xxxxxxxxxxx, y-goto@xxxxxxxxxxx
In-reply-to: <20201230165601.845024-3-ruansy.fnst@cn.fujitsu.com>
References: <20201230165601.845024-1-ruansy.fnst@cn.fujitsu.com> <20201230165601.845024-3-ruansy.fnst@cn.fujitsu.com>
User-agent: Mutt/1.5.17 (2007-11-01)

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.

Follow-Ups:
- Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device
  - From: Darrick J. Wong

References:
- [PATCH 00/10] fsdax: introduce fs query to support reflink
  - From: Shiyang Ruan
- [PATCH 02/10] blk: Introduce ->corrupted_range() for block device
  - From: Shiyang Ruan

Prev by Date: Re: [RFC PATCH v3 8/9] md: Implement ->corrupted_range()
Next by Date: Re: [PATCH 03/10] fs: Introduce ->corrupted_range() for superblock
Previous by thread: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device
Next by thread: Re: [PATCH 02/10] blk: Introduce ->corrupted_range() for block device
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux