All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	"4.0+ only" <stable@vger.kernel.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Fix locking in DRRS	flush/invalidate hooks
Date: Fri, 10 Apr 2015 14:33:09 +0300	[thread overview]
Message-ID: <87fv88qkui.fsf@intel.com> (raw)
In-Reply-To: <20150409163910.GC20904@nuc-i3427.alporthouse.com>

On Thu, 09 Apr 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, Apr 09, 2015 at 04:44:15PM +0200, Daniel Vetter wrote:
>> We must acquire the mutex before we can check drrs.dp, otherwise
>> someone might sneak in with a modeset, clear the pointer after we've
>> checked it and then the code will Oops.
>> 
>> This issue has been introduced in
>> 
>> commit a93fad0f7fb8a3ff12e8814b630648f6d187954c
>> Author: Vandana Kannan <vandana.kannan@intel.com>
>> Date:   Sat Jan 10 02:25:59 2015 +0530
>> 
>>     drm/i915: DRRS calls based on frontbuffer
>> 
>> v2: Don't blow up on uninitialized mutex and work item by checking
>> whether DRRS is support or not first. Also unconditionally initialize
>> the mutex/work item to avoid future trouble.
>> 
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Ramalingam C <ramalingam.c@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Vandana Kannan <vandana.kannan@intel.com>
>> Cc: stable@vger.kernel.org (4.0+ only)
>> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>
> Happier,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> Tested-by: Chris Wilson <chris@chris-wilson.co.uk>

Both pushed to drm-intel-next-fixes, thanks for the patch and review.

BR,
Jani.

> -Chris
>
> -- 
> Chris Wilson, Intel Open Source Technology Centre
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

      reply	other threads:[~2015-04-10 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  9:10 [PATCH] drm/i915: Fix locking in DRRS flush/invalidate hooks Daniel Vetter
2015-04-09  9:52 ` Jani Nikula
2015-04-09 12:38   ` Ville Syrjälä
2015-04-09 14:44 ` [PATCH 1/2] " Daniel Vetter
2015-04-09 14:44   ` [PATCH 2/2] drm/i915: Don't cancel DRRS worker synchronously for flush/invalidate Daniel Vetter
2015-04-09 16:40     ` Chris Wilson
2015-04-09 16:39   ` [PATCH 1/2] drm/i915: Fix locking in DRRS flush/invalidate hooks Chris Wilson
2015-04-10 11:33     ` Jani Nikula [this message]

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=87fv88qkui.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.