linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sidhartha Kumar <sidhartha.kumar@oracle.com>
To: shuah@kernel.org, akpm@linux-foundation.org
Cc: Sidhartha Kumar <sidhartha.kumar@oracle.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] selftest/vm fix segfault in mremap_test
Date: Thu, 14 Apr 2022 17:15:25 +0000	[thread overview]
Message-ID: <20220414171529.62058-1-sidhartha.kumar@oracle.com> (raw)

The mremap test currently segfaults because mremap
does not have a NOREPLACE flag which will fail if the
remap destination address collides with an existing mapping.
The segfault is caused by the mremap call destorying the
text region mapping of the program. This patch series fixes
the segfault by sanitizing the mremap destination address
and introduces other minor fixes to the test case. 

Sidhartha Kumar (4):
  selftest/vm: verify mmap addr in mremap_test
  selftest/vm: verify remap destination address in mremap_test
  selftest/vm: support xfail in mremap_test
  selftest/vm: add skip support to mremap_test

 tools/testing/selftests/vm/mremap_test.c  | 79 ++++++++++++++++++++++-
 tools/testing/selftests/vm/run_vmtests.sh | 11 +++-
 2 files changed, 85 insertions(+), 5 deletions(-)

-- 
2.27.0



             reply	other threads:[~2022-04-14 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 17:15 Sidhartha Kumar [this message]
2022-04-14 17:15 ` [PATCH 1/4] selftest/vm: verify mmap addr in mremap_test Sidhartha Kumar
2022-04-14 21:19   ` Shuah Khan
2022-04-14 21:39     ` Sidhartha Kumar
2022-04-14 17:15 ` [PATCH 2/4] selftest/vm: verify remap destination address " Sidhartha Kumar
2022-04-14 21:47   ` Shuah Khan
2022-04-14 22:24     ` Sidhartha Kumar
2022-04-19 16:21       ` Shuah Khan
2022-04-14 17:15 ` [PATCH 3/4] selftest/vm: support xfail " Sidhartha Kumar
2022-04-14 21:48   ` Shuah Khan
2022-04-14 17:15 ` [PATCH 4/4] selftest/vm: add skip support to mremap_test Sidhartha Kumar
2022-04-14 21:49   ` Shuah Khan

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=20220414171529.62058-1-sidhartha.kumar@oracle.com \
    --to=sidhartha.kumar@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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;
as well as URLs for NNTP newsgroup(s).