Hi Milan, On 09/07/2014 07:15 PM, Milan Broz wrote:
On 09/07/2014 06:46 PM, Daniel Borkmann wrote:Recently, in commit 13aa93c70e71 ("random: add and use memzero_explicit() for clearing data"), we have found that GCC may optimize some memset() cases away when it detects a stack variable is not being used anymore and going out of scope. This can happen, for example, in cases when we are clearing out sensitive information such as keying material or any e.g. intermediate results from crypto computations, etc.Hi, do you plan to send patches also for other crypto code in kernel? (I am almost sure we have the same pattern in dmcrypt.) If not, I can do this for the dmcrypt part.
Yes, please feel free and go ahead. I have checked random driver, crypto and networking subsystem. With this patch that I've sent here, these three are covered (in networking, there was no such candidate, just one false positive in Bluetooth). But if you find other areas with a similar case, feel free to go ahead and fix it, very much appreciated. Thanks & best, Daniel
Milan
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
