From: syzbot <syzbot+74f79df25c37437e4d5a@syzkaller.appspotmail.com>
To: chao@kernel.org, clm@fb.com, dsterba@suse.com,
jaegeuk@kernel.org, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (7)
Date: Wed, 18 Sep 2024 08:03:24 -0700 [thread overview]
Message-ID: <66eaebbc.050a0220.252d9a.0015.GAE@google.com> (raw)
In-Reply-To: <66e55308.050a0220.1f4381.0004.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 5f5673607153 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=137fc69f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=dedbcb1ff4387972
dashboard link: https://syzkaller.appspot.com/bug?extid=74f79df25c37437e4d5a
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=12b8f500580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dbc4a9980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/40172aed5414/disk-5f567360.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/58372f305e9d/vmlinux-5f567360.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d2aae6fa798f/Image-5f567360.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e4b8f51425ac/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+74f79df25c37437e4d5a@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 0 UID: 0 PID: 137 Comm: kworker/u8:4 Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: btrfs-endio-write btrfs_work_helper
Call trace:
dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:319
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:326
__dump_stack lib/dump_stack.c:93 [inline]
dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:119
dump_stack+0x1c/0x28 lib/dump_stack.c:128
lookup_chain_cache_add kernel/locking/lockdep.c:3815 [inline]
validate_chain kernel/locking/lockdep.c:3836 [inline]
__lock_acquire+0x1fa0/0x779c kernel/locking/lockdep.c:5142
lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5759
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x48/0x60 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
btrfs_block_rsv_size fs/btrfs/block-rsv.h:136 [inline]
btrfs_use_block_rsv+0x184/0x73c fs/btrfs/block-rsv.c:495
btrfs_alloc_tree_block+0x16c/0x12d4 fs/btrfs/extent-tree.c:5130
btrfs_force_cow_block+0x4e4/0x1c9c fs/btrfs/ctree.c:573
btrfs_cow_block+0x318/0xa28 fs/btrfs/ctree.c:754
btrfs_search_slot+0xba0/0x2a08
btrfs_lookup_file_extent+0x124/0x1bc fs/btrfs/file-item.c:267
btrfs_drop_extents+0x370/0x2ad8 fs/btrfs/file.c:251
insert_reserved_file_extent+0x2b4/0xa6c fs/btrfs/inode.c:2911
insert_ordered_extent_file_extent+0x348/0x508 fs/btrfs/inode.c:3016
btrfs_finish_one_ordered+0x6a0/0x129c fs/btrfs/inode.c:3124
btrfs_finish_ordered_io+0x120/0x134 fs/btrfs/inode.c:3266
finish_ordered_fn+0x20/0x30 fs/btrfs/ordered-data.c:331
btrfs_work_helper+0x340/0xd28 fs/btrfs/async-thread.c:314
process_one_work+0x79c/0x15b8 kernel/workqueue.c:3231
process_scheduled_works kernel/workqueue.c:3312 [inline]
worker_thread+0x978/0xec4 kernel/workqueue.c:3389
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+74f79df25c37437e4d5a@syzkaller.appspotmail.com>
To: chao@kernel.org, clm@fb.com, dsterba@suse.com,
jaegeuk@kernel.org, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [btrfs?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (7)
Date: Wed, 18 Sep 2024 08:03:24 -0700 [thread overview]
Message-ID: <66eaebbc.050a0220.252d9a.0015.GAE@google.com> (raw)
In-Reply-To: <66e55308.050a0220.1f4381.0004.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 5f5673607153 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=137fc69f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=dedbcb1ff4387972
dashboard link: https://syzkaller.appspot.com/bug?extid=74f79df25c37437e4d5a
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=12b8f500580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dbc4a9980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/40172aed5414/disk-5f567360.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/58372f305e9d/vmlinux-5f567360.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d2aae6fa798f/Image-5f567360.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e4b8f51425ac/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+74f79df25c37437e4d5a@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 0 UID: 0 PID: 137 Comm: kworker/u8:4 Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: btrfs-endio-write btrfs_work_helper
Call trace:
dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:319
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:326
__dump_stack lib/dump_stack.c:93 [inline]
dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:119
dump_stack+0x1c/0x28 lib/dump_stack.c:128
lookup_chain_cache_add kernel/locking/lockdep.c:3815 [inline]
validate_chain kernel/locking/lockdep.c:3836 [inline]
__lock_acquire+0x1fa0/0x779c kernel/locking/lockdep.c:5142
lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5759
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x48/0x60 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
btrfs_block_rsv_size fs/btrfs/block-rsv.h:136 [inline]
btrfs_use_block_rsv+0x184/0x73c fs/btrfs/block-rsv.c:495
btrfs_alloc_tree_block+0x16c/0x12d4 fs/btrfs/extent-tree.c:5130
btrfs_force_cow_block+0x4e4/0x1c9c fs/btrfs/ctree.c:573
btrfs_cow_block+0x318/0xa28 fs/btrfs/ctree.c:754
btrfs_search_slot+0xba0/0x2a08
btrfs_lookup_file_extent+0x124/0x1bc fs/btrfs/file-item.c:267
btrfs_drop_extents+0x370/0x2ad8 fs/btrfs/file.c:251
insert_reserved_file_extent+0x2b4/0xa6c fs/btrfs/inode.c:2911
insert_ordered_extent_file_extent+0x348/0x508 fs/btrfs/inode.c:3016
btrfs_finish_one_ordered+0x6a0/0x129c fs/btrfs/inode.c:3124
btrfs_finish_ordered_io+0x120/0x134 fs/btrfs/inode.c:3266
finish_ordered_fn+0x20/0x30 fs/btrfs/ordered-data.c:331
btrfs_work_helper+0x340/0xd28 fs/btrfs/async-thread.c:314
process_one_work+0x79c/0x15b8 kernel/workqueue.c:3231
process_scheduled_works kernel/workqueue.c:3312 [inline]
worker_thread+0x978/0xec4 kernel/workqueue.c:3389
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-09-18 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 9:10 [f2fs-dev] [syzbot] [net?] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (7) syzbot
2024-09-14 9:10 ` syzbot
2024-09-18 15:03 ` syzbot [this message]
2024-09-18 15:03 ` [f2fs-dev] [syzbot] [btrfs?] " syzbot
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=66eaebbc.050a0220.252d9a.0015.GAE@google.com \
--to=syzbot+74f79df25c37437e4d5a@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jaegeuk@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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.