From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Sagar Biradar <sagar.biradar@microchip.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Hannes Reinecke <hare@suse.de>, scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Gilbert Wu <gilbert.wu@microchip.com>,
John Garry <john.g.garry@oracle.com>
Subject: Re: scsi regression that after months is still not addressed and now bothering 6.1.y users, too
Date: Fri, 24 Nov 2023 17:44:24 -0500 [thread overview]
Message-ID: <yq1cyvywzk5.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <2023112456-disinfect-undoing-b5ef@gregkh> (Greg KH's message of "Fri, 24 Nov 2023 16:25:07 +0000")
Greg,
> I am loath to revert a stable patch that has been there for so long as
> any upgrade will just cause the same bug to show back up. Why can't we
> just revert it in Linus's tree now and I'll take that revert in the
> stable trees as well?
Hannes just posted another tentative patch. I'd prefer an incremental
fix if possible.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-11-24 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 9:50 scsi regression that after months is still not addressed and now bothering 6.1.y users, too Thorsten Leemhuis
2023-11-21 9:57 ` Thorsten Leemhuis
2023-11-21 11:30 ` John Garry
2023-11-21 12:24 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-21 13:05 ` James Bottomley
2023-11-21 13:24 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-21 13:31 ` James Bottomley
2023-11-24 16:25 ` Greg KH
2023-11-24 22:44 ` Martin K. Petersen [this message]
2023-11-25 7:10 ` Thorsten Leemhuis
2023-12-29 20:13 ` Salvatore Bonaccorso
2023-12-30 10:58 ` Greg KH
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=yq1cyvywzk5.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aacraid@microsemi.com \
--cc=gilbert.wu@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sagar.biradar@microchip.com \
--cc=sashal@kernel.org \
--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