BUG: unable to handle kernel paging request in stack_depot_save (4)

11 views
Skip to first unread message

syzbot

unread,
Nov 3, 2021, 6:47:21 PM11/3/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 119c85055d86 Merge tag 'powerpc-5.15-6' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=129539f2b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a38b8c18ca03c4e
dashboard link: https://syzkaller.appspot.com/bug?extid=2be5edffbc16e48d58ae
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org t...@kernel.org]

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

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

BUG: unable to handle page fault for address: 000000000770007f
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 10b26067 P4D 10b26067 PUD 7f555067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 26683 Comm: syz-executor.4 Not tainted 5.15.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:find_stack lib/stackdepot.c:209 [inline]
RIP: 0010:stack_depot_save+0x12b/0x4e0 lib/stackdepot.c:281
Code: 05 4a c8 5b 0c 89 da 81 e2 ff ff 0f 00 4c 8d 3c d0 4d 8b 37 4d 85 f6 75 11 e9 94 00 00 00 4d 8b 36 4d 85 f6 0f 84 88 00 00 00 <41> 39 5e 08 75 ee 45 3b 66 0c 75 e8 31 c0 49 8b 4c c6 18 48 39 4c
RSP: 0018:ffffc9000632f2b0 EFLAGS: 00010206
RAX: ffff88823b000000 RBX: 000000008f479a73 RCX: 0000000000000002
RDX: 0000000000079a73 RSI: 0000000000002a20 RDI: 00000000a7e63e1f
RBP: ffffc9000632f320 R08: 0000000039083d28 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000016
R13: 0000000000000016 R14: 0000000007700077 R15: ffff88823b3cd398
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0063) knlGS:00000000f453db40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000000770007f CR3: 00000000464ad000 CR4: 00000000003506e0
Call Trace:
kasan_save_stack+0x32/0x40 mm/kasan/common.c:40
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
__kasan_slab_alloc+0x83/0xb0 mm/kasan/common.c:467
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook mm/slab.h:519 [inline]
slab_alloc_node mm/slub.c:3213 [inline]
slab_alloc mm/slub.c:3221 [inline]
kmem_cache_alloc+0x142/0x390 mm/slub.c:3226
radix_tree_node_alloc.constprop.0+0x1e4/0x350 lib/radix-tree.c:251
idr_get_free+0x554/0xa60 lib/radix-tree.c:1505
idr_alloc_u32+0x16c/0x2c0 lib/idr.c:46
idr_alloc_cyclic+0x102/0x230 lib/idr.c:125
__kernfs_new_node+0x117/0x8b0 fs/kernfs/dir.c:591
kernfs_new_node+0x93/0x120 fs/kernfs/dir.c:647
__kernfs_create_file+0x51/0x350 fs/kernfs/file.c:985
sysfs_add_file_mode_ns+0x226/0x540 fs/sysfs/file.c:317
create_files fs/sysfs/group.c:64 [inline]
internal_create_group+0x328/0xb20 fs/sysfs/group.c:149
internal_create_groups.part.0+0x90/0x140 fs/sysfs/group.c:189
internal_create_groups fs/sysfs/group.c:185 [inline]
sysfs_create_groups+0x25/0x50 fs/sysfs/group.c:215
device_add_groups drivers/base/core.c:2475 [inline]
device_add_attrs drivers/base/core.c:2634 [inline]
device_add+0x14b9/0x1ee0 drivers/base/core.c:3347
netdev_register_kobject+0x181/0x430 net/core/net-sysfs.c:1955
register_netdevice+0xd33/0x1500 net/core/dev.c:10306
__tun_chr_ioctl.isra.0+0x2be2/0x4230 drivers/net/tun.c:2746
__do_compat_sys_ioctl+0x1c7/0x290 fs/ioctl.c:972
do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
__do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178
do_fast_syscall_32+0x2f/0x70 arch/x86/entry/common.c:203
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
RIP: 0023:0xf6f43549
Code: 03 74 c0 01 10 05 03 74 b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f453d5fc EFLAGS: 00000296 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00000000400454ca
RDX: 00000000200000c0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: 000000000770007f
---[ end trace 78d7f96b4a70b9e3 ]---
RIP: 0010:find_stack lib/stackdepot.c:209 [inline]
RIP: 0010:stack_depot_save+0x12b/0x4e0 lib/stackdepot.c:281
Code: 05 4a c8 5b 0c 89 da 81 e2 ff ff 0f 00 4c 8d 3c d0 4d 8b 37 4d 85 f6 75 11 e9 94 00 00 00 4d 8b 36 4d 85 f6 0f 84 88 00 00 00 <41> 39 5e 08 75 ee 45 3b 66 0c 75 e8 31 c0 49 8b 4c c6 18 48 39 4c
RSP: 0018:ffffc9000632f2b0 EFLAGS: 00010206
RAX: ffff88823b000000 RBX: 000000008f479a73 RCX: 0000000000000002
RDX: 0000000000079a73 RSI: 0000000000002a20 RDI: 00000000a7e63e1f
RBP: ffffc9000632f320 R08: 0000000039083d28 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000016
R13: 0000000000000016 R14: 0000000007700077 R15: ffff88823b3cd398
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0063) knlGS:00000000f453db40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000000770007f CR3: 00000000464ad000 CR4: 00000000003506e0
----------------
Code disassembly (best guess):
0: 05 4a c8 5b 0c add $0xc5bc84a,%eax
5: 89 da mov %ebx,%edx
7: 81 e2 ff ff 0f 00 and $0xfffff,%edx
d: 4c 8d 3c d0 lea (%rax,%rdx,8),%r15
11: 4d 8b 37 mov (%r15),%r14
14: 4d 85 f6 test %r14,%r14
17: 75 11 jne 0x2a
19: e9 94 00 00 00 jmpq 0xb2
1e: 4d 8b 36 mov (%r14),%r14
21: 4d 85 f6 test %r14,%r14
24: 0f 84 88 00 00 00 je 0xb2
* 2a: 41 39 5e 08 cmp %ebx,0x8(%r14) <-- trapping instruction
2e: 75 ee jne 0x1e
30: 45 3b 66 0c cmp 0xc(%r14),%r12d
34: 75 e8 jne 0x1e
36: 31 c0 xor %eax,%eax
38: 49 8b 4c c6 18 mov 0x18(%r14,%rax,8),%rcx
3d: 48 rex.W
3e: 39 .byte 0x39
3f: 4c rex.WR


---
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

unread,
Jan 28, 2022, 5:39:20 PM1/28/22
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages