Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1937249ybb; Sun, 29 Mar 2020 17:42:47 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvNptz5weh3FkHkv6ix4u8wV6AyO9ta/RZr/XW4pC6hQ7BZGsrtX2SWdbXd/hZrStMQXSN2 X-Received: by 2002:aca:5444:: with SMTP id i65mr5769207oib.101.1585528967795; Sun, 29 Mar 2020 17:42:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585528967; cv=none; d=google.com; s=arc-20160816; b=j1WYbKCgsOMgzBCdNkwJjBYKmgLaLfF/HWaAeHoxrHPIHKsmTHWRmpX/THDv1k4nXX p1HX1lLI64XQ9nB/63LXZ3LZIZ1arri62fWOZ4Eaf9WkT5uh6SagfD+c1A3oevjWAzCq AMyXDBJe78GEafmPpEbLGqbqEE6DUl+jjHxU3y4ispC7lGRC/V98bwNJE1DR5JGXoZIY gHM3KB5jBA4TPQ0D2OIEzRohHCInsU5l+ttuZe82ytoXS45Z9vZSAVhLmS1FWh207/wI yNDC92FuVJwT2NhemieiIw4t9BGB0W3Cnh791uBGu6MqQ6lg7OiwqT68Ep7qLKFLlpf6 YyGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:subject:cc:to :from:date:dkim-signature; bh=D4RPpTzk3HeWktWqh7BHNzEQj1l6augozWyDD564Gcs=; b=SaFGE3A4duYgOlqiRTi6HyX2grNxiBZnaqMB0kZfTs4u/I0iO7apVqmUhNXX6rCYqG C74z9GGBuTony8NFbJIYCjlN//5wLSIGPikpCrLYgV41+eVnJgsS2v8uaW1vMyvOv6OR ieRLjY3RSyj6/w4mxl4OSVGfex8Pj6MtnEqc+Iq2yQCvp0LsY8bZLkaYlCzBCARePlhf 7tMW9KPj/VjTV4iAjRV8di8OfjYx/29Yi5EkEf694dGUzt6wWWDnNQLuilWNOM48+zGb e4mtari2Jj6FzNJqsM6B4iWy+CkntOQop250Sj4kJ9zhuKDIpqgzQ6vdKPD7RoZtG/Rf jc7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=FWuUrmSw; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-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 x14si5553050otq.104.2020.03.29.17.42.23; Sun, 29 Mar 2020 17:42:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-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=@canb.auug.org.au header.s=201702 header.b=FWuUrmSw; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727755AbgC3AmQ (ORCPT + 99 others); Sun, 29 Mar 2020 20:42:16 -0400 Received: from ozlabs.org ([203.11.71.1]:36583 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727612AbgC3AmP (ORCPT ); Sun, 29 Mar 2020 20:42:15 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 48rDDz6MhVz9sPR; Mon, 30 Mar 2020 11:42:11 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1585528933; bh=B8g4PRJs5T7Ukzd8/GATXCt5GgL5C9WTKDYNobskixI=; h=Date:From:To:Cc:Subject:From; b=FWuUrmSwHX8w33pVQE9Y7fCySl2ycaPHMXPTPSvXApgtRJY+gZ8NAYSy2FLeD6v+R qiSRX6HB4u8bjYj/XDyj1MXHVco03AsqT9C/SQNPiE4n12wnUUu7kdfnPfV2tRtOa4 b+lBTzSLhwYdiCTKLIJ//ZIWrW9ZD+v4JHwlRj9vnMPRliFNCc9uJNaeHD8bmiNdA/ SjhKe5rx2B9FkXCpvLvIYzwaa6LC7Jf4D2H9xGMUOw3VB+6FhkA+mlXjvDgM1RDqLJ tJ1yutxNGupoD+F9xe4soswNhcOb+ZB0GccMSyEUVxY0AVBva3Mss6xb24zS8n9WvU CfA+L6bbFygQQ== Date: Mon, 30 Mar 2020 11:42:09 +1100 From: Stephen Rothwell To: Herbert Xu , Linux Crypto List , David Miller , Networking Cc: Linux Next Mailing List , Linux Kernel Mailing List , Rohit Maheshwari , Ayush Sawal Subject: linux-next: manual merge of the crypto tree with the net-next tree Message-ID: <20200330114209.1c7d5d11@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/qU/dK2yDyZMdgSQ7Jl4PJ7B"; protocol="application/pgp-signature"; micalg=pgp-sha256 Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org --Sig_/qU/dK2yDyZMdgSQ7Jl4PJ7B Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi all, Today's linux-next merge of the crypto tree got a conflict in: drivers/crypto/chelsio/chcr_core.c between commit: 34aba2c45024 ("cxgb4/chcr : Register to tls add and del callback") from the net-next tree and commit: 53351bb96b6b ("crypto: chelsio/chcr - Fixes a deadlock between rtnl_lock = and uld_mutex") from the crypto tree. I fixed it up (see below) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. --=20 Cheers, Stephen Rothwell diff --cc drivers/crypto/chelsio/chcr_core.c index 0015810214a9,7e24c4881c34..000000000000 --- a/drivers/crypto/chelsio/chcr_core.c +++ b/drivers/crypto/chelsio/chcr_core.c @@@ -35,12 -35,12 +35,16 @@@ static int chcr_uld_state_change(void * =20 static chcr_handler_func work_handlers[NUM_CPL_CMDS] =3D { [CPL_FW6_PLD] =3D cpl_fw6_pld_handler, +#ifdef CONFIG_CHELSIO_TLS_DEVICE + [CPL_ACT_OPEN_RPL] =3D chcr_ktls_cpl_act_open_rpl, + [CPL_SET_TCB_RPL] =3D chcr_ktls_cpl_set_tcb_rpl, +#endif }; =20 + #ifdef CONFIG_CHELSIO_IPSEC_INLINE + static void update_netdev_features(void); + #endif /* CONFIG_CHELSIO_IPSEC_INLINE */ +=20 static struct cxgb4_uld_info chcr_uld_info =3D { .name =3D DRV_MODULE_NAME, .nrxq =3D MAX_ULD_QSETS, @@@ -204,15 -204,6 +207,11 @@@ static void *chcr_uld_add(const struct=20 } u_ctx->lldi =3D *lld; chcr_dev_init(u_ctx); - #ifdef CONFIG_CHELSIO_IPSEC_INLINE - if (lld->crypto & ULP_CRYPTO_IPSEC_INLINE) - chcr_add_xfrmops(lld); - #endif /* CONFIG_CHELSIO_IPSEC_INLINE */ + +#ifdef CONFIG_CHELSIO_TLS_DEVICE + if (lld->ulp_crypto & ULP_CRYPTO_KTLS_INLINE) + chcr_enable_ktls(padap(&u_ctx->dev)); +#endif out: return u_ctx; } --Sig_/qU/dK2yDyZMdgSQ7Jl4PJ7B Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl6BQGEACgkQAVBC80lX 0Gy00Af7B/b3nw/o6e9EgWEMNQxR9lOCdBNHvqWAAJNvrfmCBzVywCrYNm+uhPav 6n0SU54O7MdSkvL5pJZKjCMQmAYqZw54qzEwMo0JDddvTd5kvrIF/wIK8GFA0zBF 5aVe7R+IIeRSALpt65TMCptq6h+mRruorPhii7ugeOvRLcwLeSoLis/3BgsqrJ7x S/9dDG9rivrKDudiXqLmkTvklRvhH+KcJM8TmtDXzN+b7bQzksa1SA2YcEv6rUNN fDUThDqFBQ/yxF9IeD90SiQlnr9cF8Ux0iP1oKyp0dNNNAUF+Pwfc6mOkemZrev1 Pl8TJbuZl7IeIpSX/ftIgvUvqFVkcQ== =J2Dh -----END PGP SIGNATURE----- --Sig_/qU/dK2yDyZMdgSQ7Jl4PJ7B--