From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Slusarz Subject: Re: [PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer. Date: Tue, 21 Sep 2010 21:35:25 +0200 Message-ID: <20100921193525.GA2746@joi.lan> References: <1285028115-5235-1-git-send-email-currojerez@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-fx0-f49.google.com (mail-fx0-f49.google.com [209.85.161.49]) by gabe.freedesktop.org (Postfix) with ESMTP id 6C0679E7EA for ; Tue, 21 Sep 2010 12:36:30 -0700 (PDT) Received: by fxm4 with SMTP id 4so2259801fxm.36 for ; Tue, 21 Sep 2010 12:36:29 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1285028115-5235-1-git-send-email-currojerez@riseup.net> 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: Francisco Jerez Cc: Thomas Hellstrom , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Tue, Sep 21, 2010 at 02:15:15AM +0200, Francisco Jerez wrote: > It makes sense for a BO to move after a process has requested > exclusive RW access on it (e.g. because the BO used to be located in > unmappable VRAM and we intercepted the CPU access from the fault > handler). > > If we let the ghost object inherit cpu_writers from the original > object, ttm_bo_release_list() will raise a kernel BUG when the ghost > object is destroyed. This can be reproduced with the nouveau driver on > nv5x. > > Reported-by: Marcin Slusarz > Signed-off-by: Francisco Jerez After few hours of testing, I can say: Tested-by: Marcin Slusarz Thanks, Marcin