From: David Ahern <dsahern@gmail.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@gmail.com>
Subject: [PATCH net-next 0/2] net/ipv6: couple of fixes for rcu change to from
Date: Mon, 23 Apr 2018 11:32:05 -0700 [thread overview]
Message-ID: <20180423183207.9124-1-dsahern@gmail.com> (raw)
So many details... I am thankful for all the robots running the
permutations and tools.
Two bug fixes from the rcu change to rt->from:
1. missing rcu lock in ip6_negative_advice
2. rcu dereferences in 2 sites
David Ahern (2):
net/ipv6: add rcu locking to ip6_negative_advice
net/ipv6: Fix missing rcu dereferences on from
net/ipv6/route.c | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
--
2.11.0
next reply other threads:[~2018-04-23 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 18:32 David Ahern [this message]
2018-04-23 18:32 ` [PATCH net-next 1/2] net/ipv6: add rcu locking to ip6_negative_advice David Ahern
2018-04-23 18:32 ` [PATCH net-next 2/2] net/ipv6: Fix missing rcu dereferences on from David Ahern
2018-04-24 15:54 ` Eric Dumazet
2018-04-24 15:56 ` Eric Dumazet
2018-04-23 20:13 ` [PATCH net-next 0/2] net/ipv6: couple of fixes for rcu change to from 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=20180423183207.9124-1-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.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 NNTP newsgroup(s).