From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org, mschmidt@redhat.com
Subject: Re: [PATCH net 0/2] bnx2x: Fix malicious VFs indication
Date: Sat, 10 Jun 2017 16:03:19 -0400 (EDT) [thread overview]
Message-ID: <20170610.160319.846840483652390189.davem@davemloft.net> (raw)
In-Reply-To: <20170609141702.20688-1-Yuval.Mintz@cavium.com>
From: Yuval Mintz <Yuval.Mintz@cavium.com>
Date: Fri, 9 Jun 2017 17:17:00 +0300
> It was discovered that for a VF there's a simple [yet uncommon] scenario
> which would cause device firmware to declare that VF as malicious -
> Add a vlan interface on top of a VF and disable txvlan offloading for
> that VF [causing VF to transmit packets where vlan is on payload].
>
> Patch #1 corrects driver transmission to prevent this issue.
> Patch #2 is a by-product correcting PF behavior once a VF is declared
> malicious.
Series applied, thank you.
prev parent reply other threads:[~2017-06-10 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 14:17 [PATCH net 0/2] bnx2x: Fix malicious VFs indication Yuval Mintz
2017-06-09 14:17 ` [PATCH net 1/2] bnx2x: Allow vfs to disable txvlan offload Yuval Mintz
2017-06-09 14:17 ` [PATCH net 2/2] bnx2x: Don't post statistics to malicious VFs Yuval Mintz
2017-06-10 20:03 ` 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=20170610.160319.846840483652390189.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Yuval.Mintz@cavium.com \
--cc=mschmidt@redhat.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