From: David Hildenbrand <david@redhat.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Peter Xu <peterx@redhat.com>
Cc: "open list : MEMORY MANAGEMENT" <linux-mm@kvack.org>
Subject: Re: soft-dirty kselftest is crashing on next-20221122
Date: Tue, 22 Nov 2022 15:49:25 +0100 [thread overview]
Message-ID: <04031393-75b4-b4f3-d727-cf9db9cb509c@redhat.com> (raw)
In-Reply-To: <12677bb0-198a-6ac2-2b01-ada23f43c45f@collabora.com>
On 22.11.22 15:00, Muhammad Usama Anjum wrote:
> Hello,
>
> I'm getting segmentation fault when mprotect file sub-tests in soft-dirty
> kselftest are run on top next-20221122 and on v6.0. These sub-tests were
> added by Peter recently. Has someone noticed this already?
On 6.0.7-200.fc36.x86_64, all tests pass.
# ./soft-dirty
TAP version 13
1..15
ok 1 Test test_simple
ok 2 Test test_vma_reuse dirty bit of allocated page
ok 3 Test test_vma_reuse dirty bit of reused address page
ok 4 Test test_hugepage huge page allocation
ok 5 Test test_hugepage huge page dirty bit
ok 6 Test test_mprotect-anon dirty bit of new written page
ok 7 Test test_mprotect-anon soft-dirty clear after clear_refs
ok 8 Test test_mprotect-anon soft-dirty clear after marking RO
ok 9 Test test_mprotect-anon soft-dirty clear after marking RW
ok 10 Test test_mprotect-anon soft-dirty after rewritten
ok 11 Test test_mprotect-file dirty bit of new written page
ok 12 Test test_mprotect-file soft-dirty clear after clear_refs
ok 13 Test test_mprotect-file soft-dirty clear after marking RO
ok 14 Test test_mprotect-file soft-dirty clear after marking RW
ok 15 Test test_mprotect-file soft-dirty after rewritten
# Totals: pass:15 fail:0 xfail:0 xpass:0 skip:0 error:0
Same on a kernel close to mm-unstable on top of 6.1.0-rc4:
# ./soft-dirty
TAP version 13
1..15
ok 1 Test test_simple
ok 2 Test test_vma_reuse dirty bit of allocated page
ok 3 Test test_vma_reuse dirty bit of reused address page
ok 4 Test test_hugepage huge page allocation
ok 5 Test test_hugepage huge page dirty bit
ok 6 Test test_mprotect-anon dirty bit of new written page
ok 7 Test test_mprotect-anon soft-dirty clear after clear_refs
ok 8 Test test_mprotect-anon soft-dirty clear after marking RO
ok 9 Test test_mprotect-anon soft-dirty clear after marking RW
ok 10 Test test_mprotect-anon soft-dirty after rewritten
ok 11 Test test_mprotect-file dirty bit of new written page
ok 12 Test test_mprotect-file soft-dirty clear after clear_refs
ok 13 Test test_mprotect-file soft-dirty clear after marking RO
ok 14 Test test_mprotect-file soft-dirty clear after marking RW
ok 15 Test test_mprotect-file soft-dirty after rewritten
# Totals: pass:15 fail:0 xfail:0 xpass:0 skip:0 error:0
Different architecture? Maybe recompile the tests?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-11-22 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 14:00 Muhammad Usama Anjum
2022-11-22 14:49 ` David Hildenbrand [this message]
2022-11-22 15:05 ` Muhammad Usama Anjum
2022-11-22 15:42 ` David Hildenbrand
2022-11-22 15:45 ` David Hildenbrand
2022-11-22 15:52 ` Muhammad Usama Anjum
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=04031393-75b4-b4f3-d727-cf9db9cb509c@redhat.com \
--to=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=usama.anjum@collabora.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