From: Sabrina Dubroca <sd@queasysnail.net>
To: Ross Lagerwall <ross.lagerwall@citrix.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Amritha Nambiar <amritha.nambiar@intel.com>
Subject: Re: [PATCH] net: Fix xps_needed inc/dec mismatch
Date: Fri, 7 Dec 2018 12:01:14 +0100 [thread overview]
Message-ID: <20181207110114.GA3378@bistromath.localdomain> (raw)
In-Reply-To: <20181207101621.24316-1-ross.lagerwall@citrix.com>
Hi Ross,
2018-12-07, 10:16:21 +0000, Ross Lagerwall wrote:
> xps_needed is incremented only when a new dev map is allocated (in
> __netif_set_xps_queue). Therefore it should be decremented only when we
> actually have a dev map to destroy. Without this, it may be decremented
> too many times which causes netif_reset_xps_queues to return early and
> not actually clean up the old dev maps. This results in a crash in
> __netif_set_xps_queue when it is called later.
>
> The crash occurred when having multiple ixgbe devices in a host. lldpad
> would reconfigure them to be FCoE-capable causing reset_xps_queues /
> set_xps_queue to be called several times. The xps_needed count would get
> out of sync and eventually the above-mentioned crash would occur.
>
> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
I posted another patchset recently (commits f28c020fb488 and
867d0ad476db in the "net" tree) for issues in XPS, including broken
xps_needed accounting, so your patch won't apply to David's "net"
tree. Could you try it with your use case, and if you still see
issues, fix them on top? You can grab the latest net tree here:
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
Thanks,
--
Sabrina
next prev parent reply other threads:[~2018-12-07 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 10:16 [PATCH] net: Fix xps_needed inc/dec mismatch Ross Lagerwall
2018-12-07 11:01 ` Sabrina Dubroca [this message]
2018-12-07 15:15 ` Ross Lagerwall
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=20181207110114.GA3378@bistromath.localdomain \
--to=sd@queasysnail.net \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ross.lagerwall@citrix.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).