Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3008480imu; Mon, 19 Nov 2018 09:17:23 -0800 (PST) X-Google-Smtp-Source: AJdET5eba4p1utks5Qf0S9rfXZHhLoluCuUuvYBIYA3Osamn7nBWrPLo70CLjKVGbndowA92XmCG X-Received: by 2002:a63:1412:: with SMTP id u18mr20556667pgl.247.1542647843361; Mon, 19 Nov 2018 09:17:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542647843; cv=none; d=google.com; s=arc-20160816; b=OcVNekgG1ESmm08ASOFZo9N/GOv095c9a7ERey+ISLC54uvLvLc08RH/LpaBgpF3IV oaXsuyL8IrbvtRMnTC0hIuYGrSBxyvfkuFHHA3ZSXMhvkIQ0/+P990xxI/E0U85vpOJh hzz7CApU695X7wh/LKALXC3vKf8ayJr/aDanThYhs66WOHwLUg3Kc/qUhZJExNfxVm+T 0cgQ7d14BnD3IscuXoc0VDDhxLU3cRC/QxySDP7DkE1Esq5T+NokkGBRhU7CsoVkwRla y1dtHuWPVieQdKA1MT0W5u1oaWc4TGUccu8e7MSTXdkxZSoNQ/uThmCboqWvdmpLp4sL jB8w== 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=qa18aiupA9Rf/gu3wzpaqCrshWiqau7G0gpGsObOTSA=; b=FcIjHAaPa+7pCF17CsBn1DS6oKa+pPQbXAuM0Cw6JS8p/JgaL9Kb9Exe2GZWY5la/U ny5aGkKlhK0kKg/MLcWutybdk2/kKHvFk4Ne/iJ0gN2Lk8FKWrZZw1qYfQOew3WaMMsM Y+hq5H/csRrFH/tyDp4WL4dawuFZkcF7Il+TAXeNueKITo5/JriXs4czyKtkapTrwR8n ProUwPB3jqqxWFOAd3PoRdn6buDp6JRKspUj2mC90jh1GnjRGnBWo/fXDr3dEhm96bMa QZGnXTqWgj3TspchGt4/6BFrWnfAx+2o4Sgd/Bl00xJM1Q9oJd9vHVVMt4L/JLDwByfM K6Hg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=RXc0EjXz; 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 i13si40603077pgj.199.2018.11.19.09.16.56; Mon, 19 Nov 2018 09:17:23 -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=RXc0EjXz; 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 S2406156AbeKTD1Y (ORCPT + 99 others); Mon, 19 Nov 2018 22:27:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:41338 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405145AbeKTD1X (ORCPT ); Mon, 19 Nov 2018 22:27:23 -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 964372151B; Mon, 19 Nov 2018 17:03:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1542646986; bh=BU5RnYl+VNO0v+iZfw3PcRwQR0Ffa6hOdXXSJMESpnA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=RXc0EjXzKuEKAY6rwlvG5fKi3wfX00o0yvcWv7MHa3yzcCqoE7R+gqs09NfbjxyKP PH0gIZ0yPccR9U2d/7jMTRgMXn60sAOF7vS1p0zPLr6GDNZ0ailxkuQNlCTCOpK38e miB1VWNBNjSbsHaqAWg2fOeQbRfk9WMV+L/b7Rss= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miklos Szeredi Subject: [PATCH 4.4 154/160] fuse: fix leaked notify reply Date: Mon, 19 Nov 2018 17:29:53 +0100 Message-Id: <20181119162644.270822153@linuxfoundation.org> X-Mailer: git-send-email 2.19.1 In-Reply-To: <20181119162630.031306128@linuxfoundation.org> References: <20181119162630.031306128@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.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Miklos Szeredi commit 7fabaf303458fcabb694999d6fa772cc13d4e217 upstream. fuse_request_send_notify_reply() may fail if the connection was reset for some reason (e.g. fs was unmounted). Don't leak request reference in this case. Besides leaking memory, this resulted in fc->num_waiting not being decremented and hence fuse_wait_aborted() left in a hanging and unkillable state. Fixes: 2d45ba381a74 ("fuse: add retrieve request") Fixes: b8f95e5d13f5 ("fuse: umount should wait for all requests") Reported-and-tested-by: syzbot+6339eda9cb4ebbc4c37b@syzkaller.appspotmail.com Signed-off-by: Miklos Szeredi Cc: #v2.6.36 Signed-off-by: Greg Kroah-Hartman --- fs/fuse/dev.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- a/fs/fuse/dev.c +++ b/fs/fuse/dev.c @@ -1771,8 +1771,10 @@ static int fuse_retrieve(struct fuse_con req->in.args[1].size = total_len; err = fuse_request_send_notify_reply(fc, req, outarg->notify_unique); - if (err) + if (err) { fuse_retrieve_end(fc, req); + fuse_put_request(fc, req); + } return err; }