{"push_id":579324926,"size":1,"distinct_size":0,"ref":"refs/heads/cm-11.0-wip","head":"5e6d2286a52390b1f3b08dd9989e4d85fe0253c6","before":"7194e1f1ed4c7bd0b5d801f866074cffa02d5c61","commits":[{"sha":"5e6d2286a52390b1f3b08dd9989e4d85fe0253c6","author":{"email":"8c1011c9d06fc72acd93645d683782ab9543044d@google.com","name":"Michael Halcrow"},"message":"eCryptfs: Remove buggy and unnecessary write in file name decode routine\n\ncommit 942080643bce061c3dd9d5718d3b745dcb39a8bc upstream.\n\nDmitry Chernenkov used KASAN to discover that eCryptfs writes past the\nend of the allocated buffer during encrypted filename decoding. This\nfix corrects the issue by getting rid of the unnecessary 0 write when\nthe current bit offset is 2.\n\nSigned-off-by: Michael Halcrow <mhalcrow@google.com>\nReported-by: Dmitry Chernenkov <dmitryc@google.com>\nSuggested-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Tyler Hicks <tyhicks@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/OpenDesireProject/android_kernel_htc_msm7x30/commits/5e6d2286a52390b1f3b08dd9989e4d85fe0253c6"}]}