public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Rebecca N. Palmer" <rebecca_palmer@zoho.com>
To: Kees Cook <keescook@google.com>, daniel.vetter@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: drm/i915: Possible security hole in command parsing
Date: Fri, 05 Jun 2015 09:04:16 +0100	[thread overview]
Message-ID: <55715800.3000202@zoho.com> (raw)
In-Reply-To: <CAGXu5jKXZHU-GTuNaTCP1_yjxZrGuPHyx8gmb2G6g_HcPzsNkA@mail.gmail.com>

In next, it was fixed by 
http://cgit.freedesktop.org/drm-intel/commit/drivers/gpu/drm/i915/i915_gem_execbuffer.c?h=for-linux-next&id=c7c7372edc4ebc173ad359aeb5752e9ce09f2741

In 4.1, the problem only exists with the marked-as-unsafe parameter 
i915.enable_ppgtt=2.  (It could be fixed there with 
http://lists.freedesktop.org/archives/intel-gfx/2015-May/066259.html , 
but doing so at this late stage would be risky.)

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-05  8:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 11:32 [PATCH] drm/i915: Possible security hole in command parsing Rebecca N. Palmer
2015-05-01 19:13 ` Rebecca N. Palmer
2015-05-05 21:39   ` Rebecca N. Palmer
2015-06-05  0:29     ` Kees Cook
2015-06-05  8:04       ` Rebecca N. Palmer [this message]
2015-05-08  9:31 ` [PATCH] " Mika Kuoppala
2015-05-08 11:24 ` Daniel Vetter
2015-05-08 13:26   ` [PATCH v2] drm/i915: Fix possible " Rebecca N. Palmer
2015-05-08 14:04     ` Mika Kuoppala
2015-05-08 14:25       ` Daniel Vetter
2015-05-08 16:51         ` [PATCH for 4.1] drm/i915: Don't clear exec_start if batch was not copied Rebecca N. Palmer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55715800.3000202@zoho.com \
    --to=rebecca_palmer@zoho.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keescook@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox