linux-kernel - Re: [syzbot] [btrfs?] BUG: MAX_LOCKDEP_CHAIN

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: <2fx4cek7oejg72jbsd77fl7bzibd4of7zgzvucpufqac3chmhv@ag6fl2kk2md2>
Date: Sun, 14 Jul 2024 16:00:34 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: syzbot <syzbot+d79987254280f6484dd2@...kaller.appspotmail.com>
Cc: bfoster@...hat.com, clm@...com, dsterba@...e.com, josef@...icpanda.com, 
	linux-bcachefs@...r.kernel.org, linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [btrfs?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (5)

The issue here is that bcachefs can lock many more btree nodes 
simultaneously, more than lockdep can track. The fix is to switch to a
single lockdep map in the btree_trans for "we have any btree nodes
lock"; it's going in this merge window.

#syz fix: bcachefs: Add lockdep support for btree node locks