Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5167938imu; Tue, 15 Jan 2019 12:26:45 -0800 (PST) X-Google-Smtp-Source: ALg8bN5t5iU3Pz1zVwKmbM4Ibz/5txoEjZI6TMW1hunPwgguw7pDUSINozpEbRK6Oay/1mYJPYKg X-Received: by 2002:a63:4926:: with SMTP id w38mr5202297pga.353.1547584005087; Tue, 15 Jan 2019 12:26:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547584005; cv=none; d=google.com; s=arc-20160816; b=aOAXX9PD89fyIov1AKLyyZQl119v0w0luYRo/cRRg2Ux0c7ND1GbsngFUSiIihi8o9 8kbHnhaY5W6FSBbgcMnNl93cIBZ6KtzWposTctLySIrLI7pkNNViZlxgSMf0Yzfn1ZuW q4+Mb6yyoC9pvTYhHgtnWW8Lk8fAajtGrjn/Bg1hpQOeoz2dh8eg7+ANVrY5u1z4amY2 592yayktXJ+8m6tRXxRoBXTFbut65z7kgTV03BMtHuHKbdKvp8GTF8c93rlsNcEEHbiy FtK+MM/E5PvfpFoFCcI3yC3tnVTPH2LrYWZ2kz0ivjEtfZmTVrF49tGvgGF3FMkXwobX CnZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=KS79v5Q8nVH15EKtjZo1kSkWX11ClVj1YrbteKUTd4I=; b=hgScJuIPaoN/D8m/jakAyyOhKJda3LOB8q3lICxnxKvdjWntgwV9m+HKUgw8TaC5vC Qi2tEF4xhupHQkvS9o7r1h/LCfda0byvOGiakN7se9vbFeFgwR+kc5UUkwEsMJveJLOB DlNSx8sOrhcjAlI6+QpWLEIU1QGz+hwOYyVQ6KVEObIPSp+527Slougglt3+N+V7B07b bRUFGVuW41mzXqLj7Oa3AVvgUKFWRXsAVcPrzeD53GfpNMlvrkDffFpiBFvJozyd4i53 LMWLBuki+GaI6fvqN+FiHZC5npWTishRMOwvu2viOKtb5+In/jTrWHmvRLlXluIqWiTB OF1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=183lkRyy; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m63si4264937pld.132.2019.01.15.12.26.29; Tue, 15 Jan 2019 12:26:45 -0800 (PST) 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=@kernel.org header.s=default header.b=183lkRyy; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732338AbfAOQjX (ORCPT + 99 others); Tue, 15 Jan 2019 11:39:23 -0500 Received: from mail.kernel.org ([198.145.29.99]:55488 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732328AbfAOQjU (ORCPT ); Tue, 15 Jan 2019 11:39:20 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BEEB42054F; Tue, 15 Jan 2019 16:39:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547570360; bh=359QpR1mmhGEUrtIHYPWtP9AsF3yyR3keLslmVQUVcE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=183lkRyyiVB93RzZLgQK1OBjRrnmvJ068Odp2SN+EESqo/QZ2WTaC3TGxKgDPdNvg DOC0HzPxBh70G9kEerMV7whVsKex8u14wjYq6nIWmNqyYnzd4pJe6d2woi2iHHZaWd dQ71I0HQxtu60+YOsDgUE+Fm71+3/Fhw0zhNcHeA= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Ilya Dryomov , Dongsheng Yang Subject: [PATCH 4.9 12/16] rbd: dont return 0 on unmap if RBD_DEV_FLAG_REMOVING is set Date: Tue, 15 Jan 2019 17:35:55 +0100 Message-Id: <20190115154849.555626084@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190115154848.164648613@linuxfoundation.org> References: <20190115154848.164648613@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Ilya Dryomov commit 85f5a4d666fd9be73856ed16bb36c5af5b406b29 upstream. There is a window between when RBD_DEV_FLAG_REMOVING is set and when the device is removed from rbd_dev_list. During this window, we set "already" and return 0. Returning 0 from write(2) can confuse userspace tools because 0 indicates that nothing was written. In particular, "rbd unmap" will retry the write multiple times a second: 10:28:05.463299 write(4, "0", 1) = 0 10:28:05.463509 write(4, "0", 1) = 0 10:28:05.463720 write(4, "0", 1) = 0 10:28:05.463942 write(4, "0", 1) = 0 10:28:05.464155 write(4, "0", 1) = 0 Cc: stable@vger.kernel.org Signed-off-by: Ilya Dryomov Tested-by: Dongsheng Yang Signed-off-by: Greg Kroah-Hartman --- drivers/block/rbd.c | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) --- a/drivers/block/rbd.c +++ b/drivers/block/rbd.c @@ -6346,7 +6346,6 @@ static ssize_t do_rbd_remove(struct bus_ struct list_head *tmp; int dev_id; char opt_buf[6]; - bool already = false; bool force = false; int ret; @@ -6379,13 +6378,13 @@ static ssize_t do_rbd_remove(struct bus_ spin_lock_irq(&rbd_dev->lock); if (rbd_dev->open_count && !force) ret = -EBUSY; - else - already = test_and_set_bit(RBD_DEV_FLAG_REMOVING, - &rbd_dev->flags); + else if (test_and_set_bit(RBD_DEV_FLAG_REMOVING, + &rbd_dev->flags)) + ret = -EINPROGRESS; spin_unlock_irq(&rbd_dev->lock); } spin_unlock(&rbd_dev_list_lock); - if (ret < 0 || already) + if (ret) return ret; if (force) {