From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: stable@vger.kernel.org
Subject: Re: [6.12.y] WARNING: CPU: 0 PID: 681 at block/blk-mq-cpumap.c:90 blk_mq_map_hw_queues+0xcf/0xe0
Date: Mon, 5 May 2025 11:24:51 +0200 [thread overview]
Message-ID: <2025050500-unchain-tricking-a90e@gregkh> (raw)
In-Reply-To: <20250503100528.C7F9.409509F4@e16-tech.com>
On Sat, May 03, 2025 at 10:05:29AM +0800, Wang Yugui wrote:
> Hi,
> Cc: Greg Kroah-Hartman
>
> > Hi,
> >
> > I noticed a WARNING in recent 6.12.y kernel.
> >
> > This WARNING happen on 6.12.26/6.12.25, but not happen on 6.12.20.
> >
> > More bisect job need to be done, but reporti it firstly.
> >
> > [ 13.288365] ------------[ cut here ]------------
> > [ 13.288366] WARNING: CPU: 0 PID: 681 at block/blk-mq-cpumap.c:90 blk_mq_map_hw_queues+0xcf/0xe0
> > void blk_mq_map_hw_queues(struct blk_mq_queue_map *qmap,
> > struct device *dev, unsigned int offset)
> > {
> > ...
> > ...
> > fallback:
> > L90: WARN_ON_ONCE(qmap->nr_queues > 1);
> > blk_mq_clear_mq_map(qmap);
> > }
> >
>
> The following patch fixed this WARNING.
>
> From a9ae6fe1c319c4776c2b11e85e15109cd3f04076 Mon Sep 17 00:00:00 2001
> From: Daniel Wagner <wagi@kernel.org>
> Date: Thu, 23 Jan 2025 14:08:29 +0100
> Subject: [PATCH] blk-mq: create correct map for fallback case
>
> please pull it to 6.12.y.
But the commit that this one says it fixes is NOT in the 6.12.y tree.
So why would this commit fix the issue?
And why haven't you cc:ed the authors involved in these changes?
confused,
greg k-h
next prev parent reply other threads:[~2025-05-05 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 1:14 [6.12.y] WARNING: CPU: 0 PID: 681 at block/blk-mq-cpumap.c:90 blk_mq_map_hw_queues+0xcf/0xe0 Wang Yugui
2025-05-03 2:05 ` Wang Yugui
2025-05-05 9:24 ` Greg Kroah-Hartman [this message]
2025-05-05 11:36 ` Jack Wang
2025-05-05 13:28 ` Greg KH
2025-05-05 13:40 ` Daniel Wagner
2025-05-05 13:52 ` Greg KH
2025-05-05 14:05 ` Daniel Wagner
2025-05-05 14:21 ` Greg KH
2025-05-05 13:41 ` Jinpu Wang
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=2025050500-unchain-tricking-a90e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=wangyugui@e16-tech.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