{"push_id":1020551739,"size":22,"distinct_size":22,"ref":"refs/heads/marshmallow","head":"60d9786bfe5ef0f62a2650c06eccf2809c980a3f","before":"332f79e411ee81032181c6dcb7dc680a5d5cfb0b","commits":[{"sha":"6744087d8729424949b6d874191f9f6c5e2396d4","author":{"email":"d4b6c51c9a0d66973fb6c9ecdf48c3f781903a82@codeaurora.org","name":"Sagar Dharia"},"message":"slimbus: Use physical address type where physical address is used\n\nUse physical address type for buffers using physical address.\n(e.g. interaction with data-mover engine)\n\nSigned-off-by: Sagar Dharia <sdharia@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/6744087d8729424949b6d874191f9f6c5e2396d4"},{"sha":"96dfcd39fcb53567f96e1ef4e9f0fe73e559a3bd","author":{"email":"5f9b166783ed56beb8d6f56b211f8346bd501e26@gmail.com","name":"gustavo"},"message":"video: Speed up console framebuffer imageblit function\n\nEspecially on platforms with a slower CPU but a relatively high\nframebuffer fill bandwidth, like current ARM devices, the existing\nconsole monochrome imageblit function used to draw console text is\nsuboptimal for common pixel depths such as 16bpp and 32bpp. The existing\ncode is quite general and can deal with several pixel depths. By creating\nspecial case functions for 16bpp and 32bpp, by far the most common pixel\nformats used on modern systems, a significant speed-up is attained\nwhich can be readily felt on ARM-based devices like the Raspberry Pi\nand the Allwinner platform, but should help any platform using the\nfb layer.\n\nThe special case functions allow constant folding, eliminating a number\nof instructions including divide operations, and allow the use of an\nunrolled loop, eliminating instructions with a variable shift size,\nreducing source memory access instructions, and eliminating excessive\nbranching. These unrolled loops also allow much better code optimization\nby the C compiler. The code that selects which optimized variant is used\nis also simplified, eliminating integer divide instructions.\n\nThe speed-up, measured by timing 'cat file.txt' in the console, varies\nbetween 40% and 70%, when testing on the Raspberry Pi and Allwinner\nARM-based platforms, depending on font size and the pixel depth, with\nthe greater benefit for 32bpp.\n\nSigned-off-by: Harm Hanemaaijer <fgenfb@yahoo.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/96dfcd39fcb53567f96e1ef4e9f0fe73e559a3bd"},{"sha":"96e690c9ed7f44e636acbbd427381fd1f87c9e0f","author":{"email":"5b1a755a6b1799d96d2e1f98e16b285f5f690241@google.com","name":"Dmitry Shmidt"},"message":"PM: Check dpm_suspend_start() return code during partial resume\n\nBug: 24986869\n\nSigned-off-by: Dmitry Shmidt <dimitrysh@google.com>\nSigned-off-by: Thierry Strudel <tstrudel@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/96e690c9ed7f44e636acbbd427381fd1f87c9e0f"},{"sha":"1793151fbefd1a795cb7db27a887be7a4a8c32bd","author":{"email":"1f4f476af99d2158a80feba547ccb06360d2f2fe@google.com","name":"Sean Wan"},"message":"partial-resume: change suspend_again_consensus to be tri-state.\n\nThe current implementation to deduce wakeup interrupts is not perfect.\nIn many cases, some non-wakeup interrupts are considered as wakeup interrupts.\nAnd sometimes, the actual wakeup interrupts are missed.\n\nThis inaccuracy brings some trouble to partial resume. Here is an example on Bass:\n\n- When a wifi interrupt (330) wakes up the device, a few more interrupts are also\n  deduced as wakeup interrupts. They are 459 (vsync_gpio), 203 (mpm) and\n  200 (smd-rpm).\n- To enable wifi partial resume, partial resume handlers are implemented for the\n  four interrupts. Because the last three (459, 203 and 200) don't actually cause\n  the wakeup, the handlers are just dummy handlers, which always agree to suspend\n  again. The wifi handler is the only one decide whether suspend again or not.\n\n- When a bluetooth interrupt (327) wakes up the device, sometimes it is not reported\n  as wakeup interrupts. But 459, 203 and 200 are reported (as happens for wifi).\n- Because the actual wakeup interrupt is missed, the device will suspend again. This\n  causes bluetooth packet is missed, and the device enters weird state.\n\nTo solve this problem, this change modifies suspend_again_consensus from bi-state\n(true or false) to tri-state (reject, neutral, and agree).\n- For the false positive wakeup interrupts (e.g. 459, 203 and 200), it always return\n  neutral.\n- For the actual wakeup interrupt, it returns either reject or agree.\n- The final decision is only based on reject and agree.\n  * continue to wakeup if there is any reject or no agree.\n  * suspend again if there is no reject and at least one agree.\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/1793151fbefd1a795cb7db27a887be7a4a8c32bd"},{"sha":"83934ee85a481a7e0d1d38318a40d955df4b970e","author":{"email":"5b1a755a6b1799d96d2e1f98e16b285f5f690241@google.com","name":"Dmitry Shmidt"},"message":"ARM: msm: shamu: modify partial resume implementation\n\nSigned-off-by: Dmitry Shmidt <dimitrysh@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/83934ee85a481a7e0d1d38318a40d955df4b970e"},{"sha":"512421f4dc2f07b215c29c2a8153f3eb4c3bd37f","author":{"email":"f66cc59a245d146467efed1402e6d2f55ef6f900@google.com","name":"Patrick Tjin"},"message":"net: wireless: bcmdhd: validate remaining space in WPS IE\n\nValidate the amount of remaining space in the WPS IE\nto prevent reading past the end of the buffer.\n\nSigned-off-by: Patrick Tjin <pattjin@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/512421f4dc2f07b215c29c2a8153f3eb4c3bd37f"},{"sha":"4f1bd8da71c7a5826ffc8976528e59c770ce1e2c","author":{"email":"d688953a19dcb476c5fb90e6abba87f77b09be65@gmail.com","name":"Pranav Vashi"},"message":"Revert \"selinux: fix bug in conditional rules handling\"\n\nThis reverts commit 13c35c3b20595d482f2f3158c51114ea85834d76.\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/4f1bd8da71c7a5826ffc8976528e59c770ce1e2c"},{"sha":"0711efe3531bde7fd34bc6432ce914cc23ed35c2","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"Revert \"SELinux: ss: Fix policy write for ioctl operations\"\n\nThis reverts commit 8cdfb356b51e29494ca0b9e4e86727d6f841a52d.\n\nBug: 22846070\nChange-Id: I4dd2fd5a1d7fb3ae8f74a5decdf8fb9d5cd43def\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/0711efe3531bde7fd34bc6432ce914cc23ed35c2"},{"sha":"df0cfd18f964b16e3fba63ceb1f9a691cd1f9120","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"Revert \"SELinux: use deletion-safe iterator to free list\"\n\nThis reverts commit 98a4d82a78914c2496989d669ecae04dedcf361f.\n\nBug: 22846070\nChange-Id: Ic047824591e8d94f937c052846ab387864c04fd7\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/df0cfd18f964b16e3fba63ceb1f9a691cd1f9120"},{"sha":"25196bd1f45ef68869ac9db600ca544bede80331","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"Revert \"SELinux: per-command whitelisting of ioctls\"\n\nThis reverts commit 8daca972e410f42a4fc1fe2de804c50013b24a28.\n\nBug: 22846070\nChange-Id: Ia2d1e2b0f46ccb0328626286216e38378650505b\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/25196bd1f45ef68869ac9db600ca544bede80331"},{"sha":"00ad698f5d3350b2facdd360333cb6cbf2a78315","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"selinux: remove unnecessary pointer reassignment\n\n(cherry pick from commit 83d4a806ae46397f606de7376b831524bd3a21e5)\n\nCommit f01e1af445fa (\"selinux: don't pass in NULL avd to avc_has_perm_noaudit\")\nmade this pointer reassignment unnecessary. Avd should continue to reference\nthe stack-based copy.\n\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nAcked-by: Stephen Smalley <sds@tycho.nsa.gov>\n[PM: tweaked subject line]\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nBug: 22846070\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/00ad698f5d3350b2facdd360333cb6cbf2a78315"},{"sha":"d15d30a729568f5babe092541f70ab8c338b46af","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"selinux: extended permissions for ioctls\n\n(cherry picked from commit fa1aa143ac4a682c7f5fd52a3cf05f5a6fe44a0a)\n\nAdd extended permissions logic to selinux. Extended permissions\nprovides additional permissions in 256 bit increments. Extend the\ngeneric ioctl permission check to use the extended permissions for\nper-command filtering. Source/target/class sets including the ioctl\npermission may additionally include a set of commands. Example:\n\nallowxperm <source> <target>:<class> ioctl unpriv_app_socket_cmds\nauditallowxperm <source> <target>:<class> ioctl priv_gpu_cmds\n\nWhere unpriv_app_socket_cmds and priv_gpu_cmds are macros\nrepresenting commonly granted sets of ioctl commands.\n\nWhen ioctl commands are omitted only the permissions are checked.\nThis feature is intended to provide finer granularity for the ioctl\npermission that may be too imprecise. For example, the same driver\nmay use ioctls to provide important and benign functionality such as\ndriver version or socket type as well as dangerous capabilities such\nas debugging features, read/write/execute to physical memory or\naccess to sensitive data. Per-command filtering provides a mechanism\nto reduce the attack surface of the kernel, and limit applications\nto the subset of commands required.\n\nThe format of the policy binary has been modified to include ioctl\ncommands, and the policy version number has been incremented to\nPOLICYDB_VERSION_XPERMS_IOCTL=30 to account for the format\nchange.\n\nThe extended permissions logic is deliberately generic to allow\ncomponents to be reused e.g. netlink filters\n\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nAcked-by: Nick Kralevich <nnk@google.com>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/d15d30a729568f5babe092541f70ab8c338b46af"},{"sha":"e14e88c57c5bf834b18f23696ea0972e35ec62e0","author":{"email":"d6e1285e1c84d3d5885c2124fdacc780e9fc0a94@tycho.nsa.gov","name":"Stephen Smalley"},"message":"selinux: fix bug in conditional rules handling\n\ncommit fa1aa143ac4a (\"selinux: extended permissions for ioctls\")\nintroduced a bug into the handling of conditional rules, skipping the\nprocessing entirely when the caller does not provide an extended\npermissions (xperms) structure.  Access checks from userspace using\n/sys/fs/selinux/access do not include such a structure since that\ninterface does not presently expose extended permission information.\nAs a result, conditional rules were being ignored entirely on userspace\naccess requests, producing denials when access was allowed by\nconditional rules in the policy.  Fix the bug by only skipping\ncomputation of extended permissions in this situation, not the entire\nconditional rules processing.\n\nReported-by: Laurent Bigonville <bigon@debian.org>\nSigned-off-by: Stephen Smalley <sds@tycho.nsa.gov>\n[PM: fixed long lines in patch description]\nCc: stable@vger.kernel.org # 4.3\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/e14e88c57c5bf834b18f23696ea0972e35ec62e0"},{"sha":"5e203f3996fb0d1580c41c52abc5a5ef5453bb0c","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"selinux: Android kernel compatibility with M userspace\n\nNOT intended for new Android devices - this commit is unnecessary\nfor a target device that does not have a previous M variant.\n\nDO NOT upstream. Android only.\n\nMotivation:\n\nThis commit mitigates a mismatch between selinux kernel and\nselinux userspace. The selinux ioctl white-listing binary policy\nformat that was accepted into Android M differs slightly from what\nwas later accepted into the upstream kernel. This leaves Android\nmaster branch kernels incompatible with Android M releases. This\npatch restores backwards compatibility. This is important because:\n\n1. kernels may be updated on a different cycle than the rest of the\n   OS e.g. security patching.\n2. Android M bringup may still be ongoing for some devices. The\n   same kernel should work for both M and master.\n\nBackwards compatibility is achieved by checking for an Android M\npolicy characteristic during initial policy read and converting to\nupstream policy format. The inverse conversion is done for policy\nwrite as required for CTS testing.\n\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/5e203f3996fb0d1580c41c52abc5a5ef5453bb0c"},{"sha":"48c52decd098236160cf243f7d8959a5b776f71e","author":{"email":"fa3a5dbc719a3c2bd207f16e6edd6f6a7641f60a@gmail.com","name":"dataanddreams"},"message":"net: wireless: bcmdhd: Add checks for stack buffer overflows\n\nThese two checks prevent exploitable buffer overflows in two scenarios.\n1. Long WPS_ID_DEVICE_NAME in WPS info elements\n2. Invalid SSID determined in certain scan results\n\nSigned-off-by: Yuan Lin <yualin@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/48c52decd098236160cf243f7d8959a5b776f71e"},{"sha":"a71699a7f77ed80d2fbead1e9ce88aab6d8317e1","author":{"email":"f66cc59a245d146467efed1402e6d2f55ef6f900@google.com","name":"Patrick Tjin"},"message":"net: wireless: bcmdhd: check packet length for event messages\n\nCheck the datalen field is less than the size of\npacket received from the network.\n\nBug: 25306181\nBug: 25682871\n\nSigned-off-by: Patrick Tjin <pattjin@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/a71699a7f77ed80d2fbead1e9ce88aab6d8317e1"},{"sha":"5280d52aca882c9d843bd4039040ecb2b33b3909","author":{"email":"fa3a5dbc719a3c2bd207f16e6edd6f6a7641f60a@gmail.com","name":"dataanddreams"},"message":"bcmdhd: Add checks for stack buffer overflows\n\nThese two checks prevent exploitable buffer overflows in two scenarios.\n1. Long WPS_ID_DEVICE_NAME in WPS info elements\n2. Invalid SSID determined in certain scan results\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/5280d52aca882c9d843bd4039040ecb2b33b3909"},{"sha":"b3aef5d258331a900312728106ec38b6eff686a6","author":{"email":"08028e1ebcd6b60dcc52cd877338133fa3c70487@gmail.com","name":"chengjia4574"},"message":"msm: arm: krait: Patch for krait array access out of bound\n\nCurrent array-bound-check does not cover all cases.\nAn attacker can use this loophole to redirect $PC to attacker-controlled functions.\n\nThe fix is to move the existing array-bound-check to a later location to cover all cases.\n\nSigned-off-by: Yuan Lin <yualin@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/b3aef5d258331a900312728106ec38b6eff686a6"},{"sha":"def4e7940d4d872003f3520bf6f963cbeca3f893","author":{"email":"5d39c857884a1d1ca828769b9ecffa221bdbcccf@gmail.com","name":"Wish Wu"},"message":"events: core: null pointer dereferencing\n\nPrevent unintended kernel NULL pointer dereferencing.\n\nOriginal code:\n  hlist_del_rcu(&event->hlist_entry);\n\nFix: Adding pointer check:\n  if(!hlist_unhashed(&p_event->hlist_entry))\n    hlist_del_rcu(&p_event->hlist_entry);\n\nSigned-off-by: Yuan Lin <yualin@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/def4e7940d4d872003f3520bf6f963cbeca3f893"},{"sha":"675a238ff927d36293f376192c2d2232f6a2288f","author":{"email":"f66cc59a245d146467efed1402e6d2f55ef6f900@google.com","name":"Patrick Tjin"},"message":"misc/drv2605: Fixup security issues with data access\n\nBug: 25981545\n\nSigned-off-by: Patrick Tjin <pattjin@google.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/neobuddy89/shamu/commits/675a238ff927d36293f376192c2d2232f6a2288f"}]}