Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: syzbot <syzbot+6a843bf8604711c8fab0@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [btrfs?] WARNING in btrfs_add_delayed_iput (3)
Date: Tue, 02 Jun 2026 07:13:27 -0700	[thread overview]
Message-ID: <6a1ee507.b4221f80.1326c5.0004.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    8fde5d1d47f6 Merge tag 'acpi-7.1-rc6' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15af697e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bd38685893011045
dashboard link: https://syzkaller.appspot.com/bug?extid=6a843bf8604711c8fab0
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7e05a6204e66/disk-8fde5d1d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc2122f096ea/vmlinux-8fde5d1d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fa9b3cad3a6c/bzImage-8fde5d1d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6a843bf8604711c8fab0@syzkaller.appspotmail.com

------------[ cut here ]------------
test_bit(BTRFS_FS_STATE_NO_DELAYED_IPUT, &fs_info->fs_state)
WARNING: fs/btrfs/inode.c:3596 at btrfs_add_delayed_iput+0x2e3/0x340 fs/btrfs/inode.c:3596, CPU#0: kworker/u8:10/1187
Modules linked in:
CPU: 0 UID: 0 PID: 1187 Comm: kworker/u8:10 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: btrfs-endio-write btrfs_work_helper
RIP: 0010:btrfs_add_delayed_iput+0x2e3/0x340 fs/btrfs/inode.c:3596
Code: 53 a3 45 fe 48 8b 3b 48 83 c4 20 5b 41 5c 41 5d 41 5e 41 5f 5d e9 dd a4 ad fd e8 48 78 de fd e9 f8 fd ff ff e8 3e 78 de fd 90 <0f> 0b 90 e9 52 fe ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 84
RSP: 0018:ffffc900065d77c8 EFLAGS: 00010293
RAX: ffffffff83e5f502 RBX: ffff88805aba0000 RCX: ffff888029768000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed100b574497 R12: 0000000000000001
R13: dffffc0000000000 R14: ffff888061194788 R15: 0000000000000200
FS:  0000000000000000(0000) GS:ffff888126186000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe553a3f000 CR3: 00000000596c2000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 btrfs_put_ordered_extent+0x18f/0x430 fs/btrfs/ordered-data.c:629
 btrfs_finish_one_ordered+0xf63/0x2680 fs/btrfs/inode.c:3433
 btrfs_work_helper+0x38b/0xc20 fs/btrfs/async-thread.c:312
 process_one_work kernel/workqueue.c:3314 [inline]
 process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397
 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2026-06-02 14:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6a1ee507.b4221f80.1326c5.0004.GAE@google.com \
    --to=syzbot+6a843bf8604711c8fab0@syzkaller.appspotmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox