From: syzbot <syzbot+fafc2cbca26ad7368aae@syzkaller.appspotmail.com>
To: driver-core@lists.linux.dev, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: [syzbot] [kernfs?] WARNING in generic_access_phys
Date: Sun, 30 Aug 2026 08:03:29 -0700 [thread overview]
Message-ID: <6a944641.4d659fcc.734b4.003b.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 45c13f3f9e3b Merge tag 'hwlock-v7.3' of git://git.kernel.o..
git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux master
console output: https://syzkaller.appspot.com/x/log.txt?x=173c5d79580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d6a4e008e57a0e64
dashboard link: https://syzkaller.appspot.com/bug?extid=fafc2cbca26ad7368aae
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: arm
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d7ac15580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17320349580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/fa3fbcfdac58/non_bootable_disk-45c13f3f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f88d9fecef79/vmlinux-45c13f3f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/87ae79a5d86d/zImage-45c13f3f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fafc2cbca26ad7368aae@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: ./arch/arm64/include/asm/io.h:283 at rcu_read_unlock include/linux/rcupdate.h:878 [inline], CPU#0: syz.2.18/3678
WARNING: ./arch/arm64/include/asm/io.h:283 at pte_unmap include/linux/pgtable.h:117 [inline], CPU#0: syz.2.18/3678
WARNING: ./arch/arm64/include/asm/io.h:283 at follow_pfnmap_end mm/memory.c:7077 [inline], CPU#0: syz.2.18/3678
WARNING: ./arch/arm64/include/asm/io.h:283 at generic_access_phys+0x26c/0x344 mm/memory.c:7126, CPU#0: syz.2.18/3678
Modules linked in:
CPU: 0 UID: 0 PID: 3678 Comm: syz.2.18 Tainted: G W syzkaller #0 PREEMPT
Tainted: [W]=WARN
Hardware name: linux,dummy-virt (DT)
pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ioremap_prot arch/arm64/include/asm/io.h:283 [inline]
pc : generic_access_phys+0x26c/0x344 mm/memory.c:7116
lr : rcu_read_unlock include/linux/rcupdate.h:882 [inline]
lr : pte_unmap include/linux/pgtable.h:117 [inline]
lr : follow_pfnmap_end mm/memory.c:7077 [inline]
lr : generic_access_phys+0xcc/0x344 mm/memory.c:7111
sp : ffff8000a1d37830
x29: ffff8000a1d378f0 x28: ffff8000a1d37870 x27: 0000000000000000
x26: 0000000000000001 x25: ffff700010ef8fd0 x24: 0000000000001000
x23: ffff8000877c7e80 x22: 0000000000000000 x21: 0160000000000f92
x20: ffff000017a38a00 x19: 0000000010042000 x18: 0000000000000000
x17: ffff800080c267fc x16: ffff800080e49be0 x15: ffff800080e496d8
x14: ffff800080a8ead0 x13: ffff800089e66530 x12: ffff600003cfbfbd
x11: 1fffe00003cfbfbc x10: ffff600003cfbfbc x9 : dfff800000000000
x8 : ffff00001e7dfde0 x7 : 0000000000000001 x6 : ffff600003cfbfbc
x5 : ffff00001e7dfde0 x4 : 0000000000000000 x3 : 1fffe000025ac430
x2 : 0000000000000000 x1 : 0000000000001000 x0 : 000000003fffffff
Call trace:
rcu_read_unlock include/linux/rcupdate.h:878 [inline] (P)
pte_unmap include/linux/pgtable.h:117 [inline] (P)
follow_pfnmap_end mm/memory.c:7077 [inline] (P)
generic_access_phys+0x26c/0x344 mm/memory.c:7126 (P)
kernfs_vma_access+0x14c/0x1f0 fs/kernfs/file.c:437
__access_remote_vm+0x3dc/0x600 mm/memory.c:7194
access_remote_vm+0x10/0x20 mm/memory.c:7241
mem_rw+0x16c/0x580 fs/proc/base.c:912
mem_read+0x14/0x20 fs/proc/base.c:940
vfs_read+0x190/0xa18 fs/read_write.c:572
ksys_read+0xf0/0x1e0 fs/read_write.c:716
__do_sys_read fs/read_write.c:725 [inline]
__se_sys_read fs/read_write.c:723 [inline]
__arm64_sys_read+0x70/0xa0 fs/read_write.c:723
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x74/0x240 arch/arm64/kernel/syscall.c:49
el0_svc_common.constprop.0+0xac/0x230 arch/arm64/kernel/syscall.c:121
do_el0_svc_compat+0x40/0x58 arch/arm64/kernel/syscall.c:146
el0_svc_compat+0x54/0x264 arch/arm64/kernel/entry-common.c:909
el0t_32_sync_handler+0x88/0xac arch/arm64/kernel/entry-common.c:927
el0t_32_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:595
irq event stamp: 2118
hardirqs last enabled at (2117): [<ffff8000859a8084>] irqentry_exit_to_kernel_mode_after_preempt include/linux/irq-entry-common.h:507 [inline]
hardirqs last enabled at (2117): [<ffff8000859a8084>] __arm64_exit_to_kernel_mode+0x38/0x98 arch/arm64/kernel/entry-common.c:60
hardirqs last disabled at (2118): [<ffff8000859a81d0>] el1_brk64+0x20/0x54 arch/arm64/kernel/entry-common.c:445
softirqs last enabled at (2112): [<ffff80008023b5b8>] softirq_handle_end kernel/softirq.c:491 [inline]
softirqs last enabled at (2112): [<ffff80008023b5b8>] handle_softirqs+0xa98/0x1048 kernel/softirq.c:673
softirqs last disabled at (2101): [<ffff8000800103d4>] __do_softirq+0x14/0x20 kernel/softirq.c:679
---[ 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 syzkaller@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 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.
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
reply other threads:[~2026-08-30 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a944641.4d659fcc.734b4.003b.GAE@google.com \
--to=syzbot+fafc2cbca26ad7368aae@syzkaller.appspotmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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.