* [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
@ 2025-05-11 17:44 syzbot
2025-05-21 17:28 ` Ard Biesheuvel
0 siblings, 1 reply; 8+ messages in thread
From: syzbot @ 2025-05-11 17:44 UTC (permalink / raw)
To: ardb, jk, linux-efi, linux-fsdevel, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: c32f8dc5aaf9 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1762d670580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea4635ffd6ad5b4a
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165c0cd4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f49cf4580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b921498959d4/disk-c32f8dc5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/04e6ad946c4b/vmlinux-c32f8dc5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4f0d8db50ee/Image-c32f8dc5.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com
efivarfs: resyncing variable state
Unable to handle kernel paging request at virtual address dfff800000000005
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
Mem abort info:
ESR = 0x0000000096000005
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x05: level 1 translation fault
Data abort info:
ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[dfff800000000005] address between user and kernel address ranges
Internal error: Oops: 0000000096000005 [#1] SMP
Modules linked in:
CPU: 1 UID: 0 PID: 6487 Comm: syz-executor120 Not tainted 6.15.0-rc5-syzkaller-gc32f8dc5aaf9 #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : alloc_fs_context+0x1b4/0x76c fs/fs_context.c:294
lr : __lse_atomic64_add arch/arm64/include/asm/atomic_lse.h:134 [inline]
lr : arch_atomic64_add arch/arm64/include/asm/atomic.h:67 [inline]
lr : raw_atomic64_add include/linux/atomic/atomic-arch-fallback.h:2672 [inline]
lr : raw_atomic_long_add include/linux/atomic/atomic-long.h:121 [inline]
lr : atomic_long_add include/linux/atomic/atomic-instrumented.h:3261 [inline]
lr : get_cred_many include/linux/cred.h:203 [inline]
lr : get_cred include/linux/cred.h:218 [inline]
lr : alloc_fs_context+0x150/0x76c fs/fs_context.c:293
sp : ffff8000a31b7760
x29: ffff8000a31b7790 x28: dfff800000000000 x27: ffff0000c8ef88d8
x26: 0000000000000028 x25: ffff0000c7e6f4c8 x24: ffff80008fb953e0
x23: 0000000000000000 x22: ffff0000c7e6f498 x21: ffff0000c8ef8000
x20: 0000000000000000 x19: ffff0000c7e6f400 x18: 00000000ffffffff
x17: ffff800092f27000 x16: ffff80008adb31c0 x15: 0000000000000001
x14: 1fffe0001a05b0e0 x13: 0000000000000000 x12: 0000000000000000
x11: ffff60001a05b0e1 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : 0000000000000005 x7 : ffff80008022b2b8 x6 : ffff80008022b4b4
x5 : ffff0000dabc9c90 x4 : ffff8000a31b7520 x3 : ffff800080dfa950
x2 : 0000000000000001 x1 : 0000000000000008 x0 : 0000000000000001
Call trace:
alloc_fs_context+0x1b4/0x76c fs/fs_context.c:294 (P)
fs_context_for_mount+0x34/0x44 fs/fs_context.c:332
vfs_kern_mount+0x38/0x178 fs/namespace.c:1313
efivarfs_pm_notify+0x1c4/0x4b4 fs/efivarfs/super.c:529
notifier_call_chain+0x1b8/0x4e4 kernel/notifier.c:85
blocking_notifier_call_chain+0x70/0xa0 kernel/notifier.c:380
pm_notifier_call_chain+0x2c/0x3c kernel/power/main.c:109
snapshot_release+0x104/0x1c4 kernel/power/user.c:125
__fput+0x340/0x75c fs/file_table.c:465
____fput+0x20/0x58 fs/file_table.c:493
task_work_run+0x1dc/0x260 kernel/task_work.c:227
exit_task_work include/linux/task_work.h:40 [inline]
do_exit+0x4e8/0x1998 kernel/exit.c:953
do_group_exit+0x194/0x22c kernel/exit.c:1102
__do_sys_exit_group kernel/exit.c:1113 [inline]
__se_sys_exit_group kernel/exit.c:1111 [inline]
pid_child_should_wake+0x0/0x1dc kernel/exit.c:1111
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x58/0x17c arch/arm64/kernel/entry-common.c:767
el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
Code: 97f8a879 f9400368 9100a11a d343ff48 (387c6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 97f8a879 bl 0xffffffffffe2a1e4
4: f9400368 ldr x8, [x27]
8: 9100a11a add x26, x8, #0x28
c: d343ff48 lsr x8, x26, #3
* 10: 387c6908 ldrb w8, [x8, 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 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
[not found] <20250512103556.1921-1-hdanton@sina.com>
@ 2025-05-12 12:16 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-05-12 12:16 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
1a0db80
[ 50.686008][ C1] x20: 100000023ea8e403 x19: 0000000000000001 x18: 1fffe0003386f276
[ 50.688206][ C1] x17: ffff80010d10c000 x16: ffff80008051bab8 x15: 0000000000000001
[ 50.690427][ C1] x14: 1ffff00012dfb9d3 x13: 0000000000000000 x12: 0000000000000000
[ 50.692586][ C1] x11: ffff700012dfb9d4 x10: 0000000000ff0100 x9 : 0000000000000000
[ 50.694762][ C1] x8 : ffff0000c1a0db80 x7 : ffff800080c2b0a4 x6 : 0000000000000000
[ 50.697084][ C1] x5 : 0000000000000001 x4 : ffff800080017ae0 x3 : ffff8000802595f4
[ 50.699307][ C1] x2 : 0000000000001000 x1 : 0000000000000100 x0 : 0000000000000000
[ 50.701519][ C1] Call trace:
[ 50.702384][ C1] __apply_to_page_range+0xdb4/0x13e4 (P)
[ 50.703979][ C1] apply_to_page_range+0x4c/0x64
[ 50.705324][ C1] __change_memory_common+0xac/0x3f8
[ 50.706701][ C1] set_memory_valid+0x68/0x7c
[ 50.707998][ C1] kfence_guarded_free+0x278/0x5a8
[ 50.709452][ C1] __kfence_free+0x104/0x198
[ 50.710773][ C1] kfree+0x268/0x474
[ 50.711881][ C1] kfree_const+0x4c/0x5c
[ 50.713049][ C1] kernfs_free_rcu+0x44/0x10c
[ 50.714419][ C1] rcu_core+0x848/0x17a4
[ 50.715638][ C1] rcu_core_si+0x10/0x1c
[ 50.716822][ C1] handle_softirqs+0x328/0xc88
[ 50.718177][ C1] __do_softirq+0x14/0x20
[ 50.719375][ C1] ____do_softirq+0x14/0x20
[ 50.720644][ C1] call_on_irq_stack+0x24/0x30
[ 50.721954][ C1] do_softirq_own_stack+0x20/0x2c
[ 50.723366][ C1] __irq_exit_rcu+0x1b0/0x478
[ 50.724682][ C1] irq_exit_rcu+0x14/0x84
[ 50.725924][ C1] el1_interrupt+0x38/0x54
[ 50.727207][ C1] el1h_64_irq_handler+0x18/0x24
[ 50.728623][ C1] el1h_64_irq+0x6c/0x70
[ 50.729813][ C1] arch_local_irq_enable+0x8/0xc (P)
[ 50.731273][ C1] do_idle+0x1d8/0x454
[ 50.732429][ C1] cpu_startup_entry+0x5c/0x74
[ 50.733755][ C1] secondary_start_kernel+0x1b8/0x1e0
[ 50.735283][ C1] __secondary_switched+0xc0/0xc4
[ 50.736649][ C1] irq event stamp: 183085
[ 50.737808][ C1] hardirqs last enabled at (183084): [<ffff80008add9260>] _raw_spin_unlock_irqrestore+0x38/0x98
[ 50.740790][ C1] hardirqs last disabled at (183085): [<ffff80008adb36f0>] el1_dbg+0x24/0x80
[ 50.743274][ C1] softirqs last enabled at (183056): [<ffff8000803ce71c>] handle_softirqs+0xaf8/0xc88
[ 50.745975][ C1] softirqs last disabled at (183063): [<ffff800080020efc>] __do_softirq+0x14/0x20
[ 50.748444][ C1] ---[ end trace 0000000000000000 ]---
[ 50.812816][ T6497] cgroup: Unknown subsys name 'cpuset'
[ 50.816645][ T6497] cgroup: Unknown subsys name 'rlimit'
[ 51.050390][ C1] ------------[ cut here ]------------
[ 51.050431][ C1] WARNING: CPU: 1 PID: 0 at ./arch/arm64/include/asm/pgtable.h:82 __apply_to_page_range+0xdb4/0x13e4
[ 51.054712][ C1] Modules linked in:
[ 51.055752][ C1] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Tainted: G W 6.15.0-rc5-syzkaller-00074-gac57c6b0f09c-dirty #0 PREEMPT
[ 51.059187][ C1] Tainted: [W]=WARN
[ 51.060165][ C1] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[ 51.062773][ C1] pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 51.064825][ C1] pc : __apply_to_page_range+0xdb4/0x13e4
[ 51.066326][ C1] lr : __apply_to_page_range+0xdb4/0x13e4
[ 51.067828][ C1] sp : ffff8000800178e0
[ 51.068927][ C1] x29: ffff800080017a00 x28: ffff0001ffab6fff x27: ffff0001fec50fe8
[ 51.071091][ C1] x26: ffff0001ffab7000 x25: dfff800000000000 x24: ffff0001ffab6000
[ 51.073228][ C1] x23: ffff0001fea8e5b0 x22: 0000000000000100 x21: ffff0000c1a0db80
[ 51.075383][ C1] x20: 100000023ea8e403 x19: 0000000000000001 x18: 1fffe0003386f276
[ 51.077521][ C1] x17: 0000000000a000ae x16: ffff80008051bab8 x15: 0000000000000001
[ 51.079741][ C1] x14: 1ffff00012dfb9d3 x13: 0000000000000000 x12: 0000000000000000
[ 51.081960][ C1] x11: ffff700012dfb9d4 x10: 0000000000ff0100 x9 : 0000000000000000
[ 51.084085][ C1] x8 : ffff0000c1a0db80 x7 : ffff800080c2b0a4 x6 : 0000000000000000
[ 51.086325][ C1] x5 : 0000000000000001 x4 : ffff800080017ae0 x3 : ffff8000802595f4
[ 51.088580][ C1] x2 : 0000000000001000 x1 : 0000000000000100 x0 : 0000000000000000
[ 51.090693][ C1] Call trace:
[ 51.091603][ C1] __apply_to_page_range+0xdb4/0x13e4 (P)
[ 51.093081][ C1] apply_to_page_range+0x4c/0x64
[ 51.094442][ C1] __change_memory_common+0xac/0x3f8
[ 51.096008][ C1] set_memory_valid+0x68/0x7c
[ 51.097312][ C1] kfence_guarded_free+0x278/0x5a8
[ 51.098643][ C1] __kfence_free+0x104/0x198
[ 51.099879][ C1] kfree+0x268/0x474
[ 51.100930][ C1] kfree_const+0x4c/0x5c
[ 51.102050][ C1] kernfs_free_rcu+0x44/0x10c
[ 51.103361][ C1] rcu_core+0x848/0x17a4
[ 51.104517][ C1] rcu_core_si+0x10/0x1c
[ 51.105679][ C1] handle_softirqs+0x328/0xc88
[ 51.107031][ C1] __do_softirq+0x14/0x20
[ 51.108222][ C1] ____do_softirq+0x14/0x20
[ 51.109457][ C1] call_on_irq_stack+0x24/0x30
[ 51.110782][ C1] do_softirq_own_stack+0x20/0x2c
[ 51.112116][ C1] __irq_exit_rcu+0x1b0/0x478
[ 51.113392][ C1] irq_exit_rcu+0x14/0x84
[ 51.114620][ C1] el1_interrupt+0x38/0x54
[ 51.115842][ C1] el1h_64_irq_handler+0x18/0x24
[ 51.117189][ C1] el1h_64_irq+0x6c/0x70
[ 51.118353][ C1] arch_local_irq_enable+0x8/0xc (P)
[ 51.119867][ C1] do_idle+0x1d8/0x454
[ 51.121024][ C1] cpu_startup_entry+0x5c/0x74
[ 51.122337][ C1] secondary_start_kernel+0x1b8/0x1e0
[ 51.123823][ C1] __secondary_switched+0xc0/0xc4
[ 51.125178][ C1] irq event stamp: 184981
[ 51.126326][ C1] hardirqs last enabled at (184980): [<ffff80008add9260>] _raw_spin_unlock_irqrestore+0x38/0x98
[ 51.129228][ C1] hardirqs last disabled at (184981): [<ffff80008adb36f0>] el1_dbg+0x24/0x80
[ 51.131633][ C1] softirqs last enabled at (184782): [<ffff8000803ce71c>] handle_softirqs+0xaf8/0xc88
[ 51.134331][ C1] softirqs last disabled at (184797): [<ffff800080020efc>] __do_softirq+0x14/0x20
[ 51.136877][ C1] ---[ end trace 0000000000000000 ]---
[ 51.243748][ T6497] Adding 124996k swap on ./swap-file. Priority:0 extents:1 across:124996k SS
[ 51.690075][ C0] ------------[ cut here ]------------
[ 51.690111][ C0] WARNING: CPU: 0 PID: 6491 at ./arch/arm64/include/asm/pgtable.h:82 __apply_to_page_range+0xdb4/0x13e4
[ 51.694504][ C0] Modules linked in:
[ 51.695522][ C0] CPU: 0 UID: 0 PID: 6491 Comm: syz-execprog Tainted: G W 6.15.0-rc5-syzkaller-00074-gac57c6b0f09c-dirty #0 PREEMPT
[ 51.699101][ C0] Tainted: [W]=WARN
[ 51.700080][ C0] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[ 51.702686][ C0] pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 51.704754][ C0] pc : __apply_to_page_range+0xdb4/0x13e4
[ 51.706283][ C0] lr : __apply_to_page_range+0xdb4/0x13e4
[ 51.707787][ C0] sp : ffff8000800078a0
[ 51.708883][ C0] x29: ffff8000800079c0 x28: ffff0001ffabafff x27: ffff0001fec50fe8
[ 51.711000][ C0] x26: ffff0001ffabb000 x25: dfff800000000000 x24: ffff0001ffaba000
[ 51.713161][ C0] x23: ffff0001fea8e5d0 x22: 0000000000000100 x21: ffff0000cbe1bd00
[ 51.715296][ C0] x20: 100000023ea8e403 x19: 0000000000000001 x18: 0000000000000000
[ 51.717395][ C0] x17: ffff80010d0e8000 x16: ffff80008051bab8 x15: 0000000000000001
[ 51.719486][ C0] x14: 1ffff00012dfb9de x13: 0000000000000000 x12: 0000000000000000
[ 51.721692][ C0] x11: ffff700012dfb9df x10: 0000000000ff0100 x9 : 0000000000000000
[ 51.723778][ C0] x8 : ffff0000cbe1bd00 x7 : ffff800080c2b0a4 x6 : 0000000000000000
[ 51.725938][ C0] x5 : 0000000000000001 x4 : ffff800080007aa0 x3 : ffff8000802595f4
[ 51.728091][ C0] x2 : 0000000000001000 x1 : 0000000000000100 x0 : 0000000000000000
[ 51.730331][ C0] Call trace:
[ 51.731253][ C0] __apply_to_page_range+0xdb4/0x13e4 (P)
[ 51.732812][ C0] apply_to_page_range+0x4c/0x64
[ 51.734169][ C0] __change_memory_common+0xac/0x3f8
[ 51.735625][ C0] set_memory_valid+0x68/0x7c
[ 51.736923][ C0] kfence_guarded_free+0x278/0x5a8
[ 51.738333][ C0] __kfence_free+0x104/0x198
[ 51.739625][ C0] kmem_cache_free+0x250/0x550
[ 51.740976][ C0] ptlock_free+0x54/0x6c
[ 51.742137][ C0] __tlb_remove_table+0x30/0x274
[ 51.743585][ C0] tlb_remove_table_rcu+0x8c/0x19c
[ 51.744997][ C0] rcu_core+0x848/0x17a4
[ 51.746179][ C0] rcu_core_si+0x10/0x1c
[ 51.747292][ C0] handle_softirqs+0x328/0xc88
[ 51.748528][ C0] __do_softirq+0x14/0x20
[ 51.749673][ C0] ____do_softirq+0x14/0x20
[ 51.750870][ C0] call_on_irq_stack+0x24/0x30
[ 51.752212][ C0] do_softirq_own_stack+0x20/0x2c
[ 51.753708][ C0] __irq_exit_rcu+0x1b0/0x478
[ 51.754990][ C0] irq_exit_rcu+0x14/0x84
[ 51.756184][ C0] el0_interrupt+0x70/0x1cc
[ 51.757440][ C0] __el0_irq_handler_common+0x18/0x24
[ 51.758933][ C0] el0t_64_irq_handler+0x10/0x1c
[ 51.760272][ C0] el0t_64_irq+0x198/0x19c
[ 51.761565][ C0] irq event stamp: 286065
[ 51.762786][ C0] hardirqs last enabled at (286064): [<ffff80008add9260>] _raw_spin_unlock_irqrestore+0x38/0x98
[ 51.765644][ C0] hardirqs last disabled at (286065): [<ffff80008adb36f0>] el1_dbg+0x24/0x80
[ 51.768096][ C0] softirqs last enabled at (283478): [<ffff8000801fbf10>] local_bh_enable+0x10/0x34
[ 51.770695][ C0] softirqs last disabled at (286021): [<ffff800080020efc>] __do_softirq+0x14/0x20
[ 51.773251][ C0] ---[ end trace 0000000000000000 ]---
[ 51.774951][ C0] ------------[ cut here ]------------
[ 51.774972][ C0] WARNING: CPU: 0 PID: 6491 at ./arch/arm64/include/asm/pgtable.h:82 __apply_to_page_range+0xdb4/0x13e4
[ 51.779515][ C0] Modules linked in:
[ 51.780538][ C0] CPU: 0 UID: 0 PID: 6491 Comm: syz-execprog Tainted: G W 6.15.0-rc5-syzkaller-00074-gac57c6b0f09c-dirty #0 PREEMPT
[ 51.784203][ C0] Tainted: [W]=WARN
[ 51.785252][ C0] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[ 51.787997][ C0] pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 51.790115][ C0] pc : __apply_to_page_range+0xdb4/0x13e4
[ 51.791695][ C0] lr : __apply_to_page_range+0xdb4/0x13e4
[ 51.793255][ C0] sp : ffff8000800078a0
[ 51.794412][ C0] x29: ffff8000800079c0 x28: ffff0001ffabcfff x27: ffff0001fec50fe8
[ 51.796586][ C0] x26: ffff0001ffabd000 x25: dfff800000000000 x24: ffff0001ffabc000
[ 51.798868][ C0] x23: ffff0001fea8e5e0 x22: 0000000000000100 x21: ffff0000cbe1bd00
[ 51.800997][ C0] x20: 100000023ea8e403 x19: 0000000000000001 x18: 0000000000000000
[ 51.803201][ C0] x17: ffff80010d0e8000 x16: ffff80008051bab8 x15: 0000000000000001
[ 51.805436][ C0] x14: 1ffff00012dfb9de x13: 0000000000000000 x12: 0000000000000000
[ 51.807588][ C0] x11: ffff700012dfb9df x10: 0000000000ff0100 x9 : 0000000000000000
[ 51.809768][ C0] x8 : ffff0000cbe1bd00 x7 : ffff800080c2b0a4 x6 : 0000000000000000
[ 51.811888][ C0] x5 : 0000000000000001 x4 : ffff800080007aa0 x3 : ffff8000802595f4
[ 51.814041][ C0] x2 : 0000000000001000 x1 : 0000000000000100 x0 : 0000000000000000
[ 51.816212][ C0] Call trace:
[ 51.817092][ C0] __apply_to_page_range+0xdb4/0x13e4 (P)
[ 51.818619][ C0] apply_to_page_range+0x4c/0x64
[ 51.820066][ C0] __change_memory_common+0xac/0x3f8
[ 51.821458][ C0] set_memory_valid+0x68/0x7c
[ 51.822766][ C0] kfence_guarded_free+0x278/0x5a8
[ 51.824160][ C0] __kfence_free+0x104/0x198
[ 51.825411][ C0] kmem_cache_free+0x250/0x550
[ 51.826691][ C0] ptlock_free+0x54/0x6c
[ 51.827867][ C0] __tlb_remove_table+0x30/0x274
[ 51.829272][ C0] tlb_remove_table_rcu+0x8c/0x19c
[ 51.830704][ C0] rcu_core+0x848/0x17a4
[ 51.831879][ C0] rcu_core_si+0x10/0x1c
[ 51.833075][ C0] handle_softirqs+0x328/0xc88
[ 51.834388][ C0] __do_softirq+0x14/0x20
[ 51.835549][ C0] ____do_softirq+0x14/0x20
[ 51.836791][ C0] call_on_irq_stack+0x24/0x30
[ 51.838086][ C0] do_softirq_own_stack+0x20/0x2c
[ 51.839483][ C0] __irq_exit_rcu+0x1b0/0x478
[ 51.840787][ C0] irq_exit_rcu+0x14/0x84
[ 51.841957][ C0] el0_interrupt+0x70/0x1cc
[ 51.843202][ C0] __el0_irq_handler_common+0x18/0x24
[ 51.844787][ C0] el0t_64_irq_handler+0x10/0x1c
[ 51.846102][ C0] el0t_64_irq+0x198/0x19c
[ 51.847396][ C0] irq event stamp: 286155
[ 51.848596][ C0] hardirqs last enabled at (286154): [<ffff80008add9260>] _raw_spin_unlock_irqrestore+0x38/0x98
[ 51.851518][ C0] hardirqs last disabled at (286155): [<ffff80008adb36f0>] el1_dbg+0x24/0x80
[ 51.853934][ C0] softirqs last enabled at (283478): [<ffff8000801fbf10>] local_bh_enable+0x10/0x34
[ 51.856474][ C0] softirqs last disabled at (286021): [<ffff800080020efc>] __do_softirq+0x14/0x20
[ 51.858941][ C0] ---[ end trace 0000000000000000 ]---
syzkaller build log:
go env (err=<nil>)
GO111MODULE='auto'
GOARCH='amd64'
GOBIN=''
GOCACHE='/syzkaller/.cache/go-build'
GOENV='/syzkaller/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/syzkaller/jobs-2/linux/gopath/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/syzkaller/jobs-2/linux/gopath'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/syzkaller/jobs-2/linux/gopath/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.7.linux-amd64'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/syzkaller/jobs-2/linux/gopath/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.7.linux-amd64/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.7'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/syzkaller/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/syzkaller/jobs-2/linux/gopath/src/github.com/google/syzkaller/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2619555960=/tmp/go-build -gno-record-gcc-switches'
git status (err=<nil>)
HEAD detached at 77908e5f2ae
nothing to commit, working tree clean
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Makefile:31: run command via tools/syz-env for best compatibility, see:
Makefile:32: https://github.com/google/syzkaller/blob/master/docs/contributing.md#using-syz-env
go list -f '{{.Stale}}' ./sys/syz-sysgen | grep -q false || go install ./sys/syz-sysgen
make .descriptions
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Makefile:31: run command via tools/syz-env for best compatibility, see:
Makefile:32: https://github.com/google/syzkaller/blob/master/docs/contributing.md#using-syz-env
bin/syz-sysgen
touch .descriptions
GOOS=linux GOARCH=arm64 go build "-ldflags=-s -w -X github.com/google/syzkaller/prog.GitRevision=77908e5f2ae80bee6d434bca762a25a0a5fc6a83 -X 'github.com/google/syzkaller/prog.gitRevisionDate=20250509-090543'" -o ./bin/linux_arm64/syz-execprog github.com/google/syzkaller/tools/syz-execprog
mkdir -p ./bin/linux_arm64
aarch64-linux-gnu-g++ -o ./bin/linux_arm64/syz-executor executor/executor.cc \
-O2 -pthread -Wall -Werror -Wparentheses -Wunused-const-variable -Wframe-larger-than=16384 -Wno-stringop-overflow -Wno-array-bounds -Wno-format-overflow -Wno-unused-but-set-variable -Wno-unused-command-line-argument -static-pie -std=c++17 -I. -Iexecutor/_include -DGOOS_linux=1 -DGOARCH_arm64=1 \
-DHOSTGOOS_linux=1 -DGIT_REVISION=\"77908e5f2ae80bee6d434bca762a25a0a5fc6a83\"
/usr/lib/gcc-cross/aarch64-linux-gnu/12/../../../../aarch64-linux-gnu/bin/ld: /tmp/cc7JM2Ed.o: in function `Connection::Connect(char const*, char const*)':
executor.cc:(.text._ZN10Connection7ConnectEPKcS1_[_ZN10Connection7ConnectEPKcS1_]+0xd8): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Error text is too large and was truncated, full error text is at:
https://syzkaller.appspot.com/x/error.txt?x=1270ccd4580000
Tested on:
commit: ac57c6b0 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
kernel config: https://syzkaller.appspot.com/x/.config?x=ea4635ffd6ad5b4a
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=16d1a2f4580000
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
[not found] <20250513204140.1987-1-hdanton@sina.com>
@ 2025-05-14 1:13 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-05-14 1:13 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com
Tested-by: syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com
Tested on:
commit: ac57c6b0 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1124f2f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea4635ffd6ad5b4a
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1009ecd4580000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
2025-05-11 17:44 syzbot
@ 2025-05-21 17:28 ` Ard Biesheuvel
2025-05-22 12:24 ` Christian Brauner
0 siblings, 1 reply; 8+ messages in thread
From: Ard Biesheuvel @ 2025-05-21 17:28 UTC (permalink / raw)
To: syzbot, James E.J. Bottomley, Al Viro, Christian Brauner
Cc: jk, linux-efi, linux-fsdevel, linux-kernel, syzkaller-bugs
(cc James, Al, Christian)
Please see the splat below.
The NULL dereference is due to get_cred() in alloc_fs_context()
attempting to increment current->cred->usage while current->cred ==
NULL, and this is a result of the fact that PM notifier call chain is
called while the task is exiting.
IIRC, the intent was for commit
11092db5b573 efivarfs: fix NULL dereference on resume
to be replaced at some point with something more robust; might that
address this issue as well?
Thanks,
Ard.
On Sun, 11 May 2025 at 19:44, syzbot
<syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: c32f8dc5aaf9 Merge branch 'for-next/core' into for-kernelci
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=1762d670580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ea4635ffd6ad5b4a
> dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
> compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
> userspace arch: arm64
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165c0cd4580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f49cf4580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/b921498959d4/disk-c32f8dc5.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/04e6ad946c4b/vmlinux-c32f8dc5.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/d4f0d8db50ee/Image-c32f8dc5.gz.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+52cd651546d11d2af06b@syzkaller.appspotmail.com
>
> efivarfs: resyncing variable state
> Unable to handle kernel paging request at virtual address dfff800000000005
> KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
> Mem abort info:
> ESR = 0x0000000096000005
> EC = 0x25: DABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> FSC = 0x05: level 1 translation fault
> Data abort info:
> ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
> CM = 0, WnR = 0, TnD = 0, TagAccess = 0
> GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
> [dfff800000000005] address between user and kernel address ranges
> Internal error: Oops: 0000000096000005 [#1] SMP
> Modules linked in:
> CPU: 1 UID: 0 PID: 6487 Comm: syz-executor120 Not tainted 6.15.0-rc5-syzkaller-gc32f8dc5aaf9 #0 PREEMPT
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
> pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : alloc_fs_context+0x1b4/0x76c fs/fs_context.c:294
> lr : __lse_atomic64_add arch/arm64/include/asm/atomic_lse.h:134 [inline]
> lr : arch_atomic64_add arch/arm64/include/asm/atomic.h:67 [inline]
> lr : raw_atomic64_add include/linux/atomic/atomic-arch-fallback.h:2672 [inline]
> lr : raw_atomic_long_add include/linux/atomic/atomic-long.h:121 [inline]
> lr : atomic_long_add include/linux/atomic/atomic-instrumented.h:3261 [inline]
> lr : get_cred_many include/linux/cred.h:203 [inline]
> lr : get_cred include/linux/cred.h:218 [inline]
> lr : alloc_fs_context+0x150/0x76c fs/fs_context.c:293
> sp : ffff8000a31b7760
> x29: ffff8000a31b7790 x28: dfff800000000000 x27: ffff0000c8ef88d8
> x26: 0000000000000028 x25: ffff0000c7e6f4c8 x24: ffff80008fb953e0
> x23: 0000000000000000 x22: ffff0000c7e6f498 x21: ffff0000c8ef8000
> x20: 0000000000000000 x19: ffff0000c7e6f400 x18: 00000000ffffffff
> x17: ffff800092f27000 x16: ffff80008adb31c0 x15: 0000000000000001
> x14: 1fffe0001a05b0e0 x13: 0000000000000000 x12: 0000000000000000
> x11: ffff60001a05b0e1 x10: 0000000000ff0100 x9 : 0000000000000000
> x8 : 0000000000000005 x7 : ffff80008022b2b8 x6 : ffff80008022b4b4
> x5 : ffff0000dabc9c90 x4 : ffff8000a31b7520 x3 : ffff800080dfa950
> x2 : 0000000000000001 x1 : 0000000000000008 x0 : 0000000000000001
> Call trace:
> alloc_fs_context+0x1b4/0x76c fs/fs_context.c:294 (P)
> fs_context_for_mount+0x34/0x44 fs/fs_context.c:332
> vfs_kern_mount+0x38/0x178 fs/namespace.c:1313
> efivarfs_pm_notify+0x1c4/0x4b4 fs/efivarfs/super.c:529
> notifier_call_chain+0x1b8/0x4e4 kernel/notifier.c:85
> blocking_notifier_call_chain+0x70/0xa0 kernel/notifier.c:380
> pm_notifier_call_chain+0x2c/0x3c kernel/power/main.c:109
> snapshot_release+0x104/0x1c4 kernel/power/user.c:125
> __fput+0x340/0x75c fs/file_table.c:465
> ____fput+0x20/0x58 fs/file_table.c:493
> task_work_run+0x1dc/0x260 kernel/task_work.c:227
> exit_task_work include/linux/task_work.h:40 [inline]
> do_exit+0x4e8/0x1998 kernel/exit.c:953
> do_group_exit+0x194/0x22c kernel/exit.c:1102
> __do_sys_exit_group kernel/exit.c:1113 [inline]
> __se_sys_exit_group kernel/exit.c:1111 [inline]
> pid_child_should_wake+0x0/0x1dc kernel/exit.c:1111
> __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
> invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
> el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
> do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
> el0_svc+0x58/0x17c arch/arm64/kernel/entry-common.c:767
> el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786
> el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
> Code: 97f8a879 f9400368 9100a11a d343ff48 (387c6908)
> ---[ end trace 0000000000000000 ]---
> ----------------
> Code disassembly (best guess):
> 0: 97f8a879 bl 0xffffffffffe2a1e4
> 4: f9400368 ldr x8, [x27]
> 8: 9100a11a add x26, x8, #0x28
> c: d343ff48 lsr x8, x26, #3
> * 10: 387c6908 ldrb w8, [x8, 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 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
2025-05-21 17:28 ` Ard Biesheuvel
@ 2025-05-22 12:24 ` Christian Brauner
2025-05-22 13:47 ` Ard Biesheuvel
0 siblings, 1 reply; 8+ messages in thread
From: Christian Brauner @ 2025-05-22 12:24 UTC (permalink / raw)
To: Ard Biesheuvel
Cc: syzbot, James E.J. Bottomley, Al Viro, jk, linux-efi,
linux-fsdevel, linux-kernel, syzkaller-bugs
On Wed, May 21, 2025 at 07:28:34PM +0200, Ard Biesheuvel wrote:
> (cc James, Al, Christian)
>
> Please see the splat below.
>
> The NULL dereference is due to get_cred() in alloc_fs_context()
> attempting to increment current->cred->usage while current->cred ==
> NULL, and this is a result of the fact that PM notifier call chain is
> called while the task is exiting.
>
> IIRC, the intent was for commit
>
> 11092db5b573 efivarfs: fix NULL dereference on resume
>
> to be replaced at some point with something more robust; might that
> address this issue as well?
Yes. It's in the merge queue for v6.16 which kills off all that
vfs_kern_mount() stuff.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
2025-05-22 12:24 ` Christian Brauner
@ 2025-05-22 13:47 ` Ard Biesheuvel
0 siblings, 0 replies; 8+ messages in thread
From: Ard Biesheuvel @ 2025-05-22 13:47 UTC (permalink / raw)
To: Christian Brauner
Cc: syzbot, James E.J. Bottomley, Al Viro, jk, linux-efi,
linux-fsdevel, linux-kernel, syzkaller-bugs
On Thu, 22 May 2025 at 14:24, Christian Brauner <brauner@kernel.org> wrote:
>
> On Wed, May 21, 2025 at 07:28:34PM +0200, Ard Biesheuvel wrote:
> > (cc James, Al, Christian)
> >
> > Please see the splat below.
> >
> > The NULL dereference is due to get_cred() in alloc_fs_context()
> > attempting to increment current->cred->usage while current->cred ==
> > NULL, and this is a result of the fact that PM notifier call chain is
> > called while the task is exiting.
> >
> > IIRC, the intent was for commit
> >
> > 11092db5b573 efivarfs: fix NULL dereference on resume
> >
> > to be replaced at some point with something more robust; might that
> > address this issue as well?
>
> Yes. It's in the merge queue for v6.16 which kills off all that
> vfs_kern_mount() stuff.
Excellent, thanks for the update.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
[not found] <CAMj1kXEUW2arc4E1z5VkqUm6yi_bPyPwUtvg99PpM4bQLpct5w@mail.gmail.com>
@ 2025-05-22 14:17 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-05-22 14:17 UTC (permalink / raw)
To: ardb, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: unable to handle kernel paging request in alloc_fs_context
Bluetooth: hci0: Opcode 0x0c1a failed: -4
efivarfs: resyncing variable state
Unable to handle kernel paging request at virtual address dfff800000000005
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
Mem abort info:
ESR = 0x0000000096000005
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x05: level 1 translation fault
Data abort info:
ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[dfff800000000005] address between user and kernel address ranges
Internal error: Oops: 0000000096000005 [#1] SMP
Modules linked in:
CPU: 1 UID: 0 PID: 7789 Comm: syz.0.174 Not tainted 6.15.0-rc7-syzkaller-gd7fa1af5b33e #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : alloc_fs_context+0x1b4/0x76c fs/fs_context.c:294
lr : __lse_atomic64_add arch/arm64/include/asm/atomic_lse.h:134 [inline]
lr : arch_atomic64_add arch/arm64/include/asm/atomic.h:67 [inline]
lr : raw_atomic64_add include/linux/atomic/atomic-arch-fallback.h:2672 [inline]
lr : raw_atomic_long_add include/linux/atomic/atomic-long.h:121 [inline]
lr : atomic_long_add include/linux/atomic/atomic-instrumented.h:3261 [inline]
lr : get_cred_many include/linux/cred.h:203 [inline]
lr : get_cred include/linux/cred.h:218 [inline]
lr : alloc_fs_context+0x150/0x76c fs/fs_context.c:293
sp : ffff80009b8c7440
x29: ffff80009b8c7470 x28: dfff800000000000 x27: ffff0000cbd6a758
x26: 0000000000000028 x25: ffff0000d6dd9cc8 x24: ffff80008fba8a20
x23: 0000000000000000 x22: ffff0000d6dd9c98 x21: ffff0000cbd69e80
x20: 0000000000000000 x19: ffff0000d6dd9c00 x18: ffff800090e6c920
x17: ffff800092f39000 x16: ffff80008adbda98 x15: 0000000000000001
x14: 1fffe00019683fa0 x13: 0000000000000000 x12: 0000000000000000
x11: ffff600019683fa1 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : 0000000000000005 x7 : ffff80008020cba8 x6 : ffff8000803f41e0
x5 : ffff0000d95932c8 x4 : ffff80009b8c71f8 x3 : ffff800080dfffa8
x2 : 0000000000000001 x1 : 0000000000000008 x0 : 0000000000000001
Call trace:
alloc_fs_context+0x1b4/0x76c fs/fs_context.c:294 (P)
fs_context_for_mount+0x34/0x44 fs/fs_context.c:332
vfs_kern_mount+0x38/0x178 fs/namespace.c:1309
efivarfs_pm_notify+0x1c4/0x4b4 fs/efivarfs/super.c:529
notifier_call_chain+0x1b8/0x4e4 kernel/notifier.c:85
blocking_notifier_call_chain+0x70/0xa0 kernel/notifier.c:380
pm_notifier_call_chain+0x2c/0x3c kernel/power/main.c:109
snapshot_release+0x104/0x1c4 kernel/power/user.c:125
__fput+0x340/0x75c fs/file_table.c:465
____fput+0x20/0x58 fs/file_table.c:493
task_work_run+0x1dc/0x260 kernel/task_work.c:227
exit_task_work include/linux/task_work.h:40 [inline]
do_exit+0x4e8/0x1998 kernel/exit.c:953
do_group_exit+0x194/0x22c kernel/exit.c:1102
get_signal+0x11dc/0x12f8 kernel/signal.c:3034
do_signal+0x274/0x4438 arch/arm64/kernel/signal.c:1615
do_notify_resume+0xac/0x1ec arch/arm64/kernel/entry-common.c:148
exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]
el0_svc+0xb4/0x17c arch/arm64/kernel/entry-common.c:768
el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
Code: 97f8aa83 f9400368 9100a11a d343ff48 (387c6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 97f8aa83 bl 0xffffffffffe2aa0c
4: f9400368 ldr x8, [x27]
8: 9100a11a add x26, x8, #0x28
c: d343ff48 lsr x8, x26, #3
* 10: 387c6908 ldrb w8, [x8, x28] <-- trapping instruction
Tested on:
commit: d7fa1af5 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1689aad4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=89c13de706fbf07a
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64
Note: no patches were applied.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context
[not found] <CAMj1kXEn_fx6=X4ixhmWST1scUH4kY0SXBt1sXT=-5_ctcKGoA@mail.gmail.com>
@ 2025-05-22 14:50 ` syzbot
0 siblings, 0 replies; 8+ messages in thread
From: syzbot @ 2025-05-22 14:50 UTC (permalink / raw)
To: ardb, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 1afe9e7d f2fs: fix freezing filesystem during resize
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs-6.16.super
console output: https://syzkaller.appspot.com/x/log.txt?x=102105f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bcb473848aa62842
dashboard link: https://syzkaller.appspot.com/bug?extid=52cd651546d11d2af06b
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64
Note: no patches were applied.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2025-05-22 14:50 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20250513204140.1987-1-hdanton@sina.com>
2025-05-14 1:13 ` [syzbot] [fs?] [efi?] BUG: unable to handle kernel paging request in alloc_fs_context syzbot
[not found] <CAMj1kXEn_fx6=X4ixhmWST1scUH4kY0SXBt1sXT=-5_ctcKGoA@mail.gmail.com>
2025-05-22 14:50 ` syzbot
[not found] <CAMj1kXEUW2arc4E1z5VkqUm6yi_bPyPwUtvg99PpM4bQLpct5w@mail.gmail.com>
2025-05-22 14:17 ` syzbot
[not found] <20250512103556.1921-1-hdanton@sina.com>
2025-05-12 12:16 ` syzbot
2025-05-11 17:44 syzbot
2025-05-21 17:28 ` Ard Biesheuvel
2025-05-22 12:24 ` Christian Brauner
2025-05-22 13:47 ` Ard Biesheuvel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox