All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chris Rankin <rankincj@gmail.com>
Cc: Linux Stable <stable@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6.8 000/143] 6.8.6-rc1 review
Date: Thu, 11 Apr 2024 13:19:46 +0200	[thread overview]
Message-ID: <2024041125-surgery-pending-cd06@gregkh> (raw)
In-Reply-To: <CAK2bqV+kpG5cm5py24TusikZYO=_vWg7CVEN3oTywVhnq1mhjQ@mail.gmail.com>

On Thu, Apr 11, 2024 at 11:38:36AM +0100, Chris Rankin wrote:
> The SCSI sg driver oopsed on my 6.8.4 kernel, and I noticed that a
> patch (presumably) to fix this was pulled from 6.8.5. However, I also
> noticed this email:

Was that a warning or a real crash?

> >> Reverted this patch and I couldn't see the reposted warning.
> >> scsi: sg: Avoid sg device teardown race
> >> [ Upstream commit 27f58c04a8f438078583041468ec60597841284d ]
> >
> > Fix is here:
> >
> > https://git.kernel.org/mkp/scsi/c/d4e655c49f47
> 
> Is this unsuitable for 6.8.6 please?

Is it in Linus's tree yet?

thanks,

greg k-h

  reply	other threads:[~2024-04-11 11:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 10:38 [PATCH 6.8 000/143] 6.8.6-rc1 review Chris Rankin
2024-04-11 11:19 ` Greg KH [this message]
2024-04-11 11:33   ` Chris Rankin
2024-04-11 11:48     ` Greg KH
2024-04-11 12:08     ` Fwd: " Chris Rankin
2024-04-11 12:22       ` Martin K. Petersen
2024-04-12  2:09         ` Martin K. Petersen
2024-04-12  8:27           ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2024-04-11  9:54 Greg Kroah-Hartman
2024-04-11 15:38 ` Justin Forbes
2024-04-11 18:17 ` SeongJae Park
2024-04-11 19:34 ` Holger Hoffstätte
2024-04-12  8:26   ` Greg Kroah-Hartman
2024-04-11 20:36 ` Ronald Warsow
2024-04-11 22:07 ` Florian Fainelli
2024-04-11 23:38 ` Shuah Khan
2024-04-12  1:32 ` Bagas Sanjaya
2024-04-12  7:19 ` Ron Economos
2024-04-12  8:08 ` Jon Hunter
2024-04-12 18:21 ` Naresh Kamboju

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=2024041125-surgery-pending-cd06@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rankincj@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.