From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: stdio self-synchronized destruction: does it need fixing?
Date: Mon, 10 Dec 2012 23:57:53 +0100 [thread overview]
Message-ID: <20121210225752.GI23126@port70.net> (raw)
In-Reply-To: <20121210180508.GA2313@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-12-10 13:05:09 -0500]:
> memory. The allocation of FILE structues is always performed by libc,
> and always happens via malloc with a small-size allocation, which
> means the memory is managed as part of the heap and never unmapped
> once it's mapped. Thus, as far as I can tell, the worst that can
> happen is a read-only access to memory no longer owned by the FILE,
at least write a comment there that the invalid read is known
(btw at some point someone may rewrite malloc so small allocations
can go to mmapped areas as well which may be reclaimed..)
next prev parent reply other threads:[~2012-12-10 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 18:05 Rich Felker
2012-12-10 22:57 ` Szabolcs Nagy [this message]
2012-12-10 23:21 ` Rich Felker
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=20121210225752.GI23126@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).