linux-ext4 - Re: [syzbot] possible deadlock in jbd2_journal_lock

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: <d30f4e74-aa75-743d-3c89-80ec61d67c6c@linux.microsoft.com>
Date:   Fri, 21 Oct 2022 12:23:41 +0200
From:   Thilo Fromm <t-lo@...ux.microsoft.com>
To:     Jan Kara <jack@...e.cz>
Cc:     Ye Bin <yebin10@...wei.com>, jack@...e.com, tytso@....edu,
        linux-ext4@...r.kernel.org, regressions@...ts.linux.dev,
        Jeremi Piotrowski <jpiotrowski@...ux.microsoft.com>
Subject: Re: [syzbot] possible deadlock in jbd2_journal_lock_updates

Hello Honza,

>> Just want to make sure this does not get lost - as mentioned earlier,
>> reverting 51ae846cff5 leads to a kernel build that does not have this issue.
> 
> Yes, I'm aware of this and still cannot quite wrap my head how it could be
> given the stacktraces I see :) They do not seem to come anywhere near that
> code...

Just reaching out to let folks know that we see more reports on this 
issue coming in for kernels >=5.15.63, see 
https://github.com/flatcar/Flatcar/issues/847#issuecomment-1286523602.

Best regards,
Thilo