From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f77.google.com (mail-oo1-f77.google.com [209.85.161.77]) (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 7B63535F615 for ; Mon, 30 Mar 2026 04:11:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774843888; cv=none; b=mOIpRmPjhPqF38lmUaY0olQ0nzpUPWL76ZVfqM6avYUVRIUmmRmtkJtE6HHvlRpMacW+plBjCaikM0DEqXdrIYSRFSSGqp5j7LTwHL8YtoCtU2USMtkHfmx2YBNEBziUPk91Yt33ka0v8r1NY5f5c7QZN6Ta9kLBfLts2VYaVE4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774843888; c=relaxed/simple; bh=WBZhRP7ycEgKXxXM3CcK1JlqqD+QzfYTXFxMM/grzfM=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=ky+8NGZ3fnMtMptmeG8jttKLV9vup7Go0OD+vZsBTPKycUKNdARETkRxYGu51PfbIOMuP/lU7hev1+Tpl676DlCQjzfsNTs773UiG1M1b1HcPNWuFj6naivt9KTjyxIP1rjISFTK9JACofk8bflH8tzT5L0uP74ioq9T1QaIS8M= 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.161.77 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-oo1-f77.google.com with SMTP id 006d021491bc7-67de56b5bd4so14984490eaf.0 for ; Sun, 29 Mar 2026 21:11:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774843885; x=1775448685; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=oJtdMSl+mOgDRmV6cq7NDe0QHly1FFMaQL3TINKOIvQ=; b=NPGzbVHyQ88p9h5+2oZiK4NDRtf62+X9Sp5anLgiV66+GZUeA3dqoFRUCGYlb1C4VA NP7bOy3uKn9BMq7lPtWl90WrD8cpTj95aBixK35/w7G+ZFZfHSHpT9I0G0QcHFRbzfKs FsgM7VbXwpZJS98eooF0RKy1rEAjeCxs0w3LjIB7s0kRLd6m/aX7Mmx4ZkHq/UjJQxrq S/LC9K2YT8VqeH3zAFY26bCiCRlDcqfX30+BbrU1NsX07lC/+RznEKsgblnumbA8AERG rJ0w+J6dHvrswzeXIbWEZ27NB9AMI8GLpWKFcuUMmzDR+Ch/xCoxuUXO1HsAY2bJMiMf oW9Q== X-Forwarded-Encrypted: i=1; AJvYcCWSPZhEv435FYN/nhQOxpzvcVkao0F3L3byPG6Ru+4sf+ofeENXdyHP6xqmyTt5vHlCxrwrMoFHOCYmiLA=@vger.kernel.org X-Gm-Message-State: AOJu0Yy4QUrclRE5bN8gb3Euw+/M2aU1iHzONn5VQIb6gfqq1rnTmkFe TMa3UkqewZn1yGWvHNofWkIbQx065HsDs5Zi0xGHXU1CZJVH8Kr7axYKeL/0dx7bN+sB/t9G8FN u/6ONRd71epzOovwXeEFMSvQrXYKf44IO9yUvanwrDw2EsGo9jF2AqrClTjc= 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:6820:4c14:b0:67b:b0bd:8bd2 with SMTP id 006d021491bc7-67e1874aa32mr5677650eaf.59.1774843885405; Sun, 29 Mar 2026 21:11:25 -0700 (PDT) Date: Sun, 29 Mar 2026 21:11:25 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69c9f7ed.050a0220.183828.0012.GAE@google.com> Subject: [syzbot] [jfs?] BUG: unable to handle kernel paging request in txAllocPMap 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: a3d97d1d3fa6 Merge tag 'ovl-fixes-7.0-rc6' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=108101ca580000 kernel config: https://syzkaller.appspot.com/x/.config?x=d46eab0cfd31c214 dashboard link: https://syzkaller.appspot.com/bug?extid=3179a62b064892f52d7e 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 (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-a3d97d1d.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/0f30a7749a53/vmlinux-a3d97d1d.xz kernel image: https://storage.googleapis.com/syzbot-assets/7303c1241ecd/bzImage-a3d97d1d.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+3179a62b064892f52d7e@syzkaller.appspotmail.com blkno = 248b4d00, nblocks = 1b6685 ERROR: (device loop0): dbUpdatePMap: blocks are outside the map ERROR: (device loop0): remounting filesystem as read-only BUG: unable to handle page fault for address: ffff88800129f1d0 #PF: supervisor write access in kernel mode #PF: error_code(0x0003) - permissions violation PGD 1a806067 P4D 1a806067 PUD 1a807067 PMD 80000000012001a1 Oops: Oops: 0003 [#1] SMP KASAN NOPTI CPU: 0 UID: 0 PID: 102 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:txAllocPMap+0x3d4/0x6b0 fs/jfs/jfs_txnmgr.c:2417 Code: 81 e5 ff ff ff 00 48 8b 7c 24 18 31 f6 48 89 ea 4c 89 e9 4c 8b 44 24 20 e8 b9 14 fb ff 42 0f b6 04 33 84 c0 0f 85 f7 00 00 00 <41> 80 24 24 fc 48 8b 44 24 28 42 0f b6 04 30 84 c0 0f 85 fb 00 00 RSP: 0018:ffffc90000e97bf8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff11000253e3a RCX: 4776158121b95000 RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000 RBP: 00000000248b4d00 R08: 0000000000000003 R09: 0000000000000004 R10: dffffc0000000000 R11: fffffbfff1cbd630 R12: ffff88800129f1d0 R13: 00000000001b6685 R14: dffffc0000000000 R15: ffff88800129f1d0 FS: 0000000000000000(0000) GS:ffff88808ca4c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff88800129f1d0 CR3: 000000000e54c000 CR4: 0000000000352ef0 Call Trace: txUpdateMap+0x2a2/0x9c0 fs/jfs/jfs_txnmgr.c:2309 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline] jfs_lazycommit+0x43d/0xaa0 fs/jfs/jfs_txnmgr.c:2734 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 Modules linked in: CR2: ffff88800129f1d0 ---[ end trace 0000000000000000 ]--- RIP: 0010:txAllocPMap+0x3d4/0x6b0 fs/jfs/jfs_txnmgr.c:2417 Code: 81 e5 ff ff ff 00 48 8b 7c 24 18 31 f6 48 89 ea 4c 89 e9 4c 8b 44 24 20 e8 b9 14 fb ff 42 0f b6 04 33 84 c0 0f 85 f7 00 00 00 <41> 80 24 24 fc 48 8b 44 24 28 42 0f b6 04 30 84 c0 0f 85 fb 00 00 RSP: 0018:ffffc90000e97bf8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff11000253e3a RCX: 4776158121b95000 RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000 RBP: 00000000248b4d00 R08: 0000000000000003 R09: 0000000000000004 R10: dffffc0000000000 R11: fffffbfff1cbd630 R12: ffff88800129f1d0 R13: 00000000001b6685 R14: dffffc0000000000 R15: ffff88800129f1d0 FS: 0000000000000000(0000) GS:ffff88808ca4c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff88800129f1d0 CR3: 000000000e54c000 CR4: 0000000000352ef0 ---------------- Code disassembly (best guess): 0: 81 e5 ff ff ff 00 and $0xffffff,%ebp 6: 48 8b 7c 24 18 mov 0x18(%rsp),%rdi b: 31 f6 xor %esi,%esi d: 48 89 ea mov %rbp,%rdx 10: 4c 89 e9 mov %r13,%rcx 13: 4c 8b 44 24 20 mov 0x20(%rsp),%r8 18: e8 b9 14 fb ff call 0xfffb14d6 1d: 42 0f b6 04 33 movzbl (%rbx,%r14,1),%eax 22: 84 c0 test %al,%al 24: 0f 85 f7 00 00 00 jne 0x121 * 2a: 41 80 24 24 fc andb $0xfc,(%r12) <-- trapping instruction 2f: 48 8b 44 24 28 mov 0x28(%rsp),%rax 34: 42 0f b6 04 30 movzbl (%rax,%r14,1),%eax 39: 84 c0 test %al,%al 3b: 0f .byte 0xf 3c: 85 fb test %edi,%ebx --- 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