From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg()
Date: Fri, 15 Apr 2022 15:53:54 +0200 [thread overview]
Message-ID: <20220415135354.478687-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <YlldsfrRJURXpp5d@boxer>
From: Maciej Fijalkowski <maciej.fijalkowski@intel.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@pensando.io>
Cc: Jacob Keller <jacob.e.keller@intel.com>
>
> >
> > > sent by VF driver but a small race window still left.
--- 8< ---
> > > --
> > > 2.35.1
Al
next prev parent reply other threads:[~2022-04-15 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 7:22 [Intel-wired-lan] [PATCH net] ice: Protect vf_state check by cfg_lock in ice_vc_process_vf_msg() Ivan Vecera
2022-04-15 11:55 ` Maciej Fijalkowski
2022-04-15 11:57 ` Maciej Fijalkowski
2022-04-15 13:53 ` Alexander Lobakin [this message]
2022-04-15 20:55 ` Tony Nguyen
2022-04-16 11:30 ` Ivan Vecera
2022-04-18 18:10 ` Tony Nguyen
2022-04-19 14:23 ` Ivan Vecera
2022-04-15 16:38 ` Ivan Vecera
2022-04-15 18:31 ` Keller, Jacob E
2022-04-15 20:53 ` Tony Nguyen
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=20220415135354.478687-1-alexandr.lobakin@intel.com \
--to=alexandr.lobakin@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox