From: Michal Hocko Subject: Re: mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page Date: Thu, 28 May 2020 17:03:10 +0200 Message-ID: <20200528150310.GG27484@dhcp22.suse.cz> References: <20200519075213.GF32497@dhcp22.suse.cz> <20200519084535.GG32497@dhcp22.suse.cz> <20200520190906.GA558281@chrisdown.name> <20200521095515.GK6462@dhcp22.suse.cz> <20200521163450.GV6462@dhcp22.suse.cz> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-block-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Naresh Kamboju Cc: Yafang Shao , Chris Down , Anders Roxell , "Linux F2FS DEV, Mailing List" , linux-ext4 , linux-block , Andrew Morton , open list , Linux-Next Mailing List , linux-mm , Arnd Bergmann , Andreas Dilger , Jaegeuk Kim , Theodore Ts'o , Chao Yu , Hugh Dickins , Andrea Arcangeli , Matthew Wilcox , Chao Yu , On Fri 22-05-20 02:23:09, Naresh Kamboju wrote: > My apology ! > As per the test results history this problem started happening from > Bad : next-20200430 (still reproducible on next-20200519) > Good : next-20200429 > > The git tree / tag used for testing is from linux next-20200430 tag and reverted > following three patches and oom-killer problem fixed. > > Revert "mm, memcg: avoid stale protection values when cgroup is above > protection" > Revert "mm, memcg: decouple e{low,min} state mutations from protectinn checks" > Revert "mm-memcg-decouple-elowmin-state-mutations-from-protection-checks-fix" The discussion has fragmented and I got lost TBH. In http://lkml.kernel.org/r/CA+G9fYuDWGZx50UpD+WcsDeHX9vi3hpksvBAWbMgRZadb0Pkww@mail.gmail.com you have said that none of the added tracing output has triggered. Does this still hold? Because I still have a hard time to understand how those three patches could have the observed effects. -- Michal Hocko SUSE Labs