archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Greg KH <>,
	Sagar Biradar <>,
	James Bottomley <>,
	"Martin K. Petersen" <>,
	Adaptec OEM Raid Solutions <>
Cc: "" <>,
	Sasha Levin <>,
	Linux kernel regressions list <>,
	Hannes Reinecke <>, scsi <>,
	LKML <>,
	Gilbert Wu <>,
	John Garry <>
Subject: Re: scsi regression that after months is still not addressed and now bothering 6.1.y users, too
Date: Tue, 21 Nov 2023 10:57:00 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 21.11.23 10:50, Thorsten Leemhuis wrote:
> * @SCSI maintainers: could you please look into below please?
> * @Stable team: you might want to take a look as well and consider a
> revert in 6.1.y (yes, I know, those are normally avoided, but here it
> might make sense).
> TLDR: I noticed a regression (Adaptec 71605z with aacraid sometimes
> hangs for a while) that was reported months ago already but is still not
> fixed. Not only that, it apparently more and more users run into this
> recently, as the culprit was recently integrated into 6.1.y; I wonder if
> it would be best to revert it there, unless a fix for mainline comes
> into reach soon.
> Details:
> Quite a few machines with Adaptec controllers seems to hang for a few
> tens of seconds to a few minutes before things start to work normally
> again for a while:

Quick follow up, only saw this now while posting something to the
ticket: according to one reporter the problem even causes data damage.
To quote:

if you run fsck.ext4 on ext4 file system with buggy kernel it will
damage file system and its data

using buggy kernel BTRFS scrub also says that checksums are wrong

Ciao, Thorsten

> That problem is apparently caused by 9dc704dcc09eae ("scsi: aacraid:
> Reply queue mapping to CPUs based on IRQ affinity") [v6.4-rc7]. That
> commit despite a warning of mine to Sasha recently made it into 6.1.53
> -- and that way apparently recently reached more users recently, as
> quite a few joined that ticket.
> The culprit is authored by Sagar Biradar who unless I missed something
> never replied even once to the ticket or earlier mails about it. Lore
> has no messages from him since early June.
> Hannes Reinecke at least tried to fix it a few weeks ago (many thx), but
> that didn't work out (see the ticket for details). Since then things
> look stalled again, which is, ehh, unfortunate when it comes to
> regressions.
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> If I did something stupid, please tell me, as explained on that page.

  reply	other threads:[~2023-11-21  9:57 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).