Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3050991imm; Mon, 28 May 2018 23:25:51 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLPWRTmcH7HU1/UECRJO3MXcWlTpdk226c4o5FkQGJcBc7P6/epU/8+1w9SQXaT964I00Ot X-Received: by 2002:a17:902:5517:: with SMTP id f23-v6mr3327477pli.108.1527575150956; Mon, 28 May 2018 23:25:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527575150; cv=none; d=google.com; s=arc-20160816; b=Amx+JUmOBX5ZgIIjkUP0ozvWGOjx/i7cLxP90oFXkNKbFenRBB2ljMI4+3/l0ah843 ntKl3GKF5ervLJAPDdScQOexi0FZUhXF9Z5yGclgFCR/QIgB2C9fsLNmCCj7en2E02aY vm67aiYy5QsTCmR6k7a6NqnoHLwKRzobpCEg+amM4fhMcKZLqOdwAyflplhI+4BQ8OwI 4gkOixpzdKtZd7BoAej45VC6Az3YE1NByJ3bxzDup+XVZ4VTO39VNxwx6gIvQeiBZtTZ 0yP300HkXJai5gugugxU9Nt0GnFd0giN0kzqnCARSkio4wFN3Li9lcW36DDgP5hqzZIV fY8g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=tSiANsE62ZgR+yigv2IvEWiUhOcWnyvXxuTcmIzCc90=; b=fWKJP1E3EdXjgi+6jpWqBkuemeBv9jmVhKK+fgGcSMctgqvi/lSSfm4EvkRp2rcXsw ChoP62bEErRIkdu8Nnsb1yIHpwYLlpMXH5Hg+/3ToAKdS1OGkDs4CYSp/DzFudXvJWnW PRv7ncKcs4y3fRzBoJkCbFEmJZjwtHnP/qhaMOHDMMr1ZMkpfwuTcE033FIsCpr7btfL UUDub4xi45ryMFknU5ekdmC6JjZdxVUdLAZkKFkryHalrtJ9PIoE4aa0zXoAer6TnrHk 6zM5ByME5/4rAY4ytlz1ExuOFFtmlG5qeiEi0gjXTnTlOVneVKgdd8nKExL7Cmj36qYS 6VfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lnAEvB+n; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 13-v6si5100606pge.159.2018.05.28.23.25.36; Mon, 28 May 2018 23:25:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lnAEvB+n; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754542AbeE2GZO (ORCPT + 99 others); Tue, 29 May 2018 02:25:14 -0400 Received: from mail-wr0-f193.google.com ([209.85.128.193]:36680 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751668AbeE2GZM (ORCPT ); Tue, 29 May 2018 02:25:12 -0400 Received: by mail-wr0-f193.google.com with SMTP id f16-v6so8066066wrm.3 for ; Mon, 28 May 2018 23:25:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=tSiANsE62ZgR+yigv2IvEWiUhOcWnyvXxuTcmIzCc90=; b=lnAEvB+nEYC8hhThLMdAZcDjAXZvUBx/tCl+3GqxtRvZ22UGDg+r96d91u844qk3k+ T/fevW3ASotCD8k6t05M1IYMpyAJPJqd1eQANShVr4Zu5cNH0FaTEANYUhehvV6BqWMT cV1lqRo98doRHP+OyVrFdjjadD6JZWpOrDgFbNShRpNPXPAY+UoqUHJKVKJL6e5F6qNJ yvHsZRfEEwdFmi90NKNo/yPfztHJ2CrtbD8MmSArneP3RDHBBDWGnB9eKVZIO3/9+eDk LeNI/YMH5FLJV5Yaod6s530sLN8n9fw/5TVkBup2YfcXIC7v7taKWOYGA3YmDisAMKYn XDTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=tSiANsE62ZgR+yigv2IvEWiUhOcWnyvXxuTcmIzCc90=; b=DCBCyPzPkosQWRJbu5eMZDb9DKDZiwhVasQ0aSePytziqolQg5/F/DnYOY4sDvBbOW QlZK7Sn/VdC8NdofE0i+Wve+WvBc2T5bW8rSnIllLqV6dbrRM02pzpH6AjdUng+3BLqd Ei+A12bo23s0qd3regwiGBzhD4UlUdT4hKNya24JNBL9eX3Yv1rZwx+pOzilqs+tqRPK D8vOJUQ4NIIvoIsqp87sEynrMKt82tOe6YQ+XuhAlUSmAeR6YMCh+fjPPbItSKpwWFQ8 MeXz96g1HmCd0hpZUQOr8vSy+UHtM57zbE2EycM78OehtrKo8ApQVTWlTJ35RLDXXGH4 GY/g== X-Gm-Message-State: ALKqPweUbzendLm7dYcouok9V4B63Pg/OZUURl4zD/62VMR9BAPQLHJh s9gz2r/ueVLdRufi8JPFty208n2j X-Received: by 2002:a19:e117:: with SMTP id y23-v6mr8496037lfg.9.1527575111625; Mon, 28 May 2018 23:25:11 -0700 (PDT) Received: from [10.17.182.9] (ll-52.209.223.85.sovam.net.ua. [85.223.209.52]) by smtp.gmail.com with ESMTPSA id p5-v6sm6284466ljh.3.2018.05.28.23.25.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 May 2018 23:25:10 -0700 (PDT) Subject: Re: [PATCH] drm: Fix possible race conditions while unplugging DRM device To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, airlied@linux.ie, daniel.vetter@intel.com, seanpaul@chromium.org, gustavo@padovan.org Cc: Oleksandr Andrushchenko , =?UTF-8?Q?Noralf_Tr=c3=b8nnes?= References: <20180522141304.18646-1-andr2000@gmail.com> From: Oleksandr Andrushchenko Message-ID: <226cb967-2464-767b-c051-95c120f6558a@gmail.com> Date: Tue, 29 May 2018 09:25:09 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180522141304.18646-1-andr2000@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ping On 05/22/2018 05:13 PM, Oleksandr Andrushchenko wrote: > From: Oleksandr Andrushchenko > > When unplugging a hotpluggable DRM device we first unregister it > with drm_dev_unregister and then set drm_device.unplugged flag which > is used to mark device critical sections with drm_dev_enter()/ > drm_dev_exit() preventing access to device resources that are not > available after the device is gone. > But drm_dev_unregister may lead to hotplug uevent(s) fired to > user-space on card and/or connector removal, thus making it possible > for user-space to try accessing a disconnected device. > > Fix this by first making sure device is properly marked as > disconnected and only then unregister it. > > Fixes: bee330f3d672 ("drm: Use srcu to protect drm_device.unplugged") > > Signed-off-by: Oleksandr Andrushchenko > Reported-by: Andrii Chepurnyi > Cc: "Noralf Trønnes" > --- > drivers/gpu/drm/drm_drv.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c > index b553a6f2ff0e..7af748ed1c58 100644 > --- a/drivers/gpu/drm/drm_drv.c > +++ b/drivers/gpu/drm/drm_drv.c > @@ -369,13 +369,6 @@ EXPORT_SYMBOL(drm_dev_exit); > */ > void drm_dev_unplug(struct drm_device *dev) > { > - drm_dev_unregister(dev); > - > - mutex_lock(&drm_global_mutex); > - if (dev->open_count == 0) > - drm_dev_put(dev); > - mutex_unlock(&drm_global_mutex); > - > /* > * After synchronizing any critical read section is guaranteed to see > * the new value of ->unplugged, and any critical section which might > @@ -384,6 +377,13 @@ void drm_dev_unplug(struct drm_device *dev) > */ > dev->unplugged = true; > synchronize_srcu(&drm_unplug_srcu); > + > + drm_dev_unregister(dev); > + > + mutex_lock(&drm_global_mutex); > + if (dev->open_count == 0) > + drm_dev_put(dev); > + mutex_unlock(&drm_global_mutex); > } > EXPORT_SYMBOL(drm_dev_unplug); >