From: Mike Kravetz <mike.kravetz@oracle.com>
To: Li Wang <liwang@redhat.com>, Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Linux-MM <linux-mm@kvack.org>, LTP List <ltp@lists.linux.it>,
xishi.qiuxishi@alibaba-inc.com, mhocko@kernel.org,
Cyril Hrubis <chrubis@suse.cz>
Subject: Re: [MM Bug?] mmap() triggers SIGBUS while doing the numa_move_pages() for offlined hugepage in background
Date: Mon, 29 Jul 2019 12:00:41 -0700 [thread overview]
Message-ID: <47999e20-ccbe-deda-c960-473db5b56ea0@oracle.com> (raw)
In-Reply-To: <CAEemH2dMW6oh6Bbm=yqUADF+mDhuQgFTTGYftB+xAhqqdYV3Ng@mail.gmail.com>
On 7/28/19 10:17 PM, Li Wang wrote:
> Hi Naoya and Linux-MMers,
>
> The LTP/move_page12 V2 triggers SIGBUS in the kernel-v5.2.3 testing.
> https://github.com/wangli5665/ltp/blob/master/testcases/kernel/syscalls/move_pages/move_pages12.c
>
> It seems like the retry mmap() triggers SIGBUS while doing thenuma_move_pages() in background. That is very similar to the kernelbug which was mentioned by commit 6bc9b56433b76e40d(mm: fix race onsoft-offlining ): A race condition between soft offline andhugetlb_fault which causes unexpected process SIGBUS killing.
>
> I'm not sure if that below patch is making sene to memory-failures.c, but after building a new kernel-5.2.3 with this change, the problem can NOT be reproduced.
>
> Any comments?
Something seems strange. I can not reproduce with unmodified 5.2.3
[root@f23d move_pages]# uname -r
5.2.3
[root@f23d move_pages]# PATH=$PATH:$PWD ./move_pages12
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
move_pages12.c:201: INFO: Free RAM 6725424 kB
move_pages12.c:219: INFO: Increasing 2048kB hugepages pool on node 0 to 4
move_pages12.c:229: INFO: Increasing 2048kB hugepages pool on node 1 to 4
move_pages12.c:145: INFO: Allocating and freeing 4 hugepages on node 0
move_pages12.c:145: INFO: Allocating and freeing 4 hugepages on node 1
move_pages12.c:135: PASS: Bug not reproduced
Summary:
passed 1
failed 0
skipped 0
warnings 0
Also, the soft_offline_huge_page() code should not come into play with
this specific test.
--
Mike Kravetz
next prev parent reply other threads:[~2019-07-29 19:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 5:17 [MM Bug?] mmap() triggers SIGBUS while doing the numa_move_pages() for offlined hugepage in background Li Wang
2019-07-29 19:00 ` Mike Kravetz [this message]
2019-07-30 6:29 ` Li Wang
2019-07-31 0:44 ` Mike Kravetz
2019-08-02 0:19 ` Mike Kravetz
2019-08-02 4:15 ` Naoya Horiguchi
2019-08-02 17:42 ` Mike Kravetz
2019-08-05 0:40 ` Naoya Horiguchi
2019-08-05 8:57 ` Michal Hocko
2019-08-05 17:36 ` Mike Kravetz
2019-08-07 0:07 ` Mike Kravetz
2019-08-07 7:39 ` Michal Hocko
2019-08-07 15:10 ` Mike Kravetz
2019-08-02 9:59 ` Li Wang
2019-07-30 6:38 ` Li Wang
2019-08-02 3:48 ` Naoya Horiguchi
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=47999e20-ccbe-deda-c960-473db5b56ea0@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=chrubis@suse.cz \
--cc=linux-mm@kvack.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=xishi.qiuxishi@alibaba-inc.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).