Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: stable@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	Abhay Kumar <abhay.kumar@intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/atomic: Clean old_state/new_state in drm_atomic_state_default_clear()
Date: Thu, 3 May 2018 13:41:52 +0300	[thread overview]
Message-ID: <20180503104152.GP23723@intel.com> (raw)
In-Reply-To: <20180503063530.GE12521@phenom.ffwll.local>

On Thu, May 03, 2018 at 08:35:30AM +0200, Daniel Vetter wrote:
> On Wed, May 02, 2018 at 09:32:47PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Clear the old_state and new_state pointers for every object in
> > drm_atomic_state_default_clear(). Otherwise
> > drm_atomic_get_{new,old}_*_state() will hand out stale pointers to
> > anyone who hasn't first confirmed that the object is in fact part of
> > the current atomic transcation, if they are called after we've done
> > the ww backoff dance while hanging on to the same drm_atomic_state.
> > 
> > For example, handle_conflicting_encoders() looks like it could hit
> > this since it iterates the full connector list and just calls
> > drm_atomic_get_new_connector_state() for each.
> > 
> > And I believe we have now witnessed this happening at least once in
> > i915 check_digital_port_conflicts(). Commit 8b69449d2663 ("drm/i915:
> > Remove last references to drm_atomic_get_existing* macros") changed
> > the safe drm_atomic_get_existing_connector_state() to the unsafe
> > drm_atomic_get_new_connector_state(), which opened the doors for
> > this particular bug there as well.
> > 
> > Cc: stable@vger.kernel.org
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Abhay Kumar <abhay.kumar@intel.com>
> > Fixes: 581e49fe6b41 ("drm/atomic: Add new iterators over all state, v3.")
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Uh ... that's some bad oversight :-/
> 
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> btw for stable we might want to split this into 1 patch for core objects
> and 1 patch for driver private stuff.

Good point. I forgot we did that after the new iterators were
introduced. I'll do the split.

> Feel free to do so while applying
> and keep my r-b. The fixes line for the 2nd patch would be:
> 
> Fixes: a4370c777406 ("drm/atomic: Make private objs proper objects")
> Cc: <stable@vger.kernel.org> # v4.14+

Ta.

> 
> Cheers, Daniel
> > ---
> >  drivers/gpu/drm/drm_atomic.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> > index 7d25c42f22db..c825c76edc1d 100644
> > --- a/drivers/gpu/drm/drm_atomic.c
> > +++ b/drivers/gpu/drm/drm_atomic.c
> > @@ -155,6 +155,8 @@ void drm_atomic_state_default_clear(struct drm_atomic_state *state)
> >  						       state->connectors[i].state);
> >  		state->connectors[i].ptr = NULL;
> >  		state->connectors[i].state = NULL;
> > +		state->connectors[i].old_state = NULL;
> > +		state->connectors[i].new_state = NULL;
> >  		drm_connector_put(connector);
> >  	}
> >  
> > @@ -169,6 +171,8 @@ void drm_atomic_state_default_clear(struct drm_atomic_state *state)
> >  
> >  		state->crtcs[i].ptr = NULL;
> >  		state->crtcs[i].state = NULL;
> > +		state->crtcs[i].old_state = NULL;
> > +		state->crtcs[i].new_state = NULL;
> >  	}
> >  
> >  	for (i = 0; i < config->num_total_plane; i++) {
> > @@ -181,6 +185,8 @@ void drm_atomic_state_default_clear(struct drm_atomic_state *state)
> >  						   state->planes[i].state);
> >  		state->planes[i].ptr = NULL;
> >  		state->planes[i].state = NULL;
> > +		state->planes[i].old_state = NULL;
> > +		state->planes[i].new_state = NULL;
> >  	}
> >  
> >  	for (i = 0; i < state->num_private_objs; i++) {
> > @@ -190,6 +196,8 @@ void drm_atomic_state_default_clear(struct drm_atomic_state *state)
> >  						 state->private_objs[i].state);
> >  		state->private_objs[i].ptr = NULL;
> >  		state->private_objs[i].state = NULL;
> > +		state->private_objs[i].old_state = NULL;
> > +		state->private_objs[i].new_state = NULL;
> >  	}
> >  	state->num_private_objs = 0;
> >  
> > -- 
> > 2.16.1
> > 
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

-- 
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-03 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 18:32 [PATCH] drm/atomic: Clean old_state/new_state in drm_atomic_state_default_clear() Ville Syrjala
2018-05-02 19:12 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-03  1:35 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-03  6:35 ` [PATCH] " Daniel Vetter
2018-05-03 10:41   ` Ville Syrjälä [this message]
2018-05-03 14:48     ` [Intel-gfx] " Ville Syrjälä
2018-05-03  7:46 ` Maarten Lankhorst

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=20180503104152.GP23723@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=abhay.kumar@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox