Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2548587pxj; Mon, 10 May 2021 05:41:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyaDEr61yEN+DQcIv1z6ZLClZP2I+t4L5THFLPQU0IW5WKCn6R620CLVip3E86TG9JxRlds X-Received: by 2002:a05:6402:2714:: with SMTP id y20mr28974932edd.348.1620650500920; Mon, 10 May 2021 05:41:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620650500; cv=none; d=google.com; s=arc-20160816; b=Nn/mU3lmr8RrwLx09uBP0P+CVn84YLMg2pDZH8aVZG2cHL+aqnez9y4gOBXY3+LiWH 92v18JPs3UqQayLER1DFGs/KfeihOxqufMF7Z8sYpoWSHdD1oRHqgeQJ1bIK7/rsPuQG GrK3+q1xZvCc1B3G3k3fgnJskVQP1eex3BxKgcRj510KWXRmtenwiGwUWBd+Z1HJNbCE wXOfrMK3c8My5sAmMUgNvcT+fvSUszQIssMBhEP6Z/kn6iCgTw7Bc0K6oVbbYhzEJNpg YenhZSRV9DM5AKAwkWVZnycp4waSrwDh4cftn+cla5WvV3qKQP/93OSrWMUOphF2JMH8 K7kg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=Z473Wdjkkx5pt9WEtbr7PtBRjzPcGa558YtXGvnsdEg=; b=J3X4zfspMT+eADYLPVKBEUrdVMOAXKFApaL6z6ra2nigLakVkxCKPDU4FSWTbuswA1 xUGpfrgktkTTe+0X4bSNNawJGKWOMpDLsBj/Zbwkc6CcMevkTRWSqZkjcCvxohFVentp 0ekRD8qetp/QKiV23Gj6ZJnNBvIXtLMqcsKvNEUzTpMl4Uv01ewKHMq55+T7MBH040gA Y5HbZtehoonaWG7PYtV9VCfs9Aqh8EmhJu0UCOR81o1ZLYrmavxiucfHxQ5oG/xD/NEU qe1VxuQjm2xM7OweJWITz6MV/UicphcgCpXVVaP+N395AxiWvAgPvs7s2Vq+rQNEbO39 It+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=WjylKRAC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 8si16193934ejx.447.2021.05.10.05.41.17; Mon, 10 May 2021 05:41:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=WjylKRAC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347571AbhEJMgW (ORCPT + 99 others); Mon, 10 May 2021 08:36:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:60380 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233638AbhEJLOP (ORCPT ); Mon, 10 May 2021 07:14:15 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id ED8366101D; Mon, 10 May 2021 11:10:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620645046; bh=dhcHTDIdSmLd56jCrErKTAtg111bdBF2obbT9o8WXWs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=WjylKRACfvA6SPr1yIwUrBb1KymmIP+oFWQGmblN7t7cpU6QFkFk8faULXtOrbJ+5 A1Pj7EtyKVIrBtaY8YnOuLOGdFZciJ3EbwCK3IR2IUsnvbGMi7eQ8wJpSZTY1yy4JE TVuW7ot5bm0pqFQILF7OMSVw1WowcW6z9CRQMyww= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Tom Talpey , Shyam Prasad N , Steve French Subject: [PATCH 5.12 329/384] smb3: when mounting with multichannel include it in requested capabilities Date: Mon, 10 May 2021 12:21:58 +0200 Message-Id: <20210510102025.641128516@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210510102014.849075526@linuxfoundation.org> References: <20210510102014.849075526@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Steve French commit 679971e7213174efb56abc8fab1299d0a88db0e8 upstream. In the SMB3/SMB3.1.1 negotiate protocol request, we are supposed to advertise CAP_MULTICHANNEL capability when establishing multiple channels has been requested by the user doing the mount. See MS-SMB2 sections 2.2.3 and 3.2.5.2 Without setting it there is some risk that multichannel could fail if the server interpreted the field strictly. Reviewed-By: Tom Talpey Reviewed-by: Shyam Prasad N Cc: # v5.8+ Signed-off-by: Steve French Signed-off-by: Greg Kroah-Hartman --- fs/cifs/smb2pdu.c | 5 +++++ 1 file changed, 5 insertions(+) --- a/fs/cifs/smb2pdu.c +++ b/fs/cifs/smb2pdu.c @@ -841,6 +841,8 @@ SMB2_negotiate(const unsigned int xid, s req->SecurityMode = 0; req->Capabilities = cpu_to_le32(server->vals->req_capabilities); + if (ses->chan_max > 1) + req->Capabilities |= cpu_to_le32(SMB2_GLOBAL_CAP_MULTI_CHANNEL); /* ClientGUID must be zero for SMB2.02 dialect */ if (server->vals->protocol_id == SMB20_PROT_ID) @@ -1032,6 +1034,9 @@ int smb3_validate_negotiate(const unsign pneg_inbuf->Capabilities = cpu_to_le32(server->vals->req_capabilities); + if (tcon->ses->chan_max > 1) + pneg_inbuf->Capabilities |= cpu_to_le32(SMB2_GLOBAL_CAP_MULTI_CHANNEL); + memcpy(pneg_inbuf->Guid, server->client_guid, SMB2_CLIENT_GUID_SIZE);