[v6.1] BUG: unable to handle kernel paging request in txBegin

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117b0c5ec80000
kernel config: https://syzkaller.appspot.com/x/.config?x=29ad3fe3c7b61175
dashboard link: https://syzkaller.appspot.com/bug?extid=e936bc3905ea91c75365
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=1360f66ec80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/34f95428f5fb/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1bdd9b2c390d/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/419140981cfa/Image-7eaef76f.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/aa3e0ee9d2b7/mount_0.gz

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

loop0: detected capacity change from 0 to 32768
find_entry called with index = 0
read_mapping_page failed!
ERROR: (device loop0): txAbort:
Unable to handle kernel paging request at virtual address dfff800000000008
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000008] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4336 Comm: syz-executor.0 Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : generic_test_bit include/asm-generic/bitops/generic-non-atomic.h:128 [inline]
pc : txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:366
lr : txBegin+0x104/0x5e0 fs/jfs/jfs_txnmgr.c:357
sp : ffff80001df17860
x29: ffff80001df17880 x28: dfff800000000000 x27: ffff80001df17940
x26: 1ffff00002b98e40 x25: 0000000000000040 x24: 0000000000000000
x23: ffff800015cd23a0 x22: ffff0000c211f830 x21: 0000000000000150
x20: 0000000000000008 x19: 0000000000000000 x18: 1ffff00003be2ec0
x17: ffff80001572d000 x16: ffff8000083239f4 x15: 0000000000000000
x14: 1ffff00002ae60b0 x13: dfff800000000000 x12: ffff700003be2ef4
x11: ff80800009a0c42c x10: 0000000000000000 x9 : ffff0000d3d13680
x8 : 1ffff00002b98e40 x7 : ffff800009a0c400 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800008323b24
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:362
jfs_link+0x1ac/0x560 fs/jfs/namei.c:802
vfs_link+0x598/0x74c fs/namei.c:4529
do_linkat+0x2f4/0x898 fs/namei.c:4600
__do_sys_linkat fs/namei.c:4628 [inline]
__se_sys_linkat fs/namei.c:4625 [inline]
__arm64_sys_linkat+0xe4/0x100 fs/namei.c:4625
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: 9400012e aa1703e0 95947120 350002f8 (387c6a88)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 9400012e bl 0x4b8
4: aa1703e0 mov x0, x23
8: 95947120 bl 0x651c488
c: 350002f8 cbnz w24, 0x68
* 10: 387c6a88 ldrb w8, [x20, x28] <-- trapping instruction


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14aa4481c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f95b212e0ccdd4d1
dashboard link: https://syzkaller.appspot.com/bug?extid=56a9533cc5dbe135edd8

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=134347d6c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1041fc5ec80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6153dfa8dcc0/disk-8020ae3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2093d52db59f/vmlinux-8020ae3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/85041d0bd356/Image-8020ae3c.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2b14963f12e4/mount_0.gz

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

Reported-by: syzbot+56a953...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 32768
find_entry called with index = 0
read_mapping_page failed!
ERROR: (device loop0): txAbort:
Unable to handle kernel paging request at virtual address dfff800000000008

Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000008] address between user and kernel address ranges

Internal error: Oops: 96000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4068 Comm: syz-executor375 Not tainted 5.15.103-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

pc : arch_test_bit include/asm-generic/bitops/non-atomic.h:118 [inline]

pc : txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:366
lr : txBegin+0x104/0x5e0 fs/jfs/jfs_txnmgr.c:357

sp : ffff80001ce47840
x29: ffff80001ce47860 x28: dfff800000000000 x27: ffff80001ce47920
x26: 1ffff000029e19cc x25: 0000000000000040 x24: 0000000000000000
x23: ffff800014f18020 x22: ffff0000c1c2a630 x21: 0000000000000150
x20: 0000000000000008 x19: 0000000000000000 x18: 0000000000000000
x17: ff8080000a6111e0 x16: ffff800008307744 x15: ffff80000a6111e0
x14: 1ffff0000293806a x13: ffffffffffffffff x12: 0000000000000000
x11: ff808000098e5910 x10: 0000000000000000 x9 : ffff0000c82f3580
x8 : 1ffff000029e19cc x7 : ffff8000098e58e4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800008307874

x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:362
jfs_link+0x1ac/0x560 fs/jfs/namei.c:802

vfs_link+0x598/0x74c fs/namei.c:4486
do_linkat+0x2f4/0x898 fs/namei.c:4557
__do_sys_linkat fs/namei.c:4585 [inline]
__se_sys_linkat fs/namei.c:4582 [inline]
__arm64_sys_linkat+0xe4/0x100 fs/namei.c:4582
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9400012e aa1703e0 95990181 350002f8 (387c6a88)
---[ end trace ae92164d26e2cc05 ]---

----------------
Code disassembly (best guess):
0: 9400012e bl 0x4b8
4: aa1703e0 mov x0, x23

8: 95990181 bl 0x664060c

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: bf4ad6fa4e53 Linux 6.1.28
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1682419e280000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee1a89a0c6a2db67

dashboard link: https://syzkaller.appspot.com/bug?extid=e936bc3905ea91c75365
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=1468e22a280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124428aa280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a7b85a636ba8/disk-bf4ad6fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a626aeb9d231/vmlinux-bf4ad6fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/78fbbffb9ee8/Image-bf4ad6fa.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/33678a244116/mount_0.gz

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

WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================

Unable to handle kernel paging request at virtual address dfff800000000008
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000008] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4215 Comm: syz-executor207 Not tainted 6.1.28-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023

pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : generic_test_bit include/asm-generic/bitops/generic-non-atomic.h:128 [inline]
pc : txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:366
lr : txBegin+0x104/0x5e0 fs/jfs/jfs_txnmgr.c:357

sp : ffff80001d957660
x29: ffff80001d957680 x28: dfff800000000000 x27: dfff800000000000
x26: ffff800015b30a08 x25: 0000000000000040 x24: 0000000000000000
x23: ffff800015b2e360 x22: ffff0000cd8eee30 x21: 0000000000000150
x20: 0000000000000008 x19: 0000000000000000 x18: ffff80001d957360
x17: ffff800008ad9574 x16: ffff80000831de80 x15: 000000000000b3dc
x14: 000000002e93d417 x13: dfff800000000000 x12: ffff700003b2aeb4
x11: ff808000099b9870 x10: 0000000000000000 x9 : ffff0000d63d8000
x8 : 1ffff00002b64638 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800018738ac8 x4 : 0000000000000008 x3 : ffff80000831dfb0

x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:362

__jfs_xattr_set+0xc8/0x190 fs/jfs/xattr.c:915
jfs_xattr_set+0x58/0x70 fs/jfs/xattr.c:941
__vfs_setxattr+0x388/0x3a4 fs/xattr.c:182
__vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:216
__vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277
vfs_setxattr+0x1a8/0x344 fs/xattr.c:309
do_setxattr fs/xattr.c:594 [inline]
setxattr+0x230/0x294 fs/xattr.c:617
path_setxattr+0x17c/0x258 fs/xattr.c:636
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648

__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Code: 9400012e aa1703e0 9595737d 350002f8 (387c6a88)

---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 9400012e bl 0x4b8
4: aa1703e0 mov x0, x23

8: 9595737d bl 0x655cdfc

c: 350002f8 cbnz w24, 0x68
* 10: 387c6a88 ldrb w8, [x20, x28] <-- trapping instruction


---

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.