Messages in this thread | | | Date | Mon, 31 Jan 2022 13:06:06 -0800 | From | Kees Cook <> | Subject | Re: linux-next: build failure after merge of the kspp tree |
| |
On Mon, Jan 31, 2022 at 11:10:19AM -0800, Saeed Mahameed wrote: > On 30 Jan 22:19, Kees Cook wrote: > > On Mon, Jan 31, 2022 at 03:59:32PM +1100, Stephen Rothwell wrote: > > > On Sun, 30 Jan 2022 20:04:00 -0800 Kees Cook <keescook@chromium.org> wrote: > > > > https://lore.kernel.org/linux-hardening/20220124172242.2410996-1-keescook@chromium.org/
Fixes: 34802a42b352 ("net/mlx5e: Do not modify the TX SKB")
> > > > https://lore.kernel.org/linux-hardening/20220124172028.2410761-1-keescook@chromium.org/
Fixes: b5503b994ed5 ("net/mlx5e: XDP TX forwarding support")
> > > 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 need proper fixes tags to submit to net, can you provide ?
Sure! See above.
> another option is to use a shared branch with those fixes and pull it to > both net-next and kspp.
It's just a handful left now, so I think we'll avoid this for now.
Thanks!
-- Kees Cook
| |