public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+23479f83731cac11ece8@syzkaller.appspotmail.com>
To: jfs-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,  shaggy@kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] [jfs?] kernel BUG in add_missing_indices
Date: Thu, 09 Apr 2026 20:35:25 -0700	[thread overview]
Message-ID: <69d86ffd.050a0220.3030df.0021.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    1791c390149f Merge tag 'char-misc-7.0-rc7' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=139d0bd6580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=45cb3c58fd963c27
dashboard link: https://syzkaller.appspot.com/bug?extid=23479f83731cac11ece8
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/430eb2c349f9/disk-1791c390.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0190d4eed4d1/vmlinux-1791c390.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca4e91c3c84e/bzImage-1791c390.xz

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

BUG at fs/jfs/jfs_dtree.c:2640 assert(p->header.flag & 0x02)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_dtree.c:2640!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 19459 Comm: syz.2.1265 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
RIP: 0010:add_missing_indices+0xcc9/0xcd0 fs/jfs/jfs_dtree.c:2640
Code: e9 75 fc ff ff e8 27 ea 71 fe 48 c7 c7 a0 ad 8a 8b 48 c7 c6 80 ac 8a 8b ba 50 0a 00 00 48 c7 c1 00 b6 8a 8b e8 48 c7 d4 fd 90 <0f> 0b 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90005197920 EFLAGS: 00010246
RAX: 000000000000003c RBX: ffff88805beee010 RCX: 2ce1a78098c85e00
RDX: ffffc9000e819000 RSI: 00000000000016a5 RDI: 00000000000016a6
RBP: ffffc90005197a30 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000a32ed5 R12: ffff88805beee000
R13: dffffc0000000000 R14: 0000000000000000 R15: 1ffff1100b7ddc02
FS:  00007f2a0ef656c0(0000) GS:ffff888126332000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2a10d79f00 CR3: 0000000070074000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 jfs_readdir+0x1e34/0x3c10 fs/jfs/jfs_dtree.c:3031
 wrap_directory_iterator+0x99/0xe0 fs/readdir.c:65
 iterate_dir+0x3a5/0x580 fs/readdir.c:108
 __do_sys_getdents fs/readdir.c:327 [inline]
 __se_sys_getdents+0xf1/0x270 fs/readdir.c:312
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2a10d2c819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2a0ef65028 EFLAGS: 00000246 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 00007f2a10fa6090 RCX: 00007f2a10d2c819
RDX: 000000000000003a RSI: 0000200000000180 RDI: 0000000000000006
RBP: 00007f2a10dc2c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2a10fa6128 R14: 00007f2a10fa6090 R15: 00007ffd98bd2fa8
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:add_missing_indices+0xcc9/0xcd0 fs/jfs/jfs_dtree.c:2640
Code: e9 75 fc ff ff e8 27 ea 71 fe 48 c7 c7 a0 ad 8a 8b 48 c7 c6 80 ac 8a 8b ba 50 0a 00 00 48 c7 c1 00 b6 8a 8b e8 48 c7 d4 fd 90 <0f> 0b 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90005197920 EFLAGS: 00010246
RAX: 000000000000003c RBX: ffff88805beee010 RCX: 2ce1a78098c85e00
RDX: ffffc9000e819000 RSI: 00000000000016a5 RDI: 00000000000016a6
RBP: ffffc90005197a30 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000a32ed5 R12: ffff88805beee000
R13: dffffc0000000000 R14: 0000000000000000 R15: 1ffff1100b7ddc02
FS:  00007f2a0ef656c0(0000) GS:ffff888126332000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2a10d79f00 CR3: 0000000070074000 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

                 reply	other threads:[~2026-04-10  3:35 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=69d86ffd.050a0220.3030df.0021.GAE@google.com \
    --to=syzbot+23479f83731cac11ece8@syzkaller.appspotmail.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@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