From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.1 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SORTED_RECIPS,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BAEA0ECDFB1 for ; Tue, 17 Jul 2018 13:15:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6F3922146E for ; Tue, 17 Jul 2018 13:15:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6F3922146E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731553AbeGQNrl (ORCPT ); Tue, 17 Jul 2018 09:47:41 -0400 Received: from mail-io0-f198.google.com ([209.85.223.198]:40465 "EHLO mail-io0-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729633AbeGQNrk (ORCPT ); Tue, 17 Jul 2018 09:47:40 -0400 Received: by mail-io0-f198.google.com with SMTP id j18-v6so781111iog.7 for ; Tue, 17 Jul 2018 06:15:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=Vn8DblY3qZQCygNbYBpC8hk2hFKEbPU4zIGFGX6Xw4A=; b=NyZnbI9aWcw1AOWQrCrifUAxs0QuFJUQIzr02bU6ZJ6ExVniSIuQkhkBeDDfR9UByo HQroX6NA3Rd0hZuL3vl/dYNHJ77IkYmD/UWah2FQvei/D1wYXwf8woo0qfVcYbEDM0m6 I3XfLyvhTsv+ZucDB5O5Tw5A3uNA95QdKWDYOCw1kkEZYqp15j+Mcwk07XlJnQZOlnYQ qyiTQB60YGVLf35gtBRni5y53fPuSWIA8iENEFZMUTkzHS8jiBHH73f5McwQ2CVdDktK t98JS17W+UbdlxPspODlmkFhV7JKPG1n8yDLOV0NBVTJA86h9Q0eEy1nI4cPKa3plLan lmWA== X-Gm-Message-State: AOUpUlHKiGp+wV8OQl2t711XcsJjVfrBu6kEqfgiBqVyuAaHMa0KqaSx l4IWIppIwkKqEeWTORCf+e4PyawRnfROS/2ymZE2g5kY7eyG X-Google-Smtp-Source: AAOMgpflqPxd66Oh4IsAvF2hnHJeaPzpks1uNeDQb9LJorjHx3cyK4h60UKvGDI/kzq+qTtqycDjXcMI8pGQK/SYPWhPNGHzuCFt MIME-Version: 1.0 X-Received: by 2002:a6b:a303:: with SMTP id m3-v6mr612635ioe.96.1531833302434; Tue, 17 Jul 2018 06:15:02 -0700 (PDT) Date: Tue, 17 Jul 2018 06:15:02 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d8cc39057131bbcd@google.com> Subject: general protection fault in list_lru_count_one From: syzbot To: akpm@linux-foundation.org, garsilva@embeddedor.com, hannes@cmpxchg.org, ktkhai@virtuozzo.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, longman@redhat.com, mhocko@suse.com, sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com, vdavydov.dev@gmail.com Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following crash on: HEAD commit: 483d835c8189 Add linux-next specific files for 20180713 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=169b4770400000 kernel config: https://syzkaller.appspot.com/x/.config?x=60e5ac2478928314 dashboard link: https://syzkaller.appspot.com/bug?extid=50d322b3e0b15a4a8d55 compiler: gcc (GCC) 8.0.1 20180413 (experimental) syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=10faa9a4400000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f57794400000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+50d322b3e0b15a4a8d55@syzkaller.appspotmail.com random: sshd: uninitialized urandom read (32 bytes read) random: sshd: uninitialized urandom read (32 bytes read) IPVS: ftp: loaded support on port[0] = 21 kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: 0000 [#1] SMP KASAN CPU: 0 PID: 4462 Comm: syz-executor763 Not tainted 4.18.0-rc4-next-20180713+ #7 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__read_once_size include/linux/compiler.h:188 [inline] RIP: 0010:list_lru_from_memcg_idx mm/list_lru.c:56 [inline] RIP: 0010:list_lru_count_one+0x156/0x460 mm/list_lru.c:201 Code: 08 3c 03 0f 8e b5 02 00 00 4d 63 bd d8 0a 00 00 e8 7f 35 d2 ff 48 8d 7b 50 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 d8 02 00 00 49 8d 46 c0 4c 8b 6b 50 48 ba 00 00 RSP: 0018:ffff8801ac967198 EFLAGS: 00010206 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff81aa3a64 RDX: 000000000000000a RSI: ffffffff81aa3ad1 RDI: 0000000000000050 RBP: ffff8801ac967228 R08: ffff8801af1c6300 R09: 0000000000000000 R10: ffffed00359e0088 R11: ffff8801acf00447 R12: 1ffff1003592ce34 R13: ffff8801ad6aa080 R14: ffff8801ac967200 R15: 0000000000000000 FS: 000000000206b880(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000006ce080 CR3: 00000001ae3c1000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: list_lru_shrink_count include/linux/list_lru.h:122 [inline] super_cache_count+0x153/0x2e0 fs/super.c:146 do_shrink_slab+0x148/0xc50 mm/vmscan.c:458 shrink_slab_memcg mm/vmscan.c:598 [inline] shrink_slab+0x861/0xa60 mm/vmscan.c:671 shrink_node+0x429/0x16a0 mm/vmscan.c:2735 shrink_zones mm/vmscan.c:2964 [inline] do_try_to_free_pages+0x3e7/0x1290 mm/vmscan.c:3026 try_to_free_mem_cgroup_pages+0x49d/0xc90 mm/vmscan.c:3324 reclaim_high.constprop.73+0x137/0x1e0 mm/memcontrol.c:2060 mem_cgroup_handle_over_high+0x8d/0x130 mm/memcontrol.c:2085 tracehook_notify_resume include/linux/tracehook.h:195 [inline] exit_to_usermode_loop+0x287/0x380 arch/x86/entry/common.c:166 prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline] syscall_return_slowpath arch/x86/entry/common.c:268 [inline] do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x440ec7 Code: 1f 40 00 b8 5a 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 6d 14 fc ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 4d 14 fc ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007ffe197f4e98 EFLAGS: 00000202 ORIG_RAX: 0000000000000053 RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000440ec7 RDX: 00007ffe197f4eb3 RSI: 00000000000001ff RDI: 00007ffe197f4eb0 RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000003 R10: 0000000000000064 R11: 0000000000000202 R12: 0000000000000001 R13: 0000000000008fab R14: 0000000000000000 R15: 0000000000000000 Modules linked in: Dumping ftrace buffer: (ftrace buffer empty) ---[ end trace 82052695a1b5b84c ]--- RIP: 0010:__read_once_size include/linux/compiler.h:188 [inline] RIP: 0010:list_lru_from_memcg_idx mm/list_lru.c:56 [inline] RIP: 0010:list_lru_count_one+0x156/0x460 mm/list_lru.c:201 Code: 08 3c 03 0f 8e b5 02 00 00 4d 63 bd d8 0a 00 00 e8 7f 35 d2 ff 48 8d 7b 50 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 d8 02 00 00 49 8d 46 c0 4c 8b 6b 50 48 ba 00 00 RSP: 0018:ffff8801ac967198 EFLAGS: 00010206 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff81aa3a64 RDX: 000000000000000a RSI: ffffffff81aa3ad1 RDI: 0000000000000050 RBP: ffff8801ac967228 R08: ffff8801af1c6300 R09: 0000000000000000 R10: ffffed00359e0088 R11: ffff8801acf00447 R12: 1ffff1003592ce34 R13: ffff8801ad6aa080 R14: ffff8801ac967200 R15: 0000000000000000 FS: 000000000206b880(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000006ce080 CR3: 00000001ae3c1000 CR4: 00000000001406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 --- 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 syzkaller@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches