From: Eric Dumazet <eric.dumazet@gmail.com>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>
Subject: Re: [PATCH net] bonding: avoid lockdep confusion in bond_get_stats()
Date: Tue, 31 Jul 2018 06:28:50 -0700 [thread overview]
Message-ID: <714200ef-93b2-d613-5ae8-30eeeabffae5@gmail.com> (raw)
In-Reply-To: <20180731132522.57029-1-edumazet@google.com>
On 07/31/2018 06:25 AM, Eric Dumazet wrote:
> syzbot found that the following sequence produces a LOCKDEP splat [1]
>
> ip link add bond10 type bond
> ip link add bond11 type bond
> ip link set bond11 master bond10
...
> +static struct lock_class_key bond_netdev_addr_lock_key;
> +
Oops, this part is not needed, I will send a V2
prev parent reply other threads:[~2018-07-31 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 13:25 [PATCH net] bonding: avoid lockdep confusion in bond_get_stats() Eric Dumazet
2018-07-31 13:28 ` Eric Dumazet [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=714200ef-93b2-d613-5ae8-30eeeabffae5@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox