From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
David Ahern <dsa@cumulusnetworks.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH v3 net-next 3/5] net: vrf: call netdev_lockdep_set_classes()
Date: Thu, 9 Jun 2016 07:45:13 -0700 [thread overview]
Message-ID: <1465483515-10821-4-git-send-email-edumazet@google.com> (raw)
In-Reply-To: <1465483515-10821-1-git-send-email-edumazet@google.com>
In case a qdisc is used on a vrf device, we need to use different
lockdep classes to avoid false positives.
Use the new netdev_lockdep_set_classes() generic helper.
Reported-by: David Ahern <dsa@cumulusnetworks.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
---
drivers/net/vrf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/vrf.c b/drivers/net/vrf.c
index e3e693bf0dec..b82e3527924e 100644
--- a/drivers/net/vrf.c
+++ b/drivers/net/vrf.c
@@ -661,7 +661,7 @@ static int vrf_dev_init(struct net_device *dev)
/* similarly, oper state is irrelevant; set to up to avoid confusion */
dev->operstate = IF_OPER_UP;
-
+ netdev_lockdep_set_classes(dev);
return 0;
out_rth:
--
2.8.0.rc3.226.g39d4020
next prev parent reply other threads:[~2016-06-09 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 14:45 [PATCH v3 net-next 0/5] net: better lockdep annotations Eric Dumazet
2016-06-09 14:45 ` [PATCH v3 net-next 1/5] net: sched: fix qdisc->running " Eric Dumazet
2016-06-09 14:45 ` [PATCH v3 net-next 2/5] net: add netdev_lockdep_set_classes() helper Eric Dumazet
2016-06-09 14:45 ` Eric Dumazet [this message]
2016-06-09 15:05 ` [PATCH v3 net-next 3/5] net: vrf: call netdev_lockdep_set_classes() David Ahern
2016-06-09 14:45 ` [PATCH v3 net-next 4/5] net: macvlan: " Eric Dumazet
2016-06-09 14:45 ` [PATCH v3 net-next 5/5] net: ipvlan: " Eric Dumazet
2016-06-09 20:29 ` [PATCH v3 net-next 0/5] net: better lockdep annotations 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=1465483515-10821-4-git-send-email-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=eric.dumazet@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).