linux-kernel - Re: Bug: INFO_ task hung in lock_two

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: <D732181A-26A9-4D11-9B2F-FE0CEC18A6D1@m.fudan.edu.cn>
Date: Tue, 14 Jan 2025 10:54:36 +0800
From: Kun Hu <huk23@...udan.edu.cn>
To: Jan Kara <jack@...e.cz>
Cc: jlayton@...hat.com,
 tytso@....edu,
 adilger.kernel@...ger.ca,
 david@...morbit.com,
 bfields@...hat.com,
 viro@...iv.linux.org.uk,
 christian.brauner@...ntu.com,
 hch@....de,
 linux-fsdevel@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 brauner@...nel.org,
 linux-bcachefs@...r.kernel.org,
 Kent Overstreet <kent.overstreet@...ux.dev>
Subject: Re: Bug: INFO_ task hung in lock_two_nondirectories

> 
> 
> Hello!
> 
> First I'd note that the list of recipients of this report seems somewhat
> arbitrary. linux-kernel & linux-fsdevel makes sense but I'm not sure how
> you have arrived at the list of other persons you have CCed :). I have to
> say syzbot folks have done a pretty good job at implementing mechanisms how
> to determine recipients of the reports (as well as managing existing
> reports over the web / email). Maybe you could take some inspiration there
> or just contribute your syzkaller modifications to syzbot folks so that
> your reports can benefit from all the other infrastructure they have?
> 
> Anyway, in this particular case, based on locks reported by lockdep, the
> problem seems to be most likely somewhere in bcachefs. Added relevant CCs.


Hi Jan,

Thank you very much for your feedback. The current method of determining recipients is indeed less structured than syzbot`s mechanism, and we have only improved the method of generating the seed, and have not yet entered very much into understanding his infrastructure. We will definitely consider taking our approach from `syzbot` and not have this problem next time.

Thanks for pointing out that it may have originated from `bcachefs`.

————
Kun Hu