Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp625350imu; Fri, 11 Jan 2019 06:24:16 -0800 (PST) X-Google-Smtp-Source: ALg8bN5qoEPHufHtaflqrhh6uUevUjMsxFcyp9IMK2gO9Yp9/rloOnliy+C7ZI+WfsBCriJmtkzI X-Received: by 2002:a17:902:9691:: with SMTP id n17mr15260082plp.9.1547216656851; Fri, 11 Jan 2019 06:24:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547216656; cv=none; d=google.com; s=arc-20160816; b=piOO29w+NVex0vePZuX/oItSZx0GY6RP4qziCEjVESijMq5TZ7C4FSq5SG/ifSZmyF MUp2cIVQh7haW3fCp1dtrZSNjMPPJuLsPSNSDgbOqIDJhHXc+qeq6TgxTS9paeubVSPx SzYWLbNWvDs4TCK9lLKaioc73EbAUEBW7O7KhRR6f1DKDMVV39EL7V2jICqVKDeln0ny ATt2ELn+vbk0F3iTMsHm8enQH2dMO1IhMR6qjean8MjMpg6GFtxVnuWg6UbFFhrA4y3t RMKPkJCbG+yOATcMaE+RvSqhCbDDIQ/TPG2P90u6u1KRoVd60QUXTfUUc5LjuALKOpKR ijoA== 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=JEsP1kM/rqBdnFSFTs/3cfiyXZFZs5nad70bWHT+Q/k=; b=elZwZ7R9N/uHJCQO9v0cxAwP2kn7l5rhYAuqCQ8pURe4dT/OHxrF3Uy94SVyO2S2uw whaMcg6py/U5SxW6kFzQ/XkIYWgwpqNCyM5UGqEejxXSL55lNjPcGHpvDpJXj3bCWE3z F2rLrDbKGNeGX23YxjNB0jqCREfMsBOblvNDygD7xCMnakjFZhvChYwgNDUjbPS27Sot j/DlcChV5vsqUSScHlmzbwaWgFPCBhjATcOZ47Gv1OtaTIAf3ACD0VlCqYmtyrQ1dxtz jb4rMzwP66zyEoSLXtV8VML3Cuu9CjwLGNN07txqDJaMsA4Sk92g3zC/03nZeT4slkDs TLdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=mXjXbFWt; 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 y18si17793791plp.269.2019.01.11.06.24.01; Fri, 11 Jan 2019 06:24:16 -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=mXjXbFWt; 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 S1733286AbfAKOPW (ORCPT + 99 others); Fri, 11 Jan 2019 09:15:22 -0500 Received: from mail.kernel.org ([198.145.29.99]:59476 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733261AbfAKOPV (ORCPT ); Fri, 11 Jan 2019 09:15: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 58145217D6; Fri, 11 Jan 2019 14:15:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547216120; bh=zdwY2VuX+lZelimmzqF3jbKBjTmH3CMzaPX4UXxK/Jc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mXjXbFWt/9sTHmeTwuEl2EP28qIiBzwpZ29YNS0jOH7rl0I9rwYsiR4gtusGqP3Oy BpF6Vc8StbhIEYgI9XiB4da/IBGC8Sh+ni5r1sDq2CJBc7+rMM1azEcxhhECGjZ3b+ +mRsECuoeh/wVHgBVwaKGr6Lhvx6Of8bD5AcA8pQ= 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 3.18 30/47] CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem Date: Fri, 11 Jan 2019 15:08:15 +0100 Message-Id: <20190111130959.957921641@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190111130956.170952125@linuxfoundation.org> References: <20190111130956.170952125@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 3.18-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 @@ -377,8 +377,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"},