From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Airlie Subject: Re: GEM - radeon cs ioctl deadlock Date: Thu, 14 Oct 2010 08:14:58 +1000 Message-ID: <1287008098.4928.9.camel@clockmaker-el6> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by gabe.freedesktop.org (Postfix) with ESMTP id 7E7BA9E930 for ; Wed, 13 Oct 2010 15:15:04 -0700 (PDT) In-Reply-To: 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: Jerome Glisse Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Wed, 2010-10-13 at 17:57 -0400, Jerome Glisse wrote: > So we are facing a deadlock with the radeon cs ioctl. When a buffer is given > a name (with flink) we could endup with 2 handle pointing to the same > object (flink object and open it from same file descriptor). Would it be ok > if i change gem open to first look if we already have an handle for the > object and to use that handle instead of creating a new one ? Or could > this break intel driver ? I think r300g worked around this already, maybe we should just avoid doing it from userspace if possible. Dave.