All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8aaf2df2ef0164ffe1fb@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel] WARNING: locking bug in try_to_wake_up
Date: Mon, 30 Sep 2024 19:10:06 -0700	[thread overview]
Message-ID: <66fb59fe.050a0220.aab67.003d.GAE@google.com> (raw)
In-Reply-To: <20241001014939.1736-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in close_ctree

BTRFS info (device loop0): last unmount of filesystem c9fe44da-de57-406a-8241-57ec7d4412cf
assertion failed: list_empty(&fs_info->delalloc_roots), in fs/btrfs/disk-io.c:4327
------------[ cut here ]------------
kernel BUG at fs/btrfs/disk-io.c:4327!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5820 Comm: syz-executor Not tainted 6.12.0-rc1-syzkaller-00031-ge32cde8d2bd7-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:close_ctree+0x912/0xd20 fs/btrfs/disk-io.c:4327
Code: ff ff 90 0f 0b e8 7e d1 da f5 48 c7 c7 40 30 4c 8c 48 c7 c6 80 60 4c 8c 48 c7 c2 c0 30 4c 8c b9 e7 10 00 00 e8 0f 9d ff ff 90 <0f> 0b e8 57 d1 da f5 48 c7 c7 40 30 4c 8c 48 c7 c6 20 7c 4c 8c 48
RSP: 0018:ffffc90002f6fb60 EFLAGS: 00010246
RAX: 0000000000000052 RBX: ffff888030de0f28 RCX: 618777cd44da3000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002f6fd00 R08: ffffffff81749d9c R09: 1ffff920005edf08
R10: dffffc0000000000 R11: fffff520005edf09 R12: ffff888030de0000
R13: dffffc0000000000 R14: 1ffff110061bc272 R15: 0000000000000000
FS:  0000555562490500(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c00191d740 CR3: 000000007010e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 generic_shutdown_super+0x139/0x2d0 fs/super.c:642
 kill_anon_super+0x3b/0x70 fs/super.c:1237
 btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2121
 deactivate_locked_super+0xc4/0x130 fs/super.c:473
 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
 task_work_run+0x24f/0x310 kernel/task_work.c:228
 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:0x7f9dd257f327
Code: a8 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 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffd8c162128 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f9dd257f327
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffd8c1621e0
RBP: 00007ffd8c1621e0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffd8c163260
R13: 00007f9dd25f0134 R14: 000000000001c212 R15: 00007ffd8c1632a0
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:close_ctree+0x912/0xd20 fs/btrfs/disk-io.c:4327
Code: ff ff 90 0f 0b e8 7e d1 da f5 48 c7 c7 40 30 4c 8c 48 c7 c6 80 60 4c 8c 48 c7 c2 c0 30 4c 8c b9 e7 10 00 00 e8 0f 9d ff ff 90 <0f> 0b e8 57 d1 da f5 48 c7 c7 40 30 4c 8c 48 c7 c6 20 7c 4c 8c 48
RSP: 0018:ffffc90002f6fb60 EFLAGS: 00010246
RAX: 0000000000000052 RBX: ffff888030de0f28 RCX: 618777cd44da3000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002f6fd00 R08: ffffffff81749d9c R09: 1ffff920005edf08
R10: dffffc0000000000 R11: fffff520005edf09 R12: ffff888030de0000
R13: dffffc0000000000 R14: 1ffff110061bc272 R15: 0000000000000000
FS:  0000555562490500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555624ab5c8 CR3: 000000007010e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Tested on:

commit:         e32cde8d Merge tag 'sched_ext-for-6.12-rc1-fixes-1' of..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1222ddd0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1f009dd80b3799c2
dashboard link: https://syzkaller.appspot.com/bug?extid=8aaf2df2ef0164ffe1fb
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=169d1980580000


  reply	other threads:[~2024-10-01  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 18:41 [syzbot] [wireguard?] WARNING: locking bug in try_to_wake_up syzbot
2024-09-30 23:39 ` [syzbot] [kernel] " syzbot
2024-10-01  1:49   ` Hillf Danton
2024-10-01  2:10     ` syzbot [this message]
2024-10-01  8:31   ` Hillf Danton
2024-10-01  8:50     ` 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=66fb59fe.050a0220.aab67.003d.GAE@google.com \
    --to=syzbot+8aaf2df2ef0164ffe1fb@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --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 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.