All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9489c9f9f3d437221ea2@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 yun.zhou@windriver.com
Subject: Re: [syzbot] [jfs?] general protection fault in txCommit (2)
Date: Sat, 08 Nov 2025 08:46:02 -0800	[thread overview]
Message-ID: <690f73ca.a70a0220.22f260.0087.GAE@google.com> (raw)
In-Reply-To: <SJ5PPF2F7FC4EE603CDF9A16121B88A38C09FC0A@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
UBSAN: array-index-out-of-bounds in dtInsertEntry

loop0: detected capacity change from 0 to 32768
UFO tlock:0xffffc900034f91f8
------------[ cut here ]------------
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:3700:8
index -1 is out of range for type 'struct dtslot[128]'
CPU: 1 UID: 0 PID: 6705 Comm: syz.0.55 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 ubsan_epilogue+0xa/0x40 lib/ubsan.c:233
 __ubsan_handle_out_of_bounds+0xe9/0xf0 lib/ubsan.c:455
 dtInsertEntry+0x936/0x1430 fs/jfs/jfs_dtree.c:3700
 dtInsert+0x931/0x5f40 fs/jfs/jfs_dtree.c:894
 jfs_create+0x6c8/0xa80 fs/jfs/namei.c:137
 lookup_open fs/namei.c:3796 [inline]
 open_last_lookups fs/namei.c:3895 [inline]
 path_openat+0x1500/0x3840 fs/namei.c:4131
 do_filp_open+0x1fa/0x410 fs/namei.c:4161
 do_sys_openat2+0x121/0x1c0 fs/open.c:1437
 do_sys_open fs/open.c:1452 [inline]
 __do_sys_creat fs/open.c:1530 [inline]
 __se_sys_creat fs/open.c:1524 [inline]
 __x64_sys_creat+0x8f/0xc0 fs/open.c:1524
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f67e06af6c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f67dfd16038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f67e0905fa0 RCX: 00007f67e06af6c9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000580
RBP: 00007f67e0731f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f67e0906038 R14: 00007f67e0905fa0 R15: 00007fff0aaff588
 </TASK>
---[ end trace ]---


Tested on:

commit:         e811c33b Merge tag 'drm-fixes-2025-11-08' of https://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11cf0b42580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=9489c9f9f3d437221ea2
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=17eaaa92580000


       reply	other threads:[~2025-11-08 16:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SJ5PPF2F7FC4EE603CDF9A16121B88A38C09FC0A@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>
2025-11-08 16:46 ` syzbot [this message]
     [not found] <SJ5PPF2F7FC4EE60B34FA683FC9B5F3EAFE9FCAA@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>
2025-11-14 15:15 ` [syzbot] [jfs?] general protection fault in txCommit (2) syzbot
     [not found] <SJ5PPF2F7FC4EE6AC25CE1A7769CDC692799FCAA@SJ5PPF2F7FC4EE6.namprd11.prod.outlook.com>
2025-11-14 14:51 ` syzbot
     [not found] <912d60c8-e898-4113-b167-9549bc15f026@windriver.com>
2025-11-10 13:07 ` syzbot
     [not found] <bf35b502-ca85-41a4-b47b-c3ae63155257@windriver.com>
2025-11-10 12:12 ` syzbot
     [not found] <e7ea1bff-0b4e-4490-b5a7-e8e366944842@windriver.com>
2025-11-08  8:36 ` syzbot
2025-11-07  7:29 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=690f73ca.a70a0220.22f260.0087.GAE@google.com \
    --to=syzbot+9489c9f9f3d437221ea2@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yun.zhou@windriver.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.