[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220131155932.3f88ec71@canb.auug.org.au>
Date: Mon, 31 Jan 2022 15:59:32 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kees Cook <keescook@...omium.org>
Cc: "David S. Miller" <davem@...emloft.net>,
Leon Romanovsky <leon@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Jakub Kicinski <kuba@...nel.org>,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: linux-next: build failure after merge of the kspp tree
Hi Kees,
On Sun, 30 Jan 2022 20:04:00 -0800 Kees Cook <keescook@...omium.org> wrote:
>
> This should be fixed by:
> https://lore.kernel.org/linux-hardening/20220124172242.2410996-1-keescook@chromium.org/
> (I was expecting this to be in netdev by now.)
>
> This should be fixed in:
> https://lore.kernel.org/linux-hardening/20220124172028.2410761-1-keescook@chromium.org/
> (Again, this was expected to be in netdev by now.)
>
yeah, neither has made it yet. However, it would not have helped as I
am merging the kspp tree very early so that new bugs get fixed in the
trees that introduce them. These 2 are in Linus tree (for a long time)
and so it would be better if these fixes went int the net tree and then
Linus' tree as bug fixes.
I will use these in the merge of the kspp tree from tomorrow until they
appear earlier (or you could put them back in your tree). Cross tree
dependencies are a pain :-( BTW Linus would have the same problem I
am having if he merges your tree during the merge window before he
merges the net-next tree ...
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists