linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: user-mode-linux-user@lists.sourceforge.net,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: linux-v3.9-rc3: BUG: Bad page map in process trinity-child6 pte:002f9045 pmd:29e421e1
Date: Tue, 26 Mar 2013 17:44:58 +0100	[thread overview]
Message-ID: <5151D08A.2060400@gmx.de> (raw)
In-Reply-To: <20130325155347.75290358a6985e17fb10ad14@linux-foundation.org>

On 03/25/2013 11:53 PM, Andrew Morton wrote:
> On Fri, 22 Mar 2013 18:28:36 +0100 Toralf F__rster <toralf.foerster@gmx.de> wrote:
> 
>> > Using trinity I often trigger under a user mode linux image with host kernel 3.8.4
>> > and guest kernel linux-v3.9-rc3-244-g9217cbb the following :
>> > (The UML guest is a 32bit stable Gentoo Linux)
> I assume 3.8 is OK?
> 
With UML kernel 3.7.10 (host kernel still 3.8.4) I can trigger this
issue too.
Just to clarify it - here the bug appears in the UML kernel - the host
kernel is ok (I can of course crash a host kernel too by trinity'ing an
UML guest, but that's another thread - see [1])


FWIW he trinity command is just a test of 1 syscall:

$> trinity --children 1 --victims /mnt/nfs/n22/victims -c mremap



[1] https://lkml.org/lkml/2013/3/24/174

-- 
MfG/Sincerely
Toralf FA?rster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

--
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>

  reply	other threads:[~2013-03-26 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <514C94C4.4050008@gmx.de>
2013-03-25 22:53 ` linux-v3.9-rc3: BUG: Bad page map in process trinity-child6 pte:002f9045 pmd:29e421e1 Andrew Morton
2013-03-26 16:44   ` Toralf Förster [this message]
2013-03-26 23:03     ` Hugh Dickins
2013-03-27 19:55       ` richard -rw- weinberger

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=5151D08A.2060400@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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).