linux-kernel - Re: [Linux kernel bug] INFO: task hung in blk_mq_get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a15774ef-1c18-4604-af10-44d458e3207a@I-love.SAKURA.ne.jp>
Date: Mon, 13 May 2024 23:16:46 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Sam Sun <samsun1006219@...il.com>, Hillf Danton <hdanton@...a.com>
Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org, axboe@...nel.dk,
        syzkaller-bugs@...glegroups.com, xrivendell7@...il.com
Subject: Re: [Linux kernel bug] INFO: task hung in blk_mq_get_tag

On 2024/05/13 21:57, Sam Sun wrote:
> On Mon, May 13, 2024 at 6:54 PM Hillf Danton <hdanton@...a.com> wrote:
>>
>> On Mon, 13 May 2024 10:38:34 +0800 Sam Sun <samsun1006219@...il.com>
>>> Dear developers and maintainers,
>>>
>>> We encountered a task hung in function blk_mq_get_tag. It was tested
>>> against the latest upstream kernel which was compiled by clang 14.

Did you confirm that the task hung messages continue forever
even after you terminated the reproducer when the task hung
message started?

If the task hung messages stop after you terminated the reproducer,
it is possible that this is just a problem of over-stressing.

If the task hung messages continue forever even after you terminated
the reproducer, collecting stacktraces of all lock holders using
https://lkml.kernel.org/r/77e32fdc-3f63-e124-588e-7d60dd66fc9a@I-love.SAKURA.ne.jp
might be helpful.

Please be sure to run

  # echo 0 > /proc/sys/kernel/hung_task_panic
  # echo -1 > /proc/sys/kernel/hung_task_warnings

before starting the reproducer, for by default hung_task_warnings
prints only up to 10 times (i.e. has a risk of misjudging that the
problem disappeared).