From: syzbot <syzbot+529a4d631f26ba0e43b5@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: [syzbot] general protection fault in bpf_lru_pop_free
Date: Mon, 12 Jul 2021 09:26:29 -0700 [thread overview]
Message-ID: <0000000000006cd48405c6ef954b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a080cdcc Merge branch 'bpf: support input xdp_md context i..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13ba01e2300000
kernel config: https://syzkaller.appspot.com/x/.config?x=4cb84363d46e9fc3
dashboard link: https://syzkaller.appspot.com/bug?extid=529a4d631f26ba0e43b5
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+529a4d631f26ba0e43b5@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 3913 Comm: syz-executor.1 Tainted: G W 5.13.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__list_add_valid+0x22/0xa0 lib/list_debug.c:23
Code: cd cc cc cc cc cc cc cc 48 b8 00 00 00 00 00 fc ff df 41 54 49 89 d4 55 48 89 fd 48 8d 7a 08 48 83 ec 08 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 50 49 8b 54 24 08 48 39 f2 0f 85 ae 1c 16 05 48 b8
RSP: 0018:ffffc90001cdfa50 EFLAGS: 00010002
RAX: dffffc0000000000 RBX: ffff88802bd14cd8 RCX: ffffc9001831b000
RDX: 0000000000000001 RSI: ffffe8ffffc69280 RDI: 0000000000000008
RBP: ffff88802bd14cc0 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff818adf47 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88802951381c R15: ffff88802bd14cc0
FS: 00007f52cf552700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000308de000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
__list_add include/linux/list.h:67 [inline]
list_add include/linux/list.h:86 [inline]
__local_list_add_pending kernel/bpf/bpf_lru_list.c:357 [inline]
bpf_common_lru_pop_free kernel/bpf/bpf_lru_list.c:452 [inline]
bpf_lru_pop_free+0x588/0x16d0 kernel/bpf/bpf_lru_list.c:499
prealloc_lru_pop+0x26/0x90 kernel/bpf/hashtab.c:264
htab_lru_map_update_elem+0x157/0x7b0 kernel/bpf/hashtab.c:1102
bpf_map_update_value.isra.0+0x6df/0x8d0 kernel/bpf/syscall.c:206
generic_map_update_batch+0x3cf/0x560 kernel/bpf/syscall.c:1371
bpf_map_do_batch+0x3d5/0x510 kernel/bpf/syscall.c:4076
__sys_bpf+0x1da7/0x5390 kernel/bpf/syscall.c:4533
__do_sys_bpf kernel/bpf/syscall.c:4573 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4571 [inline]
__x64_sys_bpf+0x75/0xb0 kernel/bpf/syscall.c:4571
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x4665d9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f52cf552188 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 000000000056c038 RCX: 00000000004665d9
RDX: 0000000000000038 RSI: 0000000020000200 RDI: 000000000000001a
RBP: 00000000004bfcb9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056c038
R13: 00007ffe08b5b5ef R14: 00007f52cf552300 R15: 0000000000022000
Modules linked in:
---[ end trace c58f4ed9330ab605 ]---
RIP: 0010:__list_add_valid+0x22/0xa0 lib/list_debug.c:23
Code: cd cc cc cc cc cc cc cc 48 b8 00 00 00 00 00 fc ff df 41 54 49 89 d4 55 48 89 fd 48 8d 7a 08 48 83 ec 08 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 50 49 8b 54 24 08 48 39 f2 0f 85 ae 1c 16 05 48 b8
RSP: 0018:ffffc90001cdfa50 EFLAGS: 00010002
RAX: dffffc0000000000 RBX: ffff88802bd14cd8 RCX: ffffc9001831b000
RDX: 0000000000000001 RSI: ffffe8ffffc69280 RDI: 0000000000000008
RBP: ffff88802bd14cc0 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff818adf47 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88802951381c R15: ffff88802bd14cc0
FS: 00007f52cf552700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000308de000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
---
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.
reply other threads:[~2021-07-12 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000006cd48405c6ef954b@google.com \
--to=syzbot+529a4d631f26ba0e43b5@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.