[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071215035200.GA22082@linux.vnet.ibm.com>
Date: Sat, 15 Dec 2007 09:22:00 +0530
From: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: htejun@...il.com, gregkh@...e.de, stable@...nel.org,
linux-kernel@...r.kernel.org, maneesh@...ux.vnet.ibm.com,
vatsa@...ux.vnet.ibm.com, balbir@...ibm.com, ego@...ibm.com,
linux-mm@...ck.org
Subject: Re: 2.6.22-stable causes oomkiller to be invoked
> Is it really the case that the bug only turns up when you run tests like
>
> while echo; do cat /sys/kernel/kexec_crash_loaded; done
> and
> while echo; do cat /sys/kernel/uevent_seqnum ; done;
>
> or will any fork-intensive workload also do it? Say,
>
> while echo ; do true ; done
>
This does not leak, but having a simple text file and reading it in a
loop causes it.
> ?
>
> Another interesting factoid here is that after the oomkilling you slabinfo has
>
> mm_struct 38 98 584 7 1 : tunables 32 16 8 : slabdata 14 14 0 : globalstat 2781 196 49 31 0 1 0 0 0 : cpustat 368800 11864 368920 11721
>
> so we aren't leaking mm_structs. In fact we aren't leaking anything from
> slab. But we are leaking pgds.
>
> iirc the most recent change we've made in the pgd_t area is the quicklist
> management which went into 2.6.22-rc1. You say the bug was present in
> 2.6.22. Can you test 2.6.21?
Nope, leak is not present in 2.6.21.7
--
regards,
Dhaval
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists