From: syzbot <syzbot+2984d1b7aef6b51353f0@syzkaller.appspotmail.com>
To: avagin@gmail.com, brauner@kernel.org, keescook@chromium.org,
linux-kernel@vger.kernel.org, shakeelb@google.com,
syzkaller-bugs@googlegroups.com, tkhai@ya.ru,
vasily.averin@linux.dev
Subject: [syzbot] upstream boot error: BUG: unable to handle kernel paging request in copy_namespaces
Date: Mon, 15 Aug 2022 11:00:29 -0700 [thread overview]
Message-ID: <0000000000003d898a05e64b68bd@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5d6a0f4da927 Merge tag 'for-linus-6.0-rc1b-tag' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1168343d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=f6bcb425ba129b87
dashboard link: https://syzkaller.appspot.com/bug?extid=2984d1b7aef6b51353f0
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2984d1b7aef6b51353f0@syzkaller.appspotmail.com
BUG: unable to handle page fault for address: ffffdc0000000013
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 11826067 P4D 11826067 PUD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11 Comm: kworker/u4:1 Not tainted 5.19.0-syzkaller-14374-g5d6a0f4da927 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: events_unbound call_usermodehelper_exec_work
RIP: 0010:copy_namespaces+0xe8/0x480 kernel/nsproxy.c:154
Code: 0e 5f 2b 00 45 85 ed 0f 84 d4 01 00 00 e8 40 62 2b 00 49 8d bf 98 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 42 03 00 00 4d 8b bf 98 00 00 00 e8 32 ab 15 00
RSP: 0000:ffffc90000107900 EFLAGS: 00010a02
RAX: dffffc0000000000 RBX: ffff888020118000 RCX: 0000000000000000
RDX: 1fffe00000000013 RSI: ffffffff8150a4b0 RDI: ffff000000000098
RBP: ffff000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000808100
R13: 0000000000000001 R14: ffff8880201188a0 R15: ffff000000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffdc0000000013 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
copy_process+0x305c/0x7090 kernel/fork.c:2259
kernel_clone+0xe7/0xab0 kernel/fork.c:2673
user_mode_thread+0xad/0xe0 kernel/fork.c:2742
call_usermodehelper_exec_work kernel/umh.c:174 [inline]
call_usermodehelper_exec_work+0xcc/0x180 kernel/umh.c:160
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
CR2: ffffdc0000000013
---[ end trace 0000000000000000 ]---
RIP: 0010:copy_namespaces+0xe8/0x480 kernel/nsproxy.c:154
Code: 0e 5f 2b 00 45 85 ed 0f 84 d4 01 00 00 e8 40 62 2b 00 49 8d bf 98 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 42 03 00 00 4d 8b bf 98 00 00 00 e8 32 ab 15 00
RSP: 0000:ffffc90000107900 EFLAGS: 00010a02
RAX: dffffc0000000000 RBX: ffff888020118000 RCX: 0000000000000000
RDX: 1fffe00000000013 RSI: ffffffff8150a4b0 RDI: ffff000000000098
RBP: ffff000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000808100
R13: 0000000000000001 R14: ffff8880201188a0 R15: ffff000000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffdc0000000013 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 5f pop %rdi
1: 2b 00 sub (%rax),%eax
3: 45 85 ed test %r13d,%r13d
6: 0f 84 d4 01 00 00 je 0x1e0
c: e8 40 62 2b 00 callq 0x2b6251
11: 49 8d bf 98 00 00 00 lea 0x98(%r15),%rdi
18: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1f: fc ff df
22: 48 89 fa mov %rdi,%rdx
25: 48 c1 ea 03 shr $0x3,%rdx
* 29: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2d: 0f 85 42 03 00 00 jne 0x375
33: 4d 8b bf 98 00 00 00 mov 0x98(%r15),%r15
3a: e8 32 ab 15 00 callq 0x15ab71
---
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:[~2022-08-15 18:01 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=0000000000003d898a05e64b68bd@google.com \
--to=syzbot+2984d1b7aef6b51353f0@syzkaller.appspotmail.com \
--cc=avagin@gmail.com \
--cc=brauner@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shakeelb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkhai@ya.ru \
--cc=vasily.averin@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox