From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f205.google.com (mail-oi1-f205.google.com [209.85.167.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DE10B377017 for ; Fri, 10 Jul 2026 18:24:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.205 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783707881; cv=none; b=pdwzxCH6fgQPcEyc9IU//blHajJmBz3OwgkMpLWN36a+KNQIRhWDf04IzWELhOlgejaJHS3IWBB4v/2f6q6a/xjUUwbqAujKcxON65EvbdJWiya4cloO+FJ7VR9fTopkoWelcrhlHu/B0wlNpQTieZvR/1LENYs5iHf3ESaRy78= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783707881; c=relaxed/simple; bh=b7lmHMciniLD3oJkIFD+AJP65+YV8Z9wnDRtj407pZE=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=kKTHpgK/JEiW7/2Jjzw5slMHI717ltgtm3EvN/gud+j+ELENJABO/+jhWlAjV07cgIequK47CkMEND2air+vapNRtwGwSu4HxgtyoA4aA29zO0Id23HYRYo40KuXkr+3u6k/K5F8qNLrg+aqGcYcdKb5ofp2jYxFJOukWVRh/PU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.205 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f205.google.com with SMTP id 5614622812f47-495f68a7973so841975b6e.2 for ; Fri, 10 Jul 2026 11:24:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783707879; x=1784312679; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=MMeeMQr1/x+Qo+ufIh5CbsWciBDPYiUAqqGihaj181A=; b=iVFxdV1deiyPx7yLEnbmqvrpCZc/0xAEseBukyWt7eWF/D/MnbbNuqepoUUNOBFuGq eWvARxrhuQr2AbhBHt7bcI+8Gu3USx5pj0nNHIGq4Rjry2SS3V06TiqarZ3Sxz59w8v4 CECJbWDipnP+FblLqXYm/bifhRa2SrA62oyZo8WjYZorYb43Ga30cOnsfxxu77IsDxZ7 j0EJyFJ9TsI5KUXy8JVrClRDtYSr+AigoSwk7tiO+B2HhcQiz+DPUWH3iwqvrjr/pkx8 g0E9oulv3AGX2eZrevQO4d6U1rHXXeNE5JKBWHwuV5QC19AasjaAUal/4VSzeKT90+ZT PFpQ== X-Forwarded-Encrypted: i=1; AFNElJ/zKdMzeOJ7UjXnxyS1RgJMUu96R8i4sfnOPNk+s11e1da66dnpPE55vYyDiauwen2b7Avpaucni84lN+I=@vger.kernel.org X-Gm-Message-State: AOJu0YyxKBiEqcQX49UEdlOX85rzV2IEKInoDLSVLx7QN8o3grichBAr aab8Gk0qSz/eWFIe4TLOL74tHF+9Hham/gw1KNL0GtZOuPVivtq+b9YlDb1NovJXamXkYlcvYDx 3fr90A3F0CLk8R9inb0lSxmgaz42XZabBKzWsSyVEmOzrohp16XYjFydSYTU= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:3999:b0:496:57c6:3dcc with SMTP id 5614622812f47-4a42ace27b5mr257603b6e.8.1783707878943; Fri, 10 Jul 2026 11:24:38 -0700 (PDT) Date: Fri, 10 Jul 2026 11:24:38 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a5138e6.63a5fcd8.28bd53.0003.GAE@google.com> Subject: [syzbot] [jfs?] kernel BUG in lbmIOWait From: syzbot To: jfs-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org, shaggy@kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 8cdeaa50eae8 Linux 7.2-rc2 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=136d3546580000 kernel config: https://syzkaller.appspot.com/x/.config?x=98da55a882774dfe dashboard link: https://syzkaller.appspot.com/bug?extid=2e5cf2352e9f69ebf172 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/5305ba8cc7ff/disk-8cdeaa50.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/9f2a82556517/vmlinux-8cdeaa50.xz kernel image: https://storage.googleapis.com/syzbot-assets/c5dc14abbf23/bzImage-8cdeaa50.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2e5cf2352e9f69ebf172@syzkaller.appspotmail.com BUG at fs/jfs/jfs_logmgr.c:1919 assert(bp->l_wqnext == NULL) ------------[ cut here ]------------ kernel BUG at fs/jfs/jfs_logmgr.c:1919! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 0 UID: 0 PID: 8824 Comm: syz-executor Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026 RIP: 0010:lbmfree fs/jfs/jfs_logmgr.c:1919 [inline] RIP: 0010:lbmIOWait+0x5ab/0x5b0 fs/jfs/jfs_logmgr.c:2154 Code: e9 c7 fc ff ff e8 05 5b 66 fe 48 c7 c7 80 dd ab 8b 48 c7 c6 80 d8 ab 8b ba 7f 07 00 00 48 c7 c1 00 e6 ab 8b e8 b6 87 c8 fd 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 RSP: 0018:ffffc9000436f9e0 EFLAGS: 00010246 RAX: 000000000000003c RBX: ffff88803d406008 RCX: bd2a06f3b920b600 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000436faf0 R08: 0000000000000000 R09: 0000000000000000 R10: dffffc0000000000 R11: fffff5200086deed R12: 000000000000002e R13: ffff88803d406010 R14: dffffc0000000000 R15: 1ffff9200086df44 FS: 000055555ba11500(0000) GS:ffff888125c4c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffa20e9d000 CR3: 000000005dbb2000 CR4: 00000000003526f0 Call Trace: lmLogShutdown+0x1ff/0x850 fs/jfs/jfs_logmgr.c:1657 lmLogClose+0x28c/0x530 fs/jfs/jfs_logmgr.c:1457 jfs_umount+0x2da/0x3b0 fs/jfs/jfs_umount.c:124 jfs_put_super+0x8c/0x190 fs/jfs/super.c:194 generic_shutdown_super+0x13d/0x2d0 fs/super.c:647 kill_block_super+0x44/0x90 fs/super.c:1665 deactivate_locked_super+0xbc/0x130 fs/super.c:477 cleanup_mnt+0x3d3/0x460 fs/namespace.c:1317 task_work_run+0x1d9/0x270 kernel/task_work.c:233 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] __exit_to_user_mode_loop kernel/entry/common.c:70 [inline] exit_to_user_mode_loop+0x1fa/0x730 kernel/entry/common.c:101 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline] syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline] do_syscall_64+0x353/0x580 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6087c0f097 Code: a2 c7 05 5c 26 25 00 00 00 00 00 eb 96 e8 e1 12 00 00 90 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 e8 ff ff ff f7 d8 64 89 02 b8 RSP: 002b:00007fffcff22d78 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007f6087ca32ca RCX: 00007f6087c0f097 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffcff22e30 RBP: 00007fffcff22e30 R08: 00007fffcff23e30 R09: 00000000ffffffff R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffcff23ec0 R13: 00007f6087ca32ca R14: 0000000000088c2a R15: 00007fffcff23f00 Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:lbmfree fs/jfs/jfs_logmgr.c:1919 [inline] RIP: 0010:lbmIOWait+0x5ab/0x5b0 fs/jfs/jfs_logmgr.c:2154 Code: e9 c7 fc ff ff e8 05 5b 66 fe 48 c7 c7 80 dd ab 8b 48 c7 c6 80 d8 ab 8b ba 7f 07 00 00 48 c7 c1 00 e6 ab 8b e8 b6 87 c8 fd 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 RSP: 0018:ffffc9000436f9e0 EFLAGS: 00010246 RAX: 000000000000003c RBX: ffff88803d406008 RCX: bd2a06f3b920b600 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000436faf0 R08: 0000000000000000 R09: 0000000000000000 R10: dffffc0000000000 R11: fffff5200086deed R12: 000000000000002e R13: ffff88803d406010 R14: dffffc0000000000 R15: 1ffff9200086df44 FS: 000055555ba11500(0000) GS:ffff888125c4c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffa20e9d000 CR3: 000000005dbb2000 CR4: 00000000003526f0 --- 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