linux-kernel - Re: [linux] [5.19.0] task hung for indefinite time with call traces when rebooted with Kexec

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] [day] [month] [year] [list]

Date:   Thu, 18 Aug 2022 19:20:08 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:     Tasmiya Nalatwad <tasmiya@...ux.vnet.ibm.com>
Cc:     abdhalee@...ux.vnet.ibm.com, mputtash@...ux.vnet.com,
        sachinp@...ux.vnet.com, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [linux] [5.19.0] task hung for indefinite time with call traces
 when rebooted with Kexec

Please check https://elinux.org/images/1/14/Linuxkerneldebugging.pdf for example.

e.g. ./scripts/faddr2line vmlinux scsi_remove_target+0x314/0x390

On 2022/08/18 18:43, Tasmiya Nalatwad wrote:
> Please find the location in source code from where i am seeing the call traces generating
> 
> On 8/6/22 15:30, Tetsuo Handa wrote:
>> On 2022/08/05 15:54, Tasmiya Nalatwad wrote:
>>> Greetings,
>>>
>>> [linux] [5.19.0] task hung for indefinite time with call traces when rebooted with Kexec, A restart is required to recover the machine.
>>
>> kexec is waiting for workqueues ("kworker/3:1" and "kworker/3:0") to complete.
>> If this problem happens only when rebooting with kexec, something in kexec path
>> might be preventing these workqueues from completing.
>>
>> Anyway, please repost with locations in source code like syzbot report does.