[Mesa-dev] [Bug 86651] [i965 Bisected]Piglit glx_glx-pixmap-multi fails, with DRI3 disabled

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86651

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Driver/intel                |GLX
           Assignee|chris at chris-wilson.co.uk    |mesa-dev at lists.freedesktop.
                   |                            |org
            Product|xorg                        |Mesa
         QA Contact|intel-gfx-bugs at lists.freede |
                   |sktop.org                   |

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
Bisecting the server reveals:

commit d0da0e9c3bb8fe0cd4879ecb24d21715bfaa209b
Author: Eric Anholt <eric at anholt.net>
Date:   Thu Sep 4 10:59:40 2014 -0700

    glx: Disable indirect GLX contexts by default.

    Almost every situation of someone running indirect GLX is a mistake
    that results in X Server crashes.  Indirect GLX is the cause of
    regular security vulnerabilities, and rarely provides any capability
    to the user.  Just disable it unless someone wants to enable it for
    their special use case (using +iglx on the command line).

    Signed-off-by: Eric Anholt <eric at anholt.net>
    Acked-by:  Keith Packard <keithp at keithp.com>
    Signed-off-by: Keith Packard <keithp at keithp.com>

So the question is why is mesa creating an indirect context in this case?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20141230/9675609d/attachment.html>