WARNING in cgroup_apply_control_disable

6 views
Skip to first unread message

syzbot

unread,
Apr 25, 2020, 1:18:13 PM4/25/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 050272a0 Linux 4.14.177
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117f7144100000
kernel config: https://syzkaller.appspot.com/x/.config?x=b24dc669afb42f8b
dashboard link: https://syzkaller.appspot.com/bug?extid=3642a97e608b3a7a509a
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11afee64100000

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6603 at kernel/cgroup/cgroup.c:2936 cgroup_apply_control_disable+0x39d/0x470 kernel/cgroup/cgroup.c:2936
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 6603 Comm: syz-executor.0 Not tainted 4.14.177-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x13e/0x194 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:cgroup_apply_control_disable+0x39d/0x470 kernel/cgroup/cgroup.c:2936
RSP: 0018:ffff8880925cf9b8 EFLAGS: 00010297
RAX: ffff8880947bc4c0 RBX: dffffc0000000000 RCX: 1ffffffff10279b4
RDX: 0000000000000000 RSI: ffffffff87da3440 RDI: ffff8880a89b8ad8
RBP: ffff8880a89b8ac0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff87da3260
R13: ffffffff87ddade0 R14: ffff888094a66dc0 R15: ffff8880aa3d7840
cgroup_finalize_control kernel/cgroup/cgroup.c:3003 [inline]
rebind_subsystems+0x364/0xa10 kernel/cgroup/cgroup.c:1631
cgroup_setup_root+0x3b3/0x980 kernel/cgroup/cgroup.c:1900
cgroup1_mount+0x55f/0xd3e kernel/cgroup/cgroup-v1.c:1245
cgroup_mount+0x145/0x8c0 kernel/cgroup/cgroup.c:2024
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x3c0 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2549 [inline]
do_mount+0x3c9/0x24f0 fs/namespace.c:2879
SYSC_mount fs/namespace.c:3095 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3072
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45f27a
RSP: 002b:00007ffd8201e618 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd8201e670 RCX: 000000000045f27a
RDX: 00000000004cad1c RSI: 00000000004c1465 RDI: 00000000004c1428
RBP: 0000000000000000 R08: 00000000004cf6d0 R09: 000000000000001c
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000418390
R13: 00007ffd8201e898 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages