From: Hangbin Liu <liuhangbin@gmail.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Vasiliy Kovalev <kovalev@altlinux.org>,
Sabrina Dubroca <sd@queasysnail.net>,
Guillaume Nault <gnault@redhat.com>,
Simon Horman <horms@kernel.org>,
David Lebrun <david.lebrun@uclouvain.be>,
Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCHv3 net 0/3] ipv6: sr: fix errors during unregister
Date: Thu, 9 May 2024 21:18:09 +0800 [thread overview]
Message-ID: <20240509131812.1662197-1-liuhangbin@gmail.com> (raw)
Fix some errors in seg6 unregister path, like missing unregister functions,
incorrect unregister order, etc.
v3:
1) fix unreachable code when CONFIG_IPV6_SEG6_LWTUNNEL=n and
CONFIG_IPV6_SEG6_HMAC=n (Sabrina Dubroca)
2) separate the patch into 3 small patches since they fix different
commits (Simon Horman)
v2: define CONFIG_IPV6_SEG6_LWTUNNEL for label out_unregister_genl (Sabrina Dubroca)
Hangbin Liu (3):
ipv6: sr: add missing seg6_local_exit
ipv6: sr: fix incorrect unregister order
ipv6: sr: fix invalid unregister error path
net/ipv6/seg6.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2024-05-09 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 13:18 Hangbin Liu [this message]
2024-05-09 13:18 ` [PATCHv3 net 1/3] ipv6: sr: add missing seg6_local_exit Hangbin Liu
2024-05-10 8:05 ` Sabrina Dubroca
2024-05-11 1:48 ` David Ahern
2024-05-09 13:18 ` [PATCHv3 net 2/3] ipv6: sr: fix incorrect unregister order Hangbin Liu
2024-05-10 8:08 ` Sabrina Dubroca
2024-05-11 1:49 ` David Ahern
2024-05-09 13:18 ` [PATCHv3 net 3/3] ipv6: sr: fix invalid unregister error path Hangbin Liu
2024-05-10 8:32 ` Sabrina Dubroca
2024-05-11 1:52 ` David Ahern
2024-05-11 7:42 ` Hangbin Liu
2024-05-11 2:30 ` [PATCHv3 net 0/3] ipv6: sr: fix errors during unregister patchwork-bot+netdevbpf
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=20240509131812.1662197-1-liuhangbin@gmail.com \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=kovalev@altlinux.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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).