Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Dec 2012 23:57:53 +0100
From: Szabolcs Nagy <>
Subject: Re: stdio self-synchronized destruction: does it need fixing?

* Rich Felker <> [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..)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.