On Thu, 8 Sep 2016, Jonathan Gray wrote:
> On Thu, Sep 08, 2016 at 06:57:44PM +0100, Emil Velikov wrote:
...
> > For a long while the intent has been to use --enable-glx-tls by
> > default and kill off the other codepaths. But with the write xor
> > execute policy, it's going to be (close to) impos
On 8 September 2016 at 19:46, Mark Kettenis wrote:
>> From: Emil Velikov
>> Date: Thu, 8 Sep 2016 18:57:44 +0100
>>
>> On 1 September 2016 at 18:23, Jonathan Gray wrote:
>> > OpenBSD now has strict W^X enforcement. Processes that violate
>> > the policy get killed by the kernel. Don't attempt
> From: Emil Velikov
> Date: Thu, 8 Sep 2016 18:57:44 +0100
>
> On 1 September 2016 at 18:23, Jonathan Gray wrote:
> > OpenBSD now has strict W^X enforcement. Processes that violate
> > the policy get killed by the kernel. Don't attempt to use
> > executable memory on OpenBSD to avoid this.
>
On Thu, Sep 08, 2016 at 06:57:44PM +0100, Emil Velikov wrote:
> On 1 September 2016 at 18:23, Jonathan Gray wrote:
> > OpenBSD now has strict W^X enforcement. Processes that violate
> > the policy get killed by the kernel. Don't attempt to use
> > executable memory on OpenBSD to avoid this.
> >
On 1 September 2016 at 18:23, Jonathan Gray wrote:
> OpenBSD now has strict W^X enforcement. Processes that violate
> the policy get killed by the kernel. Don't attempt to use
> executable memory on OpenBSD to avoid this.
>
> Patch from Mark Kettenis.
>
> --- a/src/gallium/auxiliary/rtasm/rtasm
OpenBSD now has strict W^X enforcement. Processes that violate
the policy get killed by the kernel. Don't attempt to use
executable memory on OpenBSD to avoid this.
Patch from Mark Kettenis.
Cc: 11.2 12.0
Signed-off-by: Mark Kettenis
Signed-off-by: Jonathan Gray
---
src/gallium/auxiliary/rt
