{"push_id":631585962,"size":1,"distinct_size":1,"ref":"refs/heads/test","head":"6c018e5841409162d857bf5b9eb8a96880a12561","before":"cfdb8a8b5aa4960667b86decd5505eb85ec51f37","commits":[{"sha":"6c018e5841409162d857bf5b9eb8a96880a12561","author":{"email":"95eac59efc1533ca56d004eac480fd4cd412b4e9@windriver.com","name":"JeHyeon Yeon"},"message":"LZ4 : fix the data abort issue\n\nIf the part of the compression data are corrupted, or the compression\ndata is totally fake, the memory access over the limit is possible.\n\nThis is the log from my system usning lz4 decompression.\n   [6502]data abort, halting\n   [6503]r0  0x00000000 r1  0x00000000 r2  0xdcea0ffc r3  0xdcea0ffc\n   [6509]r4  0xb9ab0bfd r5  0xdcea0ffc r6  0xdcea0ff8 r7  0xdce80000\n   [6515]r8  0x00000000 r9  0x00000000 r10 0x00000000 r11 0xb9a98000\n   [6522]r12 0xdcea1000 usp 0x00000000 ulr 0x00000000 pc  0x820149bc\n   [6528]spsr 0x400001f3\nand the memory addresses of some variables at the moment are\n    ref:0xdcea0ffc, op:0xdcea0ffc, oend:0xdcea1000\n\nAs you can see, COPYLENGH is 8bytes, so @ref and @op can access the momory\nover @oend.\n\nSigned-off-by: JeHyeon Yeon <tom.yeon@windriver.com>\nReviewed-by: David Sterba <dsterba@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Cl3Kener/UBER-L/commits/6c018e5841409162d857bf5b9eb8a96880a12561"}]}