From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@qlogic.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] qed: FLR of active VFs might lead to FW assert
Date: Mon, 22 Aug 2016 18:18:48 -0700 (PDT) [thread overview]
Message-ID: <20160822.181848.1467939282286710395.davem@davemloft.net> (raw)
In-Reply-To: <1471856609-8519-1-git-send-email-Yuval.Mintz@qlogic.com>
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
Date: Mon, 22 Aug 2016 12:03:29 +0300
> Driver never bothered marking the VF's vport with the VF's sw_fid.
> As a result, FLR flows are not going to clean those vports.
>
> If the vport was active when FLRed, re-activating it would lead
> to a FW assertion.
>
> Fixes: dacd88d6f6851 ("qed: IOV l2 functionality")
> Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com>
Applied, thanks.
prev parent reply other threads:[~2016-08-23 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 9:03 [PATCH net] qed: FLR of active VFs might lead to FW assert Yuval Mintz
2016-08-23 1:18 ` 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=20160822.181848.1467939282286710395.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Yuval.Mintz@qlogic.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).