From: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> To: <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: [RFC PATCH v3 2/9] blk: Introduce ->corrupted_range() for block device Date: Tue, 15 Dec 2020 20:14:07 +0800 [thread overview] Message-ID: <20201215121414.253660-3-ruansy.fnst@cn.fujitsu.com> (raw) In-Reply-To: <20201215121414.253660-1-ruansy.fnst@cn.fujitsu.com> In fsdax mode, the memory failure happens on block device. So, it is needed to introduce an interface for block devices. Each kind of block device can handle the memory failure in ther own ways. Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> --- include/linux/blkdev.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 033eb5f73b65..45256fe84fa7 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -1858,6 +1858,8 @@ struct block_device_operations { int (*report_zones)(struct gendisk *, sector_t sector, unsigned int nr_zones, report_zones_cb cb, void *data); char *(*devnode)(struct gendisk *disk, umode_t *mode); + int (*corrupted_range)(struct gendisk *disk, struct block_device *bdev, + loff_t offset, size_t len, void *data); struct module *owner; const struct pr_ops *pr_ops; }; -- 2.29.2 _______________________________________________ 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: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> To: <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: [RFC PATCH v3 2/9] blk: Introduce ->corrupted_range() for block device Date: Tue, 15 Dec 2020 20:14:07 +0800 [thread overview] Message-ID: <20201215121414.253660-3-ruansy.fnst@cn.fujitsu.com> (raw) In-Reply-To: <20201215121414.253660-1-ruansy.fnst@cn.fujitsu.com> In fsdax mode, the memory failure happens on block device. So, it is needed to introduce an interface for block devices. Each kind of block device can handle the memory failure in ther own ways. Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> --- include/linux/blkdev.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index 033eb5f73b65..45256fe84fa7 100644 --- a/include/linux/blkdev.h +++ b/include/linux/blkdev.h @@ -1858,6 +1858,8 @@ struct block_device_operations { int (*report_zones)(struct gendisk *, sector_t sector, unsigned int nr_zones, report_zones_cb cb, void *data); char *(*devnode)(struct gendisk *disk, umode_t *mode); + int (*corrupted_range)(struct gendisk *disk, struct block_device *bdev, + loff_t offset, size_t len, void *data); struct module *owner; const struct pr_ops *pr_ops; }; -- 2.29.2
next prev parent reply other threads:[~2020-12-15 12:14 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-15 12:14 [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 12:14 ` [RFC PATCH v3 1/9] pagemap: Introduce ->memory_failure() Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan [this message] 2020-12-15 12:14 ` [RFC PATCH v3 2/9] blk: Introduce ->corrupted_range() for block device Shiyang Ruan 2020-12-15 12:14 ` [RFC PATCH v3 3/9] fs: Introduce ->corrupted_range() for superblock Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 12:14 ` [RFC PATCH v3 4/9] mm, fsdax: Refactor memory-failure handler for dax mapping Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-16 21:26 ` Dave Chinner 2020-12-16 21:26 ` Dave Chinner 2020-12-18 1:48 ` Ruan Shiyang 2020-12-18 1:48 ` Ruan Shiyang 2020-12-15 12:14 ` [RFC PATCH v3 5/9] mm, pmem: Implement ->memory_failure() in pmem driver Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 12:14 ` [RFC PATCH v3 6/9] pmem: Implement ->corrupted_range() for " Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 12:14 ` [RFC PATCH v3 7/9] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 12:14 ` [RFC PATCH v3 8/9] md: Implement ->corrupted_range() Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 20:51 ` Darrick J. Wong 2020-12-15 20:51 ` Darrick J. Wong 2020-12-15 23:28 ` Dave Chinner 2020-12-15 23:28 ` Dave Chinner 2020-12-18 2:11 ` Ruan Shiyang 2020-12-18 2:11 ` Ruan Shiyang 2021-01-04 23:34 ` Darrick J. Wong 2021-01-04 23:34 ` Darrick J. Wong 2021-01-08 9:52 ` Ruan Shiyang 2021-01-08 9:52 ` Ruan Shiyang 2021-01-08 19:05 ` Darrick J. Wong 2021-01-08 19:05 ` Darrick J. Wong 2020-12-16 5:43 ` Jane Chu 2020-12-16 5:43 ` Jane Chu 2020-12-18 1:50 ` Ruan Shiyang 2020-12-18 1:50 ` Ruan Shiyang 2020-12-15 12:14 ` [RFC PATCH v3 9/9] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan 2020-12-15 12:14 ` Shiyang Ruan 2020-12-15 20:40 ` Darrick J. Wong 2020-12-15 20:40 ` Darrick J. Wong 2020-12-18 2:31 ` Ruan Shiyang 2020-12-18 2:31 ` Ruan Shiyang 2020-12-16 20:55 ` [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink Jane Chu 2020-12-16 20:55 ` Jane Chu 2020-12-18 2:44 ` Ruan Shiyang 2020-12-18 2:44 ` Ruan Shiyang 2020-12-18 3:49 ` Darrick J. Wong 2020-12-18 3:49 ` Darrick J. Wong 2020-12-18 9:13 ` Ruan Shiyang 2020-12-18 9:13 ` Ruan Shiyang 2021-01-08 18:14 ` Jane Chu 2021-01-08 18:14 ` Jane Chu
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=20201215121414.253660-3-ruansy.fnst@cn.fujitsu.com \ --to=ruansy.fnst@cn.fujitsu.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=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: linkBe 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.