[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7fc7ba7c-f138-4944-dcc7-ce4b3f097528@oracle.com>
Date: Wed, 16 Dec 2020 12:55:30 -0800
From: Jane Chu <jane.chu@...cle.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: [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink
Hi, Shiyang,
On 12/15/2020 4:14 AM, Shiyang Ruan wrote:
> The call trace is like this:
> memory_failure()
> pgmap->ops->memory_failure() => pmem_pgmap_memory_failure()
> gendisk->fops->corrupted_range() => - pmem_corrupted_range()
> - md_blk_corrupted_range()
> sb->s_ops->currupted_range() => xfs_fs_corrupted_range()
> xfs_rmap_query_range()
> xfs_currupt_helper()
> * corrupted on metadata
> try to recover data, call xfs_force_shutdown()
> * corrupted on file data
> try to recover data, call mf_dax_mapping_kill_procs()
>
> The fsdax & reflink support for XFS is not contained in this patchset.
>
> (Rebased on v5.10)
So I tried the patchset with pmem error injection, the SIGBUS payload
does not look right -
** SIGBUS(7): **
** si_addr(0x(nil)), si_lsb(0xC), si_code(0x4, BUS_MCEERR_AR) **
I expect the payload looks like
** si_addr(0x7f3672e00000), si_lsb(0x15), si_code(0x4, BUS_MCEERR_AR) **
thanks,
-jane
Powered by blists - more mailing lists