lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Jan 2022 10:12:33 +0100 From: Jiri Bohac <jbohac@...e.cz> To: Steffen Klassert <steffen.klassert@...unet.com> Cc: Sabrina Dubroca <sd@...asysnail.net>, Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>, Mike Maloney <maloneykernel@...il.com>, Eric Dumazet <eric.dumazet@...il.com>, netdev@...r.kernel.org Subject: Re: [PATCH] xfrm: fix MTU regression On Wed, Jan 19, 2022 at 08:35:19AM +0100, Steffen Klassert wrote: > Can you please add a 'Fixes:' tag so that it can be backported > to the stable trees? sure; I'll send a v2 with added Fixes: for the original regression (749439bf), which will reappear once b515d263 (which causes the current regression) is reverted. Note this patch needs to be accompanied by the revert! > Btw. this fixes a xfrm issue, but touches only generic IPv6 code. > To which tree should this patch be applied? I can take it to > the ipsec tee, but would also be ok if it is applied directly > to the net tree. b515d263 touches xfrm code; but being a regression maybe we want the fastest track possible? Thanks, -- Jiri Bohac <jbohac@...e.cz> SUSE Labs, Prague, Czechia
Powered by blists - more mailing lists