From: Nikolay Aleksandrov <nikolay@redhat.com>
To: Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Mahesh Bandewar <maheshb@google.com>
Subject: Re: [PATCH v2 net-next 4/4] bonding: add proper __rcu annotation for current_arp_slave
Date: Tue, 15 Jul 2014 16:07:46 +0200 [thread overview]
Message-ID: <53C535B2.4070306@redhat.com> (raw)
In-Reply-To: <1405432616-12414-5-git-send-email-edumazet@google.com>
On 07/15/2014 03:56 PM, Eric Dumazet wrote:
> Using __rcu annotation actually helps to spot all accesses to
> bond->current_arp_slave are correctly protected, with LOCKDEP support.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> drivers/net/bonding/bond_main.c | 15 +++++++++------
> drivers/net/bonding/bonding.h | 2 +-
> 2 files changed, 10 insertions(+), 7 deletions(-)
>
you're fast, thanks again :-)
Reviewed-by: Nikolay Aleksandrov <nikolay@redhat.com>
next prev parent reply other threads:[~2014-07-15 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 13:56 [PATCH v2 net-next 0/4] bonding: rcu cleanups Eric Dumazet
2014-07-15 13:56 ` [PATCH v2 net-next 1/4] bonding: get rid of bond_option_active_slave_get() Eric Dumazet
2014-07-15 13:56 ` [PATCH v2 net-next 2/4] bonding: use rcu_access_pointer() in bonding_show_mii_status() Eric Dumazet
2014-07-15 13:56 ` [PATCH v2 net-next 3/4] bonding: add proper __rcu annotation for curr_active_slave Eric Dumazet
2014-07-15 13:56 ` [PATCH v2 net-next 4/4] bonding: add proper __rcu annotation for current_arp_slave Eric Dumazet
2014-07-15 14:07 ` Nikolay Aleksandrov [this message]
2014-07-15 14:37 ` [PATCH v2 net-next 0/4] bonding: rcu cleanups Veaceslav Falico
2014-07-16 0:50 ` 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=53C535B2.4070306@redhat.com \
--to=nikolay@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.