{"push_id":2181073479,"size":14,"distinct_size":14,"ref":"refs/heads/oos_o","head":"6bc905434eb405c5dcf5cf80f7b65d26e79248df","before":"a2a3e1e715d12733bc896ec21444c8358628b282","commits":[{"sha":"9b07ce82d6469aefca6c9b79e791d1862bb9175d","author":{"name":"Suraj Das","email":"d5e926a3de4d9f3f8a025f5af523fa2e0ea96e5a@gmail.com"},"message":"update defconfig","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/9b07ce82d6469aefca6c9b79e791d1862bb9175d"},{"sha":"28ea71e2993866d5f45c9dd139ba53f197e5ea19","author":{"name":"fluxi","email":"95ab61bb01957fc548ef82d227666a28af3268a6@arcor.de"},"message":"msm: Fix Kconfig warnings\n\nChange-Id: I710d6e534ac0a5a94f2a3cf38c987ddf74841446\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/28ea71e2993866d5f45c9dd139ba53f197e5ea19"},{"sha":"5316b13d0220b215c4627cbb82a027f23e030543","author":{"name":"James Christopher Adduono","email":"6b3cf6f314263a52d028bd1a1c381fb1c2b231cc@adduono.com"},"message":"Satisfy GCC (and some bug fixes)\n\nChange-Id: I91e83476b195b4f971b576d06a7079f5409bd18d\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/5316b13d0220b215c4627cbb82a027f23e030543"},{"sha":"b436142b4223219db3cbedf01f68dff73ad520c1","author":{"name":"fluxi","email":"95ab61bb01957fc548ef82d227666a28af3268a6@arcor.de"},"message":"net: sch_generic: Allow devices to opt-out net watchdog\n\nThis enables QCOM commit 43b54948 \"net: rmnet_data: Remove\nwatchdog_timeo\".\n\nIf no watchdog_timeo value is set, we end up with a 5*HZ\ncheck interval instead of disabling the rmnet watchdog\nentirely (as obviously intended).\n\nChange-Id: Ia59f093e940bda9bcd4115d4641d10481158886f\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/b436142b4223219db3cbedf01f68dff73ad520c1"},{"sha":"a6293415eaddc91c09e9b8834e9bc4623c557213","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"time: Remove CONFIG_TIMER_STATS\n\nCurrently CONFIG_TIMER_STATS exposes process information across namespaces:\n\nkernel/time/timer_list.c print_timer():\n\n        SEQ_printf(m, \", %s/%d\", tmp, timer->start_pid);\n\n/proc/timer_list:\n\n #11: <0000000000000000>, hrtimer_wakeup, S:01, do_nanosleep, cron/2570\n\nGiven that the tracer can give the same information, this patch entirely\nremoves CONFIG_TIMER_STATS.\n\nChange-Id: Ice26d74094d3ad563808342c1604ad444234844b\nSuggested-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nAcked-by: John Stultz <john.stultz@linaro.org>\nCc: Nicolas Pitre <nicolas.pitre@linaro.org>\nCc: linux-doc@vger.kernel.org\nCc: Lai Jiangshan <jiangshanlai@gmail.com>\nCc: Shuah Khan <shuah@kernel.org>\nCc: Xing Gao <xgao01@email.wm.edu>\nCc: Jonathan Corbet <corbet@lwn.net>\nCc: Jessica Frazelle <me@jessfraz.com>\nCc: kernel-hardening@lists.openwall.com\nCc: Nicolas Iooss <nicolas.iooss_linux@m4x.org>\nCc: \"Paul E. McKenney\" <paulmck@linux.vnet.ibm.com>\nCc: Petr Mladek <pmladek@suse.com>\nCc: Richard Cochran <richardcochran@gmail.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: Michal Marek <mmarek@suse.com>\nCc: Josh Poimboeuf <jpoimboe@redhat.com>\nCc: Dmitry Vyukov <dvyukov@google.com>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: \"Eric W. Biederman\" <ebiederm@xmission.com>\nCc: Olof Johansson <olof@lixom.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: linux-api@vger.kernel.org\nCc: Arjan van de Ven <arjan@linux.intel.com>\nLink: http://lkml.kernel.org/r/20170208192659.GA32582@beast\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/a6293415eaddc91c09e9b8834e9bc4623c557213"},{"sha":"a21a794ec4fefab68ba1c1b7a7cba945120cfe25","author":{"name":"engstk","email":"ca84e5b0a34d566f438b94c1542ee60e8df448e3@sapo.pt"},"message":"defconfig: remove CONFIG_TIMER_STATS\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/a21a794ec4fefab68ba1c1b7a7cba945120cfe25"},{"sha":"733e1953770591f21c4d9a3dfb5995e8b26107da","author":{"name":"Davidlohr Bueso","email":"b4cea4bb99b2bfe98580e8a1404151e1fa946999@stgolabs.net"},"message":"ipc/shm: Fix shmat mmap nil-page protection\n\nThe issue is described here, with a nice testcase:\n\n    https://bugzilla.kernel.org/show_bug.cgi?id=192931\n\nThe problem is that shmat() calls do_mmap_pgoff() with MAP_FIXED, and\nthe address rounded down to 0.  For the regular mmap case, the\nprotection mentioned above is that the kernel gets to generate the\naddress -- arch_get_unmapped_area() will always check for MAP_FIXED and\nreturn that address.  So by the time we do security_mmap_addr(0) things\nget funky for shmat().\n\nThe testcase itself shows that while a regular user crashes, root will\nnot have a problem attaching a nil-page.  There are two possible fixes\nto this.  The first, and which this patch does, is to simply allow root\nto crash as well -- this is also regular mmap behavior, ie when hacking\nup the testcase and adding mmap(...  |MAP_FIXED).  While this approach\nis the safer option, the second alternative is to ignore SHM_RND if the\nrounded address is 0, thus only having MAP_SHARED flags.  This makes the\nbehavior of shmat() identical to the mmap() case.  The downside of this\nis obviously user visible, but does make sense in that it maintains\nsemantics after the round-down wrt 0 address and mmap.\n\nPasses shm related ltp tests.\n\nChange-Id: I47b065f965427409642892fb139d89fb5603b187\nLink: http://lkml.kernel.org/r/1486050195-18629-1-git-send-email-dave@stgolabs.net\nSigned-off-by: Davidlohr Bueso <dbueso@suse.de>\nReported-by: Gareth Evans <gareth.evans@contextis.co.uk>\nCc: Manfred Spraul <manfred@colorfullife.com>\nCc: Michael Kerrisk <mtk.manpages@googlemail.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/733e1953770591f21c4d9a3dfb5995e8b26107da"},{"sha":"af291e795fd4a6d6b5ba1bf68c3c702dc85e6d74","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race\n\ncommit 321027c1fe77f892f4ea07846aeae08cefbbb290 upstream.\n\nDi Shen reported a race between two concurrent sys_perf_event_open()\ncalls where both try and move the same pre-existing software group\ninto a hardware context.\n\nThe problem is exactly that described in commit:\n\n  d91cb84915dabffb3f7e15c326a0016c272e01d1 (\"perf: Fix event->ctx locking\")\n\n... where, while we wait for a ctx->mutex acquisition, the event->ctx\nrelation can have changed under us.\n\nThat very same commit failed to recognise sys_perf_event_context() as an\nexternal access vector to the events and thereby didn't apply the\nestablished locking rules correctly.\n\nSo while one sys_perf_event_open() call is stuck waiting on\nmutex_lock_double(), the other (which owns said locks) moves the group\nabout. So by the time the former sys_perf_event_open() acquires the\nlocks, the context we've acquired is stale (and possibly dead).\n\nApply the established locking rules as per perf_event_ctx_lock_nested()\nto the mutex_lock_double() for the 'move_group' case. This obviously means\nwe need to validate state after we acquire the locks.\n\nChange-Id: Ia490bc004a059995162beff246210082bc941766\nReported-by: Di Shen (Keen Lab)\nTested-by: John Dias <joaodias@google.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Arnaldo Carvalho de Melo <acme@kernel.org>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Kees Cook <keescook@chromium.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Min Chong <mchong@google.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Vince Weaver <vincent.weaver@maine.edu>\nFixes: f63a8daa5812 (\"perf: Fix event->ctx locking\")\nLink: http://lkml.kernel.org/r/20170106131444.GZ3174@twins.programming.kicks-ass.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[bwh: Backported to 3.2:\n - Use ACCESS_ONCE() instead of READ_ONCE()\n - Test perf_event::group_flags instead of group_caps\n - Add the err_locked cleanup block, which we didn't need before\n - Adjust context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: engstk <eng.stk@sapo.pt>\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/af291e795fd4a6d6b5ba1bf68c3c702dc85e6d74"},{"sha":"9522109be135d6360cc59ea070b1a2934059045f","author":{"name":"David S. Miller","email":"79caf591e37e1438a2d55ae59670d5cd0d717764@davemloft.net"},"message":"irda: Fix lockdep annotations in hashbin_delete().\n\nA nested lock depth was added to the hasbin_delete() code but it\ndoesn't actually work some well and results in tons of lockdep splats.\n\nFix the code instead to properly drop the lock around the operation\nand just keep peeking the head of the hashbin queue.\n\nChange-Id: I0cb630739aa44b9e7c4a5b775e906713775f13ef\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nTested-by: Dmitry Vyukov <dvyukov@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/9522109be135d6360cc59ea070b1a2934059045f"},{"sha":"bc3b0905fdbf1cfea38a4826e08adbe3d07264ce","author":{"name":"Francisco Franco","email":"0ac3193ff3d7b4e68ae404d59f776924e2be9ac9@gmail.com"},"message":"net: wireless: remove WARN_ON since it clutter kmsg logs\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/bc3b0905fdbf1cfea38a4826e08adbe3d07264ce"},{"sha":"ad9e8aa7bf7c342920f682ce5b2d5a8ccfa62456","author":{"name":"Sultanxda","email":"2a26fc11866c4c85a6bb605251817c00bbab3213@gmail.com"},"message":"PM / devfreq: Add a governor white list\n\nMany of the devfreq governors compiled in are unstable/incomplete, so we\ndon't want users switching to them. Compiling out the unused governors is\nmessy because many other drivers link to them, and there are not proper\n#ifdefs in place.\n\nAdd a white list of the only governors intended for use to the governor\nsysfs node in order to prevent users from enabling governors that unstable.\n\nSigned-off-by: Sultanxda <sultanxda@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/ad9e8aa7bf7c342920f682ce5b2d5a8ccfa62456"},{"sha":"86840934b65a77d124bc399bf3e372ff93c40447","author":{"name":"Nathan Chancellor","email":"b2febe722de126fdca89e2e24ca48c984e7dc9fc@gmail.com"},"message":"OP3T: Fix frequencies sticking at max with GCC 6 and 7\n\nLeaving these variables uninitialized yielded some interesting\nresults... I believe it is due to GCC optimization in later\nupdates (as adding -DDEBUG to the makefile also fixed it though\nI couldn't reproduce down to -O1). Without this patch, the min_index\nwill pretty much always be 21, resulting in the CPU getting pegged\nat its max value and never coming down. With this patch, GCC 4.9 and\nGCC 7.2 perform the same, as verified with logging.\n\nAlso, fix a boolean fail (!ret means equal to zero which is the\nexpected return value for that function) and a Windows carriage\nreturn (lol).\n\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/86840934b65a77d124bc399bf3e372ff93c40447"},{"sha":"70de49306020b1d9b77365ac19f3bbd46752fd74","author":{"name":"zx2c4","email":"d0f0a483cfc1e8d71178797f3ea2459585e195fb@kernel.org"},"message":"net: add WireGuard 0.0.20171127\n\nAdapted for 3.18 tree by eng.stk\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/70de49306020b1d9b77365ac19f3bbd46752fd74"},{"sha":"6bc905434eb405c5dcf5cf80f7b65d26e79248df","author":{"name":"engstk","email":"ca84e5b0a34d566f438b94c1542ee60e8df448e3@sapo.pt"},"message":"defconfig: enable wireguard\n\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/surajdazz/android_kernel_oneplus_msm8996/commits/6bc905434eb405c5dcf5cf80f7b65d26e79248df"}]}
{"actor":{"display_login":"surajdazz"}}