All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH S34 02/12] i40e: Limit the number of	mac and vlan addresses that can be added for VFs
Date: Mon, 18 Apr 2016 19:03:10 +0000	[thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A0F9D0EFB@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <1460542112-20166-3-git-send-email-harshitha.ramamurthy@intel.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
> Behalf Of Harshitha Ramamurthy
> Sent: Wednesday, April 13, 2016 3:08 AM
> To: intel-wired-lan at osuosl.org
> Subject: [Intel-wired-lan] [next PATCH S34 02/12] i40e: Limit the number of
> mac and vlan addresses that can be added for VFs
> 
> From: Anjali Singhai Jain <anjali.singhai@intel.com>
> 
> If the VF is privileged/trusted it can do as it may please including but not
> limited to hogging resources and playing unfair.
> But if the VF is not privileged/trusted it still can add some number
> (8) of MAC and VLAN addresses.
> Other restrictions with respect to Port VLAN and normal VLAN still apply to
> not privileged/trusted VF.
> 
> Signed-off-by: Anjali Singhai Jain <anjali.singhai@intel.com>
> Change-Id: I3a9529201b184c8873e1ad2e300aff468c9e6296
> ---
> Testing Hints :
> With this a non trusted VF can add up to 8 mac addresses and up to
> (8) vlan addresses if not under port vlan.
> 
>  drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c | 25
> ++++++++++++++++++++--
> drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h |  3 +++
>  2 files changed, 26 insertions(+), 2 deletions(-)

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Untrusted VF successfully limits number of addresses

  reply	other threads:[~2016-04-18 19:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 10:08 [Intel-wired-lan] [next PATCH S34 00/12] i40e/i40evf updates Harshitha Ramamurthy
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 01/12] i40e: Change the default for VFs to be not privileged Harshitha Ramamurthy
2016-04-18 21:21   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 02/12] i40e: Limit the number of mac and vlan addresses that can be added for VFs Harshitha Ramamurthy
2016-04-18 19:03   ` Bowers, AndrewX [this message]
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 03/12] i40e: Prevent falling to promiscuous if the VF is not trusted Harshitha Ramamurthy
2016-04-18 19:06   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 04/12] i40e: Remove HMC AQ API implementation Harshitha Ramamurthy
2016-04-28 15:34   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 05/12] i40e: Flow-based side-band filter count and its use for input set change Harshitha Ramamurthy
2016-04-18 19:43   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 06/12] i40evf: RSS Hash Option parameters Harshitha Ramamurthy
2016-04-27 22:19   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 07/12] i40e: Fix uninitialized variable Harshitha Ramamurthy
2016-04-18 22:01   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 08/12] i40e: ptp - avoid aggregate return warnings Harshitha Ramamurthy
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 09/12] i40e: Use consistent type for vf_id Harshitha Ramamurthy
2016-04-18 22:49   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 10/12] i40e: Drop extra copy of function Harshitha Ramamurthy
2016-04-18 22:50   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 11/12] i40e: Update device ids for X722 Harshitha Ramamurthy
2016-04-18 22:52   ` Bowers, AndrewX
2016-04-13 10:08 ` [Intel-wired-lan] [next PATCH S34 12/12] i40e/i40evf : Bump driver version from 1.5.5 to 1.5.10 Harshitha Ramamurthy
2016-04-18 22:53   ` Bowers, AndrewX

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=26D9FDECA4FBDD4AADA65D8E2FC68A4A0F9D0EFB@ORSMSX104.amr.corp.intel.com \
    --to=andrewx.bowers@intel.com \
    --cc=intel-wired-lan@osuosl.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 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.