Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3108804imu; Mon, 19 Nov 2018 10:44:28 -0800 (PST) X-Google-Smtp-Source: AJdET5fHD6iOxOD79AzRdmTkV8TVi4El1sggaFKv7qFaeW54UOvPjWex+6kF3UyfE+timdHMVkCN X-Received: by 2002:a17:902:a9:: with SMTP id a38-v6mr23660248pla.7.1542653068537; Mon, 19 Nov 2018 10:44:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542653068; cv=none; d=google.com; s=arc-20160816; b=i6PN08me0X2E2zhI6XI121vqIC+KjQ38R9R3gjxJycopbMsa1c5EkAllw7xEn686ij zbSZ2EHPzWWXmXF4VhMOQD3m0fRQlKrNVNLxSglhZDUVRDYOWUIR4mmd5GbHtIvjeE8+ BFCzCse2BoSKxxYi4VnziVDKhHwAe3X+QfcWXsdSc0MigD2ivjtDlBmBZVto21MgCsC3 myBj1KTIxqaDdIiyx9bi1Ezk3Nta2XZaMvsTHs8L8Y03hl+ijyliWtnzuPv1V7A1KgRD gThMdVxlvekhXt6CiRjBO/KCmtYmuCl01yDBN5JDxZV9MOlCF10VEhHwEpCjVnJ44VPk Wwtw== 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=6l6RfrFhmv/83pX5xtpGyPhB6pF8Lwn9ufcPhBE1MO8=; b=BLUKYMBQkFp3n+ylPHgEoNPlini/jOJJEbOq+VOTuRrSEJa4GP2yjSQHP31mpq3Ev4 x/k9bN34olw6FdWaj2vY4dR17dAl4hYH9kAxMFoRmUexsAfz72xZFHWrEenuNleJ4qZU uBDc1dpxL4XnWnFEa50vHK2U5zK9NTssrGjVse7QazVM2+khE8nS7DaEZUb8+OwAaioN Ec3RjcOX0vpXcIjMZyV0nhtV6o7wKz0XmYR/QKYcFdYnOXfcoH9l3XJ13q1FVwN7bjvs 37TrzCB0fkyGjg4tmTjWQ/E5uDv5bL9Ah4oU6Q31wPSZ81Bz38RMetSMOuY6n5dxNL1j +XFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="Ke/0/CBM"; 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 2si4370821pgj.104.2018.11.19.10.44.13; Mon, 19 Nov 2018 10:44:28 -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="Ke/0/CBM"; 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 S1732140AbeKTDBX (ORCPT + 99 others); Mon, 19 Nov 2018 22:01:23 -0500 Received: from mail.kernel.org ([198.145.29.99]:33220 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730931AbeKTDBV (ORCPT ); Mon, 19 Nov 2018 22:01:21 -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 68AB9206BA; Mon, 19 Nov 2018 16:37:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1542645432; bh=oHZ+lvbQWIkgvMN6WuljezjmZ87zrkHQyfEyCdXM5Ec=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ke/0/CBM4U0eJxEoPxnfiOGf1jg5u9fKhv5JbFdcSpHzr54adgbu8bAaKNJw8Wk1N GWWH68G76HCylXZ8283+JM2P8CIBgdyFkyet0DXMXJ1mRPvtRv6buu7xjaCU0/kHHC gAmu2PpTBmyQBP6owcbr/FYJm+xmqfKrbyb1iTlg= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miklos Szeredi Subject: [PATCH 4.19 161/205] fuse: fix possibly missed wake-up after abort Date: Mon, 19 Nov 2018 17:27:48 +0100 Message-Id: <20181119162639.608639347@linuxfoundation.org> X-Mailer: git-send-email 2.19.1 In-Reply-To: <20181119162616.586062722@linuxfoundation.org> References: <20181119162616.586062722@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review 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.19-stable review patch. If anyone has any objections, please let me know. ------------------ From: Miklos Szeredi commit 2d84a2d19b6150c6dbac1e6ebad9c82e4c123772 upstream. In current fuse_drop_waiting() implementation it's possible that fuse_wait_aborted() will not be woken up in the unlikely case that fuse_abort_conn() + fuse_wait_aborted() runs in between checking fc->connected and calling atomic_dec(&fc->num_waiting). Do the atomic_dec_and_test() unconditionally, which also provides the necessary barrier against reordering with the fc->connected check. The explicit smp_mb() in fuse_wait_aborted() is not actually needed, since the spin_unlock() in fuse_abort_conn() provides the necessary RELEASE barrier after resetting fc->connected. However, this is not a performance sensitive path, and adding the explicit barrier makes it easier to document. Signed-off-by: Miklos Szeredi Fixes: b8f95e5d13f5 ("fuse: umount should wait for all requests") Cc: #v4.19 Signed-off-by: Greg Kroah-Hartman --- fs/fuse/dev.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) --- a/fs/fuse/dev.c +++ b/fs/fuse/dev.c @@ -129,9 +129,13 @@ static bool fuse_block_alloc(struct fuse static void fuse_drop_waiting(struct fuse_conn *fc) { - if (fc->connected) { - atomic_dec(&fc->num_waiting); - } else if (atomic_dec_and_test(&fc->num_waiting)) { + /* + * lockess check of fc->connected is okay, because atomic_dec_and_test() + * provides a memory barrier mached with the one in fuse_wait_aborted() + * to ensure no wake-up is missed. + */ + if (atomic_dec_and_test(&fc->num_waiting) && + !READ_ONCE(fc->connected)) { /* wake up aborters */ wake_up_all(&fc->blocked_waitq); } @@ -2167,6 +2171,8 @@ EXPORT_SYMBOL_GPL(fuse_abort_conn); void fuse_wait_aborted(struct fuse_conn *fc) { + /* matches implicit memory barrier in fuse_drop_waiting() */ + smp_mb(); wait_event(fc->blocked_waitq, atomic_read(&fc->num_waiting) == 0); }