> -Original Message-
> From: Dan Williams
> Subject: Re: [PATCH v4 03/10] fs: Introduce ->corrupted_range() for superblock
>
> On Wed, Jun 16, 2021 at 11:51 PM ruansy.f...@fujitsu.com
> wrote:
> >
> > > -Original Message-
> > > From: Dan Williams
> > > Subject: Re: [PATCH v4
> -Original Message-
> From: Dan Williams
> Subject: Re: [PATCH v4 03/10] fs: Introduce ->corrupted_range() for superblock
>
> [ drop old linux-nvd...@lists.01.org, add nvd...@lists.linux.dev ]
>
> On Thu, Jun 3, 2021 at 6:19 PM Shiyang Ruan wrote:
> >
> > Memory failure occurs in
On Wed, Jun 16, 2021 at 11:51 PM ruansy.f...@fujitsu.com
wrote:
>
> > -Original Message-
> > From: Dan Williams
> > Subject: Re: [PATCH v4 03/10] fs: Introduce ->corrupted_range() for
> > superblock
> >
> > [ drop old linux-nvd...@lists.01.org, add nvd...@lists.linux.dev ]
> >
> > On
[ drop old linux-nvd...@lists.01.org, add nvd...@lists.linux.dev ]
On Thu, Jun 3, 2021 at 6:19 PM Shiyang Ruan wrote:
>
> 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
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
---
include/linux/fs.h | 2 ++
1 file changed, 2
