Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2984679imu; Sun, 9 Dec 2018 14:18:09 -0800 (PST) X-Google-Smtp-Source: AFSGD/Ub2XQisSO9XUH0x4K661lvvu3cZ/m1KzpPCeychEOqPrp7PsqQ6nvqtwR1qTkZnbba/FaP X-Received: by 2002:a62:7c47:: with SMTP id x68mr10189679pfc.209.1544393889559; Sun, 09 Dec 2018 14:18:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544393889; cv=none; d=google.com; s=arc-20160816; b=n7ixCFuSt+LCuoTQv6qDo+t5XI2LFa5Upt4sIGkLVhMEJu7pnvceoFs8k+uCIMpJf8 tvDlIB/jJHwbDpZ2JzaiLrLumKOgeKqnR4l+mJXDPbnAzvm1jZGP4ARHSasQWBuskBYJ 5FQgWzX1FPXkQ48qAu9s6Mq+uluFfDBZrTYWyfOCHfdErSrfLI+soWJfqy5UKpc6uS0X 9u/xleDQeFsS3qjxiuFOAVDMelj21m7Ggq155qLXpuAfA1NRCbpQ4MR0KkiztNsLfVEB lBqSyTzXlzd/jAJF/fCQHtuD9rQxDaZI+K94x8807n6yIyf0Ebfv2/jTd0KR2wgUb9OI My9w== 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:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=DEYznMQ7NZRk8yQa8INCenKy1sZo//792GGMxd9+VJ8=; b=hT6JrR8a9qVLtc5/nPymP2CBLXfnU5xtwFg/bQlIgbjOryjUR5yHIIzIugvdlWw5d2 lXzHCP6WSLMpmILwdgS5n10z1Sz0CBM823DQYpX1AasTYbcwGEDGcaZKf3ERYoHAheoP c1UMVtwzT6uLqOUbeSOi2WMzYT9F1SrOsHNYF1dvMS9jS/GqHIFDDtdgVcan6/KV7qrM ohdsbcK7zD7mFgPq7oc4ByMCDT9gYOhaj7a4M+GlAInA5cERGb/VOukV1LqPxtJeyHKQ PHUuCezo/6MkHxmJcqr5MaLScyhQtr7r6HrhsQJ6rKMTPttBjOFai2MrRMfDnrkflXp+ t2YA== ARC-Authentication-Results: i=1; mx.google.com; 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 z143si9495956pfc.97.2018.12.09.14.17.46; Sun, 09 Dec 2018 14:18:09 -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; 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 S1728557AbeLIWPP (ORCPT + 99 others); Sun, 9 Dec 2018 17:15:15 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:38164 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727187AbeLIWPN (ORCPT ); Sun, 9 Dec 2018 17:15:13 -0500 Received: from pub.yeoldevic.com ([81.174.156.145] helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gW73F-0002iZ-Ke; Sun, 09 Dec 2018 21:55:49 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gW72d-0003Nh-5k; Sun, 09 Dec 2018 21:55:11 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Dominique Martinet" , "Eric Van Hensbergen" , "Ron Minnich" , "Latchesar Ionkov" , "piaojun" Date: Sun, 09 Dec 2018 21:50:33 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 130/328] fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr failed In-Reply-To: X-SA-Exim-Connect-IP: 81.174.156.145 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.62-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: piaojun commit 3111784bee81591ea2815011688d28b65df03627 upstream. In my testing, v9fs_fid_xattr_set will return successfully even if the backend ext4 filesystem has no space to store xattr key-value. That will cause inconsistent behavior between front end and back end. The reason is that lsetxattr will be triggered by p9_client_clunk, and unfortunately we did not catch the error. This patch will catch the error to notify upper caller. p9_client_clunk (in 9p) p9_client_rpc(clnt, P9_TCLUNK, "d", fid->fid); v9fs_clunk (in qemu) put_fid free_fid v9fs_xattr_fid_clunk v9fs_co_lsetxattr s->ops->lsetxattr ext4_xattr_user_set (in host ext4 filesystem) Link: http://lkml.kernel.org/r/5B57EACC.2060900@huawei.com Signed-off-by: Jun Piao Cc: Eric Van Hensbergen Cc: Ron Minnich Cc: Latchesar Ionkov Cc: Andrew Morton Signed-off-by: Dominique Martinet [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben Hutchings --- fs/9p/xattr.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) --- a/fs/9p/xattr.c +++ b/fs/9p/xattr.c @@ -121,7 +121,7 @@ int v9fs_fid_xattr_set(struct p9_fid *fi const void *value, size_t value_len, int flags) { u64 offset = 0; - int retval, msize, write_count; + int retval, err, msize, write_count; p9_debug(P9_DEBUG_VFS, "name = %s value_len = %zu flags = %d\n", name, value_len, flags); @@ -158,7 +158,9 @@ int v9fs_fid_xattr_set(struct p9_fid *fi } retval = 0; err: - p9_client_clunk(fid); + err = p9_client_clunk(fid); + if (!retval && err) + retval = err; return retval; }