From: Catalin Marinas <catalin.marinas@arm.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Florent Revest <revest@chromium.org>,
Helge Kreutzmann <debian@helgefjell.de>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page PR_SET_MDWE.2const
Date: Fri, 16 Jan 2026 13:38:09 +0000 [thread overview]
Message-ID: <aWo_QapqzcfksqQD@arm.com> (raw)
In-Reply-To: <aWowCOHKdluUVvfl@devuan>
On Fri, Jan 16, 2026 at 01:39:08PM +0100, Alejandro Colomar wrote:
> I've applied the following patch:
>
> commit 6352d57d7324d8c6fee2d335f103d8755ea5a620
> Author: Alejandro Colomar <alx@kernel.org>
> Date: Fri Jan 16 13:37:28 2026 +0100
>
> man/man2const/PR_SET_MDWE.2const: wfix
>
> Reported-by: Helge Kreutzmann <debian@helgefjell.de>
> Suggested-by: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Florent Revest <revest@chromium.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
>
> diff --git a/man/man2const/PR_SET_MDWE.2const b/man/man2const/PR_SET_MDWE.2const
> index db75b1873..4749ea5be 100644
> --- a/man/man2const/PR_SET_MDWE.2const
> +++ b/man/man2const/PR_SET_MDWE.2const
> @@ -26,7 +26,7 @@ .SH DESCRIPTION
> must be a bit mask of:
> .TP
> .B PR_MDWE_REFUSE_EXEC_GAIN
> -New memory mapping protections can't be writable and executable.
> +New memory mappings can't be writable and executable.
> Non-executable mappings can't become executable.
> .TP
> .B PR_MDWE_NO_INHERIT " (since Linux 6.6)"
Looks good. Thanks!
--
Catalin
prev parent reply other threads:[~2026-01-16 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:38 Issue in man page PR_SET_MDWE.2const Helge Kreutzmann
2025-12-25 20:54 ` Alejandro Colomar
2026-01-16 10:11 ` Catalin Marinas
2026-01-16 12:39 ` Alejandro Colomar
2026-01-16 13:38 ` Catalin Marinas [this message]
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=aWo_QapqzcfksqQD@arm.com \
--to=catalin.marinas@arm.com \
--cc=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
--cc=revest@chromium.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