From: Dave Jones <davej@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: David Rientjes <rientjes@google.com>,
khlebnikov@openvz.org, Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: BUG: Bad rss-counter state
Date: Wed, 22 Jan 2014 21:21:47 -0500 [thread overview]
Message-ID: <20140123022147.GA3221@redhat.com> (raw)
In-Reply-To: <52E07B63.1070400@oracle.com>
On Wed, Jan 22, 2014 at 09:16:03PM -0500, Sasha Levin wrote:
> On 01/22/2014 08:52 PM, Dave Jones wrote:
> > Sasha, is this the current git tree version of Trinity ?
> > (I'm wondering if yesterdays munmap changes might be tickling this bug).
>
> Ah yes, my tree has the munmap patch from yesterday, which would explain why we
> started seeing this issue just now.
So that change is basically allowing trinity to munmap just part of a prior mmap.
So it may do things like..
mmap |--------------|
munmap |----XXX-------|
munmap |------XXX-----|
ie, it might try unmapping some pages more than once, and may even overlap prior munmaps.
until yesterdays change, it would only munmap the entire mmap.
There's no easy way to tell exactly what happened without a trinity log of course.
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-23 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 1:07 Sasha Levin
2014-01-23 1:39 ` David Rientjes
2014-01-23 1:52 ` Dave Jones
2014-01-23 2:16 ` Sasha Levin
2014-01-23 2:21 ` Dave Jones [this message]
2014-01-23 3:14 ` Sasha Levin
2014-01-23 2:15 ` Sasha Levin
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=20140123022147.GA3221@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.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