From: Sabrina Dubroca <sd@queasysnail•net>
To: netdev@vger•kernel.org
Cc: Sabrina Dubroca <sd@queasysnail•net>, Xin Long <lxin@redhat•com>
Subject: [PATCH net 0/3] ipv6: fix error path of inet6_init()
Date: Tue, 28 Aug 2018 13:40:50 +0200 [thread overview]
Message-ID: <cover.1535451234.git.sd@queasysnail.net> (raw)
The error path of inet6_init() can trigger multiple kernel panics,
mostly due to wrong ordering of cleanups. This series fixes those
issues.
Sabrina Dubroca (3):
ipv6: fix cleanup ordering for ip6_mr failure
ipv6: fix cleanup ordering for pingv6 registration
net: rtnl: return early from rtnl_unregister_all when protocol isn't
registered
net/core/rtnetlink.c | 4 ++++
net/ipv6/af_inet6.c | 10 +++++-----
2 files changed, 9 insertions(+), 5 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-28 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 11:40 Sabrina Dubroca [this message]
2018-08-28 11:40 ` [PATCH net 1/3] ipv6: fix cleanup ordering for ip6_mr failure Sabrina Dubroca
2018-08-28 11:40 ` [PATCH net 2/3] ipv6: fix cleanup ordering for pingv6 registration Sabrina Dubroca
2018-08-28 11:40 ` [PATCH net 3/3] net: rtnl: return early from rtnl_unregister_all when protocol isn't registered Sabrina Dubroca
2018-08-28 15:30 ` [PATCH net 0/3] ipv6: fix error path of inet6_init() Xin Long
2018-08-30 2:29 ` David Miller
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=cover.1535451234.git.sd@queasysnail.net \
--to=sd@queasysnail$(echo .)net \
--cc=lxin@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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