From: syzbot <syzbot+9bbbacfbf1e04d5221f7@syzkaller.appspotmail.com>
To: dsterba@suse.cz
Cc: bakmitopiacibubur@boga.indosterling.com, clm@fb.com,
davem@davemloft.net, dsahern@kernel.org, dsterba@suse.com,
dsterba@suse.cz, fw@strlen.de, gregkh@linuxfoundation.org,
jirislaby@kernel.org, josef@toxicpanda.com, kadlec@netfilter.org,
kuba@kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com,
yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] [btrfs?] [netfilter?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (2)
Date: Wed, 19 Jul 2023 10:11:27 -0700 [thread overview]
Message-ID: <00000000000042a3ac0600da1f69@google.com> (raw)
In-Reply-To: <20230719170446.GR20457@twin.jikos.cz>
> On Wed, Jul 19, 2023 at 02:32:51AM -0700, syzbot wrote:
>> syzbot has found a reproducer for the following issue on:
>>
>> HEAD commit: e40939bbfc68 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=15d92aaaa80000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=c4a2640e4213bc2f
>> dashboard link: https://syzkaller.appspot.com/bug?extid=9bbbacfbf1e04d5221f7
>> 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=149b2d66a80000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1214348aa80000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/9d87aa312c0e/disk-e40939bb.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/22a11d32a8b2/vmlinux-e40939bb.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/0978b5788b52/Image-e40939bb.gz.xz
>
> #syz unset btrfs
The following labels did not exist: btrfs
>
> The MAX_LOCKDEP_CHAIN_HLOCKS bugs/warnings can be worked around by
> configuration, otherwise are considered invalid. This report has also
> 'netfilter' label so I'm not closing it right away.
next prev parent reply other threads:[~2023-07-19 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 6:02 BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (2) syzbot
2023-07-19 9:32 ` [syzbot] [btrfs?] [netfilter?] " syzbot
2023-07-19 17:04 ` David Sterba
2023-07-19 17:11 ` syzbot [this message]
2023-07-19 17:14 ` Aleksandr Nogikh
2023-07-19 23:12 ` Florian Westphal
2023-07-20 3:30 ` Jakub Kicinski
2023-07-20 7:18 ` Paolo Abeni
2023-07-20 8:51 ` Taehee Yoo
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=00000000000042a3ac0600da1f69@google.com \
--to=syzbot+9bbbacfbf1e04d5221f7@syzkaller.appspotmail.com \
--cc=bakmitopiacibubur@boga.indosterling.com \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.