All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: linux-block <linux-block@vger.kernel.org>
Subject: Re: [bug report] WARNING at block/mq-deadline.c:600 dd_exit_sched+0x1c6/0x260 triggered with blktests block/031
Date: Fri, 26 Nov 2021 10:27:47 +0800	[thread overview]
Message-ID: <YaBGI7bR/9ot514F@T590> (raw)
In-Reply-To: <CAHj4cs8=xDxBZF62-OekAGtHDtP6ynALKXm7fK2D2ChpNXnGAw@mail.gmail.com>

Hi Yi,

On Thu, Nov 25, 2021 at 07:02:43PM +0800, Yi Zhang wrote:
> Hello
> 
> blktests block/031 triggered below WARNING with latest
> linux-block/for-next[1], pls check it.
> 
> [1]
> f0afafc21027 (HEAD, origin/for-next) Merge branch 'for-5.17/io_uring'
> into for-next

After running block/031 for several times in today's linus tree, not
reproduce the issue:

[root@ktest-09 blktests]# uname -a
Linux ktest-09 5.16.0-rc2_up+ #47 SMP PREEMPT Thu Nov 25 21:14:38 EST 2021 x86_64 x86_64 x86_64 GNU/Linux
[root@ktest-09 blktests]# ./check block/031
block/031 (do IO on null-blk with a host tag set)            [passed]
    runtime  30.302s  ...  30.298s

Both for-5.17/block and for-5.17/io_uring have been rebased on v5.16-rc2,
maybe you can try the test again with latest block tree and see if it
can be reproduced.


Thanks, 
Ming


  reply	other threads:[~2021-11-26  2:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 11:02 [bug report] WARNING at block/mq-deadline.c:600 dd_exit_sched+0x1c6/0x260 triggered with blktests block/031 Yi Zhang
2021-11-26  2:27 ` Ming Lei [this message]
     [not found]   ` <CAHj4cs8L0Q0oS2RgNOr+cC55NeALKCYW_BzeFxctWvcrub-iVQ@mail.gmail.com>
2021-11-26  9:10     ` Ming Lei
2021-11-26 16:24   ` Ming Lei
2021-11-26 16:38     ` Jens Axboe
2021-11-27  2:19       ` Yi Zhang

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=YaBGI7bR/9ot514F@T590 \
    --to=ming.lei@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=yi.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.