BUG: unable to handle kernel paging request in bpf_trace_run2

BUG: unable to handle kernel paging request in bpf_trace_run2

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    70b97111 bpf: Use hlist_add_head_rcu when linking to local..
git tree:       bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1375823d900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7e0ca96a9b6ee858
dashboard link: https://syzkaller.appspot.com/bug?extid=cc36fd07553c0512f5f7
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+cc36fd07553c0512f5f7@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffffc90001bca030
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD aa000067 P4D aa000067 PUD aa169067 PMD a930f067 PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3912 Comm: systemd-udevd Not tainted 5.9.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:bpf_dispatcher_nop_func include/linux/bpf.h:613 [inline]
RIP: 0010:__bpf_trace_run kernel/trace/bpf_trace.c:1937 [inline]
RIP: 0010:bpf_trace_run2+0x12e/0x3d0 kernel/trace/bpf_trace.c:1974
Code: f7 ff 48 8d 7b 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 02 00 00 48 8d 73 38 48 8d 7c 24 28 <ff> 53 30 e8 ca 02 f7 ff e8 55 fb 86 06 31 ff 89 c3 89 c6 e8 1a ff
RSP: 0018:ffffc90005257e90 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffc90001bca000 RCX: ffffffff817f7778
RDX: 0000000000000000 RSI: ffffc90001bca038 RDI: ffffc90005257eb8
RBP: 1ffff92000a4afd3 R08: 0000000000000000 R09: ffffffff8ce329e7
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffc90005257f58 R14: 0000000000000000 R15: 0000000000000000
FS:  00007f32dd08f8c0(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90001bca030 CR3: 00000000a2fb8000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 trace_sys_enter include/trace/events/syscalls.h:18 [inline]
 syscall_trace_enter kernel/entry/common.c:64 [inline]
 syscall_enter_from_user_mode+0x22c/0x290 kernel/entry/common.c:82
 do_syscall_64+0xf/0x70 arch/x86/entry/common.c:41
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f32dbf022e2
Code: 48 8b 05 b9 db 2b 00 64 c7 00 16 00 00 00 b8 ff ff ff ff c3 0f 1f 40 00 83 ff 01 77 33 48 63 fe b8 05 00 00 00 48 89 d6 0f 05 <48> 3d 00 f0 ff ff 77 06 f3 c3 0f 1f 40 00 48 8b 15 81 db 2b 00 f7
RSP: 002b:00007fff10a5d048 EFLAGS: 00000246 ORIG_RAX: 0000000000000005
RAX: ffffffffffffffda RBX: 0000000000000010 RCX: 00007f32dbf022e2
RDX: 00007fff10a5d050 RSI: 00007fff10a5d050 RDI: 0000000000000010
RBP: 00007f32dd08f710 R08: 00005630652cd480 R09: 0000000000001010
R10: 00007f32dc1c0b58 R11: 0000000000000246 R12: 0000000000000000
R13: 00005630652c69c0 R14: 00000000000000fe R15: 00005630652c69c0
Modules linked in:
CR2: ffffc90001bca030
---[ end trace 105c336028757ea7 ]---
RIP: 0010:bpf_dispatcher_nop_func include/linux/bpf.h:613 [inline]
RIP: 0010:__bpf_trace_run kernel/trace/bpf_trace.c:1937 [inline]
RIP: 0010:bpf_trace_run2+0x12e/0x3d0 kernel/trace/bpf_trace.c:1974
Code: f7 ff 48 8d 7b 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 02 00 00 48 8d 73 38 48 8d 7c 24 28 <ff> 53 30 e8 ca 02 f7 ff e8 55 fb 86 06 31 ff 89 c3 89 c6 e8 1a ff
RSP: 0018:ffffc90005257e90 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffc90001bca000 RCX: ffffffff817f7778
RDX: 0000000000000000 RSI: ffffc90001bca038 RDI: ffffc90005257eb8
RBP: 1ffff92000a4afd3 R08: 0000000000000000 R09: ffffffff8ce329e7
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffc90005257f58 R14: 0000000000000000 R15: 0000000000000000
FS:  00007f32dd08f8c0(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90001bca030 CR3: 00000000a2fb8000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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

Re: BUG: unable to handle kernel paging request in bpf_trace_run2

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit:    12450081 libbpf: Fix native endian assumption when parsing..
git tree:       bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=17fedf8b900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ac0d21536db480b
dashboard link: https://syzkaller.appspot.com/bug?extid=cc36fd07553c0512f5f7
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1365d2c3900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16d5f08d900000

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

BUG: unable to handle page fault for address: ffffc90000ed0030
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD aa000067 P4D aa000067 PUD aa169067 PMD a9031067 PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6868 Comm: syz-executor454 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:bpf_dispatcher_nop_func include/linux/bpf.h:586 [inline]
RIP: 0010:__bpf_trace_run kernel/trace/bpf_trace.c:1887 [inline]
RIP: 0010:bpf_trace_run2+0x12e/0x3d0 kernel/trace/bpf_trace.c:1924
Code: f7 ff 48 8d 7b 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 02 00 00 48 8d 73 38 48 8d 7c 24 28 <ff> 53 30 e8 fa 03 f7 ff e8 45 c8 a4 06 31 ff 89 c3 89 c6 e8 4a 00
RSP: 0018:ffffc900018e7e90 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffc90000ed0000 RCX: ffffffff817f2b88
RDX: 0000000000000000 RSI: ffffc90000ed0038 RDI: ffffc900018e7eb8
RBP: 1ffff9200031cfd3 R08: 0000000000000000 R09: ffffffff8d0b69e7
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffc900018e7f58 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000001079880(0000) GS:ffff8880ae500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000ed0030 CR3: 000000009f63f000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 trace_sys_enter include/trace/events/syscalls.h:18 [inline]
 syscall_trace_enter kernel/entry/common.c:64 [inline]
 syscall_enter_from_user_mode+0x22c/0x290 kernel/entry/common.c:82
 do_syscall_64+0xf/0x70 arch/x86/entry/common.c:41
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4441da
Code: 25 18 00 00 00 00 74 01 f0 48 0f b1 3d cf f9 28 00 48 39 c2 75 da f3 c3 0f 1f 84 00 00 00 00 00 48 63 ff b8 e4 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 06 f3 c3 0f 1f 40 00 48 c7 c2 d0 ff ff ff f7
RSP: 002b:00007ffc59deef98 EFLAGS: 00000246 ORIG_RAX: 00000000000000e4
RAX: ffffffffffffffda RBX: 0000000000001ae1 RCX: 00000000004441da
RDX: 0000000000000000 RSI: 00007ffc59deefa0 RDI: 0000000000000001
RBP: 000000000000ee75 R08: 0000000000001ad4 R09: 0000000001079880
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004022f0
R13: 0000000000402380 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: ffffc90000ed0030
---[ end trace 7a32b71ba0e36806 ]---
RIP: 0010:bpf_dispatcher_nop_func include/linux/bpf.h:586 [inline]
RIP: 0010:__bpf_trace_run kernel/trace/bpf_trace.c:1887 [inline]
RIP: 0010:bpf_trace_run2+0x12e/0x3d0 kernel/trace/bpf_trace.c:1924
Code: f7 ff 48 8d 7b 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 02 00 00 48 8d 73 38 48 8d 7c 24 28 <ff> 53 30 e8 fa 03 f7 ff e8 45 c8 a4 06 31 ff 89 c3 89 c6 e8 4a 00
RSP: 0018:ffffc900018e7e90 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffc90000ed0000 RCX: ffffffff817f2b88
RDX: 0000000000000000 RSI: ffffc90000ed0038 RDI: ffffc900018e7eb8
RBP: 1ffff9200031cfd3 R08: 0000000000000000 R09: ffffffff8d0b69e7
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffc900018e7f58 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000001079880(0000) GS:ffff8880ae500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000ed0030 CR3: 000000009f63f000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Re: BUG: unable to handle kernel paging request in bpf_trace_run2

[syzbot]

syzbot has bisected this issue to:

commit 58956317c8de52009d1a38a721474c24aef74fe7
Author: David Ahern <dsahern@gmail.com>
Date:   Fri Dec 7 20:24:57 2018 +0000

    neighbor: Improve garbage collection

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12d31675900000
start commit:   12450081 libbpf: Fix native endian assumption when parsing..
git tree:       bpf
final oops:     https://syzkaller.appspot.com/x/report.txt?x=11d31675900000
console output: https://syzkaller.appspot.com/x/log.txt?x=16d31675900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ac0d21536db480b
dashboard link: https://syzkaller.appspot.com/bug?extid=cc36fd07553c0512f5f7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1365d2c3900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16d5f08d900000

Reported-by: syzbot+cc36fd07553c0512f5f7@syzkaller.appspotmail.com
Fixes: 58956317c8de ("neighbor: Improve garbage collection")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Re: [syzbot] BUG: unable to handle kernel paging request in bpf_trace_run2

[syzbot]

syzbot suspects this issue was fixed by commit:

commit befe6d946551d65cddbd32b9cb0170b0249fd5ed
Author: Steven Rostedt (VMware) <rostedt@goodmis.org>
Date:   Wed Nov 18 14:34:05 2020 +0000

    tracepoint: Do not fail unregistering a probe due to memory failure

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14f0260ed00000
start commit:   12450081 libbpf: Fix native endian assumption when parsing..
git tree:       bpf
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ac0d21536db480b
dashboard link: https://syzkaller.appspot.com/bug?extid=cc36fd07553c0512f5f7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1365d2c3900000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16d5f08d900000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: tracepoint: Do not fail unregistering a probe due to memory failure

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Re: [syzbot] BUG: unable to handle kernel paging request in bpf_trace_run2

[Dmitry Vyukov]

On Thu, Apr 1, 2021 at 8:01 PM syzbot
<syzbot+cc36fd07553c0512f5f7@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit befe6d946551d65cddbd32b9cb0170b0249fd5ed
> Author: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Date:   Wed Nov 18 14:34:05 2020 +0000
>
>     tracepoint: Do not fail unregistering a probe due to memory failure
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14f0260ed00000
> start commit:   12450081 libbpf: Fix native endian assumption when parsing..
> git tree:       bpf
> kernel config:  https://syzkaller.appspot.com/x/.config?x=5ac0d21536db480b
> dashboard link: https://syzkaller.appspot.com/bug?extid=cc36fd07553c0512f5f7
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1365d2c3900000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16d5f08d900000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: tracepoint: Do not fail unregistering a probe due to memory failure
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

Looks reasonable:

#syz fix:
tracepoint: Do not fail unregistering a probe due to memory failure