public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Add TCP_MD5SIG_FLAG_IFINDEX from Linux 5.6 to netinet/tcp.h.
Date: Tue, 28 Nov 2023 12:45:07 +0000 (GMT)	[thread overview]
Message-ID: <20231128124507.CD88B388217A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=06bbe63e367abd5f7b225cbae30d1e487f237c85

commit 06bbe63e367abd5f7b225cbae30d1e487f237c85
Author: Tobias Klauser <tklauser@distanz.ch>
Date:   Tue Nov 28 12:06:43 2023 +0100

    Add TCP_MD5SIG_FLAG_IFINDEX from Linux 5.6 to netinet/tcp.h.
    
    This patch adds the TCP_MD5SIG_FLAG_IFINDEX constant from Linux 5.6 to
    sysdeps/gnu/netinet/tcp.h and updates struct tcp_md5sig accordingly to
    contain the device index.
    
    Reviewed-by: Florian Weimer <fweimer@redhat.com>

Diff:
---
 sysdeps/gnu/netinet/tcp.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/sysdeps/gnu/netinet/tcp.h b/sysdeps/gnu/netinet/tcp.h
index 1793724642..b2acbb4350 100644
--- a/sysdeps/gnu/netinet/tcp.h
+++ b/sysdeps/gnu/netinet/tcp.h
@@ -272,6 +272,7 @@ struct tcp_info
 
 /* tcp_md5sig extension flags for TCP_MD5SIG_EXT.  */
 #define TCP_MD5SIG_FLAG_PREFIX	1 /* Address prefix length.  */
+#define TCP_MD5SIG_FLAG_IFINDEX	2 /* Ifindex set.  */
 
 struct tcp_md5sig
 {
@@ -279,7 +280,7 @@ struct tcp_md5sig
   uint8_t	tcpm_flags;			/* Extension flags.  */
   uint8_t	tcpm_prefixlen;			/* Address prefix.  */
   uint16_t	tcpm_keylen;			/* Key length.  */
-  uint32_t	__tcpm_pad;			/* Zero.  */
+  int		tcpm_ifindex;			/* Device index for scope.  */
   uint8_t	tcpm_key[TCP_MD5SIG_MAXKEYLEN];	/* Key (binary).  */
 };

                 reply	other threads:[~2023-11-28 12:45 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=20231128124507.CD88B388217A@sourceware.org \
    --to=fw@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).