From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Down Subject: Re: mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page Date: Fri, 29 May 2020 02:56:44 +0100 Message-ID: <20200529015644.GA84588@chrisdown.name> References: <20200520190906.GA558281@chrisdown.name> <20200521095515.GK6462@dhcp22.suse.cz> <20200521163450.GV6462@dhcp22.suse.cz> <20200528150310.GG27484@dhcp22.suse.cz> <20200528164121.GA839178@chrisdown.name> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisdown.name; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=GN9DgkPdwejhyEVH1kmP5gS0KBOAcxSeuTuQOx2XI9o=; b=lkBaXTV2ZUB6ZO5yX3Ng0K/CASCbc9oNlaDIc8KLZ8e4v2cb+z5+AxOSC0HUqdLw42 pPHQXKJiXMf7fSmverIul8xSND7c0ygaABLVaG0hqIXTL8OJ4e0fS8l8+kZ0LHaXgNsT f3Y+1qQWXh34SIawtNNfPuqOwbkRTPMzu6he4= Content-Disposition: inline In-Reply-To: Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit To: Yafang Shao Cc: Naresh Kamboju , Michal Hocko , 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 , lkft- Yafang Shao writes: >Look at this patch[1] carefully you will find that it introduces the >same issue that I tried to fix in another patch [2]. Even more sad is >these two patches are in the same patchset. Although this issue isn't >related with the issue found by Naresh, we have to ask ourselves why >we always make the same mistake ? >One possible answer is that we always forget the lifecyle of >memory.emin before we read it. memory.emin doesn't have the same >lifecycle with the memcg, while it really has the same lifecyle with >the reclaimer. IOW, once a reclaimer begins the protetion value should >be set to 0, and after we traversal the memcg tree we calculate a >protection value for this reclaimer, finnaly it disapears after the >reclaimer stops. That is why I highly suggest to add an new protection >member in scan_control before. I agree with you that the e{min,low} lifecycle is confusing for everyone -- the only thing I've not seen confirmation of is any confirmed correlation with the i386 oom killer issue. If you've validated that, I'd like to see the data :-)