Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink
To:     Jane Chu <jane.chu@oracle.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>
References: <20201215121414.253660-1-ruansy.fnst@cn.fujitsu.com>
 <7fc7ba7c-f138-4944-dcc7-ce4b3f097528@oracle.com>
From:   Ruan Shiyang <ruansy.fnst@cn.fujitsu.com>
Message-ID: <a57c44dd-127a-3bd2-fcb3-f1373572de27@cn.fujitsu.com>
Date:   Fri, 18 Dec 2020 10:44:26 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <7fc7ba7c-f138-4944-dcc7-ce4b3f097528@oracle.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk


On 2020/12/17 上午4:55, Jane Chu wrote:
> 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 for testing.  I test the SIGBUS by writing a program which calls 
madvise(... ,MADV_HWPOISON) to inject memory-failure.  It just shows 
that the program is killed by SIGBUS.  I cannot get any detail from it. 
  So, could you please show me the right way(test tools) to test it?


--
Thanks,
Ruan Shiyang.

> 
> thanks,
> -jane
> 
> 
> 
> 
> 
>