{"push_id":878081072,"size":31,"distinct_size":31,"ref":"refs/heads/m","head":"2e4018233bb4b9034e56f38f2d5e2b20c4b679de","before":"5fe82bdcb6bb5f5c6284b9e2c03b7a8250cfb948","commits":[{"sha":"a4a4933b2f61aa518071eb0fbee39b2b668187c6","author":{"email":"1a2f18c7887fc8d384193bb926e616097dea5b69@google.com","name":"JP Abgrall"},"message":"netfilter: IDLETIMER: fix invalid deference of timer\n\n\"timer\" was checked for null, but used later without being re-checked.\n\nChange-Id: Ib4d08cd49860c9f157d1cac556705ba85cd44f4e\nReported-by: dan.carpenter@oracle.com\nSigned-off-by: JP Abgrall <jpa@google.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/a4a4933b2f61aa518071eb0fbee39b2b668187c6"},{"sha":"0576332321b842a4b112e87072e1009c4e82f59f","author":{"email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@rasmusvillemoes.dk","name":"Rasmus Villemoes"},"message":"cpuidle: Replace strnicmp with strncasecmp\n\nThe kernel used to contain two functions for length-delimited,\ncase-insensitive string comparison, strnicmp with correct semantics\nand a slightly buggy strncasecmp. The latter is the POSIX name, so\nstrnicmp was renamed to strncasecmp, and strnicmp made into a wrapper\nfor the new strncasecmp to avoid breaking existing users.\n\nTo allow the compat wrapper strnicmp to be removed at some point in\nthe future, and to avoid the extra indirection cost, do\ns/strnicmp/strncasecmp/g.\n\nChange-Id: Ie127ba8940ba2e6a186577c22b445f48ed415794\nSigned-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/0576332321b842a4b112e87072e1009c4e82f59f"},{"sha":"5316d37dc69758d0f774fef53ced1b0394abab2c","author":{"email":"a8167b9d27aca9c6624754deb52c4c6420eded04@huawei.com","name":"Li Zefan"},"message":"kmemleak: free internal objects only if there're no leaks to be reported\n\nCurrently if you stop kmemleak thread before disabling kmemleak,\nkmemleak objects will be freed and so you won't be able to check\npreviously reported leaks.\n\nWith this patch, kmemleak objects won't be freed if there're leaks that\ncan be reported.\n\nChange-Id: I31c837fa63f99f65a553471de46729d8d8e08ed5\nSigned-off-by: Li Zefan <lizefan@huawei.com>\nAcked-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: dc9b3f424903f7d6992778b69b1e35d864914ae5\nGit-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/\nSigned-off-by: Vignesh Radhakrishnan <vigneshr@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/5316d37dc69758d0f774fef53ced1b0394abab2c"},{"sha":"72c356a21f04afbac71dcc11585fbdf29bd2f3f3","author":{"email":"15ce75b290ebaf27c3f9fd73ab848685ed3d8261@arm.com","name":"Catalin Marinas"},"message":"mm: kmemleak: avoid false negatives on vmalloc'ed objects\n\nCommit 248ac0e1943a (\"mm/vmalloc: remove guard page from between vmap\nblocks\") had the side effect of making vmap_area.va_end member point to\nthe next vmap_area.va_start.  This was creating an artificial reference\nto vmalloc'ed objects and kmemleak was rarely reporting vmalloc() leaks.\n\nThis patch marks the vmap_area containing pointers explicitly and\nreduces the min ref_count to 2 as vm_struct still contains a reference\nto the vmalloc'ed object.  The kmemleak add_scan_area() function has\nbeen improved to allow a SIZE_MAX argument covering the rest of the\nobject (for simpler calling sites).\n\nChange-Id: I237dd983d000c956ede36b5492dfe046a3060ce4\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: 7f88f88f83ed609650a01b18572e605ea50cd163\nGit-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/\nSigned-off-by: Vignesh Radhakrishnan <vigneshr@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/72c356a21f04afbac71dcc11585fbdf29bd2f3f3"},{"sha":"21c994b2c5c57f7aa81e44757f5937e33c49c500","author":{"email":"a8167b9d27aca9c6624754deb52c4c6420eded04@huawei.com","name":"Li Zefan"},"message":"kmemleak: allow freeing internal objects after kmemleak was disabled\n\nCurrently if kmemleak is disabled, the kmemleak objects can never be\nfreed, no matter if it's disabled by a user or due to fatal errors.\n\nThose objects can be a big waste of memory.\n\n    OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME\n  1200264 1197433  99%    0.30K  46164       26    369312K kmemleak_object\n\nWith this patch, after kmemleak was disabled you can reclaim memory\nwith:\n\n\t# echo clear > /sys/kernel/debug/kmemleak\n\nAlso inform users about this with a printk.\n\nChange-Id: I13fdd5f0439bf6bc23824d37a44813eb0fe6a392\nSigned-off-by: Li Zefan <lizefan@huawei.com>\nAcked-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: c89da70c7360294e715df5abd4b7239db3274c86\nGit-repo: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/\nSigned-off-by: Vignesh Radhakrishnan <vigneshr@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/21c994b2c5c57f7aa81e44757f5937e33c49c500"},{"sha":"137357f0449e00717cef7e72c37795cbd9388de0","author":{"email":"2f9537c6ec687a8748c4f2e7dccd545b87138ca3@yahoo.com","name":"Harm Hanemaaijer"},"message":"Optimize copy_page for modern ARM platforms\n\nThe existing implementation of copy_page for ARM appears to be\noptimized for older platforms. Benchmark testing in a sandbox\nenvironment shows suboptimal performance on modern platforms\nlike armv6 and armv7, with speed-ups ranging from 10% (Cortex A8)\nto 80% (armv6 used in Raspberry Pi) being achievable.\n\nThis commit optimizes copy_page and introduces the new compile-time\nconstant PREFETCH_DISTANCE, defined in cache.h, which when\nmultiplied by L1_CACHE_BYTES is equal to the offset used for\nprefetches performed with the PLD instruction. For platforms where\nL1_CACHE_BYTES is 32 (armv5 and armv6), copy_page processes 32 bytes\nat a time while doing one prefetch per iteration, while for armv7\n(with L1_CACHE_BYTES equal to 64), 64 bytes are processed at at time\nwith one prefetch per iteration. When no preload instruction is\navailable (platforms earlier than armv5), no preload instructions\nare generated and 32 bytes are processed at at time.\n\nTo facilitate specifying instructions for architectures with no\npreload instruction, the NO_PLD macro is added to assembler.h,\naugmenting the PLD macro.\n\nChange-Id: I4b4fc4d478e4840cad66f9b112d0787d369c2edb\nSigned-off-by: Harm Hanemaaijer <fgenfb@yahoo.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/137357f0449e00717cef7e72c37795cbd9388de0"},{"sha":"cae792506eec92246b1ede7c97c1cd6eaa08f512","author":{"email":"3807cf899f217da549814bf6c330d3b6e6819ccf@gmail.com","name":"Akinobu Mita"},"message":"block_dev: implement readpages() to optimize sequential read\n\nSequential read from a block device is expected to be equal or faster than\nfrom the file on a filesystem.  But it is not correct due to the lack of\neffective readpages() in the address space operations for block device.\n\nThis implements readpages() operation for block device by using\nmpage_readpages() which can create multipage BIOs instead of BIOs for each\npage and reduce system CPU time consumption.\n\nInstall 1GB of RAM disk storage:\n\n\t# modprobe scsi_debug dev_size_mb=1024 delay=0\n\nSequential read from file on a filesystem:\n\n\t# mkfs.ext4 /dev/$DEV\n\t# mount /dev/$DEV /mnt\n\t# fio --name=t --size=512m --rw=read --filename=/mnt/file\n\t...\n\t  read : io=524288KB, bw=2133.4MB/s, iops=546133, runt=   240msec\n\nSequential read from a block device:\n\t# fio --name=t --size=512m --rw=read --filename=/dev/$DEV\n\t...\n(Without this commit)\n\t  read : io=524288KB, bw=1700.2MB/s, iops=435455, runt=   301msec\n\n(With this commit)\n\t  read : io=524288KB, bw=2160.4MB/s, iops=553046, runt=   237msec\n\nChange-Id: I7386391689d53fc466ada9a8f61ff850911c5688\nSigned-off-by: Akinobu Mita <akinobu.mita@gmail.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: Alexander Viro <viro@zeniv.linux.org.uk>\nCc: Jeff Moyer <jmoyer@redhat.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/cae792506eec92246b1ede7c97c1cd6eaa08f512"},{"sha":"5959919c1653ea55c0d31fb42c75aa9edc5f29a7","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: Ignore interval prediction result when timer is shorter\n\nThis patch prevents cpuidle menu governor from using repeating interval\nprediction result if the idle period predicted is longer than the one\nallowed by shortest running timer.\n\nChange-Id: I664a2e4093a5bf462be984e2a40410dec0b76088\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/5959919c1653ea55c0d31fb42c75aa9edc5f29a7"},{"sha":"54489cfa8f57d26c0f4402fff8304920bf66ffb3","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: Rearrange code and comments in get_typical_interval()\n\nThis patch rearranges a if-return-elsif-goto-fi-return sequence into\nif-return-fi-if-return-fi-goto sequence. The functionality remains the\nsame. Also, a lengthy comment that did not describe the functionality\nin the order it occurs is split into half and top half is moved closer\nto actual implementation it describes.\n\nChange-Id: I82d139a502055eb03358bc811c4e8ee63736bfbb\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/54489cfa8f57d26c0f4402fff8304920bf66ffb3"},{"sha":"260d7496a2a7ac26c80861071171ee77409a80cd","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: Check called function parameter in get_typical_interval()\n\nget_typical_interval() uses int_sqrt() in calculation of standard\ndeviation. The formal parameter of int_sqrt() is unsigned long, which\nmay on some platforms be smaller than the 64 bit unsigned integer used\nas the actual parameter. The overflow can occur frequently when actual\nidle period lengths are in hundreds of milliseconds.\n\nThis patch adds a check for such overflow and rejects the candidate\naverage when an overflow would occur.\n\nChange-Id: I4e584387bdb2e7a33adff001c71fdbefc96ba863\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/260d7496a2a7ac26c80861071171ee77409a80cd"},{"sha":"3219843d5b3bb162881c2c6ae03b658a732b4619","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: CodingStyle: Break up multiple assignments on single line\n\nThe function get_typical_interval() initializes a number of variables\nthat are immediately after declarations assigned constant values.\nIn addition, there are multiple assignments on a single line, which\nis explicitly forbidden by Documentation/CodingStyle.\n\nThis patch removes redundant initial values for the variables and\nbreaks up the multiple assignment line.\n\nChange-Id: I5bff9c0824765b2b8ca76774b4a825f18491976c\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/3219843d5b3bb162881c2c6ae03b658a732b4619"},{"sha":"88581102d8de49e7e438b4cd250c6ef38ebd9714","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: Fix menu_device->intervals type\n\nStruct menu_device member intervals is declared as u32, but the value\nstored is (unsigned) int. The type is changed to match the value being\nstored.\n\nChange-Id: Id3bda1cf4f3065025c5ccf9c42ae45ae835f545c\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/88581102d8de49e7e438b4cd250c6ef38ebd9714"},{"sha":"c6785a77db8d673ddb32c0bc124527598fc27ed6","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: Fix variable domains in get_typical_interval()\n\nThe menu governor uses a static function get_typical_interval() to\ntry to detect a repeating pattern of wakeups. The previous interval\ndurations are stored as an array of unsigned ints, but the arithmetic\nin the function is performed exclusively as 64 bit values, even when\nthe value stored in a variable is known not to exceed unsigned int,\nwhich may be smaller and more efficient on some platforms.\n\nThis patch changes the types of varibles used to store some\nintermediates, the maximum and and the cutoff threshold to unsigned\nints. Average and standard deviation are still treated as 64 bit values,\neven when the values are known to be within the domain of unsigned int,\nto avoid casts to ensure correct integer promotion for arithmetic\noperations.\n\nChange-Id: I29be0dee64f63fce68bda8ee56c030653b685879\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/c6785a77db8d673ddb32c0bc124527598fc27ed6"},{"sha":"61d4d3193f1c0175ffb0e413bc7c1b33a0e9e49e","author":{"email":"43fc4de20078a3cb47bd11cd83c602ec6b51a993@linaro.org","name":"Tuukka Tikkanen"},"message":"cpuidle: Change struct menu_device field types\n\nField predicted_us value can never exceed expected_us value, but it has\na potentially larger type. As there is no need for additional 32 bits of\nzeroes on 32 bit plaforms, change the type of predicted_us to match the\ntype of expected_us.\n\nField correction_factor is used to store a value that cannot exceed the\nproduct of RESOLUTION and DECAY (default 1024*8 = 8192). The constants\ncannot in practice be incremented to such values, that they'd overflow\nunsigned int even on 32 bit systems, so the type is changed to avoid\nunnecessary 64 bit arithmetic on 32 bit systems.\n\nOne multiplication of (now) 32 bit values needs an added cast to avoid\ntruncation of the result and has been added.\n\nIn order to avoid another multiplication from 32 bit domain to 64 bit\ndomain, the new correction_factor calculation has been changed from\nnew = old * (DECAY-1) / DECAY\nto\nnew = old - old / DECAY,\nwhich with infinite precision would yeild exactly the same result, but\nnow changes the direction of rounding. The impact is not significant as\nthe maximum accumulated difference cannot exceed the value of DECAY,\nwhich is relatively small compared to product of RESOLUTION and DECAY\n(8 / 8192).\n\nChange-Id: Ic6e6d9541bd83d8e2a9918d01dc133f2ece1dea8\nSigned-off-by: Tuukka Tikkanen <tuukka.tikkanen@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/61d4d3193f1c0175ffb0e413bc7c1b33a0e9e49e"},{"sha":"025b6b00846939a4997095b7654b9902bd3faf7c","author":{"email":"5f9b166783ed56beb8d6f56b211f8346bd501e26@gmail.com","name":"gustavo"},"message":"Optimize kernel cfbfillrect function\n\nThis is a  patch to speed up the kernel\ncfbfillrect function used for clearing the screen or filling an area\nwith a solid color.\n\nThe previous implementation was doing reads from the uncached framebuffer,\nin certain circumstances, even for simple fills, which for performance\nreasons, on most platforms, is ill-advised unless strictly necessary to\nconform to the raster operation. In these circumstances, doing 64-bit\naccess on 64-bit systems does not serve much purpose except for probing\nfor corner-case bugs and race conditions in the hardware's framebuffer\nbus implementation. On all systems, for 16bpp, it is better to take\nadvantage of write-combining features of the framebuffer and write a\nhalf-word if required for the left and right edges.\n\nAdditionally, on most platforms, integer divides are relatively slow so are\nbest avoided, especially in inner loops.\n\nThis patch implements optimizations for 16bpp and 32bpp that avoid\nframebuffer read operations during cfbfillrect if the raster-operation\nis GXcopy. This applies to both 32-bit (BITS_PER_LONG) and 64-bit\nsystems (BITS_PER_LONG == 64). Although cfbfillrect is not usually a\nbottleneck for the console text framebuffer (because regions filled\nusually are aligned to a multiple of 2 or 4 x-coordinate and reads\nare avoided), in some use-cases this patch could deliver a significant\nspeed-up.\n\nChange-Id: I9e42036c622cb5bd098a12bac43f71b47ae9cf90\nSigned-off-by: Harm Hanemaaijer <fgenfb@yahoo.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/025b6b00846939a4997095b7654b9902bd3faf7c"},{"sha":"2d0b39be0b05447a3384fcceddcd7be7794926c7","author":{"email":"5f9b166783ed56beb8d6f56b211f8346bd501e26@gmail.com","name":"gustavo"},"message":"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\nChange-Id: Ib78321c6fd5451f4c8e7ca99fe3f02954eb8f455\nSigned-off-by: Harm Hanemaaijer <fgenfb@yahoo.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/2d0b39be0b05447a3384fcceddcd7be7794926c7"},{"sha":"9b634eba91daa682a3cff863a995b61eada91eb6","author":{"email":"1dd89e5367785ba89076cd264daac0464fdf0d7b@cellrox.com","name":"Amir Goldstein"},"message":"sysrq: Emergency Remount R/O in reverse order\n\nThis change fixes a problem where reboot on Android panics the kernel\nalmost every time when file systems are mounted over loop devices.\n\nAndroid reboot command does:\n- sync\n- echo u > /proc/sysrq-trigger\n- syscall_reboot\n\nThe problem is with sysrq emergency remount R/O trying to remount-ro\nin wrong order.\nsince /data is re-mounted ro before loop devices, loop device\nremount-ro fails to flush the journal and panics the kernel:\n\n  EXT4-fs (loop0): Remounting filesystem read-only\n  EXT4-fs (loop0): previous I/O error to superblock detected\n  loop: Write error at byte offset 0, length 4096.\n  Buffer I/O error on device loop0, logical block 0\n  lost page write due to I/O error on loop0\n  Kernel panic - not syncing: EXT4-fs panic from previous error\n\nThe fix is quite simple. In do_emergency_remount(), use\nlist_for_each_entry_reverse() on sb list instead of list_for_each_entry().\nIt makes a lot of sense to umount the file systems in reverse order in\nwhich they were added to sb list.\n\nChange-Id: I4370e39b5873bd16ade5d5f9ddb2704beb02a2bb\nSigned-off-by: Amir Goldstein <amir@cellrox.com>\nAcked-by: Oren Laadan <orenl@cellrox.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/9b634eba91daa682a3cff863a995b61eada91eb6"},{"sha":"b1fe15087ff5efd004ee8a72d7ac8abc65a2a106","author":{"email":"fbe788dcd509b324901fbdfe505a4d610d560569@google.com","name":"Jeff Vander Stoep"},"message":"arm64 Kconfig: Move LIST_POISON to a safe value\n\nMove the poison pointer offset to 0xdead000000000000, a\nrecognized value that is not mappable by user-space exploits.\n\nChange-Id: I1ddae985f2fc28ca1366747169d4ca91801a9d31\nSigned-off-by: Thierry Strudel <tstrudel@google.com>\nSigned-off-by: Jeff Vander Stoep <jeffv@google.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/b1fe15087ff5efd004ee8a72d7ac8abc65a2a106"},{"sha":"7838c0392875e2403d2ca93ae3b5de4dfd78013f","author":{"email":"2c98d18550b6e94ee93faf6d92fa2bedb58842c9@codeaurora.org","name":"Patrick Daly"},"message":"rcu: Fix missing task information during rcu-preempt stall\n\nThe first item list_for_each_entry_continue(alist) iterates over is\nalist->next, rather than alist itself. Consequently,\nrcu_print_detail_task_stall_rnp() skips the task referenced by gp_tasks.\n\nUse gp_tasks->prev as the argument to list_for_each_entry_continue()\ninstead.\n\nChange-Id: Iaa2be14139d0f6c1a1ed25817f0e5737b3e74753\nSigned-off-by: Patrick Daly <pdaly@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/7838c0392875e2403d2ca93ae3b5de4dfd78013f"},{"sha":"82a808a68bda44d111f99eb91c7132968101c3f8","author":{"email":"1e0ce936bb9b355d257bf5790d2513c3f28be22b@linux.vnet.ibm.com","name":"Paul E. McKenney"},"message":"rcu: Avoid redundant grace-period kthread wakeups\n\nWhen setting up an in-the-future \"advanced\" grace period, the code needs\nto wake up the relevant grace-period kthread, which it currently does\nunconditionally.  However, this results in needless wakeups in the case\nwhere the advanced grace period is being set up by the grace-period\nkthread itself, which is a non-uncommon situation.  This commit therefore\nchecks to see if the running thread is the grace-period kthread, and\navoids doing the irq_work_queue()-mediated wakeup in that case.\n\nSigned-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nReviewed-by: Josh Triplett <josh@joshtriplett.org>\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nGit-commit: 1eafd31c640d6799c63136246a59d608bed93c74\n[kishank@codeaurora.org resolve trivial conflicts]\nSigned-off-by: Kishan Kumar <kishank@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nChange-Id: I1fdcf6664fdc7dce188488f05f33931e3614c853","distinct":true,"url":"https://api.github.com/repos/nychitman1/android_kernel_lge_bullhead/commits/82a808a68bda44d111f99eb91c7132968101c3f8"}]}