[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000000000042a3ac0600da1f69@google.com>
Date: Wed, 19 Jul 2023 10:11:27 -0700
From: syzbot <syzbot+9bbbacfbf1e04d5221f7@...kaller.appspotmail.com>
To: dsterba@...e.cz
Cc: bakmitopiacibubur@...a.indosterling.com, clm@...com,
davem@...emloft.net, dsahern@...nel.org, dsterba@...e.com,
dsterba@...e.cz, fw@...len.de, gregkh@...uxfoundation.org,
jirislaby@...nel.org, josef@...icpanda.com, kadlec@...filter.org,
kuba@...nel.org, linux-btrfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, linux@...linux.org.uk,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
pablo@...filter.org, syzkaller-bugs@...glegroups.com,
yoshfuji@...ux-ipv6.org
Subject: Re: [syzbot] [btrfs?] [netfilter?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too
low! (2)
> 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.
Powered by blists - more mailing lists