From: Greg KH <gregkh@linuxfoundation.org>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"Jankowski, Konrad0" <konrad0.jankowski@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF ndo ops
Date: Sat, 5 Mar 2022 14:43:28 +0100 [thread overview]
Message-ID: <YiNpANXX8hi1enjc@kroah.com> (raw)
In-Reply-To: <CO1PR11MB508937A170C114A274CBE809D6019@CO1PR11MB5089.namprd11.prod.outlook.com>
On Mon, Feb 28, 2022 at 08:57:50PM +0000, Keller, Jacob E wrote:
>
>
> > -----Original Message-----
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Monday, February 28, 2022 3:24 AM
> > To: Keller, Jacob E <jacob.e.keller@intel.com>
> > Cc: stable@vger.kernel.org; Brett Creeley <brett.creeley@intel.com>; Jankowski,
> > Konrad0 <konrad0.jankowski@intel.com>; Nguyen, Anthony L
> > <anthony.l.nguyen@intel.com>
> > Subject: Re: [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF
> > ndo ops
> >
> > On Mon, Feb 28, 2022 at 12:10:20PM +0100, Greg KH wrote:
> > > On Fri, Feb 25, 2022 at 12:21:00PM -0800, Jacob Keller wrote:
> > > > From: Brett Creeley <brett.creeley@intel.com>
> > > >
> > > > commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d upstream.
> > > >
> > > > [I had to fix the cherry-pick manually as the patch added a line around
> > > > some context that was missing.]
> > >
> > > What stable tree(s) is this for?$
> >
> > Looks like it applied only to 5.15.y. Can you also provide backports
> > for the other older kernels that these are needed for?
> >
>
> Hi Greg!
>
> I sent a series that should apply from v5.8 through 5.12 (excepting one patch that was already on 5.10 but not the other trees, for some reason). I also sent a series for 5.13 and one for 5.14.
>
> The code prior to 5.8 still has this bug, going back to the first release with ice, (4.20), but it is different enough that I had trouble determining what the correct patch is. Especially for the first patch which is necessary for the later fixes, since it introduces the lock we need. I'm going to spend a bit more time later this evening to see if I can sort it out. If not, we may have to live without the fixes on those trees.
I've applied the 2 missing changes to the 5.10.y tree. The other ones
are all end-of-life, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-05 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 20:21 [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF ndo ops Jacob Keller
2022-02-25 20:21 ` [PATCH 2/2] ice: fix concurrent reset and removal of VFs Jacob Keller
2022-02-28 11:10 ` [PATCH 1/2] ice: Fix race conditions between virtchnl handling and VF ndo ops Greg KH
2022-02-28 11:23 ` Greg KH
2022-02-28 19:13 ` Keller, Jacob E
2022-02-28 20:57 ` Keller, Jacob E
2022-03-05 13:43 ` Greg KH [this message]
2022-03-07 18:38 ` Keller, Jacob E
2022-02-28 19:13 ` Keller, Jacob E
-- strict thread matches above, loose matches on Subject: below --
2022-02-28 20:46 Jacob Keller
2022-03-05 13:40 ` Greg KH
2022-03-07 18:38 ` Keller, Jacob E
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=YiNpANXX8hi1enjc@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anthony.l.nguyen@intel.com \
--cc=jacob.e.keller@intel.com \
--cc=konrad0.jankowski@intel.com \
--cc=stable@vger.kernel.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