All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, netdev@vger.kernel.org, ivecera@redhat.com,
	horms@kernel.org, rafal.romanowski@intel.com
Subject: Re: [PATCH net] i40e: Do not allow untrusted VF to remove administratively set MAC
Date: Tue, 13 Feb 2024 01:10:25 +0000	[thread overview]
Message-ID: <170778662561.1111.13664477407499666556.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240208180335.1844996-1-anthony.l.nguyen@intel.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  8 Feb 2024 10:03:33 -0800 you wrote:
> From: Ivan Vecera <ivecera@redhat.com>
> 
> Currently when PF administratively sets VF's MAC address and the VF
> is put down (VF tries to delete all MACs) then the MAC is removed
> from MAC filters and primary VF MAC is zeroed.
> 
> Do not allow untrusted VF to remove primary MAC when it was set
> administratively by PF.
> 
> [...]

Here is the summary with links:
  - [net] i40e: Do not allow untrusted VF to remove administratively set MAC
    https://git.kernel.org/netdev/net/c/73d9629e1c8c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-02-13  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 18:03 [PATCH net] i40e: Do not allow untrusted VF to remove administratively set MAC Tony Nguyen
2024-02-12 18:11 ` Tony Nguyen
2024-02-13  0:37   ` Jakub Kicinski
2024-02-13  0:57     ` Tony Nguyen
2024-02-13  1:10 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31 13:17 Ivan Vecera
2024-02-02 12:43 ` Simon Horman

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=170778662561.1111.13664477407499666556.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=ivecera@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafal.romanowski@intel.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.