All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c1056fdfe414463fdb33@syzkaller.appspotmail.com>
To: ghandatmanas@gmail.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, syzkaller@googlegroups.com
Subject: Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in diWrite
Date: Fri, 03 Nov 2023 00:40:06 -0700	[thread overview]
Message-ID: <000000000000fab6b506093a9cc3@google.com> (raw)
In-Reply-To: <CAEt2hJ5MpDyGhxVX9OHhiA78xQNWMoKT+qL7SnkDA5tUNsWCDA@mail.gmail.com>

Hello,

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

BUG at fs/jfs/jfs_txnmgr.c:931 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:931!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 107 Comm: jfsCommit Not tainted 6.6.0-syzkaller-12401-g8f6f76a6a29f-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:txUnlock+0xc6e/0xca0 fs/jfs/jfs_txnmgr.c:931
Code: 18 58 4b 07 0f 0b e8 f1 9a 7b fe 48 c7 c7 40 ed e2 8a 48 c7 c6 39 e9 e2 8a ba a3 03 00 00 48 c7 c1 20 fa e2 8a e8 f2 57 4b 07 <0f> 0b e8 cb 9a 7b fe 48 c7 c7 40 ed e2 8a 48 c7 c6 39 e9 e2 8a ba
RSP: 0018:ffffc90002cafce8 EFLAGS: 00010246
RAX: 0000000000000037 RBX: 0000000000000000 RCX: af7f11a66accc000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff888027157aa8 R08: ffffffff816e5b5c R09: 1ffff92000595f3c
R10: dffffc0000000000 R11: fffff52000595f3d R12: 0000000000000a06
R13: 0000000000000000 R14: ffffc90002802000 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555660e938 CR3: 0000000027c28000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 jfs_lazycommit+0x5d4/0xb80 fs/jfs/jfs_txnmgr.c:2682
 kthread+0x2cd/0x360 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txUnlock+0xc6e/0xca0 fs/jfs/jfs_txnmgr.c:931
Code: 18 58 4b 07 0f 0b e8 f1 9a 7b fe 48 c7 c7 40 ed e2 8a 48 c7 c6 39 e9 e2 8a ba a3 03 00 00 48 c7 c1 20 fa e2 8a e8 f2 57 4b 07 <0f> 0b e8 cb 9a 7b fe 48 c7 c7 40 ed e2 8a 48 c7 c6 39 e9 e2 8a ba
RSP: 0018:ffffc90002cafce8 EFLAGS: 00010246
RAX: 0000000000000037 RBX: 0000000000000000 RCX: af7f11a66accc000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff888027157aa8 R08: ffffffff816e5b5c R09: 1ffff92000595f3c
R10: dffffc0000000000 R11: fffff52000595f3d R12: 0000000000000a06
R13: 0000000000000000 R14: ffffc90002802000 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555660e938 CR3: 0000000026057000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Tested on:

commit:         8f6f76a6 Merge tag 'mm-nonmm-stable-2023-11-02-14-08' ..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1751405b680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f696cf620c46c5db
dashboard link: https://syzkaller.appspot.com/bug?extid=c1056fdfe414463fdb33
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1022abe3680000


       reply	other threads:[~2023-11-03  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEt2hJ5MpDyGhxVX9OHhiA78xQNWMoKT+qL7SnkDA5tUNsWCDA@mail.gmail.com>
2023-11-03  7:40 ` syzbot [this message]
     [not found] <12128c3a-3a38-ac09-577f-320e811f421f@gmail.com>
2023-11-03  7:26 ` [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in diWrite syzbot
     [not found] <a33a632b-9cb6-3187-53b2-5e3309ea0467@gmail.com>
2023-11-03  3:37 ` syzbot
     [not found] <526dbcf1-a6ee-54b5-15a4-756979ae2d90@gmail.com>
2023-11-02 20:27 ` syzbot
2022-10-21  4:45 [syzbot] " syzbot
2024-01-14  7:18 ` [syzbot] [jfs?] " syzbot
2024-01-15 13:42   ` Jan Kara
2024-01-15 14:12     ` Christian Brauner

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=000000000000fab6b506093a9cc3@google.com \
    --to=syzbot+c1056fdfe414463fdb33@syzkaller.appspotmail.com \
    --cc=ghandatmanas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller@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.