Hello,
syzbot found the following issue on:
HEAD commit: 91786f140358 Linux 5.15.175
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12cfb8b0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=792c138814af56fb
dashboard link:
https://syzkaller.appspot.com/bug?extid=7f1ee65449b27b007e6b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/703bce36932e/disk-91786f14.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/f72d0cd34063/vmlinux-91786f14.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3ea47692ed8c/Image-91786f14.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7f1ee6...@syzkaller.appspotmail.com
Is remount racy?
jfs_dirty_inode called on read-only volume
Is remount racy?
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: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 8663 Comm: syz.0.528 Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : arch_test_bit include/asm-generic/bitops/non-atomic.h:118 [inline]
pc : txBeginAnon+0xac/0x154 fs/jfs/jfs_txnmgr.c:465
lr : spin_lock include/linux/spinlock.h:363 [inline]
lr : txBeginAnon+0x78/0x154 fs/jfs/jfs_txnmgr.c:458
sp : ffff8000218373e0
x29: ffff8000218373e0 x28: ffff80001b926e68 x27: ffff80001b926000
x26: ffff80001b926000 x25: 0000000000000008 x24: 0000000000000150
x23: dfff800000000000 x22: 0000000000000001 x21: 0000000000000000
x20: 0000000000000040 x19: ffff8000150e0200 x18: ffff8000218371a8
x17: 0000000000000002 x16: ffff800008305354 x15: 0000000000000005
x14: 1ffff0000296e06c x13: dfff800000000000 x12: ffff700004306e60
x11: 1ffff00004306e60 x10: 0000000000000004 x9 : b6503a6e477d1f00
x8 : b6503a6e477d1f00 x7 : ffff80000998543c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800008305484
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
txBeginAnon+0xac/0x154
extAlloc+0xe0/0xe68 fs/jfs/jfs_extent.c:81
jfs_get_block+0x34c/0xbfc fs/jfs/inode.c:258
nobh_write_begin+0x2d8/0xa28 fs/buffer.c:2650
jfs_write_begin+0x58/0xa0 fs/jfs/inode.c:322
generic_perform_write+0x24c/0x520 mm/filemap.c:3785
__generic_file_write_iter+0x230/0x454 mm/filemap.c:3912
generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3944
call_write_iter include/linux/fs.h:2174 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x884/0xb44 fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: aa1803e0 97ffff65 aa1303e0 95964225 (38776b28)
---[ end trace 37e8835c6e2323f6 ]---
----------------
Code disassembly (best guess):
0: aa1803e0 mov x0, x24
4: 97ffff65 bl 0xfffffffffffffd98
8: aa1303e0 mov x0, x19
c: 95964225 bl 0x65908a0
* 10: 38776b28 ldrb w8, [x25, x23] <-- 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.
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