From: Joey Gouly <joey.gouly@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <nd@arm.com>, <acme@redhat.com>, <catalin.marinas@arm.com>,
<izbyshev@ispras.ru>, <joey.gouly@arm.com>, <peterx@redhat.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>, Kees Cook <keescook@chromium.org>
Subject: [PATCH v1 0/4] Fixes for MDWE prctl
Date: Wed, 8 Mar 2023 19:04:19 +0000 [thread overview]
Message-ID: <20230308190423.46491-1-joey.gouly@arm.com> (raw)
Hi all,
These are four small fixes for the recent memory-write-deny-execute prctl patches [1].
Two reported by Alexey about error handling and two tooling fixes by Peter.
Thanks,
Joey
[1] https://lore.kernel.org/linux-arm-kernel/20230119160344.54358-1-joey.gouly@arm.com/
Joey Gouly (2):
mm: deduplicate error handling for map_deny_write_exec
mm: fix error handling for map_deny_write_exec
Peter Xu (2):
kselftest: vm: fix unused variable warning
tools headers UAPI: Sync linux/prctl.h with the kernel sources
mm/mmap.c | 7 +------
mm/mprotect.c | 2 +-
tools/include/uapi/linux/prctl.h | 6 ++++++
tools/testing/selftests/mm/mdwe_test.c | 3 +--
4 files changed, 9 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2023-03-08 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 19:04 Joey Gouly [this message]
2023-03-08 19:04 ` [PATCH v1 3/4] kselftest: vm: fix unused variable warning Joey Gouly
2023-03-13 14:12 ` Catalin Marinas
2023-03-08 19:04 ` [PATCH v1 4/4] tools headers UAPI: Sync linux/prctl.h with the kernel sources Joey Gouly
2023-03-13 14:13 ` Catalin Marinas
[not found] ` <20230308190423.46491-2-joey.gouly@arm.com>
2023-03-13 14:11 ` [PATCH v1 1/4] mm: deduplicate error handling for map_deny_write_exec Catalin Marinas
[not found] ` <20230308190423.46491-3-joey.gouly@arm.com>
2023-03-13 14:11 ` [PATCH v1 2/4] mm: fix " Catalin Marinas
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=20230308190423.46491-1-joey.gouly@arm.com \
--to=joey.gouly@arm.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=izbyshev@ispras.ru \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nd@arm.com \
--cc=peterx@redhat.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