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]
Message-Id: <C2EE930A-5B60-4DB7-861A-3CE836560E94@m.fudan.edu.cn>
Date: Sun, 12 Jan 2025 00:34:42 +0800
From: Kun Hu <huk23@...udan.edu.cn>
To: Namjae Jeon <linkinjeon@...nel.org>
Cc: sj1557.seo@...sung.com,
 yuezhang.mo@...y.com,
 linux-fsdevel@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 "jjtan24@...udan.edu.cn" <jjtan24@...udan.edu.cn>
Subject: Re: Bug: soft lockup in exfat_clear_bitmap


> Please try to reproduce it with linux-next or the latest Linus tree.


Hi Namjae,

We have reproduced this issue in v6.13-rc6 and obtained a new crash log. The links are provided below:

Crash log: https://drive.google.com/file/d/1qUmBfpcGeDMHsqBjurhymaH43Jnbvt-F/view?usp=sharing

It seems that the new report highlights additional issues beyond the original one. While both involve exfat_clear_bitmap and __exfat_free_cluster, the new report indicates broader impacts, such as multiple CPUs encountering soft lockups, resource contention across threads, and potential conflicts with the sanitizer_cov_trace_pcinstrumentation. These suggest that the underlying issue might extend beyond simple bitmap management to systemic resource handling flaws in the exFAT module.

Could you please help to check the cause of the issue?

Thanks,
Kun Hu




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ