From: Jeff Dike <jdike@addtoit.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Ingo Molnar <mingo@redhat.com>, Pete Zaitcev <zaitcev@redhat.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: Segfault of UML-TT on FC1
Date: Tue, 17 Feb 2004 12:10:34 -0500 [thread overview]
Message-ID: <200402171710.i1HHAYMM002541@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 16 Feb 2004 19:32:30 GMT." <Pine.LNX.4.58.0402161916440.8742@vega.dur.ac.uk>
m.a.young@durham.ac.uk said:
> The remaining issue which the final part addresses is that a later
> routine that reserves area to act as physical memory still assumes the
> areas are adjacent, and you get a random amount less memory reserved
> than you expect (something like 16M), and this might not leave you
> with enough memory to use.
The space is non-zero even on a non-exec-shield system, probably because some
mallocing has pushed the brk across a page boundary. So I changed it to add
memory only if it's > 1M, and also added a printf saying what's happening.
Jeff
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-02-17 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 7:25 [uml-devel] Segfault of UML-TT on FC1 Pete Zaitcev
2004-02-16 7:47 ` Steven Pritchard
2004-02-16 7:50 ` [uml-devel] " Ingo Molnar
2004-02-16 19:32 ` M A Young
2004-02-17 17:10 ` Jeff Dike [this message]
2004-02-16 20:27 ` Jeff Dike
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=200402171710.i1HHAYMM002541@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=m.a.young@durham.ac.uk \
--cc=mingo@redhat.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=zaitcev@redhat.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