{"push_id":767098544,"size":1,"distinct_size":1,"ref":"refs/heads/M_staging","head":"99b9ff778d3800129da0858514f5b5de40d68c77","before":"edeae13bdbef330a090339268b770972dda68d1d","commits":[{"sha":"99b9ff778d3800129da0858514f5b5de40d68c77","author":{"email":"9ff04a02a69f376b2b9aeec27187017cbf3cf5f9@redhat.com","name":"Daniel Borkmann"},"message":"random: add and use memzero_explicit() for clearing data\n\ncommit d4c5efdb97773f59a2b711754ca0953f24516739 upstream.\n\nzatimend has reported that in his environment (3.16/gcc4.8.3/corei7)\nmemset() calls which clear out sensitive data in extract_{buf,entropy,\nentropy_user}() in random driver are being optimized away by gcc.\n\nAdd a helper memzero_explicit() (similarly as explicit_bzero() variants)\nthat can be used in such cases where a variable with sensitive data is\nbeing cleared out in the end. Other use cases might also be in crypto\ncode. [ I have put this into lib/string.c though, as it's always built-in\nand doesn't need any dependencies then. ]\n\nFixes kernel bugzilla: 82041\n\nReported-by: zatimend@hotmail.co.uk\nSigned-off-by: Daniel Borkmann <dborkman@redhat.com>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nCc: Alexey Dobriyan <adobriyan@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Starship-Android/android_kernel_moto_shamu/commits/99b9ff778d3800129da0858514f5b5de40d68c77"}]}