[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6100b7ca-7968-e1ea-84b8-074dc216a453@cloud.ionos.com>
Date: Tue, 26 Jan 2021 01:50:32 +0100
From: Guoqing Jiang <guoqing.jiang@...ud.ionos.com>
To: 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
Cc: 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 v2 08/10] md: Implement ->corrupted_range()
On 1/25/21 23:55, Shiyang Ruan wrote:
> With the support of ->rmap(), it is possible to obtain the superblock on
> a mapped device.
>
> If a pmem device is used as one target of mapped device, we cannot
> obtain its superblock directly. With the help of SYSFS, the mapped
> device can be found on the target devices. So, we iterate the
> bdev->bd_holder_disks to obtain its mapped device.
>
> Signed-off-by: Shiyang Ruan <ruansy.fnst@...fujitsu.com>
> ---
> drivers/md/dm.c | 61 +++++++++++++++++++++++++++++++++++++++++++
> drivers/nvdimm/pmem.c | 11 +++-----
> fs/block_dev.c | 42 ++++++++++++++++++++++++++++-
> include/linux/genhd.h | 2 ++
> 4 files changed, 107 insertions(+), 9 deletions(-)
I can't see md raid is involved here, perhaps dm-devel need to be cced
instead of raid list. And the subject need to be changed as well.
Thanks,
Guoqing
Powered by blists - more mailing lists