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: <CANP3RGcdptMfnJXQNjNdiD4kuoZxj4vETro_aWRQqzsxY=yAfQ@mail.gmail.com> Date: Tue, 5 Feb 2019 14:54:29 -0800 From: Maciej Żenczykowski <zenczykowski@...il.com> To: Benedict Wong <benedictwong@...gle.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Greg Kroah-Hartman <gregkh@...gle.com> Cc: Linux NetDev <netdev@...r.kernel.org>, Nathan Harold <nharold@...gle.com>, Lorenzo Colitti <lorenzo@...gle.com>, Steffen Klassert <steffen.klassert@...unet.com>, Eyal Birger <eyal.birger@...il.com>, tobias@...ongswan.org Subject: Re: [xfrm, backport request] Request backport of e2612cd496e7 - set-mark backwards compatibility > I propose backporting commit e2612cd496e7 ("xfrm: Make set-mark default > behavior backward compatible") to 4.19 and 4.20 kernels to fix a backwards > compatibility bug introduced in 9b42c1f179a6 (“xfrm: Extend the > output_mark to support input direction and masking”). > > The fix is small, relatively simple, and has unit tests. :) > > Without this change, systems using mark-based routing on 4.19 or 4.20 > kernels will by fail to route IPsec tunnel mode packets correctly in the > default case. This specifically affects Android devices. Looks like it already includes a 'fixes: sha1' tag. I'm not sure what causes these patches to get picked up for stable... I'm guessing it's some sort of Greg-fu-style-magic...?
Powered by blists - more mailing lists