linux-kernel - Re: [PATCH v4 7/9] liblockdep: Support using LD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51A50708.3000203@oracle.com>
Date:	Tue, 28 May 2013 15:35:36 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	torvalds@...ux-foundation.org, mingo@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 7/9] liblockdep: Support using LD_PRELOAD

On 05/22/2013 05:24 AM, Peter Zijlstra wrote:
> Do we still need this with the glibc __pthread_* static initialization?

Sadly we do.

We need to deal with the two things that cause allocation in our code (because
they loop back into our code via malloc()->malloc_init()->pthread_mutex_init() ).

The first one was the glibc trick to avoid the malloc() caused by dlsym(). The
second one is the malloc() we do when we allocate new lock. Static allocation
deals with that one.

Thanks,
Sasha

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/