From: Yisheng Xie <xieyisheng1@huawei.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Jan Stancek <jstancek@redhat.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: Is MADV_HWPOISON supposed to work only on faulted-in pages?
Date: Sat, 25 Feb 2017 10:28:15 +0800 [thread overview]
Message-ID: <1ba376aa-5e7c-915f-35d1-2d4eef0cad88@huawei.com> (raw)
In-Reply-To: <20170223032342.GA18740@hori1.linux.bs1.fc.nec.co.jp>
hi Naoya,
On 2017/2/23 11:23, Naoya Horiguchi wrote:
> On Mon, Feb 20, 2017 at 05:00:17AM +0000, Horiguchi Naoya(堀口 直也) wrote:
>> On Tue, Feb 14, 2017 at 04:41:29PM +0100, Jan Stancek wrote:
>>> Hi,
>>>
>>> code below (and LTP madvise07 [1]) doesn't produce SIGBUS,
>>> unless I touch/prefault page before call to madvise().
>>>
>>> Is this expected behavior?
>>
>> Thank you for reporting.
>>
>> madvise(MADV_HWPOISON) triggers page fault when called on the address
>> over which no page is faulted-in, so I think that SIGBUS should be
>> called in such case.
>>
>> But it seems that memory error handler considers such a page as "reserved
>> kernel page" and recovery action fails (see below.)
>>
>> [ 383.371372] Injecting memory failure for page 0x1f10 at 0x7efcdc569000
>> [ 383.375678] Memory failure: 0x1f10: reserved kernel page still referenced by 1 users
>> [ 383.377570] Memory failure: 0x1f10: recovery action for reserved kernel page: Failed
>>
>> I'm not sure how/when this behavior was introduced, so I try to understand.
>
> I found that this is a zero page, which is not recoverable for memory
> error now.
>
>> IMO, the test code below looks valid to me, so no need to change.
>
> I think that what the testcase effectively does is to test whether memory
> handling on zero pages works or not.
> And the testcase's failure seems acceptable, because it's simply not-implemented yet.
> Maybe recovering from error on zero page is possible (because there's no data
> loss for memory error,) but I'm not sure that code might be simple enough and/or
> it's worth doing ...
I question about it, if a memory error happened on zero page, it will
cause all of data read from zero page is error, I mean no-zero, right?
And can we just use re-initial it with zero data maybe by memset ?
Thanks
Yisheng Xie.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-02-25 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 15:41 Jan Stancek
2017-02-20 5:00 ` Naoya Horiguchi
2017-02-23 3:23 ` Naoya Horiguchi
2017-02-25 2:28 ` Yisheng Xie [this message]
2017-02-27 1:20 ` Naoya Horiguchi
2017-02-27 4:27 ` Zi Yan
2017-02-27 6:33 ` Naoya Horiguchi
2017-02-27 16:10 ` Zi Yan
2017-03-14 13:20 ` [LTP] " Cyril Hrubis
2017-03-27 12:08 ` Richard Palethorpe
2017-03-27 23:54 ` Andi Kleen
2017-03-28 8:25 ` [LTP] " Cyril Hrubis
2017-03-28 20:26 ` Andi Kleen
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=1ba376aa-5e7c-915f-35d1-2d4eef0cad88@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=jstancek@redhat.com \
--cc=linux-mm@kvack.org \
--cc=ltp@lists.linux.it \
--cc=n-horiguchi@ah.jp.nec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox