All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-nvdimm@lists.01.org, linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
	darrick.wong@oracle.com, david@fromorbit.com, hch@lst.de,
	song@kernel.org, rgoldwyn@suse.de, qi.fuli@fujitsu.com,
	y-goto@fujitsu.com
Subject: Re: [PATCH v2 08/10] md: Implement ->corrupted_range()
Date: Tue, 26 Jan 2021 01:50:32 +0100	[thread overview]
Message-ID: <6100b7ca-7968-e1ea-84b8-074dc216a453@cloud.ionos.com> (raw)
In-Reply-To: <20210125225526.1048877-9-ruansy.fnst@cn.fujitsu.com>



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@cn.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
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-nvdimm@lists.01.org, linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
	darrick.wong@oracle.com, dan.j.williams@intel.com,
	david@fromorbit.com, hch@lst.de, song@kernel.org,
	rgoldwyn@suse.de, qi.fuli@fujitsu.com, y-goto@fujitsu.com
Subject: Re: [PATCH v2 08/10] md: Implement ->corrupted_range()
Date: Tue, 26 Jan 2021 01:50:32 +0100	[thread overview]
Message-ID: <6100b7ca-7968-e1ea-84b8-074dc216a453@cloud.ionos.com> (raw)
In-Reply-To: <20210125225526.1048877-9-ruansy.fnst@cn.fujitsu.com>



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@cn.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

  reply	other threads:[~2021-01-26  0:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 22:55 [PATCH v2 00/10] fsdax: introduce fs query to support reflink Shiyang Ruan
2021-01-25 22:55 ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 01/10] pagemap: Introduce ->memory_failure() Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 02/10] blk: Introduce ->corrupted_range() for block device Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 03/10] fs: Introduce ->corrupted_range() for superblock Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 05/10] mm, pmem: Implement ->memory_failure() in pmem driver Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 06/10] pmem: Implement ->corrupted_range() for " Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 07/10] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 08/10] md: Implement ->corrupted_range() Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-26  0:50   ` Guoqing Jiang [this message]
2021-01-26  0:50     ` Guoqing Jiang
2021-01-25 22:55 ` [PATCH v2 09/10] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan
2021-01-25 22:55 ` [PATCH v2 10/10] fs/dax: Remove useless functions Shiyang Ruan
2021-01-25 22:55   ` Shiyang Ruan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6100b7ca-7968-e1ea-84b8-074dc216a453@cloud.ionos.com \
    --to=guoqing.jiang@cloud.ionos.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=qi.fuli@fujitsu.com \
    --cc=rgoldwyn@suse.de \
    --cc=ruansy.fnst@cn.fujitsu.com \
    --cc=song@kernel.org \
    --cc=y-goto@fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.