From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: cw@f00f.org (Chris Wedgwood)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
hpa@zytor.com (H. Peter Anvin),
linux-kernel@vger.kernel.org
Subject: Re: /proc/<n>/maps getting _VERY_ long
Date: Mon, 6 Aug 2001 14:17:32 +0100 (BST) [thread overview]
Message-ID: <E15TkGC-0000z3-00@the-village.bc.nu> (raw)
In-Reply-To: <20010807002320.A23937@weta.f00f.org> from "Chris Wedgwood" at Aug 07, 2001 12:23:20 AM
> On Mon, Aug 06, 2001 at 12:52:37PM +0100, Alan Cox wrote:
>
> That would explain a lot since mprotect currently doesn't seem to do
> merging, and worse it also seems to not be doing rlimit checking right
>
> Err stupid question, but why does it need to do rlimit checking?
mmap nothing over a large space
mprotect it read/write
next prev parent reply other threads:[~2001-08-06 13:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 15:43 /proc/<n>/maps getting _VERY_ long Chris Wedgwood
2001-08-05 2:17 ` Rik van Riel
2001-08-05 5:12 ` Chris Wedgwood
2001-08-05 13:06 ` Alan Cox
2001-08-05 13:18 ` Chris Wedgwood
2001-08-05 23:07 ` Jakob Østergaard
2001-08-05 23:41 ` Linus Torvalds
2001-08-06 0:41 ` Michael H. Warfield
2001-08-06 1:01 ` Linus Torvalds
2001-08-06 1:17 ` H. Peter Anvin
2001-08-06 4:26 ` Linus Torvalds
2001-08-06 6:30 ` H. Peter Anvin
2001-08-06 18:41 ` Jamie Lokier
2001-08-10 21:55 ` Linus Torvalds
2001-08-10 22:00 ` H. Peter Anvin
2001-08-10 23:03 ` Nicolas Pitre
2001-08-10 23:26 ` Linus Torvalds
2001-08-10 23:55 ` Rik van Riel
2001-08-11 1:04 ` Pavel Machek
2001-08-06 11:52 ` Alan Cox
2001-08-06 12:23 ` Chris Wedgwood
2001-08-06 13:17 ` Alan Cox [this message]
2001-08-06 13:55 ` Chris Wedgwood
2001-08-06 9:43 ` [LONGish] Brief analysis of VMAs (was: /proc/<n>/maps getting _VERY_ long) Chris Wedgwood
2001-08-05 6:44 /proc/<n>/maps getting _VERY_ long David Luyer
2001-08-05 7:21 ` Anders Eriksson
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=E15TkGC-0000z3-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@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 NNTP newsgroup(s).