This is the mail archive of the libc-alpha@sourceware.org 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: [PATCH 14/17 v5] Avoid stack-protecting signal-handling functions sibcalled from assembly.

From: Florian Weimer <fweimer at redhat dot com>
To: Nix <nix at esperi dot org dot uk>
Cc: libc-alpha at sourceware dot org
Date: Fri, 13 May 2016 11:53:58 +0200
Subject: Re: [PATCH 14/17 v5] Avoid stack-protecting signal-handling functions sibcalled from assembly.
Authentication-results: sourceware.org; auth=none
References: <1457882222-22599-1-git-send-email-nix at esperi dot org dot uk> <1457882222-22599-15-git-send-email-nix at esperi dot org dot uk>

On 03/13/2016 04:16 PM, Nix wrote:

Certain signal-handling functions are sibcalled from assembly on
x86, both on Linux and the Hurd.  As such, they depend on having
the same-shaped stack frame, an assumption it seems likely that
-fstack-protector violates.

I think that's not actually true for tail calls tostack-protector-enabled functions from those who are not so enabled.

The lack of rebuild is more problematic. Does it really make adifference, considering that the affected function is not active whilewe initialize the stack guard value?


Thanks,
Florian

Follow-Ups:
- Re: [PATCH 14/17 v5] Avoid stack-protecting signal-handling functions sibcalled from assembly.
  - From: Nix
- Re: [PATCH 14/17 v5] Avoid stack-protecting signal-handling functions sibcalled from assembly.
  - From: Nix

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