[v5.15] kernel BUG in txUnlock

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14f0717d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a2696a271d0eba
dashboard link: https://syzkaller.appspot.com/bug?extid=3c3866c71da45ef61201
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8ff3613d3f6b/disk-0ab06468.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eebe2d8c6813/vmlinux-0ab06468.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f30284c26197/Image-0ab06468.gz.xz

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

BUG at fs/jfs/jfs_txnmgr.c:926 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:926!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 239 Comm: jfsCommit Not tainted 5.15.114-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
lr : txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
sp : ffff80001ae97be0
x29: ffff80001ae97c60 x28: dfff800000000000 x27: ffff800018503438
x26: ffff800018503000 x25: ffff8000185033e4 x24: ffff800018503000
x23: ffff80001c222000 x22: 0000000000000000 x21: 0000000000000048
x20: 0000000000001000 x19: ffff0000ce4492e8 x18: 0000000000000001
x17: ff80800008335ea8 x16: ffff8000119495b4 x15: ffff800008335ea8
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000832d950 x10: 0000000000000000 x9 : ced532e0a9f6e800
x8 : ced532e0a9f6e800 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001ae97358 x4 : ffff8000149afca0 x3 : ffff80000a951d80
x2 : ffff0001b481ed10 x1 : 0000000100000000 x0 : 0000000000000037
Call trace:
txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
txLazyCommit fs/jfs/jfs_txnmgr.c:2711 [inline]
jfs_lazycommit+0x4a0/0xa40 fs/jfs/jfs_txnmgr.c:2761
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: b0042803 913d8063 528073c2 95992a7c (d4210000)
---[ end trace 3119dae63aeb8850 ]---


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10faa41d280000

kernel config: https://syzkaller.appspot.com/x/.config?x=9a2696a271d0eba
dashboard link: https://syzkaller.appspot.com/bug?extid=3c3866c71da45ef61201
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10897cb6280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=157c8293280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8ff3613d3f6b/disk-0ab06468.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eebe2d8c6813/vmlinux-0ab06468.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f30284c26197/Image-0ab06468.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/29fed4fbe8f5/mount_0.gz

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

BUG at fs/jfs/jfs_txnmgr.c:926 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:926!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 240 Comm: jfsCommit Not tainted 5.15.114-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
lr : txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
sp : ffff80001ae97be0
x29: ffff80001ae97c60 x28: dfff800000000000 x27: ffff800018503438
x26: ffff800018503000 x25: ffff8000185033e4 x24: ffff800018503000
x23: ffff80001c222000 x22: 0000000000000000 x21: 0000000000000048

x20: 0000000000001000 x19: ffff0000da3d6d90 x18: 0000000000000001

x17: ff80800008335ea8 x16: ffff8000119495b4 x15: ffff800008335ea8
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000

x11: ff8080000832d950 x10: 0000000000000000 x9 : bef0a64e51e52d00
x8 : bef0a64e51e52d00 x7 : 0000000000000001 x6 : 0000000000000001

x5 : ffff80001ae97358 x4 : ffff8000149afca0 x3 : ffff80000a951d80
x2 : ffff0001b481ed10 x1 : 0000000100000000 x0 : 0000000000000037
Call trace:
txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
txLazyCommit fs/jfs/jfs_txnmgr.c:2711 [inline]
jfs_lazycommit+0x4a0/0xa40 fs/jfs/jfs_txnmgr.c:2761
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: b0042803 913d8063 528073c2 95992a7c (d4210000)

---[ end trace b5ce0db03c174a3c ]---


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2869ace6eeb Linux 6.1.31
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e91969280000
kernel config: https://syzkaller.appspot.com/x/.config?x=11263f470b7a4c92
dashboard link: https://syzkaller.appspot.com/bug?extid=d1ae34d83d7e0bb72ed8

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c46c45280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156c4101280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b17a7cd87498/disk-d2869ace.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cc8291ae723a/vmlinux-d2869ace.xz
kernel image: https://storage.googleapis.com/syzbot-assets/04943541fc25/Image-d2869ace.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4ef94641530e/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+d1ae34...@syzkaller.appspotmail.com

BUG at fs/jfs/jfs_txnmgr.c:926 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:926!

Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 92 Comm: jfsCommit Not tainted 6.1.31-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926
lr : txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926

sp : ffff80001d6c7c00
x29: ffff80001d6c7c80 x28: dfff800000000000 x27: ffff8000197915f8
x26: ffff800019791000 x25: ffff8000197915a4 x24: ffff800019791000
x23: ffff80001d23a000 x22: 0000000000000000 x21: 0000000000000048
x20: 0000000000001000 x19: ffff0000cc818d90 x18: ffff80001d6c7860
x17: 0000000000000000 x16: ffff8000120fd0f4 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000001
x11: ff80800008345658 x10: 0000000000000000 x9 : f698e708dcc9e400
x8 : f698e708dcc9e400 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001d6c7518 x4 : ffff8000156a2ac0 x3 : ffff80000aa75f4c
x2 : ffff0001b45cfcd0 x1 : 0000000100000000 x0 : 0000000000000037

Call trace:
txUnlock+0xb84/0xbb0 fs/jfs/jfs_txnmgr.c:926

txLazyCommit fs/jfs/jfs_txnmgr.c:2677 [inline]
jfs_lazycommit+0x490/0x988 fs/jfs/jfs_txnmgr.c:2727
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: 90045fe3 913a0063 528073c2 95958e61 (d4210000)
---[ end trace 0000000000000000 ]---

---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.