From: Aili Yao <yaoaili@kingsoft.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: Oscar Salvador <osalvador@suse.de>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"yangfeng1@kingsoft.com" <yangfeng1@kingsoft.com>
Subject: Re: [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early
Date: Tue, 19 Jan 2021 14:04:18 +0800 [thread overview]
Message-ID: <20210119140418.115bb906.yaoaili@kingsoft.com> (raw)
In-Reply-To: <20210119052537.GA1642@hori.linux.bs1.fc.nec.co.jp>
> Thanks, so which interface did you use for error injection? I guess first
> you used /sys/devices/system/memory/hard_offline_page, but if it's true,
> then the error event should be action optional (no MF_ACTION_REQUIRED set).
> So now I'm wondering why you are observing action required events?
> My another guess is that you might have used mce-inject tool, if that's true,
> please use hard_offline_page, then current kernel code should properly send
> SIGBUS to dedicated process.
>
The test has no relation to ce and hard_offline_page, sorry for misleading.
if the test code will compiled to my_test bin, here is my script:
./my_test hola salut servus test haaa --- this case no early-kill flag set
or
./my_test -s hola salut servus test haaa --- this case early-kill is set.
there must be a process names "test" which will trigger the UE;
when the my_test start, the shared page's physical address will be printed;
In another console, I will use einj module to inject the 0X10 LEVEL error to this
physical address.
After that, the test process trigger the memory-failure process, and then the log
should be observed.
Thanks.
--
Best Regards!
Aili Yao
next prev parent reply other threads:[~2021-01-19 6:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 7:55 [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early Aili Yao
2021-01-15 8:49 ` Oscar Salvador
2021-01-15 9:26 ` Aili Yao
2021-01-15 9:31 ` Aili Yao
2021-01-15 9:40 ` Oscar Salvador
2021-01-15 9:53 ` Aili Yao
2021-01-15 10:31 ` Oscar Salvador
2021-01-18 5:15 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 5:57 ` Aili Yao
2021-01-18 6:50 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 7:16 ` Aili Yao
2021-01-18 8:15 ` Aili Yao
2021-01-18 8:57 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 9:09 ` Aili Yao
2021-01-19 5:25 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-19 6:04 ` Aili Yao [this message]
2021-01-19 7:33 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 9:24 ` Oscar Salvador
2021-01-18 9:38 ` Aili Yao
2021-01-18 10:09 ` Oscar Salvador
2021-01-19 4:21 ` Aili Yao
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=20210119140418.115bb906.yaoaili@kingsoft.com \
--to=yaoaili@kingsoft.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=yangfeng1@kingsoft.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;
as well as URLs for NNTP newsgroup(s).