t; full syntax for the latter which I thought you were referring too.
>>
>> //M
>>
>> Sent from my BlackBerry - the most secure mobile device
>>
>>
>> Original Message
>>
>>
>> From: chris.pack...@alliedtelesis.co.nz
>> Sent: April 30, 2
@alliedtelesis.co.nz
Sent: April 30, 2020 05:55
To: nietzs...@lysator.liu.se; christophe.le...@c-s.fr; busybox@busybox.net
Subject: Re: Kernel warns of executable stack
So just to summarize (i.e. this is what I'm about to include as the
commit message that sets the flags in our build
;
> From: chris.pack...@alliedtelesis.co.nz
> Sent: April 30, 2020 04:15
> To: nietzs...@lysator.liu.se; christophe.le...@c-s.fr; busybox@busybox.net
> Subject: Re: Kernel warns of executable stack
>
>
> Just to aid future mailing list searchers
>
> The correct setting is &q
, 2020 04:15
To: nietzs...@lysator.liu.se; christophe.le...@c-s.fr; busybox@busybox.net
Subject: Re: Kernel warns of executable stack
Just to aid future mailing list searchers
The correct setting is "-z noexecstack" putting it in my targets default
CFLAGS seems to have done the trick. I ha
t; From: chris.pack...@alliedtelesis.co.nz
> Sent: April 30, 2020 02:00
> To: nietzs...@lysator.liu.se; christophe.le...@c-s.fr; busybox@busybox.net
> Subject: Re: Kernel warns of executable stack
>
>
>
> On 24/04/20 10:54 am, Markus Gothe wrote:
>> It's not re
ietzs...@lysator.liu.se; christophe.le...@c-s.fr; busybox@busybox.net
Subject: Re: Kernel warns of executable stack
On 24/04/20 10:54 am, Markus Gothe wrote:
> It's not required per se for an application.
>
> But you would need to relink your binaries with '-z,noexecstack' to turn
&
On 24/04/20 10:54 am, Markus Gothe wrote:
> It's not required per se for an application.
>
> But you would need to relink your binaries with '-z,noexecstack' to turn
> it off.
>
> //M
So I've been trying to set CONFIG_EXTRA_LDFLAGS="-z,noexecstack" in my
.config but it doesn't seem to make it thr
It's not required per se for an application.
But you would need to relink your binaries with '-z,noexecstack' to turn
it off.
//M
On 2020-04-24 00:25, Chris Packham wrote:
> On Fri, 2020-04-24 at 00:08 +0200, Markus Gothe wrote:
>> Background: The executable stack is needed for MIPS and the FPU
On Fri, 2020-04-24 at 00:08 +0200, Markus Gothe wrote:
> Background: The executable stack is needed for MIPS and the FPU
> (which
> decodes any unknown instruction as well).
>
> There have been some patches floating around to fix this behavior
> since
> Linux 3.12 so probably that's why you didn't
Background: The executable stack is needed for MIPS and the FPU (which
decodes any unknown instruction as well).
There have been some patches floating around to fix this behavior since
Linux 3.12 so probably that's why you didn't notice before upgrading.
The 'dc' applet at least requires an execu
On Thu, 2020-04-23 at 07:29 +0200, Christophe Leroy wrote:
> Hi,
>
> Christophe
>
> Le 23/04/2020 à 03:13, Chris Packham a écrit :
> > Hi,
> >
> > I'm just in the process of updating our products to Linux v5.6 and
> > one
> > of them produces a new warning message from the kernel about
> > busyb
Hi all!
On 23/04/2020 01:13, Chris Packham wrote:
[...
> Can anyone shed some light on this?
See the other mails - GNU_STACK isn't shown.
I just checked myself: Funny, it's RWE on
Fedora 31 and it's RW on Ubuntu-disco. Both
installed from their official repos.
However there's the linker option
Hi again Chris,
On 04/23/2020 05:29 AM, Christophe Leroy wrote:
Hi,
Christophe
Le 23/04/2020 à 03:13, Chris Packham a écrit :
Hi,
I'm just in the process of updating our products to Linux v5.6 and one
of them produces a new warning message from the kernel about busybox
(v1.31.1)
kernel:
Hi,
Christophe
Le 23/04/2020 à 03:13, Chris Packham a écrit :
Hi,
I'm just in the process of updating our products to Linux v5.6 and one
of them produces a new warning message from the kernel about busybox
(v1.31.1)
kernel: process '/bin/busybox' started with executable stack
Got similar
Hi,
I'm just in the process of updating our products to Linux v5.6 and one
of them produces a new warning message from the kernel about busybox
(v1.31.1)
kernel: process '/bin/busybox' started with executable stack
The target in question is a mips64 (octeon3). We have other targets
(mips32, ar
15 matches
Mail list logo
