From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrea Arcangeli <andrea@suse.de>, Chris Wedgwood <cw@f00f.org>,
"David S. Miller" <davem@redhat.com>,
David Luyer <david_luyer@pacific.net.au>,
<linux-kernel@vger.kernel.org>
Subject: Re: /proc/<n>/maps growing...
Date: Mon, 06 Aug 2001 18:46:09 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20010806184120.04b9b640@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0108061019280.8972-100000@penguin.transmeta. com>
In-Reply-To: <20010806143603.C20837@athlon.random>
At 18:20 06/08/2001, Linus Torvalds wrote:
>On Mon, 6 Aug 2001, Andrea Arcangeli wrote:
>
> > On Tue, Aug 07, 2001 at 12:26:50AM +1200, Chris Wedgwood wrote:
> > > mmap does merge in many common cases.
> >
> > (assuming you speak about 2.2 because 2.4 obviously doesn't merge
> > anything and that's the point of the discussion) So what? What do you
> > mean with your observation?
>
>2.4.x _does_ merge. Look for yourself. It doesn't merge mprotects, no. And
>why should glibc do mprotect() for a malloc() call? Electric Fence, yes.
>glibc, no.
Is it possible that is has something to do with what "man malloc" on my
machine says in the notes section:
---quote from man page, glibc 2.2.3-14 on RedHat 7.something---
Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x)
include a malloc implementation which is tunable via environment variables.
When MALLOC_CHECK_ is set, a special (less efficient) implementation is
used which is designed to be tolerant against simple errors, such as double
calls of free() with the same argument, or overruns of a single byte
(off-by-one bugs). Not all such errors can be proteced against, however,
and memory leaks can result. If MALLOC_CHECK_ is set to 0, any detected
heap corruption is silently ignored; if set to 1, a diagnostic is printed
on stderr; if set to 2, abort() is called immediately. This can be useful
because otherwise a crash may happen much later, and the true cause for the
problem is then very hard to track down.
---eoq---
That sounds like the kind of stuff Electric Fence would be doing, doesn't it?
Best regards,
Anton
--
"Nothing succeeds like success." - Alexandre Dumas
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2001-08-06 17:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 6:41 /proc/<n>/maps growing David Luyer
2001-08-06 7:43 ` Chris Wedgwood
2001-08-06 8:59 ` Andrea Arcangeli
2001-08-06 10:30 ` Jakub Jelinek
2001-08-06 10:49 ` Andrea Arcangeli
2001-08-06 11:01 ` Jakub Jelinek
2001-08-06 11:25 ` Andrea Arcangeli
2001-08-06 17:17 ` Linus Torvalds
2001-08-06 17:26 ` Alan Cox
2001-08-06 22:55 ` Chris Wedgwood
2001-08-06 11:16 ` Jakub Jelinek
2001-08-06 17:18 ` Linus Torvalds
2001-08-06 9:20 ` David S. Miller
2001-08-06 9:46 ` Chris Wedgwood
2001-08-06 10:57 ` Andrea Arcangeli
2001-08-06 12:26 ` Chris Wedgwood
2001-08-06 12:36 ` Andrea Arcangeli
2001-08-06 12:45 ` Chris Wedgwood
2001-08-06 12:50 ` Andrea Arcangeli
2001-08-06 13:06 ` David S. Miller
2001-08-06 13:29 ` Andrea Arcangeli
2001-08-06 17:27 ` Linus Torvalds
2001-09-03 15:44 ` mmap-rb-7 [was Re: /proc/<n>/maps growing...] Andrea Arcangeli
2001-08-06 17:20 ` /proc/<n>/maps growing Linus Torvalds
2001-08-07 2:24 ` David Luyer
2001-08-06 17:46 ` Anton Altaparmakov [this message]
2001-08-06 16:12 ` Rik van Riel
2001-08-06 17:46 ` Linus Torvalds
2001-08-07 3:46 Rick Hohensee
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=5.1.0.14.2.20010806184120.04b9b640@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=andrea@suse.de \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=david_luyer@pacific.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).