{"push_id":857773878,"size":2,"distinct_size":2,"ref":"refs/heads/gcc5","head":"727e64c86eca7e788769efdf8ae278dd240ba580","before":"76f2cc0919673b9227bd5aada858d88b32209630","commits":[{"sha":"d820e52e79c81dfa93105bbfa4d4c1d82904df16","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"selinux: do not check open perm on ftruncate call\n\nUse the ATTR_FILE attribute to distinguish between truncate()\nand ftruncate() system calls. The two other cases where\ndo_truncate is called with a filp (and therefore ATTR_FILE is set)\nare for coredump files and for open(O_TRUNC). In both of those cases\nthe open permission has already been checked during file open and\ntherefore does not need to be repeated.\n\nCommit 95dbf739313f (\"SELinux: check OPEN on truncate calls\")\nfixed a major issue where domains were allowed to truncate files\nwithout the open permission. However, it introduced a new bug where\na domain with the write permission can no longer ftruncate files\nwithout the open permission, even when they receive an already open\nfile.\n\n(cherry picked from commit b21800f304392ee5d20f411c37470183cc779f11)\n\nBug: 22567870\nChange-Id: Id7c305e46beba5091c2c777529bd468216aae1c3\n\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nAcked-by: Stephen Smalley <sds@tycho.nsa.gov>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/sultanqasim/android_kernel_motorola_msm8916/commits/d820e52e79c81dfa93105bbfa4d4c1d82904df16"},{"sha":"727e64c86eca7e788769efdf8ae278dd240ba580","author":{"email":"d3aad9cbe8fcdbde8b04c22067b9f5d8db334022@gmail.com","name":"Sultan Qasim Khan"},"message":"compilation fixes for Linaro 5.1\n\nMost of these are probably false positive caused by bugs in the beta compiler.\nHowever, some of these might be legitimate bugs or even security issues.\n\nThere's something wierd going on with the fs/f2fs/segment.c that prevented me\nfrom stopping the warning now matter how much ridiculously explicit bounds\nchecking I put around the macro invocation that it seems to grumble about.\nI then tried masking out the warning just for the line in question, but that\ndidn't fix it either. I eventually gave up and ignored array bounds warnings\nfor the whole file, but there is almost certainly a GCC bug at play there.","distinct":true,"url":"https://api.github.com/repos/sultanqasim/android_kernel_motorola_msm8916/commits/727e64c86eca7e788769efdf8ae278dd240ba580"}]}