[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18b3745d3e5de2ffd9b74f9cc826c2c3235dc6ca.camel@HansenPartnership.com>
Date: Tue, 21 Nov 2023 08:05:20 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Linux regressions mailing list <regressions@...ts.linux.dev>,
John Garry <john.g.garry@...cle.com>,
Greg KH <gregkh@...uxfoundation.org>,
Sagar Biradar <sagar.biradar@...rochip.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Adaptec OEM Raid Solutions <aacraid@...rosemi.com>
Cc: "stable@...r.kernel.org" <stable@...r.kernel.org>,
Sasha Levin <sashal@...nel.org>,
Hannes Reinecke <hare@...e.de>,
scsi <linux-scsi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Gilbert Wu <gilbert.wu@...rochip.com>
Subject: Re: scsi regression that after months is still not addressed and
now bothering 6.1.y users, too
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
Powered by blists - more mailing lists