[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220131111111.36510e25@elm.ozlabs.ibm.com>
Date: Mon, 31 Jan 2022 11:15:31 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Kees Cook <keescook@...omium.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Shijith Thotton <sthotton@...vell.com>,
Srujana Challa <schalla@...vell.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kspp tree
Hi Herbert,
On Mon, 31 Jan 2022 10:24:09 +1100 Herbert Xu <herbert@...dor.apana.org.au> wrote:
>
> On Mon, Jan 31, 2022 at 09:34:06AM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the kspp tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
>
> This should be fixed if you merge the latest cryptodev tree as
> it includes the following fix:
>
> commit f0a26ee8e1f8bda99f1e0050292de928cec17f92
> Author: Kees Cook <keescook@...omium.org>
> Date: Wed Jan 12 12:38:11 2022 -0800
>
> crypto: octeontx2 - Avoid stack variable overflow
Are you intending to send that to Linus soon (as it fixes a commit that
was merged in v5.17-rc1)? I would have expected to see it in the
crypto-current tree
(git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git#master)
in which case it would have been merged before the kspp tree.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists