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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20220125094102.ju7bhuplcxnkyv4x@dwarf.suse.cz> Date: Tue, 25 Jan 2022 10:41:02 +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 Mon, Jan 24, 2022 at 04:45:31PM +0100, Steffen Klassert wrote: > > 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? > > The patch is already marked as 'awaiting upstream' in patchwork, > so I'll take it into the ipsec tree. OK, thanks! Will you also revert b515d263 in the ipsec tree? -- Jiri Bohac <jbohac@...e.cz> SUSE Labs, Prague, Czechia
Powered by blists - more mailing lists