357839 – /usr/bin/X requires MPROTECT off if mesa-9999 is built with gallium&llvm on hardened

Bug 357839 - /usr/bin/X requires MPROTECT off if mesa-9999 is built with gallium&llvm on hardened

Summary: /usr/bin/X requires MPROTECT off if mesa-9999 is built with gallium&llvm on h...

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal major (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-03-07 21:34 UTC by Piotrek Juzwiak
Modified:	2011-03-07 22:28 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Piotrek Juzwiak 2011-03-07 21:34:58 UTC

X server requires MPROTECT flag disabled if mesa has been built with gallium & llvm use flags. Using classic mesa backend doesn't trigger it since it doesn't use llvm.

I have temporarily fixed by disabling MPROTECT flag on /usb/bin/X but i guess this is very bad idea especially for X. I believe it is due to LLVM having JIT compiler and X on gallium can't start without it?

Reproducible: Always

Steps to Reproduce:
1.Emerge mesa-9999 with gallium&llvm flags on hardened profile
2.(Re)start X server 
3.
Actual Results:  
X server crashes with LLVM stating it can't map memory as RWX

Expected Results:  
X server starts just fine