[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201123114328.00c0b933@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Mon, 23 Nov 2020 11:43:28 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: drt <drt@...ux.vnet.ibm.com>
Cc: Lijun Pan <ljp@...ux.ibm.com>, netdev@...r.kernel.org,
sukadev@...ux.ibm.com, drt@...ux.ibm.com
Subject: Re: [PATCH net 02/15] ibmvnic: process HMC disable command
On Sun, 22 Nov 2020 07:12:38 -0800 drt wrote:
> On 2020-11-21 15:36, Jakub Kicinski wrote:
> > On Fri, 20 Nov 2020 16:40:36 -0600 Lijun Pan wrote:
> >> From: Dany Madden <drt@...ux.ibm.com>
> >>
> >> Currently ibmvnic does not support the disable vnic command from the
> >> Hardware Management Console. This patch enables ibmvnic to process
> >> CRQ message 0x07, disable vnic adapter.
> >
> > What user-visible problem does this one solve?
> This allows HMC to disconnect a Linux client from the network if the
> vNIC adapter is misbehaving and/or sending malicious traffic. The effect
> is the same as when a sysadmin sets a link down (ibmvnic_close()) on the
> Linux client. This patch extends this ability to the HMC.
Okay, sounds to me like net-next material, then.
IIUC we don't need to fix this ASAP and backport to stable.
Powered by blists - more mailing lists