From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
John Garry <john.g.garry@oracle.com>,
Greg KH <gregkh@linuxfoundation.org>,
Sagar Biradar <sagar.biradar@microchip.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Adaptec OEM Raid Solutions <aacraid@microsemi.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>, Hannes Reinecke <hare@suse.de>,
scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Gilbert Wu <gilbert.wu@microchip.com>
Subject: Re: scsi regression that after months is still not addressed and now bothering 6.1.y users, too
Date: Tue, 21 Nov 2023 08:05:20 -0500 [thread overview]
Message-ID: <18b3745d3e5de2ffd9b74f9cc826c2c3235dc6ca.camel@HansenPartnership.com> (raw)
In-Reply-To: <a3ddbd03-7a94-4b6a-9be1-b268ce883551@leemhuis.info>
On Tue, 2023-11-21 at 13:24 +0100, Linux regression tracking (Thorsten
Leemhuis) wrote:
> On 21.11.23 12:30, John Garry wrote:
[...]
> > Is there a full kernel log for this hanging system?
> >
> > I can only see snippets in the ticket.
> >
> > And what does /sys/class/scsi_host/host*/nr_hw_queues show?
>
> Sorry, I'm just the man-in-the-middle: you need to ask in the ticket,
> as the privacy policy for bugzilla.kernel.org does not allow to CC
> the reporters from the ticket here without their consent.
How did you arrive at that conclusion? Tickets for linux-scsi are
vectored to the list:
https://lore.kernel.org/linux-scsi/bug-217599-11613@https.bugzilla.kernel.org%2F/
So all the email addresses in the bugzilla are already archived on our
list.
James
next prev parent reply other threads:[~2023-11-21 13:05 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 [this message]
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
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=18b3745d3e5de2ffd9b74f9cc826c2c3235dc6ca.camel@HansenPartnership.com \
--to=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=martin.petersen@oracle.com \
--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 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.