From: Chengming Zhou <zhouchengming@bytedance.com>
To: Changhui Zhong <czhong@redhat.com>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [bug report] WARNING: CPU: 12 PID: 51497 at block/mq-deadline.c:679 dd_exit_sched+0xd5/0xe0
Date: Mon, 21 Aug 2023 10:35:57 +0800 [thread overview]
Message-ID: <f0c0937f-485c-d317-8bd9-b7d32ace4e1f@bytedance.com> (raw)
In-Reply-To: <CAGVVp+VRcQs1qvsEeKyvmOXz=8KTybHpNDAwS9GzVMVw+FvTUg@mail.gmail.com>
On 2023/8/21 10:17, Changhui Zhong wrote:
> On Mon, Aug 21, 2023 at 9:56 AM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> On 8/20/23 7:43 PM, Changhui Zhong wrote:
>>> Hello,
>>>
>>> triggered below warning issue with branch 'block-6.5',
>>
>> What sha? Please always include that in bug reports, people don't know
>> when you pulled it.
>>
>
> ok,I pulled the whole branch of block-6.5, I don't know which patch
> caused the issue，the HEAD is：
Hi, this problem should be fixed in the latest block-6.5 branch,
specifically including this commit:
commit e5c0ca13659e9d18f53368d651ed7e6e433ec1cf
blk-mq: release scheduler resource when request completes
Could you please help to check again?
Thanks!
next prev parent reply other threads:[~2023-08-21 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 1:43 [bug report] WARNING: CPU: 12 PID: 51497 at block/mq-deadline.c:679 dd_exit_sched+0xd5/0xe0 Changhui Zhong
2023-08-21 1:56 ` Jens Axboe
2023-08-21 2:17 ` Changhui Zhong
2023-08-21 2:24 ` Jens Axboe
2023-08-21 2:35 ` Chengming Zhou [this message]
2023-08-21 3:08 ` Changhui Zhong
2023-08-21 9:32 ` Changhui Zhong
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=f0c0937f-485c-d317-8bd9-b7d32ace4e1f@bytedance.com \
--to=zhouchengming@bytedance.com \
--cc=axboe@kernel.dk \
--cc=czhong@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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