mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
	Roland McGrath <roland@redhat.com>,
	Oleg Nesterov <oleg@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [PATCH] consider stack access while checking for alternate signal stack
Date: Mon, 19 Oct 2009 09:33:58 +0200	[thread overview]
Message-ID: <20091019073358.GE17960@elte.hu> (raw)
In-Reply-To: <20091018191247.GA21844@Chamillionaire.breakpoint.cc>


(Cc:-ed more folks, quoted mail and patch can be found below.)

* Sebastian Andrzej Siewior <sebastian@breakpoint.cc> wrote:

> The stack pointer can be either first incremented/decremented and then
> used (lets call it PRE) or incremented/decremented after its use (lets
> call it POST). The difference is whether the stack pointer points to the
> last variable on the stack or to the first free slot. This tiny little
> detail caused Debian bug #544905 on AMD64. gcc-4.3 with -O2 optimized
> the code in a way where the signal stack pointer had the same value as
> the real stack pointer. The stack pointer is PRE_DEC and therefore we
> are not on the alternative stack yet.
> This patch should handle all corned cases now. AVR is the only
> architecture which has a POST operation defined and a Linux port
> avaiable. All other architectures are POST_DEC except PA-RISC which is
> POST_INC
> 
> Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
> ---
> I have also a reduced testcase at [0] which is AMD64 only. Most other
> architectures I've looked at store some register(s) between the stack
> pointer and the first/last variable so I could only trigger it on AMD64.
> 
> Haavard: The AVR32 assumption is pure on gcc's STACK_PUSH_CODE which is
> POST_DEC. Could you please ack/nak it?
> 
> [0] http://download.breakpoint.cc/tc-sig-stack.c
> 
>  arch/avr32/Kconfig    |    3 +++
>  include/linux/sched.h |   24 ++++++++++++++++++++++--
>  2 files changed, 25 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/avr32/Kconfig b/arch/avr32/Kconfig
> index 35e3bd9..520c489 100644
> --- a/arch/avr32/Kconfig
> +++ b/arch/avr32/Kconfig
> @@ -70,6 +70,9 @@ config GENERIC_BUG
>  	def_bool y
>  	depends on BUG
>  
> +config STACK_STORE_POST
> +	def_bool y
> +
>  source "init/Kconfig"
>  
>  source "kernel/Kconfig.freezer"
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 75e6e60..23e6eb6 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -2086,11 +2086,31 @@ static inline int is_si_special(const struct siginfo *info)
>  	return info <= SEND_SIG_FORCED;
>  }
>  
> -/* True if we are on the alternate signal stack.  */
> -
> +/*
> + * True if we are on the alternate signal stack, based on the follwoing
> + * example: The alternative stack handler starts at 0x10 and its size is 0x20
> + * bytes. The numbers behind PRE and POST are aimed as the result.
> + * PRE means the stack is first decremented and than the content of the variale
> + * is stored. This means, the stack pointer points in the PRE case to the last
> + * variable on the stack. In the POST case it points to the first free slot.
> + *
> + *         0   5       10    15   30     40   80
> + *         +-----------+-----------+----------+
> + *         |           | SIG STACK |          |
> + *         +-----------+-----------+----------+
> + * POST        0       1     1     0     0
> + * PRE         0       0     1     1     0
> + */
>  static inline int on_sig_stack(unsigned long sp)
>  {
> +#if defined(CONFIG_STACK_STORE_POST)
>  	return (sp - current->sas_ss_sp < current->sas_ss_size);
> +
> +#else
> +	if (!(sp - current->sas_ss_sp))
> +		return 0;
> +	return (sp - current->sas_ss_sp <= current->sas_ss_size);
> +#endif
>  }
>  
>  static inline int sas_ss_flags(unsigned long sp)
> -- 
> 1.6.4.GIT

  parent reply	other threads:[~2009-10-19  7:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 19:12 Sebastian Andrzej Siewior
2009-10-19  4:09 ` Haavard Skinnemoen
2009-10-19  7:58   ` Sebastian Andrzej Siewior
2009-10-19  9:26     ` Haavard Skinnemoen
2009-10-19  7:33 ` Ingo Molnar [this message]
2009-10-19  8:02   ` Sebastian Andrzej Siewior
2009-10-19 18:08     ` Roland McGrath
2009-10-19 19:30       ` Sebastian Andrzej Siewior
2009-10-20 21:11         ` Roland McGrath
2009-10-21  8:28           ` Sebastian Andrzej Siewior
2009-10-25 14:37           ` [PATCH v2] consider the kind of stack incrementation " Sebastian Andrzej Siewior
2009-11-04 17:27             ` [tip:core/signal] signal: Fix alternate signal stack check tip-bot for Sebastian Andrzej Siewior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091019073358.GE17960@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.com \
    --cc=sebastian@breakpoint.cc \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®