From: Ruan Shiyang <ruansy.fnst@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org,
david@fromorbit.com, hch@lst.de, song@kernel.org,
rgoldwyn@suse.de, qi.fuli@fujitsu.com, y-goto@fujitsu.com
Subject: Re: [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink
Date: Fri, 18 Dec 2020 17:13:23 +0800 [thread overview]
Message-ID: <16ac8000-2892-7491-26a0-84de4301f168@cn.fujitsu.com> (raw)
In-Reply-To: <20201218034907.GG6918@magnolia>
On 2020/12/18 上午11:49, Darrick J. Wong wrote:
> On Fri, Dec 18, 2020 at 10:44:26AM +0800, Ruan Shiyang wrote:
>>
>>
>> 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?
>
> I'm assuming that Jane is using a program that calls sigaction to
> install a SIGBUS handler, and dumps the entire siginfo_t structure
> whenever it receives one...
OK. Let me try it and figure out what's wrong in it.
--
Thanks,
Ruan Shiyang.
>
> --D
>
>>
>> --
>> Thanks,
>> Ruan Shiyang.
>>
>>>
>>> thanks,
>>> -jane
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
_______________________________________________
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: Ruan Shiyang <ruansy.fnst@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: 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>, <linux-fsdevel@vger.kernel.org>,
<linux-raid@vger.kernel.org>, <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: Re: [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink
Date: Fri, 18 Dec 2020 17:13:23 +0800 [thread overview]
Message-ID: <16ac8000-2892-7491-26a0-84de4301f168@cn.fujitsu.com> (raw)
In-Reply-To: <20201218034907.GG6918@magnolia>
On 2020/12/18 上午11:49, Darrick J. Wong wrote:
> On Fri, Dec 18, 2020 at 10:44:26AM +0800, Ruan Shiyang wrote:
>>
>>
>> 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?
>
> I'm assuming that Jane is using a program that calls sigaction to
> install a SIGBUS handler, and dumps the entire siginfo_t structure
> whenever it receives one...
OK. Let me try it and figure out what's wrong in it.
--
Thanks,
Ruan Shiyang.
>
> --D
>
>>
>> --
>> Thanks,
>> Ruan Shiyang.
>>
>>>
>>> thanks,
>>> -jane
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
next prev parent reply other threads:[~2020-12-18 9:15 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 ` [RFC PATCH v3 2/9] blk: Introduce ->corrupted_range() for block device Shiyang Ruan
2020-12-15 12:14 ` 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 [this message]
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=16ac8000-2892-7491-26a0-84de4301f168@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: link
Be 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.