All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Marc Strämke" <marc.straemke@eltropuls.de>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Hang/Reboot when using CONFIG_CC_STACKPROTECTOR_REGULAR
Date: Thu, 30 Apr 2015 16:53:52 +0200	[thread overview]
Message-ID: <20150430145352.GV1993@hermes.click-hack.org> (raw)
In-Reply-To: <5455853.puTnBMi752@eltrolinux48.eltroad.eltropuls>

On Thu, Apr 30, 2015 at 04:44:46PM +0200, Marc Strämke wrote:
> Am Donnerstag, 30. April 2015, 16:41:05 schrieb Gilles Chanteperdrix:
> > No. At least ARM and x86 architectures are supposed to support the
> > stack protector. Maybe you could tell us on what architecture you
> > have this issue?
> 
> The platform is 32bit x86. GCC version is 4.9.2. I can reliably get the 
> behaviour by switching just this single config option on three different 
> machines. 

I have no doubt about that. I am just telling you that disabling the
stack protector is not an option.

> 
> Anything else I can do to help troubleshooting? The kernel actually does not 
> print any message to the console even with all debugging information (ipipe 
> and xenomai) switched on. Most of the time it just reboots, which seems 
> strange to me as is (the TCO watchdog etc is switched off and reboot on panic 
> also..). It did hang on some trys also though ... (not fully reproducible)

Is CONFIG_CC_STACKPROTECTOR enabled when you enable the *_REGULAR
option ? The first thing to check is that the xnarch_switch_to
function contains the necessary bits in the kernel ELF image
disassembly (function vmlinux at the top of the kernel build
directory). You should compare this code to the contents of
kernel/cobalt/arch/x86/thread.c in xenomai sources (where you see
some code with #ifdef CONFIG_CC_STACKPROTECTOR).

-- 
					    Gilles.


  reply	other threads:[~2015-04-30 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 14:33 [Xenomai] Hang/Reboot when using CONFIG_CC_STACKPROTECTOR_REGULAR Marc Strämke
2015-04-30 14:41 ` Gilles Chanteperdrix
2015-04-30 14:44   ` Marc Strämke
2015-04-30 14:53     ` Gilles Chanteperdrix [this message]
2015-04-30 15:03       ` Marc Strämke
2015-04-30 15:12         ` Marc Strämke
2015-04-30 15:14           ` Gilles Chanteperdrix
2015-04-30 15:17             ` Marc Strämke
2015-05-01  8:15               ` Jan Kiszka
2015-05-02 15:31                 ` Marc Strämke

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=20150430145352.GV1993@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=marc.straemke@eltropuls.de \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.