BUG: unable to handle kernel paging request in __memmove (2)

5 views
Skip to first unread message

syzbot

unread,
Mar 25, 2019, 3:42:07 AM3/25/19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 526949e8 rxrpc: avoid clang -Wuninitialized warning
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=13b657ef200000
kernel config: https://syzkaller.appspot.com/x/.config?x=f05902bca21d8935
dashboard link: https://syzkaller.appspot.com/bug?extid=7061b7b29bc00861f7aa
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org
vi...@zeniv.linux.org.uk net...@vger.kernel.org]

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+7061b7...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at ffffe8ffffe00000
#PF error: [normal kernel read fault]
PGD 12c25b067 P4D 12c25b067 PUD 12c25c067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 26603 Comm: syz-executor.1 Not tainted 5.0.0+ #136
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__memmove+0x24/0x1a0 arch/x86/lib/memmove_64.S:43
Code: 90 90 90 90 90 90 48 89 f8 48 83 fa 20 0f 82 03 01 00 00 48 39 fe 7d
0f 49 89 f0 49 01 d0 49 39 f8 0f 8f 9f 00 00 00 48 89 d1 <f3> a4 c3 48 81
fa a8 02 00 00 72 05 40 38 fe 74 3b 48 83 ea 20 48
RSP: 0018:ffff888098f9fbd0 EFLAGS: 00010002
RAX: ffffe8ffffc77b20 RBX: 000000000000008e RCX: 00000007ffe77cd0
RDX: 00000007fffffd40 RSI: ffffe8ffffe00000 RDI: ffffe8ffffdffb90
RBP: ffff888098f9fc38 R08: 1ffff11013f0b580 R09: ffffed1013f0b581
R10: ffffed1013f0b580 R11: ffff88809f85ac03 R12: ffff8880a02fbd80
R13: ffff8880960f4b80 R14: ffff888098f9fbf8 R15: ffffe8ffffc77b10
FS: 0000000000b06940(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffe8ffffe00000 CR3: 00000000993cf000 CR4: 00000000001406f0
Call Trace:
qlink_free mm/kasan/quarantine.c:148 [inline]
qlist_free_all+0x85/0x150 mm/kasan/quarantine.c:167
quarantine_reduce+0x169/0x1b0 mm/kasan/quarantine.c:260
__kasan_kmalloc.constprop.0+0xa3/0xe0 mm/kasan/common.c:478
kasan_slab_alloc+0xf/0x20 mm/kasan/common.c:505
slab_post_alloc_hook mm/slab.h:436 [inline]
slab_alloc mm/slab.c:3392 [inline]
kmem_cache_alloc+0x11a/0x6f0 mm/slab.c:3554
getname_flags fs/namei.c:138 [inline]
getname_flags+0xd6/0x5b0 fs/namei.c:128
getname fs/namei.c:209 [inline]
user_path_mountpoint_at+0x29/0x50 fs/namei.c:2745
ksys_umount+0x167/0xf00 fs/namespace.c:1687
__do_sys_umount fs/namespace.c:1713 [inline]
__se_sys_umount fs/namespace.c:1711 [inline]
__x64_sys_umount+0x54/0x80 fs/namespace.c:1711
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45ac57
Code: 44 00 00 b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 4d 8e fb ff c3
66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff
ff 0f 83 2d 8e fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffffcdd04f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: ffffffffffffffda RBX: 00000000002a36a8 RCX: 000000000045ac57
RDX: 000000000000000c RSI: 0000000000000002 RDI: 00007ffffcdd1630
RBP: 0000000000004771 R08: 0000000000000001 R09: 0000000000b06940
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffffcdd1630
R13: 00007ffffcdd1620 R14: 0000000000000000 R15: 00007ffffcdd1630
Modules linked in:
CR2: ffffe8ffffe00000
---[ end trace a09fada1be6227a0 ]---
RIP: 0010:__memmove+0x24/0x1a0 arch/x86/lib/memmove_64.S:43
Code: 90 90 90 90 90 90 48 89 f8 48 83 fa 20 0f 82 03 01 00 00 48 39 fe 7d
0f 49 89 f0 49 01 d0 49 39 f8 0f 8f 9f 00 00 00 48 89 d1 <f3> a4 c3 48 81
fa a8 02 00 00 72 05 40 38 fe 74 3b 48 83 ea 20 48
RSP: 0018:ffff888098f9fbd0 EFLAGS: 00010002
RAX: ffffe8ffffc77b20 RBX: 000000000000008e RCX: 00000007ffe77cd0
RDX: 00000007fffffd40 RSI: ffffe8ffffe00000 RDI: ffffe8ffffdffb90
RBP: ffff888098f9fc38 R08: 1ffff11013f0b580 R09: ffffed1013f0b581
R10: ffffed1013f0b580 R11: ffff88809f85ac03 R12: ffff8880a02fbd80
R13: ffff8880960f4b80 R14: ffff888098f9fbf8 R15: ffffe8ffffc77b10
FS: 0000000000b06940(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffe8ffffe00000 CR3: 00000000993cf000 CR4: 00000000001406f0


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Dmitry Vyukov

unread,
May 7, 2019, 5:47:52 AM5/7/19
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
memmove frame is now skipped
#syz invalid
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000005cd4970584e657b1%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages