Re: [PATCH 0/2] wireguard-linux-compat: grsecurity compat patches

[Mathias Krause <minipli@grsecurity.net>]

Hi Jason,

Am 12.12.21 um 22:43 schrieb Jason A. Donenfeld:
> [snip]
>  
> Thanks for that! I've imported this into my staging tree here:
> https://w-g.pw/l/rmQK
> 
> I'll wait a few days -- and until the Vale PR has been merged -- to
> submit that to the linux-crypto mailing list, but there's a preview.
> Mathias - I wonder if you still need alternatives with the new codegen
> there.

yes, the alternative is still needed, as Aymeric's change doesn't lower
the number of required registers -- neither would a "rm" operand
constraint do, as gcc still insists in all constraints to be possible at
least, even if it would choose "m" instead of "r" in the end.

So, after importing Aymeric's changes into wireguard-linux-compat, the
alternatives change is still needed. I can help you create one, if you
want me to (we have that change in grsec anyway, just used named asm
operands here, as the %0/%1/%2/... was rather confusing and hard to follow).

Thanks,
Mathias