Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp806727ybz; Wed, 15 Apr 2020 19:33:25 -0700 (PDT) X-Google-Smtp-Source: APiQypLzinm8QzthzjZs9CPOXG0iHXDYZ2S11WjPYJe4jd88zmKtSBhH3+dI3FAfGsVrN/f2oifc X-Received: by 2002:a17:906:1490:: with SMTP id x16mr7144009ejc.323.1587004405517; Wed, 15 Apr 2020 19:33:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587004405; cv=none; d=google.com; s=arc-20160816; b=Ene6JIiu0IGHkVd8b1zLr0OlGfImF/QBl8Zk2layMs9M49Rk6uR3nH+kFX0Tci0pkY Pjoh8Q16BjpdAr34wx7yzITy/k1ErJ+BE2RmfEpMLA2IzYa+cL2/dvWE4koxWJIjasUC 0e9CwmacKG68D6CyV0cE3UnC3JeITcXA0Xw4ZCFLSiK6nN8F7keKA++4c5oCGhf6bILq IPsfferxeozXpIRGExQQvdbDIEPzfewnz4K197W7EknzcD21uGuqUpR0jPnLgC0JptUZ ya1uNqjFv9B34niaFSHAn5+ClWBWbn7kyGLzKuWRcBtM/NsRtCLVJnaUpgPeqcNY7Z/h EtlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=MvV/kU/pFrjkbAJ+eW/cY6VL5dwLgz9Jc5F00dhkTB0=; b=ru1VMG2sJ26GPcMTkfFbf46dJx+uWVG4DtVULK7pNT3VbHpKafWZSKvkqghseze7A+ 5w5pzeU1DxkPSvwlCHzGV3ENcS38/GctD1e50bciaoo4OIaBLX2yd2OPg3O0d+WA2Ct7 +ANWLqyPBduRqZvc7LrPtmI9/ALlJm/hYm8mlSlMIYgm/pWqG/5lKGC5/lwHyZUiromx GCa00IreHoGxMKfW3gJ4dSiaqWFruD58a4PxTlK6X3yw1ID4FcbS7i8aJ/1XeOzpktE5 ubGSXc6mujLr3b0j+2qmRIxdCf4lIxas7ulQdfjwW+BJsoj1QkLtXKOto2JdY1Sw5+aQ HbvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TCFUfL8V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dk9si5420285edb.403.2020.04.15.19.33.01; Wed, 15 Apr 2020 19:33:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TCFUfL8V; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387984AbgDPCbu (ORCPT + 99 others); Wed, 15 Apr 2020 22:31:50 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:28242 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2387827AbgDPCbr (ORCPT ); Wed, 15 Apr 2020 22:31:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587004306; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MvV/kU/pFrjkbAJ+eW/cY6VL5dwLgz9Jc5F00dhkTB0=; b=TCFUfL8VmU4pgAuynaRGA1B4g6UyhBHNZmlDNyYyy5xBVfWe3tTEmo+tocerAxLTQjS8bH SKU1i1q9AfqKYV7eOwR/mmgRfYzXhdTz9amwyj9Sma6oLykAtcUPVhuLcou7FCEf/+Xoos 3F4kmaPu8Q/M6uuHv+rLNi1AYimrsoc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-458-fZPwCsSMMmSAl1giz5QxOw-1; Wed, 15 Apr 2020 22:31:42 -0400 X-MC-Unique: fZPwCsSMMmSAl1giz5QxOw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id ADBBC1005509; Thu, 16 Apr 2020 02:31:39 +0000 (UTC) Received: from T590 (ovpn-8-29.pek2.redhat.com [10.72.8.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 947DA272A1; Thu, 16 Apr 2020 02:31:27 +0000 (UTC) Date: Thu, 16 Apr 2020 10:31:22 +0800 From: Ming Lei To: Luis Chamberlain Cc: axboe@kernel.dk, viro@zeniv.linux.org.uk, bvanassche@acm.org, gregkh@linuxfoundation.org, rostedt@goodmis.org, mingo@redhat.com, jack@suse.cz, nstange@suse.de, akpm@linux-foundation.org, mhocko@suse.com, yukuai3@huawei.com, linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Omar Sandoval , Hannes Reinecke , Michal Hocko Subject: Re: [PATCH 3/5] blktrace: refcount the request_queue during ioctl Message-ID: <20200416023122.GB2717677@T590> References: <20200414041902.16769-1-mcgrof@kernel.org> <20200414041902.16769-4-mcgrof@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200414041902.16769-4-mcgrof@kernel.org> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 14, 2020 at 04:19:00AM +0000, Luis Chamberlain wrote: > Ensure that the request_queue is refcounted during its full > ioctl cycle. This avoids possible races against removal, given > blk_get_queue() also checks to ensure the queue is not dying. > > This small race is possible if you defer removal of the request_queue > and userspace fires off an ioctl for the device in the meantime. > > Cc: Bart Van Assche > Cc: Omar Sandoval > Cc: Hannes Reinecke > Cc: Nicolai Stange > Cc: Greg Kroah-Hartman > Cc: Michal Hocko > Cc: yu kuai > Reviewed-by: Bart Van Assche > Signed-off-by: Luis Chamberlain > --- > kernel/trace/blktrace.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c > index 15086227592f..17e144d15779 100644 > --- a/kernel/trace/blktrace.c > +++ b/kernel/trace/blktrace.c > @@ -701,6 +701,9 @@ int blk_trace_ioctl(struct block_device *bdev, unsigned cmd, char __user *arg) > if (!q) > return -ENXIO; > > + if (!blk_get_queue(q)) > + return -ENXIO; > + > mutex_lock(&q->blk_trace_mutex); > > switch (cmd) { > @@ -729,6 +732,9 @@ int blk_trace_ioctl(struct block_device *bdev, unsigned cmd, char __user *arg) > } > > mutex_unlock(&q->blk_trace_mutex); > + > + blk_put_queue(q); > + > return ret; > } Actually when bdev is opened, one extra refcount is held on gendisk, so gendisk won't go away. And __device_add_disk() does grab one extra refcount on request queue, so request queue shouldn't go away when ioctl is running. Can you describe a bit more what the issue is to be addressed by this patch? Thanks, Ming