From: Dave Jones <davej@redhat.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, kirill.shutemov@linux.intel.com,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: oops in pgtable_trans_huge_withdraw
Date: Wed, 11 Dec 2013 11:38:09 -0500 [thread overview]
Message-ID: <20131211163809.GA26342@redhat.com> (raw)
In-Reply-To: <52A8877A.10209@suse.cz>
On Wed, Dec 11, 2013 at 04:40:42PM +0100, Vlastimil Babka wrote:
> On 12/06/2013 10:02 PM, Dave Jones wrote:
> > I've spent a few days enhancing trinity's use of mmap's, trying to make it
> > reproduce https://lkml.org/lkml/2013/12/4/499
>
> FYI, I managed to reproduce that using trinity today,
> trinity was from git at commit e8912cc which is from Dec 09 so I guess
> your enhancements were already there?
yep, everything I had pending is in HEAD now.
> kernel was linux-next-20131209
> I was running trinity -c mmap -c munmap -c mremap -c remap_file_pages -c
> mlock -c munlock
A shorthand for all those -c's is '-G vm'. (Though there might be a couple
extra syscalls in the list too, madvise, mprotect etc).
> Now I'm running with Kirill's patch, will post results later.
Seemed to fix it for me, I've not reproduced that particular bug since applying it.
Kirill, is that on its way to Linus soon ?
thanks,
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:[~2013-12-11 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 21:02 oops in pgtable_trans_huge_withdraw Dave Jones
2013-12-06 21:21 ` Dave Jones
2013-12-07 8:21 ` Kirill A. Shutemov
2013-12-09 15:42 ` Dave Jones
2013-12-11 15:40 ` Vlastimil Babka
2013-12-11 15:54 ` Sasha Levin
2013-12-11 19:59 ` Sasha Levin
2013-12-11 16:38 ` Dave Jones [this message]
2013-12-12 0:24 ` Kirill A. Shutemov
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=20131211163809.GA26342@redhat.com \
--to=davej@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
--cc=vbabka@suse.cz \
/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).