lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CO1PR11MB5089695CB3733F4B1284E3CED6EE9@CO1PR11MB5089.namprd11.prod.outlook.com> Date: Fri, 15 Apr 2022 18:31:51 +0000 From: "Keller, Jacob E" <jacob.e.keller@...el.com> To: ivecera <ivecera@...hat.com>, "Fijalkowski, Maciej" <maciej.fijalkowski@...el.com> CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Fei Liu <feliu@...hat.com>, "moderated list:INTEL ETHERNET DRIVERS" <intel-wired-lan@...ts.osuosl.org>, mschmidt <mschmidt@...hat.com>, "Brett Creeley" <brett.creeley@...el.com>, open list <linux-kernel@...r.kernel.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() > -----Original Message----- > From: Ivan Vecera <ivecera@...hat.com> > Sent: Friday, April 15, 2022 9:39 AM > To: Fijalkowski, Maciej <maciej.fijalkowski@...el.com> > Cc: netdev@...r.kernel.org; Fei Liu <feliu@...hat.com>; moderated list:INTEL > ETHERNET DRIVERS <intel-wired-lan@...ts.osuosl.org>; mschmidt > <mschmidt@...hat.com>; Brett Creeley <brett.creeley@...el.com>; open list > <linux-kernel@...r.kernel.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() > > On Fri, 15 Apr 2022 13:55:02 +0200 > Maciej Fijalkowski <maciej.fijalkowski@...el.com> 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? > > Well, that commit were already tested and now it is present in Tony's queue > but not in upstream yet. It is not problem to squash together but the first > was about ignored VF messages and this one is about race and I didn't want > to make single patch with huge description that cover both issues. > But as I said, no problem to squash if needed. > > Thx, > Ivan I'm fine with either squashing or keeping them as separate changes.
Powered by blists - more mailing lists