Re: [PATCH 03/10] fs: Introduce ->corrupted_range() for superblock
From: Christoph Hellwig <hch@lst.de>
Date: 2021-01-08 09:57:14
Also in:
linux-fsdevel, linux-raid, linux-xfs, lkml, nvdimm
On Thu, Dec 31, 2020 at 12:55:54AM +0800, Shiyang Ruan wrote:
quoted hunk ↗ jump to hunk
Memory failure occurs in fsdax mode will finally be handled in filesystem. We introduce this interface to find out files or metadata affected by the corrupted range, and try to recover the corrupted data if possiable. Signed-off-by: Shiyang Ruan <redacted> --- include/linux/fs.h | 2 ++ 1 file changed, 2 insertions(+)diff --git a/include/linux/fs.h b/include/linux/fs.h index 8667d0cdc71e..282e2139b23e 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h@@ -1965,6 +1965,8 @@ struct super_operations { struct shrink_control *); long (*free_cached_objects)(struct super_block *, struct shrink_control *); + int (*corrupted_range)(struct super_block *sb, struct block_device *bdev,
This adds an overly long line. But more importantly it must work on the dax device and not the block device. I'd also structure the callback so that it is called on the dax device only, with the file system storing the super block in a private data member.