From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Hellstrom Subject: Re: Broken locking in ttm_bo_swapout Date: Thu, 27 Jan 2011 09:47:39 +0100 Message-ID: <4D41312B.6090207@shipmail.org> References: <4D38849C.5020808@tadpole.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [65.115.85.69]) by gabe.freedesktop.org (Postfix) with ESMTP id 115719EB68 for ; Thu, 27 Jan 2011 00:47:46 -0800 (PST) In-Reply-To: <4D38849C.5020808@tadpole.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Matthew Bullock Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On 01/20/2011 07:53 PM, Matthew Bullock wrote: > I have a fairly simple opengl application running on nouveau. It > effectively just plots a couple of very large images that change > regularly. > > I've been getting an easily repeatable failure, hitting the > BUG_ON(in_interrupt) in vfree() that is called during ttm_shrink_work(). > Obviously vfree() is being called with a lock held... > > Looking at the locking up through the stack trace, there's an obvious > mistake: > > There should be a: > spin_lock(&glob->lru_lock); > before the continue in ttm_bo_swapout() in drivers/gpu/drm/ttm/ttm_bo.c > > --- ttm_bo.c~ 2011-01-05 00:50:19.000000000 +0000 > +++ ttm_bo.c 2011-01-20 18:11:57.262813765 +0000 > @@ -1761,6 +1761,7 @@ static int ttm_bo_swapout(struct ttm_mem > spin_unlock(&glob->lru_lock); > (void) ttm_bo_cleanup_refs(bo, false, false, > false); > kref_put(&bo->list_kref, ttm_bo_release_list); > + spin_lock(&glob->lru_lock); > continue; > } > > That fixes the problem for me. > > Matthew > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel Indeed this fix looks correct. Sorry for taking so long to respond. Could you spin a patch against Dave's drm-fixes tree or do you want me to do that? Thanks, Thomas