On 09/16/16 07:09, Sam Varshavchik wrote:
Tom Horsley writes:
> On Wed, 14 Sep 2016 06:47:28 -0400
> Sam Varshavchik wrote:
>
> > But why even bother
> > mapping anything. I would think that accessing an unmapped region would
> > result in a SIGSEGV just as well.
>
> Ah-HA! A question I can answer :-).
>
> You need to map something because otherwise the program itself
> might have code to map something of its own and unless you reserve
> the protected space, it might wind up becoming unprotected.
>
> I also see a new 4.7.3 kernel showed up in the repos. I wonder
> if the problem goes away with it?
Nope, and the issue is being reported by others, too. Not just me.
Do you happen to know the Bugzilla?
--
You're Welcome Zachary Quinto