From: syzbot <syzbot+bf76b4978f531b8e2edb@syzkaller.appspotmail.com>
To: casey@schaufler-ca.com, jmorris@namei.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, serge@hallyn.com,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in smk_write_net4addr
Date: Fri, 15 Jan 2021 23:39:15 -0800 [thread overview]
Message-ID: <000000000000f9ab3905b8ff959f@google.com> (raw)
In-Reply-To: <0000000000003e36df05b8ed6677@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: f4e087c6 Merge tag 'acpi-5.11-rc4' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=161212d0d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee2266946ed36986
dashboard link: https://syzkaller.appspot.com/bug?extid=bf76b4978f531b8e2edb
compiler: clang version 11.0.1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1449f3e0d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a71868d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bf76b4978f531b8e2edb@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8454 at mm/page_alloc.c:4976 __alloc_pages_nodemask+0x4e5/0x5a0 mm/page_alloc.c:5020
Modules linked in:
CPU: 0 PID: 8454 Comm: syz-executor791 Not tainted 5.11.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__alloc_pages_nodemask+0x4e5/0x5a0 mm/page_alloc.c:5020
Code: aa 09 00 e9 dd fd ff ff 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c eb fd ff ff 4c 89 ef e8 54 aa 09 00 8b 74 24 18 e9 da fd ff ff <0f> 0b e9 f3 fd ff ff a9 00 00 08 00 75 16 8b 4c 24 1c 89 cb 81 e3
RSP: 0018:ffffc9000945f940 EFLAGS: 00010246
RAX: ffffc9000945f9c0 RBX: ffffc9000945f9c0 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc9000945f9e8
RBP: ffffc9000945fa80 R08: dffffc0000000000 R09: ffffc9000945f9c0
R10: fffff5200128bf3d R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000012 R14: 1ffff9200128bf34 R15: 0000000000040cc0
FS: 0000000000ffe880(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000140 CR3: 000000001c506000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
alloc_pages include/linux/gfp.h:547 [inline]
kmalloc_order+0x40/0x130 mm/slab_common.c:837
kmalloc_order_trace+0x15/0x70 mm/slab_common.c:853
kmalloc_large include/linux/slab.h:481 [inline]
__kmalloc_track_caller+0x246/0x330 mm/slub.c:4457
memdup_user_nul+0x26/0xf0 mm/util.c:260
smk_write_net4addr+0xde/0x13d0 security/smack/smackfs.c:1173
vfs_write+0x289/0xc90 fs/read_write.c:603
ksys_write+0x171/0x2a0 fs/read_write.c:658
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x440249
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 0f 83 7b 13 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fff42192178 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 0000000000440249
RDX: 00000000200001e2 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000401a50
R13: 0000000000401ae0 R14: 0000000000000000 R15: 0000000000000000
prev parent reply other threads:[~2021-01-16 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 9:57 WARNING in smk_write_net4addr syzbot
2021-01-16 7:39 ` syzbot [this message]
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=000000000000f9ab3905b8ff959f@google.com \
--to=syzbot+bf76b4978f531b8e2edb@syzkaller.appspotmail.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.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.