From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, vfalico@gmail.com,
andy@greyhouse.net, nikolay@redhat.com, maheshb@google.com
Subject: Re: [PATCH v2 net-next 0/4] bonding: rcu cleanups
Date: Tue, 15 Jul 2014 17:50:41 -0700 (PDT) [thread overview]
Message-ID: <20140715.175041.1779643875444299705.davem@davemloft.net> (raw)
In-Reply-To: <1405432616-12414-1-git-send-email-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Tue, 15 Jul 2014 06:56:52 -0700
> RCU was added to bonding in linux-3.12 but lacked proper sparse annotations.
>
> Using __rcu annotation actually helps to spot all accesses to
> bond->curr_active_slave & cond->current_arp_slave
> are correctly protected, with full sparse & LOCKDEP support.
>
> Lets clean the code.
Series applied, thanks a lot Eric.
prev parent reply other threads:[~2014-07-16 0:50 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
2014-07-15 14:37 ` [PATCH v2 net-next 0/4] bonding: rcu cleanups Veaceslav Falico
2014-07-16 0:50 ` David Miller [this message]
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=20140715.175041.1779643875444299705.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--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 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).