[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220415135354.478687-1-alexandr.lobakin@intel.com>
Date: Fri, 15 Apr 2022 15:53:54 +0200
From: Alexander Lobakin <alexandr.lobakin@...el.com>
To: Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Cc: Alexander Lobakin <alexandr.lobakin@...el.com>,
Ivan Vecera <ivecera@...hat.com>,
Jacob Keller <jacob.e.keller@...el.com>,
Fei Liu <feliu@...hat.com>, netdev@...r.kernel.org,
mschmidt@...hat.com, Brett Creeley <brett@...sando.io>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:INTEL ETHERNET DRIVERS"
<intel-wired-lan@...ts.osuosl.org>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg()
From: Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Date: Fri, 15 Apr 2022 13:57:37 +0200
> On Fri, Apr 15, 2022 at 01:55:10PM +0200, Maciej Fijalkowski wrote:
> > On Wed, Apr 13, 2022 at 09:22:59AM +0200, Ivan Vecera wrote:
> > > Previous patch labelled "ice: Fix incorrect locking in
> > > ice_vc_process_vf_msg()" fixed an issue with ignored messages
> >
> > tiny tiny nit: double space after "
> > Also, has mentioned patch landed onto some tree so that we could provide
> > SHA-1 of it? If not, then maybe squashing this one with the mentioned one
> > would make sense?
>
> Again, Brett's Intel address is bouncing, so:
> CC: Brett Creeley <brett@...sando.io>
Cc: Jacob Keller <jacob.e.keller@...el.com>
>
> >
> > > sent by VF driver but a small race window still left.
--- 8< ---
> > > --
> > > 2.35.1
Al
Powered by blists - more mailing lists