Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
syzkaller-upstream-moderation
Conversations
About
WARNING: zero-size vmalloc in vzalloc
6 views
Skip to first unread message
syzbot
unread,
Feb 3, 2023, 1:14:39 AM
2/3/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: ea4dabbb4ad7 Add linux-next specific files for 20230202
git tree: linux-next
console output:
https://syzkaller.appspot.com/x/log.txt?x=129591fd480000
kernel config:
https://syzkaller.appspot.com/x/.config?x=e14cff5442dd778f
dashboard link:
https://syzkaller.appspot.com/bug?extid=87fd16ee5e117dd08972
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [
and...@kernel.org
a...@kernel.org
b...@vger.kernel.org
dan...@iogearbox.net
da...@davemloft.net
hao...@google.com
ha...@kernel.org
john.fa...@gmail.com
jo...@kernel.org
kps...@kernel.org
ku...@kernel.org
linux-...@vger.kernel.org
ll...@lists.linux.dev
marti...@linux.dev
nat...@kernel.org
ndesau...@google.com
net...@vger.kernel.org
s...@google.com
so...@kernel.org
tr...@redhat.com
y...@fb.com
]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/57ad4810d023/disk-ea4dabbb.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/58c832fe14db/vmlinux-ea4dabbb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2729f1953a1d/bzImage-ea4dabbb.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+87fd16...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 15973 at mm/vmalloc.c:3108 __vmalloc_node_range+0x1036/0x1300 mm/vmalloc.c:3108
Modules linked in:
CPU: 1 PID: 15973 Comm: syz-executor.3 Not tainted 6.2.0-rc6-next-20230202-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:__vmalloc_node_range+0x1036/0x1300 mm/vmalloc.c:3108
Code: 00 65 48 2b 04 25 28 00 00 00 0f 85 7b 01 00 00 48 81 c4 58 01 00 00 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 3a 3b bd ff <0f> 0b 45 31 e4 eb a3 e8 2e 3b bd ff 44 8b 64 24 68 41 83 cc 02 66
RSP: 0018:ffffc90015d7f6d0 EFLAGS: 00010216
RAX: 0000000000000bd2 RBX: dffffc0000000000 RCX: ffffc9000c7ef000
RDX: 0000000000040000 RSI: ffffffff81c78f96 RDI: 0000000000000007
RBP: 0000000000000000 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: 1ffff1100ef9f7da R12: 0000000000000000
R13: 0000000000000000 R14: 00000000ffffffff R15: 0000000000000000
FS: 00007f934abfe700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005599831f0190 CR3: 0000000029865000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__vmalloc_node mm/vmalloc.c:3246 [inline]
vzalloc+0x6b/0x80 mm/vmalloc.c:3319
bpf_check+0x1b8/0xae50 kernel/bpf/verifier.c:17253
bpf_prog_load+0x16d9/0x21d0 kernel/bpf/syscall.c:2617
__sys_bpf+0x1435/0x5100 kernel/bpf/syscall.c:4977
__do_sys_bpf kernel/bpf/syscall.c:5081 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5079 [inline]
__x64_sys_bpf+0x79/0xc0 kernel/bpf/syscall.c:5079
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f934c08c0c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f934abfe168 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f934c1ac050 RCX: 00007f934c08c0c9
RDX: 0000000000000080 RSI: 0000000020000180 RDI: 0000000000000005
RBP: 00007f934c0e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff8af372ef R14: 00007f934abfe300 R15: 0000000000022000
</TASK>
---
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,
Apr 3, 2023, 1:30:42 AM
4/3/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to syzkaller-upst...@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