From: David Hildenbrand <david@redhat.com>
To: "Ryan Roberts" <ryan.roberts@arm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <shuah@kernel.org>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Mark Brown" <broonie@kernel.org>,
"John Hubbard" <jhubbard@nvidia.com>,
"Florent Revest" <revest@chromium.org>,
"Peter Xu" <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 6/8] selftests/mm: Make migration test robust to failure
Date: Mon, 24 Jul 2023 13:35:08 +0200 [thread overview]
Message-ID: <83a3f3e5-d41b-07d5-0dfd-ed9a380baae4@redhat.com> (raw)
In-Reply-To: <20230724082522.1202616-7-ryan.roberts@arm.com>
On 24.07.23 10:25, Ryan Roberts wrote:
> The `migration` test currently has a number of robustness problems that
> cause it to hang and leak resources.
>
> Timeout: There are 3 tests, which each previously ran for 60 seconds.
> However, the timeout in mm/settings for a single test binary was set to
> 45 seconds. So when run using run_kselftest.sh, the top level timeout
> would trigger before the test binary was finished. Solve this by meeting
> in the middle; each of the 3 tests now runs for 20 seconds (for a total
> of 60), and the top level timeout is set to 90 seconds.
>
> Leaking child processes: the `shared_anon` test fork()s some children
> but then an ASSERT() fires before the test kills those children. The
> assert causes immediate exit of the parent and leaking of the children.
> Furthermore, if run using the run_kselftest.sh wrapper, the wrapper
> would get stuck waiting for those children to exit, which never happens.
> Solve this by setting the "parent death signal" to SIGHUP in the child,
> so that the child is killed automatically if the parent dies.
>
> With these changes, the test binary now runs to completion on arm64,
> with 2 tests passing and the `shared_anon` test failing.
>
> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-07-24 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:25 [PATCH v3 0/8] selftests/mm fixes for arm64 Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 1/8] selftests: Line buffer test program's stdout Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 2/8] selftests/mm: Skip soft-dirty tests on arm64 Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 3/8] selftests/mm: Enable mrelease_test for arm64 Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 4/8] selftests/mm: Fix thuge-gen test bugs Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 5/8] selftests/mm: va_high_addr_switch should skip unsupported arm64 configs Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 6/8] selftests/mm: Make migration test robust to failure Ryan Roberts
2023-07-24 11:35 ` David Hildenbrand [this message]
2023-07-24 8:25 ` [PATCH v3 7/8] selftests/mm: Optionally pass duration to transhuge-stress Ryan Roberts
2023-07-24 8:25 ` [PATCH v3 8/8] selftests/mm: Run all tests from run_vmtests.sh Ryan Roberts
2023-07-24 16:38 ` [PATCH v3 0/8] selftests/mm fixes for arm64 Andrew Morton
2023-07-24 18:49 ` Ryan Roberts
2023-07-24 19:01 ` Andrew Morton
2023-07-24 21:23 ` Mark Brown
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=83a3f3e5-d41b-07d5-0dfd-ed9a380baae4@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=revest@chromium.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
/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