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=-0.7 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 AA7C4C4646F for ; Sat, 4 Aug 2018 13:33:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5BD6E217CD for ; Sat, 4 Aug 2018 13:33:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5BD6E217CD 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 S1728904AbeHDPdq (ORCPT ); Sat, 4 Aug 2018 11:33:46 -0400 Received: from mail-it0-f69.google.com ([209.85.214.69]:42304 "EHLO mail-it0-f69.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727293AbeHDPdq (ORCPT ); Sat, 4 Aug 2018 11:33:46 -0400 Received: by mail-it0-f69.google.com with SMTP id l138-v6so8352863itb.7 for ; Sat, 04 Aug 2018 06:33: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=Oo2hWJLKsRmIvjh6T743wZT6V0GWebx+aiK0xPSb8GI=; b=k2rnqYp+jZTeqw21ifg6g6MjO97xeek+8WlLg0j60SWrX0PY4ySc6Z5SoHdFu/Ai1H /yxXoxLlyJqAPY0MVoi/5at/LXqvDHVXzK5nM6k+WjmC343IlNAgwX1GRSO9Z0MEmPrP V8kz2/rBk9UDB58yRY3r0lkKiQjpv7r5K7NRsXPzXC+sVKJz7eevr4UPzYs2j/C4HH0U MjQveFrAlK9Fc/F7JzYip2FomcaGlubprA2cAiX4xz70wTrSH6zW5Jtg2VgdQM8wlezM t6VGTrIN8IeYVzPTSoHlKQarQbdFbKgXvUrU3KhkLUCIxD8eubFayy48MY45HM+HBOXm jcyw== X-Gm-Message-State: AOUpUlHHQbpnFU578hNRkm8vpxUxZbz/bsQqMHnjrC+3vMtxmNPLBsO6 K6viyR3T66l38gFm9CMQ4PUA/KfH/7ECNUXcUOl8XGCJNAjq X-Google-Smtp-Source: AAOMgpfyvl4RA58Md2vZjfZRj3i6TGnKd6h6T5mHjJr42THY0SmZ+oZ2QBw0dXUNOLeRmENku914Z82NOzsN/zBT+m09VoPq1AK7 MIME-Version: 1.0 X-Received: by 2002:a24:f707:: with SMTP id x7-v6mr1306512ith.11.1533389582535; Sat, 04 Aug 2018 06:33:02 -0700 (PDT) Date: Sat, 04 Aug 2018 06:33:02 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000005e979605729c1564@google.com> Subject: WARNING in try_charge From: syzbot To: cgroups@vger.kernel.org, hannes@cmpxchg.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, mhocko@kernel.org, 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: d1e0b8e0cb7a Add linux-next specific files for 20180725 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=15a1c770400000 kernel config: https://syzkaller.appspot.com/x/.config?x=eef3552c897e4d33 dashboard link: https://syzkaller.appspot.com/bug?extid=bab151e82a4e973fa325 compiler: gcc (GCC) 8.0.1 20180413 (experimental) Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+bab151e82a4e973fa325@syzkaller.appspotmail.com Killed process 23767 (syz-executor2) total-vm:70472kB, anon-rss:104kB, file-rss:32768kB, shmem-rss:0kB oom_reaper: reaped process 23767 (syz-executor2), now anon-rss:0kB, file-rss:32000kB, shmem-rss:0kB ------------[ cut here ]------------ Memory cgroup charge failed because of no reclaimable memory! This looks like a misconfiguration or a kernel bug. WARNING: CPU: 1 PID: 23767 at mm/memcontrol.c:1710 mem_cgroup_oom mm/memcontrol.c:1709 [inline] WARNING: CPU: 1 PID: 23767 at mm/memcontrol.c:1710 try_charge+0x734/0x1680 mm/memcontrol.c:2211 Kernel panic - not syncing: panic_on_warn set ... CPU: 1 PID: 23767 Comm: syz-executor2 Not tainted 4.18.0-rc6-next-20180725+ #18 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 panic+0x238/0x4e7 kernel/panic.c:184 --- 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.