From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Vladis Dronov <vdronov@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireguard: Kconfig: select CRYPTO_CHACHA_S390
Date: Tue, 5 Jul 2022 03:50:53 +0200 [thread overview]
Message-ID: <YsOY/eWq7gRjXJK1@zx2c4.com> (raw)
In-Reply-To: <YsOKj/GE2Mb2UsYa@zx2c4.com>
On Tue, Jul 05, 2022 at 02:49:19AM +0200, Jason A. Donenfeld wrote:
> Hi Vladis,
>
> On Mon, Jul 04, 2022 at 09:15:35PM +0200, Vladis Dronov wrote:
> > Select the new implementation of CHACHA20 for S390 when available,
> > it is faster than the generic software implementation.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Link: https://lore.kernel.org/linux-kernel/202207030630.6SZVkrWf-lkp@intel.com/
> > Signed-off-by: Vladis Dronov <vdronov@redhat.com>
> > ---
> > drivers/net/Kconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> > index b2a4f998c180..8c1eeb5a8db8 100644
> > --- a/drivers/net/Kconfig
> > +++ b/drivers/net/Kconfig
> > @@ -94,6 +94,7 @@ config WIREGUARD
> > select CRYPTO_CURVE25519_NEON if ARM && KERNEL_MODE_NEON
> > select CRYPTO_CHACHA_MIPS if CPU_MIPS32_R2
> > select CRYPTO_POLY1305_MIPS if MIPS
> > + select CRYPTO_CHACHA_S390 if S390
> > help
> > WireGuard is a secure, fast, and easy to use replacement for IPSec
> > that uses modern cryptography and clever networking tricks. It's
> > --
> > 2.36.1
>
> Thanks for the patch. Queued up as:
> https://git.zx2c4.com/wireguard-linux/commit/?id=1b4ab028730cd00c144eaa51160865504b780961
>
> I'll include this in my series to net.git soon.
This actually leads to a minor problem:
WARNING: unmet direct dependencies detected for CRYPTO_CHACHA_S390
Depends on [n]: CRYPTO [=y] && CRYPTO_HW [=n] && S390 [=y]
This is of course harmless, since this doesn't *actually* depend on
CRYPTO_HW. In fact, the dependency on CRYPTO_HW is entirely a mistake
here that was repeated a few times. I cleaned this up and fixed it in
this patch:
https://lore.kernel.org/linux-crypto/20220705014653.111335-1-Jason@zx2c4.com/
So hopefully Herbert will take that for 5.19 and then we'll be all set
here.
Jason
next prev parent reply other threads:[~2022-07-05 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 19:15 Vladis Dronov
2022-07-05 0:49 ` Jason A. Donenfeld
2022-07-05 1:50 ` Jason A. Donenfeld [this message]
2022-07-05 12:07 ` Vlad Dronov
2022-07-05 13:21 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YsOY/eWq7gRjXJK1@zx2c4.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=freude@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vdronov@redhat.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).