From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Subject: do not mremap the sub page of UML [ was:Re: [uml-devel] [info] syscall mremap can't be tested at a UML w/ fuzzy tool trinity]
Date: Sun, 02 Mar 2014 13:03:14 +0100 [thread overview]
Message-ID: <53131E02.9010800@gmx.de> (raw)
In-Reply-To: <CAFLxGvw+1NH-t1jbsc44EzTGD+Jp2jGCn=Ds4dEJ+7LtzDq7pw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
How can I tell trinity to not mremap it ?
On 03/01/2014 10:34 AM, Richard Weinberger wrote:
> On Sat, Mar 1, 2014 at 10:28 AM, Toralf Förster
> <toralf.foerster@gmx.de> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>>>
>>> Today I tested if I can activate that syscall again here
>>> (munmap works fine since few days). Testing a 32 bit user mode
>>> linux image with "$>trinity -q -N 100000 -C 8" gave in the
>>> syslog of the UML guest:
>>>
>>> Mar 1 10:09:18 trinity kernel: Stub registers - Mar 1
>>> 10:09:18 trinity kernel: 0 - 100000
> Looks like the stub page. You cannot remap it. If you do so the
> calling process will die.
>
- --
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlMTHgIACgkQxOrN3gB26U7mJAD+NoKRpLbpLjbQyry7y0Ngkbmx
oH9pVUr0bu1tbbfB+pYBAIQ+scnrW97kngcFAM2bJb/R9fp6osEB4AbPpV5ZEmwC
=hgfr
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-03-02 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 9:28 [info] syscall mremap can't be tested at a UML w/ fuzzy tool trinity Toralf Förster
2014-03-01 9:34 ` [uml-devel] " Richard Weinberger
2014-03-02 12:03 ` Toralf Förster [this message]
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=53131E02.9010800@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=trinity@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).