linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: CAI Qian <caiqian@redhat.com>
To: avagin@gmail.com
Cc: Andrey Vagin <avagin@openvz.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mel@csn.ul.ie>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Minchan Kim <minchan.kim@gmail.com>
Subject: Re: [PATCH] mm: check zone->all_unreclaimable in all_unreclaimable()
Date: Tue, 3 May 2011 21:38:39 -0400 (EDT)	[thread overview]
Message-ID: <1593977838.225469.1304473119444.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <4D72580D.4000208@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]



----- Original Message -----
> On 03/05/2011 06:20 PM, Minchan Kim wrote:
> > On Sat, Mar 05, 2011 at 02:44:16PM +0300, Andrey Vagin wrote:
> >> Check zone->all_unreclaimable in all_unreclaimable(), otherwise the
> >> kernel may hang up, because shrink_zones() will do nothing, but
> >> all_unreclaimable() will say, that zone has reclaimable pages.
> >>
> >> do_try_to_free_pages()
> >> 	shrink_zones()
> >> 		 for_each_zone
> >> 			if (zone->all_unreclaimable)
> >> 				continue
> >> 	if !all_unreclaimable(zonelist, sc)
> >> 		return 1
> >>
> >> __alloc_pages_slowpath()
> >> retry:
> >> 	did_some_progress = do_try_to_free_pages(page)
> >> 	...
> >> 	if (!page&& did_some_progress)
> >> 		retry;
> >>
> >> Signed-off-by: Andrey Vagin<avagin@openvz.org>
> >> ---
> >>   mm/vmscan.c | 2 ++
> >>   1 files changed, 2 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/mm/vmscan.c b/mm/vmscan.c
> >> index 6771ea7..1c056f7 100644
> >> --- a/mm/vmscan.c
> >> +++ b/mm/vmscan.c
> >> @@ -2002,6 +2002,8 @@ static bool all_unreclaimable(struct zonelist
> >> *zonelist,
> >>
> >>   	for_each_zone_zonelist_nodemask(zone, z, zonelist,
> >>   			gfp_zone(sc->gfp_mask), sc->nodemask) {
> >> + if (zone->all_unreclaimable)
> >> + continue;
> >>   		if (!populated_zone(zone))
> >>   			continue;
> >>   		if (!cpuset_zone_allowed_hardwall(zone, GFP_KERNEL))
> >
> > zone_reclaimable checks it. Isn't it enough?
> I sent one more patch [PATCH] mm: skip zombie in OOM-killer.
> This two patches are enough.
> > Does the hang up really happen or see it by code review?
> Yes. You can reproduce it for help the attached python program. It's
> not
> very clever:)
> It make the following actions in loop:
> 1. fork
> 2. mmap
> 3. touch memory
> 4. read memory
> 5. munmmap
> 
> >> --
> >> 1.7.1
I have tested this for the latest mainline kernel using the reproducer
attached, the system just hung or deadlock after oom. The whole oom
trace is here.
http://people.redhat.com/qcai/oom.log

Did I miss anything?

[-- Attachment #2: memeater.py --]
[-- Type: text/plain, Size: 695 bytes --]

import sys, time, mmap, os
from subprocess import Popen, PIPE
import random

global mem_size

def info(msg):
	pid = os.getpid()
	print >> sys.stderr, "%s: %s" % (pid, msg)
	sys.stderr.flush()



def memory_loop(cmd = "a"):
	"""
	cmd may be:
		c: check memory
		else: touch memory
	"""
	c = 0
	for j in xrange(0, mem_size):
		if cmd == "c":
			if f[j<<12] != chr(j % 255):
				info("Data corruption")
				sys.exit(1)
		else:
			f[j<<12] = chr(j % 255)

while True:
	pid = os.fork()
	if (pid != 0):
		mem_size = random.randint(0, 56 * 4096)
		f = mmap.mmap(-1, mem_size << 12, mmap.MAP_ANONYMOUS|mmap.MAP_PRIVATE)
		memory_loop()
		memory_loop("c")
		f.close()

  parent reply	other threads:[~2011-05-04  1:39 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 11:44 [PATCH] mm: check zone->all_unreclaimable in all_unreclaimable() Andrey Vagin
2011-03-05 15:20 ` Minchan Kim
2011-03-05 15:34   ` Andrew Vagin
2011-03-05 15:53     ` Minchan Kim
2011-03-05 16:41       ` Andrew Vagin
2011-03-05 17:07         ` Minchan Kim
2011-03-07 21:58           ` Andrew Morton
2011-03-07 23:45             ` Minchan Kim
2011-03-09  5:37               ` KAMEZAWA Hiroyuki
2011-03-09  5:43                 ` KAMEZAWA Hiroyuki
2011-03-10  6:58                 ` Minchan Kim
2011-03-10 23:58                   ` KAMEZAWA Hiroyuki
2011-03-11  0:18                     ` Minchan Kim
2011-03-11  6:08                       ` avagin
2011-03-14  1:03                         ` Minchan Kim
2011-03-08  0:44             ` KAMEZAWA Hiroyuki
2011-03-08  3:06               ` KOSAKI Motohiro
2011-03-08 19:02                 ` avagin
2011-03-09  5:52                   ` KAMEZAWA Hiroyuki
2011-03-09  6:17                   ` KOSAKI Motohiro
2011-03-10 14:08                     ` KOSAKI Motohiro
2011-03-08  8:12               ` Andrew Vagin
2011-03-09  6:06                 ` KAMEZAWA Hiroyuki
2011-05-04  1:38     ` CAI Qian [this message]
2011-05-09  6:54       ` KOSAKI Motohiro
2011-05-09  8:47         ` CAI Qian
2011-05-09  9:19           ` KOSAKI Motohiro
2011-05-10  8:11             ` OOM Killer don't works at all if the system have >gigabytes memory (was Re: [PATCH] mm: check zone->all_unreclaimable in all_unreclaimable()) KOSAKI Motohiro
2011-05-10  8:14               ` [PATCH 1/4] oom: improve dump_tasks() show items KOSAKI Motohiro
2011-05-10 23:29                 ` David Rientjes
2011-05-13 10:14                   ` KOSAKI Motohiro
2011-05-10  8:15               ` [PATCH 2/4] oom: kill younger process first KOSAKI Motohiro
2011-05-10 23:31                 ` David Rientjes
2011-05-13 10:15                   ` KOSAKI Motohiro
2011-05-11 23:33                 ` Minchan Kim
2011-05-12  0:52                 ` KAMEZAWA Hiroyuki
2011-05-12  1:30                   ` Minchan Kim
2011-05-12  1:53                     ` KAMEZAWA Hiroyuki
2011-05-12  2:23                       ` Minchan Kim
2011-05-12  3:39                         ` KAMEZAWA Hiroyuki
2011-05-12  4:17                           ` Minchan Kim
2011-05-12 14:38                             ` Paul E. McKenney
2011-05-13 10:18                   ` KOSAKI Motohiro
2011-05-10  8:15               ` [PATCH 3/4] oom: oom-killer don't use permillage of system-ram internally KOSAKI Motohiro
2011-05-10 23:40                 ` David Rientjes
2011-05-13 10:30                   ` KOSAKI Motohiro
2011-05-10  8:16               ` [PATCH 4/4] oom: don't kill random process KOSAKI Motohiro
2011-05-10 23:41                 ` David Rientjes
2011-05-10 23:22               ` OOM Killer don't works at all if the system have >gigabytes memory (was Re: [PATCH] mm: check zone->all_unreclaimable in all_unreclaimable()) David Rientjes
2011-05-11  2:30               ` CAI Qian
2011-05-11 20:34                 ` David Rientjes
2011-05-12  0:13                   ` Minchan Kim
2011-05-12 19:38                     ` David Rientjes
2011-05-13  4:16                       ` Minchan Kim
2011-05-13 11:04                         ` KOSAKI Motohiro
2011-05-16 20:42                           ` David Rientjes
2011-05-13  6:53                   ` CAI Qian
2011-05-16 20:46                     ` David Rientjes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1593977838.225469.1304473119444.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
    --to=caiqian@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@gmail.com \
    --cc=avagin@openvz.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).