On Fri, Mar 26, 2021 at 01:53:47PM -0400, Len Brown wrote:
> At Dave's suggestion, we had a 64 *KB* sanity check on this path.
> Boris forced us to remove it, because we could not tell him
> how we chose the number 64.
The only 64 I can remember is
#define XSTATE_BUFFER_MAX_BYTES (64 * 1024)
What does an arbitrary number have to do with signal handling and
pushing a fat frame on the sigaltstack?
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG
Nürnberg
