From: James Bottomley <jejb@linux.ibm.com>
To: John Garry <john.g.garry@oracle.com>,
Sagar Biradar <sagar.biradar@microchip.com>,
Don Brace <don.brace@microchip.com>,
Gilbert Wu <gilbert.wu@microchip.com>,
linux-scsi@vger.kernel.org,
Martin Petersen <martin.petersen@oracle.com>,
Brian King <brking@linux.vnet.ibm.com>,
stable@vger.kernel.org, Tom White <tom.white@microchip.com>,
regressions@leemhuis.info, hare@suse.com
Subject: Re: [PATCH v4] aacraid: reply queue mapping to CPUs based of IRQ affinity
Date: Thu, 23 Nov 2023 07:51:54 -0500 [thread overview]
Message-ID: <d3ec8bb44e69f1dbc0a0cc31077b5a8e09a277ef.camel@linux.ibm.com> (raw)
In-Reply-To: <c830058d-8d03-4da4-bdd4-0e56c567308f@oracle.com>
On Thu, 2023-11-23 at 12:01 +0000, John Garry wrote:
> On 20/05/2023 00:08, Sagar Biradar wrote:
> > Fix the IO hang that arises because of MSIx vector not
> > having a mapped online CPU upon receiving completion.
> >
> > The SCSI cmds take the blk_mq route, which is setup during the
> > init. The reserved cmds fetch the vector_no from mq_map after the
> > init is complete and before the init, they use 0 - as per the norm.
> >
> > Reviewed-by: Gilbert Wu <gilbert.wu@microchip.com>
> > Signed-off-by: Sagar Biradar <Sagar.Biradar@microchip.com>
>
> This the patch which seems to be causing the issue in
> https://bugzilla.kernel.org/show_bug.cgi?id=217599
>
> I will comment here since I got no response there...
We can still do a clean revert of this commit if no other solution is
found before the end of the 6.7 rc cycle.
Regards,
James
next prev parent reply other threads:[~2023-11-23 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 23:08 [PATCH v4] aacraid: reply queue mapping to CPUs based of IRQ affinity Sagar Biradar
2023-06-08 21:09 ` Sagar.Biradar
2023-06-15 2:15 ` Martin K. Petersen
2023-11-23 12:01 ` John Garry
2023-11-23 12:51 ` James Bottomley [this message]
2023-11-24 6:32 ` Hannes Reinecke
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=d3ec8bb44e69f1dbc0a0cc31077b5a8e09a277ef.camel@linux.ibm.com \
--to=jejb@linux.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=don.brace@microchip.com \
--cc=gilbert.wu@microchip.com \
--cc=hare@suse.com \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=regressions@leemhuis.info \
--cc=sagar.biradar@microchip.com \
--cc=stable@vger.kernel.org \
--cc=tom.white@microchip.com \
/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;
as well as URLs for NNTP newsgroup(s).