This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Knobs to detect undefined behaviour.

On 10/09/2013 03:28 AM, OndÅej BÃlka wrote:
> On Tue, Oct 08, 2013 at 01:04:16PM -0600, Jeff Law wrote:
>> When I first proposed the idea for these sanity checking dl-preload
>> libraries for Fedora I envisioned that we could go beyond just
>> checking for overlapping memory areas in the mem* and str*
>> functions.  There could be a set of pthread wrapper functions that
>> check for whatever invariants we can in the pthread* functions
>> without a huge performance hit.
> It is possible but we could use a environment variable in libc as
> alternative. Then we could choose detecting implementation by ifunc.
> Or add assert-like macro that will be compiled into
> Main advantage is visibility. If user needs to find ten various libraries 
> and preload them few of users will do that. It should be moved to one place
> As we could add to manpages something like:
> A glibc could detect various undefined behaviours and abort when it is
> detected. But it could break third party binaries so this needs to be
> enabled manually. For checking use:
> GLIBC_SANITIZE=true program
> There are various areas that could be covered:
> str/mem routines - could we merge memstomp?
> malloc - A efence got this almost right but tried to detect all
> overruns.
> If we detect these only statisticaly it could be done only with using
> twice more memory, for requests upto 4096 bytes we will use arena that
> alternates between protected and usable pages like:
> prot use prot use prot use prot
> and for more than 4096 bytes we could use mmap.
> If we placed a 64-bit canary before/after each alloc we could also add
> bounds checking by looking for that canary.
> What else?

There is a lot we could talk about here.

The linker already does process the environment variables so it could
be done via env vars I think.

We need to make forward progress on tunnables per our discussions 
at Cauldron 2013, which is to unify internally all the existing

We also need to make forward progress on env vars, which is to flesh
out the policy and check to see if existing env vars match the
policy and if not then talk about how we might clean things up.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]