From: Eric Dumazet <eric.dumazet@gmail.com>
To: Benjamin Poirier <bpoirier@suse.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] ipv6: Annotate change of locking mechanism for np->opt
Date: Thu, 18 Feb 2016 09:08:27 +0100 [thread overview]
Message-ID: <1455782907.648.6.camel@edumazet-ThinkPad-T530> (raw)
In-Reply-To: <1455754833-31567-1-git-send-email-bpoirier@suse.com>
On mer., 2016-02-17 at 16:20 -0800, Benjamin Poirier wrote:
> follows up commit 45f6fad84cc3 ("ipv6: add complete rcu protection around
> np->opt") which added mixed rcu/refcount protection to np->opt.
>
> Given the current implementation of rcu_pointer_handoff(), this has no
> effect at runtime.
>
> Signed-off-by: Benjamin Poirier <bpoirier@suse.com>
> ---
LGTM
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2016-02-18 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 0:20 [PATCH] ipv6: Annotate change of locking mechanism for np->opt Benjamin Poirier
2016-02-18 8:08 ` Eric Dumazet [this message]
2016-02-18 20:27 ` 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=1455782907.648.6.camel@edumazet-ThinkPad-T530 \
--to=eric.dumazet@gmail.com \
--cc=bpoirier@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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