BUG: unable to handle kernel NULL pointer dereference in rcu_core (2)

已查看 6 次
跳至第一个未读帖子

syzbot

未读,
2022年11月25日 14:51:332022/11/25
收件人 syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9500fc6e9e60 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=177d59f9880000
kernel config: https://syzkaller.appspot.com/x/.config?x=b25c9f218686dd5e
dashboard link: https://syzkaller.appspot.com/bug?extid=01a568f75d7787cf7bfb
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [ar...@kernel.org bro...@kernel.org catalin...@arm.com linux-ar...@lists.infradead.org linux-...@vger.kernel.org mark.r...@arm.com samito...@google.com wi...@kernel.org zhengq...@bytedance.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1363e60652f7/disk-9500fc6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fcc4da811bb6/vmlinux-9500fc6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0b554298f1fa/Image-9500fc6e.gz.xz

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

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Mem abort info:
ESR = 0x0000000086000004
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
user pgtable: 4k pages, 48-bit VAs, pgdp=00000001283f8000
[0000000000000000] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 32389 Comm: modprobe Not tainted 6.1.0-rc5-syzkaller-32269-g9500fc6e9e60 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0x0
lr : rcu_do_batch+0x1a4/0x584 kernel/rcu/tree.c:2250
sp : ffff800008003e60
x29: ffff800008003e90 x28: 0000000000000009 x27: 000000000000000a
x26: 0000000000000000 x25: ffff0000e9c4da20 x24: ffff80000d3ac000
x23: ffff80000d4d4690 x22: ffff80000c0eec40 x21: ffff00010b198000
x20: ffff0001fefd0cc0 x19: ffff80000d300cb8 x18: 00000000000000dd
x17: ffff80000c0ed83c x16: ffff80000dc18158 x15: ffff00010b198000
x14: 0000000000000018 x13: 0000000000000001 x12: ffff00010b198000
x11: ff808000095f6cf8 x10: 0000000000000000 x9 : 2b7dc7a063c30200
x8 : 0000000000000000 x7 : ffff8000081f8124 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000002
x2 : 0000000000000008 x1 : ffff80000cbcb6a8 x0 : ffff0000e9c4da20
Call trace:
0x0
rcu_core+0x2bc/0x5b4 kernel/rcu/tree.c:2510
rcu_core_si+0x10/0x1c kernel/rcu/tree.c:2527
_stext+0x168/0x37c
____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
call_on_irq_stack+0x2c/0x54 arch/arm64/kernel/entry.S:892
do_softirq_own_stack+0x20/0x2c arch/arm64/kernel/irq.c:84
invoke_softirq+0x70/0xbc kernel/softirq.c:452
__irq_exit_rcu+0xf0/0x140 kernel/softirq.c:650
irq_exit_rcu+0x10/0x40 kernel/softirq.c:662
__el1_irq arch/arm64/kernel/entry-common.c:472 [inline]
el1_interrupt+0x38/0x68 arch/arm64/kernel/entry-common.c:486
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:491
el1h_64_irq+0x64/0x68 arch/arm64/kernel/entry.S:580
arch_local_irq_restore+0x8/0x10 arch/arm64/include/asm/irqflags.h:122
lock_is_held include/linux/lockdep.h:283 [inline]
task_css include/linux/cgroup.h:508 [inline]
mem_cgroup_from_task+0x4c/0xac mm/memcontrol.c:985
get_mem_cgroup_from_mm+0xa8/0x204 mm/memcontrol.c:1038
__mem_cgroup_charge+0x24/0x64 mm/memcontrol.c:6899
mem_cgroup_charge include/linux/memcontrol.h:667 [inline]
do_anonymous_page+0x1ac/0x89c mm/memory.c:4118
handle_pte_fault mm/memory.c:4953 [inline]
__handle_mm_fault mm/memory.c:5097 [inline]
handle_mm_fault+0x7a0/0xa48 mm/memory.c:5218
__do_page_fault arch/arm64/mm/fault.c:512 [inline]
do_page_fault+0x428/0x79c arch/arm64/mm/fault.c:612
do_translation_fault+0x78/0x194 arch/arm64/mm/fault.c:695
do_mem_abort+0x54/0x130 arch/arm64/mm/fault.c:831
el0_da+0x70/0x16c arch/arm64/kernel/entry-common.c:515
el0t_64_sync_handler+0xcc/0xf0 arch/arm64/kernel/entry-common.c:658
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
Code: bad PC value
---[ 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.

syzbot

未读,
2023年3月10日 21:30:372023/3/10
收件人 syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
回复全部
回复作者
转发
0 个新帖子