From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Phill Wombat <uml@webwombat.com>
Subject: Re: [uml-devel] sysctl -w va.legacy_va_layout=1
Date: Tue, 4 Oct 2005 19:01:41 +0200 [thread overview]
Message-ID: <200510041901.42002.blaisorblade@yahoo.it> (raw)
In-Reply-To: <003e01c59644$3893a5b0$3c01010a@webwombat.com.au>
On Monday 01 August 2005 04:53, Phill Wombat wrote:
> With 2.6.12+bs9 on x86_64 the error now changes
> On the host set:
> sysctl -w va.legacy_va_layout=1
> sysctl -w kernel.randomize_va_space=0
> Starting the uml with init=/bin/sh starts up as usual. Performing the ls
> command now result in a different thing happening: Bad op in do_proc_op
> Where as before it produced:
> Child 22915 exited with signal 11
Hi Phil, I was looking to old bugs and I came through your mail.
Has your bug been fixed in later releases?
Also, I see it's mostly related to x86_64 hosts - which are working a lot
better now (especially thanks to SKAS0 mode).
IOW: is this still an issue, or can I consider this bug "closed"?
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-10-06 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 2:53 [uml-devel] sysctl -w va.legacy_va_layout=1 Phill Wombat
2005-10-04 17:01 ` Blaisorblade [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=200510041901.42002.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=uml@webwombat.com \
--cc=user-mode-linux-devel@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