mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Witold Baryluk <baryluk@smp.if.uj.edu.pl>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [BUG] drm/radeon: locking problems with page_flip
Date: Wed, 14 Sep 2011 17:36:19 +0200	[thread overview]
Message-ID: <20110914153619.GN23706@smp.if.uj.edu.pl> (raw)
In-Reply-To: <1315906152.17617.24.camel@thor.local>

[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]

On 09-13 11:29, Michel Dänzer wrote:
> On Die, 2011-09-13 at 05:49 +0200, Witold Baryluk wrote: 
> > 
> > I yeasterday discovered pretty nasty issue in radeon / drm code,
> > and page_flip locking code on my ThinkPad T43.
> 
> Does the patch below fix the problem?
> 
> 
> From ed7cf809c4fb737fa486b24004ee47056bf0e797 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Michel=20D=C3=A4nzer?= <michel.daenzer@amd.com>
> Date: Thu, 8 Sep 2011 17:36:22 +0200
> Subject: [PATCH] drm/radeon: Unreference GEM object outside of spinlock
>  in page flip error path.
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> Should fix https://bugzilla.redhat.com/show_bug.cgi?id=726277 .
> 
> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
> ---
>  drivers/gpu/drm/radeon/radeon_display.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/gpu/drm/radeon/radeon_display.c b/drivers/gpu/drm/radeon/radeon_display.c
> index 6cc17fb..6adb3e5 100644
> --- a/drivers/gpu/drm/radeon/radeon_display.c
> +++ b/drivers/gpu/drm/radeon/radeon_display.c
> @@ -473,8 +473,8 @@ pflip_cleanup:
>  	spin_lock_irqsave(&dev->event_lock, flags);
>  	radeon_crtc->unpin_work = NULL;
>  unlock_free:
> -	drm_gem_object_unreference_unlocked(old_radeon_fb->obj);
>  	spin_unlock_irqrestore(&dev->event_lock, flags);
> +	drm_gem_object_unreference_unlocked(old_radeon_fb->obj);
>  	radeon_fence_unref(&work->fence);
>  	kfree(work);
>  
> -- 
> 1.7.5.4

Hi,

unfortunetly I cannot reproduce problem with or without patch.
Will do more stress testing and wait until something happens.


-- 
Witold Baryluk
JID: witold.baryluk // jabster.pl

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-09-14 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13  3:49 Witold Baryluk
2011-09-13  9:29 ` Michel Dänzer
2011-09-14 15:36   ` Witold Baryluk [this message]
2011-09-13 10:19 Chris Rankin

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=20110914153619.GN23706@smp.if.uj.edu.pl \
    --to=baryluk@smp.if.uj.edu.pl \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@daenzer.net \
    /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

all inboxes | Powered by JetHome®