public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Francis Laniel <flaniel@linux.microsoft.com>
To: libc-alpha@sourceware.org
Cc: Kir Kolyshkin <kolyshkin@gmail.com>
Subject: Re: [PATCH v2] Add F_SEAL_EXEC from Linux 6.3 to bits/fcntl-linux.h.
Date: Fri, 08 Sep 2023 17:07:20 +0200	[thread overview]
Message-ID: <12280820.O9o76ZdvQC@pwmachine> (raw)
In-Reply-To: <20230825023140.1384486-1-kolyshkin@gmail.com>

Hi.


Le vendredi 25 août 2023, 04:31:40 CEST Kir Kolyshkin via Libc-alpha a écrit :
> This patch adds the new F_SEAL_EXEC constant from Linux 6.3 (see Linux
> commit 6fd7353829c ("mm/memfd: add F_SEAL_EXEC") to bits/fcntl-linux.h.
> 
> [v2: fix comment]
> 
> Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
> ---
>  sysdeps/unix/sysv/linux/bits/fcntl-linux.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/sysdeps/unix/sysv/linux/bits/fcntl-linux.h
> b/sysdeps/unix/sysv/linux/bits/fcntl-linux.h index 1babbdc84e..df378c7b89
> 100644
> --- a/sysdeps/unix/sysv/linux/bits/fcntl-linux.h
> +++ b/sysdeps/unix/sysv/linux/bits/fcntl-linux.h
> @@ -286,6 +286,7 @@ struct f_owner_ex
>  # define F_SEAL_WRITE	0x0008	/* Prevent writes.  */
>  # define F_SEAL_FUTURE_WRITE	0x0010	/* Prevent future writes while
>  					   mapped.  */
> +# define F_SEAL_EXEC	0x0020	/* Prevent chmod modifying exec bits. */
>  #endif
> 
>  #ifdef __USE_GNU

Thank you for the patch!

Reviewed-by: Francis Laniel <flaniel@linux.microsoft.com>


Best regards.



      parent reply	other threads:[~2023-09-08 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 20:36 [PATCH] " Kir Kolyshkin
2023-08-25  2:31 ` [PATCH v2] " Kir Kolyshkin
2023-08-28 17:41   ` Adhemerval Zanella Netto
2023-09-08 15:07   ` Francis Laniel [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=12280820.O9o76ZdvQC@pwmachine \
    --to=flaniel@linux.microsoft.com \
    --cc=kolyshkin@gmail.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).