public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Add SCM_SECURITY, SCM_PIDFD to bits/socket.h
Date: Mon, 16 Oct 2023 13:19:42 +0000 (GMT)	[thread overview]
Message-ID: <20231016131942.8F6893858D33@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5ef608f36493c5d711418c5d31a7ebe710decc6e

commit 5ef608f36493c5d711418c5d31a7ebe710decc6e
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Mon Oct 16 13:19:26 2023 +0000

    Add SCM_SECURITY, SCM_PIDFD to bits/socket.h
    
    Linux 6.5 adds a constant SCM_PIDFD (recall that the non-uapi
    linux/socket.h, where this constant is added, is in fact a header
    providing many constants that are part of the kernel/userspace
    interface).  This shows up that SCM_SECURITY, from the same set of
    definitions and added in Linux 2.6.17, is also missing from glibc,
    although glibc has the first two constants from this set, SCM_RIGHTS
    and SCM_CREDENTIALS; add both missing constants to glibc.
    
    Tested for x86_64.

Diff:
---
 sysdeps/unix/sysv/linux/bits/socket.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sysdeps/unix/sysv/linux/bits/socket.h b/sysdeps/unix/sysv/linux/bits/socket.h
index 57b05715be..c19814c5cf 100644
--- a/sysdeps/unix/sysv/linux/bits/socket.h
+++ b/sysdeps/unix/sysv/linux/bits/socket.h
@@ -367,6 +367,10 @@ enum
 #ifdef __USE_GNU
     , SCM_CREDENTIALS = 0x02	/* Credentials passing.  */
 # define SCM_CREDENTIALS SCM_CREDENTIALS
+    , SCM_SECURITY = 0x03	/* Security label.  */
+# define SCM_SECURITY SCM_SECURITY
+    , SCM_PIDFD = 0x04		/* Pidfd.  */
+# define SCM_PIDFD SCM_PIDFD
 #endif
   };

                 reply	other threads:[~2023-10-16 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231016131942.8F6893858D33@sourceware.org \
    --to=jsm28@sourceware.org \
    --cc=glibc-cvs@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).