On Wed, Mar 18, 2015, at 18:41, Theodore Ts'o wrote:
> Maybe we should add a kernel self-test that automatically checks
> whether or not memset_explicit() gets optimized away? Otherwise we
> might not notice when gcc or how we implement barrier() or whatever
> else we end up using ends up changing.
>
> It shold be something that is really fast, so it might be a good idea
> to simply automatically run it as part of an __initcall()
> unconditionally. We can debate where the __initcall() lives, but I'd
> prefer that it be run even if the crypto layer isn't configured for
> some reason. Hopefully such an self-test is small enough that the
> kernel bloat people won't complain. :-)
>
> -Ted
Maybe a BUILD_BUGON: ;)
__label__ l1, l2;
char buffer[1024];
l1:
memset(buffer, 0, 1024);
l2:
BUILD_BUGON(&&l1 == &&l2);
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
