Re: Stop mesa W^X violations

Mark Kettenis writes: >> From: j...@wxcvbn.org (Jeremie Courreges-Anglas) >> Date: Mon, 27 Jun 2016 23:40:35 +0200 >> >> Mark Kettenis writes: >> >> > As reported by several people, mesa contains code that violates W^X. >> > As a result

Re: Stop mesa W^X violations

> From: j...@wxcvbn.org (Jeremie Courreges-Anglas) > Date: Mon, 27 Jun 2016 23:40:35 +0200 > > Mark Kettenis writes: > > > As reported by several people, mesa contains code that violates W^X. > > As a result glxgears aborts when using the swrast driver. The diff > >

Re: Stop mesa W^X violations

Mark Kettenis writes: > As reported by several people, mesa contains code that violates W^X. > As a result glxgears aborts when using the swrast driver. The diff > below disables the offending code. The code seems to deal the absence > of W|X memory just fine. There

Re: Stop mesa W^X violations

On Mon, Jun 20, 2016 at 10:22:58PM +0200, Mark Kettenis wrote: > As reported by several people, mesa contains code that violates W^X. > As a result glxgears aborts when using the swrast driver. The diff > below disables the offending code. The code seems to deal the absence > of W|X memory just

Re: Stop mesa W^X violations

>Note that the existing code would have worked just fine if mmap >returned MAP_FAILED for W^X violations instead of terminating the >program. Not entirely sure what the long-term plans are. Yeah, I am not sure of the long-term plans yet either. In discussions with the ports people the idea was

Stop mesa W^X violations

As reported by several people, mesa contains code that violates W^X. As a result glxgears aborts when using the swrast driver. The diff below disables the offending code. The code seems to deal the absence of W|X memory just fine. There is a fallback path that is also used on SELinux systems.