From: syzbot <syzbot+fe3566bcb509ae7764ef@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in __btrfs_free_extent (2)
Date: Thu, 27 Jun 2024 18:20:02 -0700 [thread overview]
Message-ID: <000000000000fa30a9061be90b81@google.com> (raw)
In-Reply-To: <20240628010120.3584455-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __btrfs_free_extent
------------[ cut here ]------------
BTRFS: Transaction aborted (error -2)
WARNING: CPU: 1 PID: 5913 at fs/btrfs/extent-tree.c:2985 do_free_extent_accounting fs/btrfs/extent-tree.c:2985 [inline]
WARNING: CPU: 1 PID: 5913 at fs/btrfs/extent-tree.c:2985 __btrfs_free_extent+0x3564/0x3a40 fs/btrfs/extent-tree.c:3360
Modules linked in:
CPU: 1 PID: 5913 Comm: syz-executor.2 Not tainted 6.10.0-rc3-syzkaller-00044-g2ccbdf43d5e7-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:do_free_extent_accounting fs/btrfs/extent-tree.c:2985 [inline]
RIP: 0010:__btrfs_free_extent+0x3564/0x3a40 fs/btrfs/extent-tree.c:3360
Code: ff ff 48 89 df e8 9c f9 50 fe e9 9d e0 ff ff e8 22 7f ee fd 90 48 c7 c7 00 2e 0b 8c 44 8b 6c 24 18 44 89 ee e8 ad ad b0 fd 90 <0f> 0b 90 90 4c 8b 24 24 e9 13 f5 ff ff 48 8b 4c 24 20 80 e1 07 80
RSP: 0018:ffffc900042af340 EFLAGS: 00010246
RAX: 6c4a53fef53c7400 RBX: ffff88807135c001 RCX: ffff88802ae55a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900042af510 R08: ffffffff81585742 R09: 1ffff92000855e08
R10: dffffc0000000000 R11: fffff52000855e09 R12: dffffc0000000000
R13: 00000000fffffffe R14: 0000000000000000 R15: ffff88806f7cf818
FS: 0000555588813480(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055558881c938 CR3: 000000007124e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
run_delayed_tree_ref fs/btrfs/extent-tree.c:1736 [inline]
run_one_delayed_ref fs/btrfs/extent-tree.c:1762 [inline]
btrfs_run_delayed_refs_for_head fs/btrfs/extent-tree.c:2027 [inline]
__btrfs_run_delayed_refs+0x117c/0x4670 fs/btrfs/extent-tree.c:2097
btrfs_run_delayed_refs+0xe3/0x2c0 fs/btrfs/extent-tree.c:2209
btrfs_commit_transaction+0xf5d/0x3740 fs/btrfs/transaction.c:2400
sync_filesystem+0x1c8/0x230 fs/sync.c:66
generic_shutdown_super+0x72/0x2d0 fs/super.c:621
kill_anon_super+0x3b/0x70 fs/super.c:1226
btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2096
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1267
task_work_run+0x24f/0x310 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x168/0x370 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9668a7e257
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffdf71b8e28 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f9668a7e257
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffdf71b8ee0
RBP: 00007ffdf71b8ee0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffdf71b9f90
R13: 00007f9668ad96c6 R14: 0000000000019832 R15: 0000000000000002
</TASK>
Tested on:
commit: 2ccbdf43 Merge tag 'for-linus' of git://git.kernel.org..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16868cd1980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c79815c08cc14227
dashboard link: https://syzkaller.appspot.com/bug?extid=fe3566bcb509ae7764ef
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1666bda9980000
next parent reply other threads:[~2024-06-28 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240628010120.3584455-1-lizhi.xu@windriver.com>
2024-06-28 1:20 ` syzbot [this message]
2024-06-23 15:39 [syzbot] [btrfs?] WARNING in __btrfs_free_extent (2) syzbot
2024-06-28 21:46 ` Boris Burkov
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=000000000000fa30a9061be90b81@google.com \
--to=syzbot+fe3566bcb509ae7764ef@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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