Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3526028imu; Mon, 7 Jan 2019 05:06:21 -0800 (PST) X-Google-Smtp-Source: ALg8bN4TkI+ruqciJMVrnILd+HlPAQWHCyIStu0d4pfpdIwkfcU6NcPLEIB5qt1y/wqCK9eGIUYQ X-Received: by 2002:a63:4d:: with SMTP id 74mr11045434pga.248.1546866381685; Mon, 07 Jan 2019 05:06:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546866381; cv=none; d=google.com; s=arc-20160816; b=FMEUMOWuY+9oSRmMqZCagl1F8jo2WeCTMe+2EY8F6Nu4dJUBswWCqsGQpMcrvT02Pr EqVYB41lNXJAd6qqNXosYd0JADoIDaJRsvdvSYtQ+ULDu5oCc2Yh/jqlhvU/FKD4xc1N rwSIlSHiGgIbTkBICGL6g7dfH7Ib1JEgHgrdZ4aGlJMnE1zpnT8u/hD1kU6Ahj8gTtAm 4nekoMNQO4Gv+rTU8UsI98XtRxXfJSBwJJV3cU0yR0Wn/CSggK3cZElzmpDL6yW7zCGR HUKSCc8OtNI88dGcUHdfnHv/x6eUtWLUwvb/8rGnSashCt5n9SpcO1/Le+bM2ppTXJ8J jmUg== 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=A7ZeVITBy2GcXrpx/wkBf9Fzq33jZXnLdE/aSadygJc=; b=dggvQyragbmQF6C98b+SruSfo5V2Dz6aj3XraU3mpIsdyY0eT1iL07IX6JnIJLx4Kv 78DEdQBE7BbmsNpzij+ydq0yhBdc9H/W8ve9rz611Zp8TQknEytSyrzmGPAyd6m/ceUU bD7HClPvQflSrIlHgZ974gdpeWIksQl3pNv02+N73vx+QlYPIbwqTlC9Qbe9ysHdNMLX c3ZSKiMw+iOw4OKRq4o7ZEaoxB8yOJoKZEq6wS3+5Y4XGfTpUkgKdlm9J/LAxhi5FWGP PMpBjSBrc/dcix7mwE73+0JwZpokrx+bEvuj01JcnFwUutx+f6S4wGKyS1FVYxKuYNWW H0tg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=HUAFfxeR; 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 x64si64117533pfb.120.2019.01.07.05.06.06; Mon, 07 Jan 2019 05:06:21 -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=HUAFfxeR; 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 S1731145AbfAGNEH (ORCPT + 99 others); Mon, 7 Jan 2019 08:04:07 -0500 Received: from mail.kernel.org ([198.145.29.99]:51652 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731123AbfAGNED (ORCPT ); Mon, 7 Jan 2019 08:04:03 -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 5850C206BB; Mon, 7 Jan 2019 13:04:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546866242; bh=mZomK6BCGNMZvAVJX9eDxKIakGMRZaJ+7dEUZJOcwDw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=HUAFfxeRGzw1UU4+ZyHI1/0bP89pRtIyGJtlSFPjvvtXegVpG8VmBwgW2KdVFCtW5 k9PBYxWH8gCCK5j2tAjk8pt0WLM2ep9UnCDg8bDERirUAnSoFV16Bn5sSknFp+8+BN Qlv/4w0Qib9j/GhPCG6GgJbbjA5d2HBMLO0axyHM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Georgy A Bystrenin , Pavel Shilovsky , Steve French Subject: [PATCH 4.14 095/101] CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem Date: Mon, 7 Jan 2019 13:33:23 +0100 Message-Id: <20190107105338.002620728@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190107105330.372621917@linuxfoundation.org> References: <20190107105330.372621917@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.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Georgy A Bystrenin commit 9a596f5b39593414c0ec80f71b94a226286f084e upstream. While resolving a bug with locks on samba shares found a strange behavior. When a file locked by one node and we trying to lock it from another node it fail with errno 5 (EIO) but in that case errno must be set to (EACCES | EAGAIN). This isn't happening when we try to lock file second time on same node. In this case it returns EACCES as expected. Also this issue not reproduces when we use SMB1 protocol (vers=1.0 in mount options). Further investigation showed that the mapping from status_to_posix_error is different for SMB1 and SMB2+ implementations. For SMB1 mapping is [NT_STATUS_LOCK_NOT_GRANTED to ERRlock] (See fs/cifs/netmisc.c line 66) but for SMB2+ mapping is [STATUS_LOCK_NOT_GRANTED to -EIO] (see fs/cifs/smb2maperror.c line 383) Quick changes in SMB2+ mapping from EIO to EACCES has fixed issue. BUG: https://bugzilla.kernel.org/show_bug.cgi?id=201971 Signed-off-by: Georgy A Bystrenin Reviewed-by: Pavel Shilovsky CC: Stable Signed-off-by: Steve French Signed-off-by: Greg Kroah-Hartman --- fs/cifs/smb2maperror.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/fs/cifs/smb2maperror.c +++ b/fs/cifs/smb2maperror.c @@ -378,8 +378,8 @@ static const struct status_to_posix_erro {STATUS_NONEXISTENT_EA_ENTRY, -EIO, "STATUS_NONEXISTENT_EA_ENTRY"}, {STATUS_NO_EAS_ON_FILE, -ENODATA, "STATUS_NO_EAS_ON_FILE"}, {STATUS_EA_CORRUPT_ERROR, -EIO, "STATUS_EA_CORRUPT_ERROR"}, - {STATUS_FILE_LOCK_CONFLICT, -EIO, "STATUS_FILE_LOCK_CONFLICT"}, - {STATUS_LOCK_NOT_GRANTED, -EIO, "STATUS_LOCK_NOT_GRANTED"}, + {STATUS_FILE_LOCK_CONFLICT, -EACCES, "STATUS_FILE_LOCK_CONFLICT"}, + {STATUS_LOCK_NOT_GRANTED, -EACCES, "STATUS_LOCK_NOT_GRANTED"}, {STATUS_DELETE_PENDING, -ENOENT, "STATUS_DELETE_PENDING"}, {STATUS_CTL_FILE_NOT_SUPPORTED, -ENOSYS, "STATUS_CTL_FILE_NOT_SUPPORTED"},