From: Hillf Danton <hdanton@sina.com>
To: Sam Sun <samsun1006219@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
axboe@kernel.dk,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
syzkaller-bugs@googlegroups.com, xrivendell7@gmail.com
Subject: Re: [Linux kernel bug] INFO: task hung in blk_mq_get_tag
Date: Tue, 14 May 2024 18:37:42 +0800 [thread overview]
Message-ID: <20240514103742.3137-1-hdanton@sina.com> (raw)
In-Reply-To: <CAEkJfYMhv8AxxHSVdPT9bCX1cJZXw39+bMFh=2N9uNOB4Hcr=w@mail.gmail.com>
On Tue, 14 May 2024 10:05:21 +0800 Sam Sun <samsun1006219@gmail.com>
> On Tue, May 14, 2024 at 6:54 AM Hillf Danton <hdanton@sina.com> wrote:
> > On Mon, 13 May 2024 20:57:44 +0800 Sam Sun <samsun1006219@gmail.com>
> > >
> > > I applied this patch and tried using the C repro, but it still crashed
> > > with the same task hang kernel dump log.
> >
> > Oh low-hanging pear is sour, and try again seeing if there is missing
> > wakeup due to wake batch.
> >
> > --- x/lib/sbitmap.c
> > +++ y/lib/sbitmap.c
> > @@ -579,6 +579,8 @@ void sbitmap_queue_wake_up(struct sbitma
> > unsigned int wake_batch = READ_ONCE(sbq->wake_batch);
> > unsigned int wakeups;
> >
> > + __sbitmap_queue_wake_up(sbq, nr);
> > +
> > if (!atomic_read(&sbq->ws_active))
> > return;
> >
> > --
>
> I applied this patch together with the last patch. Unfortunately it
> still crashed.
After two rounds of test, what is clear now so far is -- it is IOs
in flight that caused the task hung reported, though without spotting
why they failed to complete within 120 seconds.
>
> Pointed out by Tetsuo, this kernel panic might be caused by sending
> NMI between cpus. As dump log shows:
> ```
> [ 429.046960][ T32] NMI backtrace for cpu 0
> [ 429.047499][ T32] CPU: 0 PID: 32 Comm: khungtaskd Not tainted 6.9.0-dirty #6
> [ 429.048417][ T32] Hardware name: QEMU Standard PC (i440FX + PIIX,
> 1996), BIOS rel-1.16.1-0-g3208b098f51a-prebuilt.qemu.org 04/01/2014
> [ 429.049873][ T32] Call Trace:
> [ 429.050299][ T32] <TASK>
> [ 429.050672][ T32] dump_stack_lvl+0x201/0x300
> ...
> [ 429.063133][ T32] ret_from_fork_asm+0x11/0x20
> [ 429.063735][ T32] </TASK>
> [ 429.064168][ T32] Sending NMI from CPU 0 to CPUs 1:
> [ 429.064833][ T32] BUG: unable to handle page fault for address:
> ffffffff813d4cf1
Given many syzbot reports without gpf like this one, I have difficulty
understanding it. If it is printed after task hung detected, it should
be a seperate issue.
> [ 429.065765][ T32] #PF: supervisor write access in kernel mode
> [ 429.066502][ T32] #PF: error_code(0x0003) - permissions violation
> [ 429.067274][ T32] PGD db38067 P4D db38067 PUD db39063 PMD 12001a1
> [ 429.068068][ T32] Oops: 0003 [#1] PREEMPT SMP KASAN NOPTI
> [ 429.068767][ T32] CPU: 0 PID: 32 Comm: khungtaskd Not tainted
> 6.9.0-dirty #6
> [ 429.069666][ T32] Hardware name: QEMU Standard PC (i440FX + PIIX,
> 1996), BIOS rel-1.16.1-0-g3208b098f51a-prebuilt.qemu.org 04/01/2014
> [ 429.071142][ T32] RIP: 0010:__send_ipi_mask+0x541/0x690
next prev parent reply other threads:[~2024-05-14 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 2:38 [Linux kernel bug] INFO: task hung in blk_mq_get_tag Sam Sun
2024-05-13 10:54 ` Hillf Danton
2024-05-13 12:57 ` Sam Sun
2024-05-13 14:16 ` Tetsuo Handa
2024-05-13 14:49 ` Sam Sun
2024-05-13 22:54 ` Hillf Danton
2024-05-14 2:05 ` Sam Sun
2024-05-14 7:39 ` Tetsuo Handa
2024-05-14 10:37 ` Hillf Danton [this message]
2024-05-14 12:07 ` Sam Sun
2024-05-14 14:45 ` Tetsuo Handa
2024-05-15 12:46 ` Sam Sun
2024-05-15 13:12 ` Tetsuo Handa
2024-05-14 22:41 ` Hillf Danton
2024-05-15 10:13 ` Tetsuo Handa
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=20240514103742.3137-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=samsun1006219@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xrivendell7@gmail.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