{"push_id":2484768166,"size":200,"distinct_size":200,"ref":"refs/heads/8.1.0-unified","head":"fd37d80a44bff404e227861937dfa3a792878e0f","before":"76e42932e306f6688bc176b950d9ae3987a37505","commits":[{"sha":"d6e38b394abd87532a300f89e8f15f1604a1f059","author":{"name":"Nathan Chancellor","email":"f65d3f2dc139dcfe7b6f0b0a466af3bc5fed8fa7@gmail.com"},"message":"diag: Fix misleading indentation warning\n\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/d6e38b394abd87532a300f89e8f15f1604a1f059"},{"sha":"58ef44b9243ceeaeb44f49420e9e537535a9b1c3","author":{"name":"Nathan Chancellor","email":"f65d3f2dc139dcfe7b6f0b0a466af3bc5fed8fa7@gmail.com"},"message":"cpufreq: fallback to interactive if governor is not found\n\nNowadays, custom ROMs are starting to set custom governor profiles via\ninit scripts, often times involving custom governors (like DrunkSauce,\nwhich is impulse on little and ironactive on big). If the user sticks\nwith the built-in kernel, that is totally fine as everything will get\nloaded up properly. However, if the user decides to switch to a custom\nkernel and those governors are not present, this function will fail to\nfind them when and the governor will not change. I attempt to work\naround this by modifying how the method handles finding the governor.\n\nProcess without this patch:\n1. Phone boots with performance governor.\n2. Init scripts attempts to write custom governor to sys path.\n3. The function cpufreq_parse_governor fails to locate the\n   governor and returns -EINVAL since the input was invalid.\n4. The phone does not switch from the performance governor.\n\nProcess with this patch:\n1. Phone boots with performance governor.\n2. Init scripts attempts to write the custom governor to sys path.\n3. The function cpufreq_parse_governor fails to locate the\n   governor but then tries to locate the interactive governor.\n4. The interactive governor is then applied.\n\nA couple of notes:\n1. If you have a different governor that you want to be set on\n   boot, make sure to change interactive to that governor's\n   name.\n2. This is a little bit of a hack; ideally, it'd be nice to\n   only switch to interactive if the current governor is\n   performance so that already applied governors/settings\n   are not overwritten but there is not really a scenario\n   where this will be accidentally be activated since\n   custom kernel tweaking apps will only show governors that\n   are currently available. Maybe when I have more time will\n   I explore this in depth.\n\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/58ef44b9243ceeaeb44f49420e9e537535a9b1c3"},{"sha":"773c7f0933d8f26591d1f66fabcc093c911ea47d","author":{"name":"Johannes Berg","email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com"},"message":"cfg80211: make RATE_INFO_BW_20 the default\n\n\n[ Upstream commit 842be75c77cb72ee546a2b19da9c285fb3ded660 ]\n\nDue to the way I did the RX bitrate conversions in mac80211 with\nspatch, going setting flags to setting the value, many drivers now\ndon't set the bandwidth value for 20 MHz, since with the flags it\nwasn't necessary to (there was no 20 MHz flag, only the others.)\n\nRather than go through and try to fix up all the drivers, instead\nrenumber the enum so that 20 MHz, which is the typical bandwidth,\nactually has the value 0, making those drivers all work again.\n\nIf VHT was hit used with a driver not reporting it, e.g. iwlmvm,\nthis manifested in hitting the bandwidth warning in\ncfg80211_calculate_bitrate_vht().\n\nReported-by: Linus Torvalds <torvalds@linux-foundation.org>\nTested-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/773c7f0933d8f26591d1f66fabcc093c911ea47d"},{"sha":"5c6230241a858905eadbfcbfa19d715191d9d394","author":{"name":"Julia Cartwright","email":"b43b0ad1e8108e7ab870d7a54feac93ae8b8600e@ni.com"},"message":"md/raid5: make use of spin_lock_irq over local_irq_disable + spin_lock\n\n\n[ Upstream commit 3d05f3aed5d721c2c77d20288c29ab26c6193ed5 ]\n\nOn mainline, there is no functional difference, just less code, and\nsymmetric lock/unlock paths.\n\nOn PREEMPT_RT builds, this fixes the following warning, seen by\nAlexander GQ Gerasiov, due to the sleeping nature of spinlocks.\n\n   BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:993\n   in_atomic(): 0, irqs_disabled(): 1, pid: 58, name: kworker/u12:1\n   CPU: 5 PID: 58 Comm: kworker/u12:1 Tainted: G        W       4.9.20-rt16-stand6-686 #1\n   Hardware name: Supermicro SYS-5027R-WRF/X9SRW-F, BIOS 3.2a 10/28/2015\n   Workqueue: writeback wb_workfn (flush-253:0)\n   Call Trace:\n    dump_stack+0x47/0x68\n    ? migrate_enable+0x4a/0xf0\n    ___might_sleep+0x101/0x180\n    rt_spin_lock+0x17/0x40\n    add_stripe_bio+0x4e3/0x6c0 [raid456]\n    ? preempt_count_add+0x42/0xb0\n    raid5_make_request+0x737/0xdd0 [raid456]\n\nReported-by: Alexander GQ Gerasiov <gq@redlab-i.ru>\nTested-by: Alexander GQ Gerasiov <gq@redlab-i.ru>\nSigned-off-by: Julia Cartwright <julia@ni.com>\nSigned-off-by: Shaohua Li <shli@fb.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/5c6230241a858905eadbfcbfa19d715191d9d394"},{"sha":"fdd8b15f86e2f27823f4e4380bd2d4ddfff58cab","author":{"name":"Pan Bian","email":"10d7ad8858c5990f87a888a439b19a315f02cd42@163.com"},"message":"rtc: snvs: fix an incorrect check of return value\n\n\n[ Upstream commit 758929005f06f954b7e1c87a1c9fdb44157b228f ]\n\nFunction devm_regmap_init_mmio() returns an ERR_PTR on error. However,\nin function snvs_rtc_probe() its return value is checked against NULL.\nThis patch fixes it by checking the return value with IS_ERR().\n\nSigned-off-by: Pan Bian <bianpan2016@163.com>\nSigned-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/fdd8b15f86e2f27823f4e4380bd2d4ddfff58cab"},{"sha":"7ea10d0dd2a009352217990e26ea263363f1d9c7","author":{"name":"Josh Poimboeuf","email":"4e2e91f15355af385c021c68a9357f2fd253fb9d@redhat.com"},"message":"x86/asm: Don't use RBP as a temporary register in csum_partial_copy_generic()\n\n\n[ Upstream commit 42fc6c6cb1662ba2fa727dd01c9473c63be4e3b6 ]\n\nAndrey Konovalov reported the following warning while fuzzing the kernel\nwith syzkaller:\n\n  WARNING: kernel stack regs at ffff8800686869f8 in a.out:4933 has bad 'bp' value c3fc855a10167ec0\n\nThe unwinder dump revealed that RBP had a bad value when an interrupt\noccurred in csum_partial_copy_generic().\n\nThat function saves RBP on the stack and then overwrites it, using it as\na scratch register.  That's problematic because it breaks stack traces\nif an interrupt occurs in the middle of the function.\n\nReplace the usage of RBP with another callee-saved register (R15) so\nstack traces are no longer affected.\n\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nTested-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Josh Poimboeuf <jpoimboe@redhat.com>\nCc: Cong Wang <xiyou.wangcong@gmail.com>\nCc: David S . Miller <davem@davemloft.net>\nCc: Dmitry Vyukov <dvyukov@google.com>\nCc: Eric Dumazet <edumazet@google.com>\nCc: Kostya Serebryany <kcc@google.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>\nCc: Neil Horman <nhorman@tuxdriver.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Vlad Yasevich <vyasevich@gmail.com>\nCc: linux-sctp@vger.kernel.org\nCc: netdev <netdev@vger.kernel.org>\nCc: syzkaller <syzkaller@googlegroups.com>\nLink: http://lkml.kernel.org/r/4b03a961efda5ec9bfe46b7b9c9ad72d1efad343.1493909486.git.jpoimboe@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/7ea10d0dd2a009352217990e26ea263363f1d9c7"},{"sha":"88824fe7a89c7dad7fe9e79754a0a1a24fe53117","author":{"name":"Trond Myklebust","email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com"},"message":"NFSv4.1: RECLAIM_COMPLETE must handle NFS4ERR_CONN_NOT_BOUND_TO_SESSION\n\n\n[ Upstream commit 0048fdd06614a4ea088f9fcad11511956b795698 ]\n\nIf the server returns NFS4ERR_CONN_NOT_BOUND_TO_SESSION because we\nare trunking, then RECLAIM_COMPLETE must handle that by calling\nnfs4_schedule_session_recovery() and then retrying.\n\nReported-by: Chuck Lever <chuck.lever@oracle.com>\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nTested-by: Chuck Lever <chuck.lever@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/88824fe7a89c7dad7fe9e79754a0a1a24fe53117"},{"sha":"727631ffc04979fe38434c200cb0d5e04bcc923f","author":{"name":"Bart Van Assche","email":"28563a2d387a4f8f033bf7abbf80937064dfbe0c@sandisk.com"},"message":"IB/srpt: Fix abort handling\n\n\n[ Upstream commit 55d694275f41a1c0eef4ef49044ff29bc3999490 ]\n\nLet the target core check the CMD_T_ABORTED flag instead of the SRP\ntarget driver. Hence remove the transport_check_aborted_status()\ncall. Since state == SRPT_STATE_CMD_RSP_SENT is something that really\nshould not happen, do not try to recover if srpt_queue_response() is\ncalled for an I/O context that is in that state. This patch is a bug\nfix because the srpt_abort_cmd() call is misplaced - if that function\nis called from srpt_queue_response() it should either be called\nbefore the command state is changed or after the response has been\nsent.\n\nSigned-off-by: Bart Van Assche <bart.vanassche@sandisk.com>\nReviewed-by: Hannes Reinecke <hare@suse.com>\nCc: Doug Ledford <dledford@redhat.com>\nCc: Christoph Hellwig <hch@lst.de>\nCc: Andy Grover <agrover@redhat.com>\nCc: David Disseldorp <ddiss@suse.de>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/727631ffc04979fe38434c200cb0d5e04bcc923f"},{"sha":"f477b9157b6f703ae802ada7f5a3438a80b68976","author":{"name":"Steffen Klassert","email":"66deb1d63f85161cc287ce2bac0c65cb5ae958a7@secunet.com"},"message":"af_key: Fix slab-out-of-bounds in pfkey_compile_policy.\n\n\n[ Upstream commit d90c902449a7561f1b1d58ba5a0d11728ce8b0b2 ]\n\nThe sadb_x_sec_len is stored in the unit 'byte divided by eight'.\nSo we have to multiply this value by eight before we can do\nsize checks. Otherwise we may get a slab-out-of-bounds when\nwe memcpy the user sec_ctx.\n\nFixes: df71837d502 (\"[LSM-IPSec]: Security association restriction.\")\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nTested-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Steffen Klassert <steffen.klassert@secunet.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/f477b9157b6f703ae802ada7f5a3438a80b68976"},{"sha":"41a00b47fa91fd4953dfbcbfbd877157a446fd2c","author":{"name":"Luca Coelho","email":"48024ebf6407f04843f8b4062a045f41623c6d61@intel.com"},"message":"mac80211: bail out from prep_connection() if a reconfig is ongoing\n\n\n[ Upstream commit f8860ce836f2d502b07ef99559707fe55d90f5bc ]\n\nIf ieee80211_hw_restart() is called during authentication, the\nauthentication process will continue, causing the driver to be called\nin a wrong state.  This ultimately causes an oops in the iwlwifi\ndriver (at least).\n\nThis fixes bugzilla 195299 partly.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195299\nSigned-off-by: Luca Coelho <luciano.coelho@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/41a00b47fa91fd4953dfbcbfbd877157a446fd2c"},{"sha":"a1db0c29e6d38e876098041896b855288d8f2dd6","author":{"name":"Kees Cook","email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org"},"message":"bna: Avoid reading past end of buffer\n\n\n[ Upstream commit 9e4eb1ce472fbf7b007f23c88ec11c37265e401c ]\n\nUsing memcpy() from a string that is shorter than the length copied means\nthe destination buffer is being filled with arbitrary data from the kernel\nrodata segment. Instead, use strncpy() which will fill the trailing bytes\nwith zeros.\n\nThis was found with the future CONFIG_FORTIFY_SOURCE feature.\n\nCc: Daniel Micay <danielmicay@gmail.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/a1db0c29e6d38e876098041896b855288d8f2dd6"},{"sha":"c2e24f7b2ef0fa2ba5c95fc057959d9e8c73e8b8","author":{"name":"Kees Cook","email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org"},"message":"qlge: Avoid reading past end of buffer\n\n\n[ Upstream commit df5303a8aa9a0a6934f4cea7427f1edf771f21c2 ]\n\nUsing memcpy() from a string that is shorter than the length copied means\nthe destination buffer is being filled with arbitrary data from the kernel\nrodata segment. Instead, use strncpy() which will fill the trailing bytes\nwith zeros.\n\nThis was found with the future CONFIG_FORTIFY_SOURCE feature.\n\nCc: Daniel Micay <danielmicay@gmail.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/c2e24f7b2ef0fa2ba5c95fc057959d9e8c73e8b8"},{"sha":"008da9d04c57dc4def240b15b0bbed112fe7f420","author":{"name":"Dan Carpenter","email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com"},"message":"ipmi_ssif: unlock on allocation failure\n\n\n[ Upstream commit cf9806f32ef63b745f2486e0dbb2ac21f4ca44f0 ]\n\nWe should unlock and re-enable IRQs if this allocation fails.\n\nFixes: 259307074bfc (\"ipmi: Add SMBus interface driver (SSIF) \")\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Corey Minyard <cminyard@mvista.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/008da9d04c57dc4def240b15b0bbed112fe7f420"},{"sha":"c81deea4de1c24a8613ce1ee25aaee5f99098fdf","author":{"name":"Jim Baxter","email":"5388595df52a9cd8d1ed1943eb39f79d18e5bc10@mentor.com"},"message":"net: cdc_ncm: Fix TX zero padding\n\n\n[ Upstream commit aeca3a77b1e0ed06a095933b89c86aed007383eb ]\n\nThe zero padding that is added to NTB's does\nnot zero the memory correctly.\nThis is because the skb_put modifies the value\nof skb_out->len which results in the memset\ncommand not setting any memory to zero as\n(ctx->tx_max - skb_out->len) == 0.\n\nI have resolved this by storing the size of\nthe memory to be zeroed before the skb_put\nand using this in the memset call.\n\nSigned-off-by: Jim Baxter <jim_baxter@mentor.com>\nReviewed-by: Bjørn Mork <bjorn@mork.no>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/c81deea4de1c24a8613ce1ee25aaee5f99098fdf"},{"sha":"246db5901f4a7f0823a37ff0aa4237813bf44e81","author":{"name":"Grygorii Strashko","email":"bfa0a1520768723a1c60e18250fb841c342eb8d8@ti.com"},"message":"net: ethernet: ti: cpsw: adjust cpsw fifos depth for fullduplex flow control\n\n\n[ Upstream commit 48f5bccc60675f8426a6159935e8636a1fd89f56 ]\n\nWhen users set flow control using ethtool the bits are set properly in the\nCPGMAC_SL MACCONTROL register, but the FIFO depth in the respective Port n\nMaximum FIFO Blocks (Pn_MAX_BLKS) registers remains set to the minimum size\nreset value. When receive flow control is enabled on a port, the port's\nassociated FIFO block allocation must be adjusted. The port RX allocation\nmust increase to accommodate the flow control runout. The TRM recommends\nnumbers of 5 or 6.\n\nHence, apply required Port FIFO configuration to\nPn_MAX_BLKS.Pn_TX_MAX_BLKS=0xF and Pn_MAX_BLKS.Pn_RX_MAX_BLKS=0x5 during\ninterface initialization.\n\nCc: Schuyler Patton <spatton@ti.com>\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/246db5901f4a7f0823a37ff0aa4237813bf44e81"},{"sha":"f1d74fa2dbb1d447fd62de91872cff5a4d5b442a","author":{"name":"J. Bruce Fields","email":"51738506c1b2ccb0761f23bdc612c93babf738ea@redhat.com"},"message":"lockd: fix lockd shutdown race\n\n\n[ Upstream commit efda760fe95ea15291853c8fa9235c32d319cd98 ]\n\nAs reported by David Jeffery: \"a signal was sent to lockd while lockd\nwas shutting down from a request to stop nfs.  The signal causes lockd\nto call restart_grace() which puts the lockd_net structure on the grace\nlist.  If this signal is received at the wrong time, it will occur after\nlockd_down_net() has called locks_end_grace() but before\nlockd_down_net() stops the lockd thread.  This leads to lockd putting\nthe lockd_net structure back on the grace list, then exiting without\nanything removing it from the list.\"\n\nSo, perform the final locks_end_grace() from the the lockd thread; this\nensures it's serialized with respect to restart_grace().\n\nReported-by: David Jeffery <djeffery@redhat.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/f1d74fa2dbb1d447fd62de91872cff5a4d5b442a"},{"sha":"7ada1278f772af126426d9649cdbc2236b71d77e","author":{"name":"Dan Carpenter","email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com"},"message":"drivers/misc/vmw_vmci/vmci_queue_pair.c: fix a couple integer overflow tests\n\n\n[ Upstream commit 146180c052a00172f4dc08eaade836fd02f61fb5 ]\n\nThe \"DIV_ROUND_UP(size, PAGE_SIZE)\" operation can overflow if \"size\" is\nmore than ULLONG_MAX - PAGE_SIZE.\n\nLink: http://lkml.kernel.org/r/20170322111950.GA11279@mwanda\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nCc: Jorgen Hansen <jhansen@vmware.com>\nCc: Masahiro Yamada <yamada.masahiro@socionext.com>\nCc: Michal Hocko <mhocko@suse.com>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/7ada1278f772af126426d9649cdbc2236b71d77e"},{"sha":"b355536c1f6257103fc0a0c8b234bef2737164c3","author":{"name":"Kirill Tkhai","email":"e5b39230c99b4d3ebd6aa54f6d823f95134bc39d@virtuozzo.com"},"message":"pidns: disable pid allocation if pid_ns_prepare_proc() is failed in alloc_pid()\n\n\n[ Upstream commit 8896c23d2ef803f1883fea73117a435925c2b4c4 ]\n\nalloc_pidmap() advances pid_namespace::last_pid.  When first pid\nallocation fails, then next created process will have pid 2 and\npid_ns_prepare_proc() won't be called.  So, pid_namespace::proc_mnt will\nnever be initialized (not to mention that there won't be a child\nreaper).\n\nI saw crash stack of such case on kernel 3.10:\n\n    BUG: unable to handle kernel NULL pointer dereference at (null)\n    IP: proc_flush_task+0x8f/0x1b0\n    Call Trace:\n        release_task+0x3f/0x490\n        wait_consider_task.part.10+0x7ff/0xb00\n        do_wait+0x11f/0x280\n        SyS_wait4+0x7d/0x110\n\nWe may fix this by restore of last_pid in 0 or by prohibiting of futher\nallocations.  Since there was a similar issue in Oleg Nesterov's commit\n314a8ad0f18a (\"pidns: fix free_pid() to handle the first fork failure\").\nand it was fixed via prohibiting allocation, let's follow this way, and\ndo the same.\n\nLink: http://lkml.kernel.org/r/149201021004.4863.6762095011554287922.stgit@localhost.localdomain\nSigned-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>\nAcked-by: Cyrill Gorcunov <gorcunov@openvz.org>\nCc: Andrei Vagin <avagin@virtuozzo.com>\nCc: Andreas Gruenbacher <agruenba@redhat.com>\nCc: Kees Cook <keescook@chromium.org>\nCc: Michael Kerrisk <mtk.manpages@googlemail.com>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Paul Moore <paul@paul-moore.com>\nCc: Eric Biederman <ebiederm@xmission.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Serge Hallyn <serge@hallyn.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/b355536c1f6257103fc0a0c8b234bef2737164c3"},{"sha":"cebe1ddda977b57011fa788e6a18c5e1a66977de","author":{"name":"Heiko Carstens","email":"8dcf0f69152f32f23184f83357a3731522e56b9c@de.ibm.com"},"message":"s390: move _text symbol to address higher than zero\n\n\n[ Upstream commit d04a4c76f71dd5335f8e499b59617382d84e2b8d ]\n\nThe perf tool assumes that kernel symbols are never present at address\nzero. In fact it assumes if functions that map symbols to addresses\nreturn zero, that the symbol was not found.\n\nGiven that s390's _text symbol historically is located at address zero\nthis yields at least a couple of false errors and warnings in one of\nperf's test cases about not present symbols (\"perf test 1\").\n\nTo fix this simply move the _text symbol to address 0x200, just behind\nthe initial psw and channel program located at the beginning of the\nkernel image. This is now hard coded within the linker script.\n\nI tried a nicer solution which moves the initial psw and channel\nprogram into an own section. However that would move the symbols\nwithin the \"real\" head.text section to different addresses, since the\n\".org\" statements within head.S are relative to the head.text\nsection. If there is a new section in front, everything else will be\nmoved. Alternatively I could have adjusted all \".org\" statements. But\nthis current solution seems to be the easiest one, since nobody really\ncares where the _text symbol is actually located.\n\nReported-by: Zvonko Kosic <zkosic@linux.vnet.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/cebe1ddda977b57011fa788e6a18c5e1a66977de"},{"sha":"ecd9a27e6d4aaaf64563daf98201cf19a94890bf","author":{"name":"Talat Batheesh","email":"379516cd0d56f969290cc4bc3774b7586d2e10bf@mellanox.com"},"message":"net/mlx4_en: Avoid adding steering rules with invalid ring\n\n\n[ Upstream commit 89c557687a32c294e9d25670a96e9287c09f2d5f ]\n\nInserting steering rules with illegal ring is an invalid operation,\nblock it.\n\nFixes: 820672812f82 ('net/mlx4_en: Manage flow steering rules with ethtool')\nSigned-off-by: Talat Batheesh <talatb@mellanox.com>\nSigned-off-by: Tariq Toukan <tariqt@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mTresk/android_kernel_oneplus_msm8998/commits/ecd9a27e6d4aaaf64563daf98201cf19a94890bf"}]}
{"actor":{"display_login":"mTresk"}}