Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Pedro Falcato <pedro.falcato@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Jeff Xu <jeffxu@chromium.org>, Kees Cook <kees@kernel.org>,
	linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Pedro Falcato <pedro.falcato@gmail.com>
Subject: [PATCH 0/2] mseal: Fix is_madv_discard()
Date: Wed,  7 Aug 2024 18:33:34 +0100	[thread overview]
Message-ID: <20240807173336.2523757-1-pedro.falcato@gmail.com> (raw)

This small series fixes is_madv_discard() and adds a small sanity check
test to selftests/mm/mseal_test. Without this patch, is_madv_discard()
erroneously thinks innocent ops like MADV_RANDOM are discard operations
(which they are not, and are supposed to be allowed, per the overall
design).

Based on Linus's tree and taken from my mseal depessimization series[1].
[1]: https://lore.kernel.org/all/20240806212808.1885309-1-pedro.falcato@gmail.com/

Pedro Falcato (2):
  mseal: Fix is_madv_discard()
  selftests/mm: Add mseal test for no-discard madvise

 mm/mseal.c                              | 14 +++++++---
 tools/testing/selftests/mm/mseal_test.c | 34 +++++++++++++++++++++++++
 2 files changed, 45 insertions(+), 3 deletions(-)

-- 
2.46.0


             reply	other threads:[~2024-08-07 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 17:33 Pedro Falcato [this message]
2024-08-07 17:33 ` [PATCH 1/2] mseal: Fix is_madv_discard() Pedro Falcato
2024-08-07 18:58   ` Andrew Morton
2024-08-07 19:25     ` Pedro Falcato
2024-08-07 19:31       ` Andrew Morton
2024-08-07 17:33 ` [PATCH 2/2] selftests/mm: Add mseal test for no-discard madvise Pedro Falcato
2024-08-07 20:37   ` [PATCH] fixup! " Pedro Falcato

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=20240807173336.2523757-1-pedro.falcato@gmail.com \
    --to=pedro.falcato@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeffxu@chromium.org \
    --cc=kees@kernel.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