On Fri, Jun 24, 2011 at 05:37:11PM -0700, Eric Anholt wrote: > On Fri, 24 Jun 2011 12:42:48 -0700, Ben Widawsky <[email protected]> wrote: > > The debugger shared memory needs to be a fixed size. Since this is > > scratch memory that is already used by register spilling, add > > appropriate hooks to do the right thing when debugging. > > > > Also copy in a binary blob system routine based on an environment > > variable. This blob will need to be relocated, and emitted as part of > > the state setup. We do this part now since there is no point debugging > > if that fails. > > > > Signed-off-by: Ben Widawsky <[email protected]> > > This patch loads a file from a user-defined path into graphics memory, > which is accessible by any user with DRI permissions. If the X Server > is setuid, then it seems this patch would allow loading any file on the > system by a user with permission to start the setuid X Server.
Well since you put it that way, that does sound like a really bad idea. Do you have a recommendation? I suppose I can get a make install working to install the system routine to wherever mesa was installed and read it from there when mesa runs. Does that sound like the best solution to you?
pgpmS9DuFra71.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
