From: David Sterba <dsterba@suse.cz>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+b2869947e0c9467a41b6@syzkaller.appspotmail.com>,
clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [syzbot] [btrfs?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (4)
Date: Mon, 23 Oct 2023 16:36:37 +0200 [thread overview]
Message-ID: <20231023143637.GI26353@suse.cz> (raw)
In-Reply-To: <CANp29Y4VNqAX0oPiGy557ubwQKjhWVbwjT7xdCBGLricJPJ5Yg@mail.gmail.com>
On Mon, Oct 23, 2023 at 03:30:16PM +0200, Aleksandr Nogikh wrote:
> On Mon, Oct 23, 2023 at 3:15 PM David Sterba <dsterba@suse.cz> wrote:
> >
> > On Sat, Oct 21, 2023 at 07:40:53PM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit: 78124b0c1d10 Merge branch 'for-next/core' into for-kernelci
> > > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=1557da89680000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=f27cd6e68911e026
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=b2869947e0c9467a41b6
> > > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> > > userspace arch: arm64
> > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137ac45d680000
> > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e4640b680000
> > >
> > > Downloadable assets:
> > > disk image: https://storage.googleapis.com/syzbot-assets/bd512de820ae/disk-78124b0c.raw.xz
> > > vmlinux: https://storage.googleapis.com/syzbot-assets/a47a437b1d4f/vmlinux-78124b0c.xz
> > > kernel image: https://storage.googleapis.com/syzbot-assets/3ae8b966bcd7/Image-78124b0c.gz.xz
> > > mounted in repro: https://storage.googleapis.com/syzbot-assets/d5d514495f15/mount_0.gz
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+b2869947e0c9467a41b6@syzkaller.appspotmail.com
> > >
> > > BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
> >
> > #syz invalid
> >
> > This is a frequent warning, can be worked around by increasing
> > CONFIG_LOCKDEP_CHAINS_BITS in config (18 could be a good value but may
> > still not be enough).
>
> By invalidating a frequently occurring issue we only cause syzbot to
> report it once again, so it's better to keep the report open until the
> root cause is resolved. There'll likely be a report (5) soon.
The root cause is somewhere in lockdep and not easy to fix so we'll have
to see the duplicate reports or
> We keep CONFIG_LOCKDEP_CHAINS_BITS at 16 for arm64 because (at least
> in 2022) the kernel used not to boot on GCE arm64 VMs with
> CONFIG_LOCKDEP_CHAINS_BITS=18. Maybe it's time to try it once more.
yeah, you can increase the config value.
prev parent reply other threads:[~2023-10-23 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 2:40 [syzbot] [btrfs?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (4) syzbot
2023-10-23 13:08 ` David Sterba
2023-10-23 13:30 ` Aleksandr Nogikh
2023-10-23 14:36 ` David Sterba [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231023143637.GI26353@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dvyukov@google.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+b2869947e0c9467a41b6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).