From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: netdev@vger.kernel.org
Cc: oss-drivers@netronome.com, Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net 0/3] nfp: fix SR-IOV deadlock and representor bugs
Date: Tue, 22 Aug 2017 23:22:41 -0700 [thread overview]
Message-ID: <20170823062244.26580-1-jakub.kicinski@netronome.com> (raw)
This series tackles the bug I've already tried to fix in commit
6d48ceb27af1 ("nfp: allocate a private workqueue for driver work").
I created a separate workqueue to avoid possible deadlock, and
the lockdep error disappeared, coincidentally. The way workqueues
are operating, separate workqueue doesn't necessarily mean separate
thread of execution. Luckily we can safely forego the lock.
Second fix changes the order in which vNIC netdevs and representors
are created/destroyed. The fix is kept small and should be sufficient
for net because of how flower uses representors, a more thorough fix
will be targeted at net-next.
Third fix avoids leaking mapped frame buffers if FW sent a frame with
unknown portid.
Jakub Kicinski (3):
nfp: don't hold PF lock while enabling SR-IOV
nfp: make sure representors are destroyed before their lower netdev
nfp: avoid buffer leak when representor is missing
drivers/net/ethernet/netronome/nfp/nfp_main.c | 16 +++++++---------
.../net/ethernet/netronome/nfp/nfp_net_common.c | 10 +++++-----
drivers/net/ethernet/netronome/nfp/nfp_net_main.c | 22 ++++++++++++++--------
3 files changed, 26 insertions(+), 22 deletions(-)
--
2.11.0
next reply other threads:[~2017-08-23 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 6:22 Jakub Kicinski [this message]
2017-08-23 6:22 ` [PATCH net 1/3] nfp: don't hold PF lock while enabling SR-IOV Jakub Kicinski
2017-08-23 6:22 ` [PATCH net 2/3] nfp: make sure representors are destroyed before their lower netdev Jakub Kicinski
2017-08-23 6:22 ` [PATCH net 3/3] nfp: avoid buffer leak when representor is missing Jakub Kicinski
2017-08-24 3:40 ` [PATCH net 0/3] nfp: fix SR-IOV deadlock and representor bugs 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=20170823062244.26580-1-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).