[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230314134357.GH36557@unreal>
Date: Tue, 14 Mar 2023 15:43:57 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, netdev@...r.kernel.org,
Jacob Keller <jacob.e.keller@...el.com>,
Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>,
Marek Szlosek <marek.szlosek@...el.com>
Subject: Re: [PATCH net-next 03/14] ice: track malicious VFs in new
ice_mbx_vf_info structure
On Mon, Mar 13, 2023 at 11:21:12AM -0700, Tony Nguyen wrote:
> From: Jacob Keller <jacob.e.keller@...el.com>
>
> Currently the PF tracks malicious VFs in a malvfs bitmap which is used by
> the ice_mbx_clear_malvf and ice_mbx_report_malvf functions. This bitmap is
> used to ensure that we only report a VF as malicious once rather than
> continuously spamming the event log.
I would say that idea that VF is allowed to spam PF is very questionable.
Even with overflow logic.
Thanks
Powered by blists - more mailing lists