From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f199.google.com (mail-pf1-f199.google.com [209.85.210.199]) by kanga.kvack.org (Postfix) with ESMTP id F09686B026D for ; Mon, 6 Aug 2018 11:12:18 -0400 (EDT) Received: by mail-pf1-f199.google.com with SMTP id d1-v6so8733421pfo.16 for ; Mon, 06 Aug 2018 08:12:18 -0700 (PDT) Received: from www262.sakura.ne.jp (www262.sakura.ne.jp. [202.181.97.72]) by mx.google.com with ESMTPS id b35-v6si13501533pgl.562.2018.08.06.08.12.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Aug 2018 08:12:17 -0700 (PDT) Subject: Re: WARNING in try_charge References: <884de816-671a-44d4-a6a1-2ad7eff53715@I-love.SAKURA.ne.jp> <00000000000070698b0572c28ebc@google.com> <20180806113212.GK19540@dhcp22.suse.cz> <39db7dbc-fedf-a86e-3c8b-0192e83d3c8d@i-love.sakura.ne.jp> <20180806145833.GA8607@dhcp22.suse.cz> From: Tetsuo Handa Message-ID: <570de9f7-eda8-ec72-a4d0-92b4cc2b4fd7@i-love.sakura.ne.jp> Date: Tue, 7 Aug 2018 00:12:01 +0900 MIME-Version: 1.0 In-Reply-To: <20180806145833.GA8607@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: syzbot , cgroups@vger.kernel.org, dvyukov@google.com, hannes@cmpxchg.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, vdavydov.dev@gmail.com, David Howells On 2018/08/06 23:58, Michal Hocko wrote: >> Since I can't find mm related changes between next-20180803 (syzbot can reproduce) and >> next-20180806 (syzbot has not reproduced), I can't guess what makes this problem go away. > > Hmm, but original report was against 4.18.0-rc6-next-20180725+ kernel. > And that one had the old group oom code. /me confused. > Yes. But I confirmed that syzbot can reproduce this problem with next-20180803 which already dropped the old group oom code. Therefore, I think that syzbot is hitting a problem other than the old group oom code.