BUG: unable to handle kernel paging request in ipv6_rcv

5 views
Skip to first unread message

syzbot

unread,
Oct 31, 2020, 7:07:29 AM10/31/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2b791501 Linux 4.14.203
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16d8ae0a500000
kernel config: https://syzkaller.appspot.com/x/.config?x=e52bb6f2a595a463
dashboard link: https://syzkaller.appspot.com/bug?extid=2609ff297e0c2b7d06b8
compiler: gcc (GCC) 10.1.0-syz 20200507

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+2609ff...@syzkaller.appspotmail.com

BTRFS info (device loop3): disk space caching is enabled
BTRFS error (device loop3): cannot mount because of unsupported optional features (800)
BTRFS error (device loop3): open_ctree failed
BUG: unable to handle kernel paging request at ffffe8ffba500008
IP: ipv6_rcv+0xca1/0x1bd0 net/ipv6/ip6_input.c:90
PGD 23f83e067 P4D 23f83e067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 17 Comm: ksoftirqd/1 Not tainted 4.14.203-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880b548e480 task.stack: ffff8880b54a0000
RIP: 0010:ipv6_rcv+0xca1/0x1bd0 net/ipv6/ip6_input.c:90
RSP: 0018:ffff8880b54a7a18 EFLAGS: 00010206
RAX: 0000000000000001 RBX: ffff88800012f6c0 RCX: 0000000000000000
RDX: 0000000000000100 RSI: ffffffff885efce0 RDI: ffffffff885efce0
RBP: ffff8880a26b16c0 R08: ffffffff8650616f R09: 0000000000022012
R10: ffff8880b548ed30 R11: ffff8880b548e480 R12: ffff8880a26b1740
R13: 0000607f00000000 R14: ffff8880a26b16d0 R15: ffff88809d2308c0
FS: 0000000000000000(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffe8ffba500008 CR3: 0000000008e6a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__netif_receive_skb_core+0x15ee/0x2a30 net/core/dev.c:4474
__netif_receive_skb+0x27/0x1a0 net/core/dev.c:4512
process_backlog+0x218/0x6f0 net/core/dev.c:5194
napi_poll net/core/dev.c:5596 [inline]
net_rx_action+0x466/0xfd0 net/core/dev.c:5662
__do_softirq+0x254/0xa1d kernel/softirq.c:288
run_ksoftirqd+0x50/0x1a0 kernel/softirq.c:670
smpboot_thread_fn+0x5c1/0x920 kernel/smpboot.c:164
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 80 3c 02 00 0f 85 35 0c 00 00 48 c7 c7 e0 fc 5e 88 4c 8b ab e0 02 00 00 e8 ed 46 d1 fc 4c 8d a5 80 00 00 00 48 c7 c7 e0 fc 5e 88 <65> 49 ff 45 08 e8 d5 46 d1 fc 4c 89 e2 48 b8 00 00 00 00 00 fc
RIP: ipv6_rcv+0xca1/0x1bd0 net/ipv6/ip6_input.c:90 RSP: ffff8880b54a7a18
CR2: ffffe8ffba500008
---[ end trace 2380397680b97d46 ]---


---
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,
Feb 28, 2021, 6:07:09 AM2/28/21
to syzkaller...@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