From: Or Gerlitz <gerlitz.or@gmail.com>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
David Miller <davem@davemloft.net>,
"Greenwalt, Paul" <paul.greenwalt@intel.com>,
Linux Netdev List <netdev@vger.kernel.org>,
"nhorman@redhat.com" <nhorman@redhat.com>,
"sassmann@redhat.com" <sassmann@redhat.com>,
"jogreene@redhat.com" <jogreene@redhat.com>
Subject: Re: [net-next v2 6/6] ixgbe: Add malicious driver detection support
Date: Wed, 28 Jun 2017 17:28:59 +0300 [thread overview]
Message-ID: <CAJ3xEMgAOMM3g0sqc6AfWLWf_VKwuHQGh_ZSYfmeQg=JotGbbg@mail.gmail.com> (raw)
In-Reply-To: <87618083B2453E4A8714035B62D67992B3E89F1D@FMSMSX105.amr.corp.intel.com>
On Wed, Jun 28, 2017 at 1:14 AM, Tantilov, Emil S
<emil.s.tantilov@intel.com> wrote:
> Mainly because I am not sure that other (non-Intel) drivers will benefit from
> such an option. In normal operation this functionality should not cause issues
> and if it doesn't we may be able to deprecate the private flag in the future.
If you think this functionality makes sense any driver running over HW
implementing
it would like to be able to expose that and hence you better not use
private flag.
Are we sure the trust UAPI can't be extended for that matter?
next prev parent reply other threads:[~2017-06-28 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 8:51 [net-next v2 0/6][pull request] 10GbE Intel Wired LAN Driver Updates 2017-06-27 Jeff Kirsher
2017-06-27 8:51 ` [net-next v2 1/6] ixgbe: Ensure MAC filter was added before setting MACVLAN Jeff Kirsher
2017-06-27 8:51 ` [net-next v2 2/6] ixgbe: Enable LASI interrupts for X552 devices Jeff Kirsher
2017-06-27 8:51 ` [net-next v2 3/6] ixgbe: Update NW_MNG_IF_SEL support for X553 Jeff Kirsher
2017-06-27 8:51 ` [net-next v2 4/6] ixgbe: Do not support flow control autonegotiation " Jeff Kirsher
2017-06-27 8:51 ` [net-next v2 5/6] ixgbe: Disable flow control for XFI Jeff Kirsher
2017-06-27 8:51 ` [net-next v2 6/6] ixgbe: Add malicious driver detection support Jeff Kirsher
2017-06-27 9:07 ` Or Gerlitz
2017-06-27 20:59 ` Tantilov, Emil S
2017-06-27 21:07 ` Or Gerlitz
2017-06-27 22:14 ` Tantilov, Emil S
2017-06-28 14:28 ` Or Gerlitz [this message]
2017-06-29 18:28 ` David Miller
2017-06-29 21:19 ` Tantilov, Emil S
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='CAJ3xEMgAOMM3g0sqc6AfWLWf_VKwuHQGh_ZSYfmeQg=JotGbbg@mail.gmail.com' \
--to=gerlitz.or@gmail.com \
--cc=davem@davemloft.net \
--cc=emil.s.tantilov@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=paul.greenwalt@intel.com \
--cc=sassmann@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.