This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 02/18] Initialize the stack guard earlier when linking statically.
- From: Nix <nix at esperi dot org dot uk>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 09 Mar 2016 22:47:36 +0000
- Subject: Re: [PATCH 02/18] Initialize the stack guard earlier when linking statically.
- Authentication-results: sourceware.org; auth=none
- References: <1457445064-7107-1-git-send-email-nix at esperi dot org dot uk> <1457445064-7107-3-git-send-email-nix at esperi dot org dot uk> <20160309223809 dot GC6588 at vapier dot lan>
On 9 Mar 2016, Mike Frysinger outgrape:
> these patches that can be merged by themselves (like this one) i think
> we should do so sooner so we don't have to keep iterating on 15+ patches.
> as things get reviewed, the pending patchset dwindles and we don't go so
> crazy.
I have no fundamental objection to people doing that, as long as they're
happy with the patches -- but in most cases the patches are useless
deadweight if we don't get stack-protection in the end, so maybe you'd
rather I simply email out only those patches that have changed in each
round (which is easy, I'm tracking that anyway), and then apply the lot
at the end, once you know it's going to be accepted as a whole?
(The only patch here I'd call of truly general utility without
stack-protection is patch 17, the fix for the missing reload of %eax in
the pthread_cond_*wait() x86 assembler implementations.)
--
NULL && (void)