{"push_id":2843886028,"size":248,"distinct_size":0,"ref":"refs/heads/caf/aosp-new/android-4.4","head":"7e85a4b796e80a224b48a524d1efb0485d8b0602","before":"139622602304abdded7433a218d8a499822c7c19","commits":[{"sha":"760fed99e2bfcf0c4c7b1880ebbe19fdb4d9738a","author":{"name":"Quinn Tran","email":"a02f5c47ee09ecfb205631316fdc727ed52eb140@cavium.com"},"message":"scsi: qla2xxx: Fix ISP recovery on unload\n\ncommit b08abbd9f5996309f021684f9ca74da30dcca36a upstream.\n\nDuring unload process, the chip can encounter problem where a FW dump would\nbe captured. For this case, the full reset sequence will be skip to bring\nthe chip back to full operational state.\n\nFixes: e315cd28b9ef (\"[SCSI] qla2xxx: Code changes for qla data structure refactoring\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Quinn Tran <quinn.tran@cavium.com>\nSigned-off-by: Himanshu Madhani <himanshu.madhani@cavium.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/760fed99e2bfcf0c4c7b1880ebbe19fdb4d9738a"},{"sha":"468926f8dbb747b2612459113a926be404c9a6d6","author":{"name":"Anil Gurumurthy","email":"8232ec98ab8c1cce5a65c8f10bee6666d72e75d0@cavium.com"},"message":"scsi: qla2xxx: Return error when TMF returns\n\ncommit b4146c4929ef61d5afca011474d59d0918a0cd82 upstream.\n\nPropagate the task management completion status properly to avoid\nunnecessary waits for commands to complete.\n\nFixes: faef62d13463 (\"[SCSI] qla2xxx: Fix Task Management command asynchronous handling\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Anil Gurumurthy <anil.gurumurthy@cavium.com>\nSigned-off-by: Himanshu Madhani <himanshu.madhani@cavium.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/468926f8dbb747b2612459113a926be404c9a6d6"},{"sha":"09a0de491c5ec0e40f8f9d21b13af306667360f4","author":{"name":"Thomas Gleixner","email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de"},"message":"genirq: Make force irq threading setup more robust\n\ncommit d1f0301b3333eef5efbfa1fe0f0edbea01863d5d upstream.\n\nThe support of force threading interrupts which are set up with both a\nprimary and a threaded handler wreckaged the setup of regular requested\nthreaded interrupts (primary handler == NULL).\n\nThe reason is that it does not check whether the primary handler is set to\nthe default handler which wakes the handler thread. Instead it replaces the\nthread handler with the primary handler as it would do with force threaded\ninterrupts which have been requested via request_irq(). So both the primary\nand the thread handler become the same which then triggers the warnon that\nthe thread handler tries to wakeup a not configured secondary thread.\n\nFortunately this only happens when the driver omits the IRQF_ONESHOT flag\nwhen requesting the threaded interrupt, which is normaly caught by the\nsanity checks when force irq threading is disabled.\n\nFix it by skipping the force threading setup when a regular threaded\ninterrupt is requested. As a consequence the interrupt request which lacks\nthe IRQ_ONESHOT flag is rejected correctly instead of silently wreckaging\nit.\n\nFixes: 2a1d3ab8986d (\"genirq: Handle force threading of irqs with primary and thread handler\")\nReported-by: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nTested-by: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/09a0de491c5ec0e40f8f9d21b13af306667360f4"},{"sha":"0a022859e2304b21a6cd620c2eb008cc60de0ab8","author":{"name":"Anna-Maria Gleixner","email":"f9bac0f0e30e9cf4bb848bd8d45768c85995065f@linutronix.de"},"message":"nohz: Fix local_timer_softirq_pending()\n\ncommit 80d20d35af1edd632a5e7a3b9c0ab7ceff92769e upstream.\n\nlocal_timer_softirq_pending() checks whether the timer softirq is\npending with: local_softirq_pending() & TIMER_SOFTIRQ.\n\nThis is wrong because TIMER_SOFTIRQ is the softirq number and not a\nbitmask. So the test checks for the wrong bit.\n\nUse BIT(TIMER_SOFTIRQ) instead.\n\nFixes: 5d62c183f9e9 (\"nohz: Prevent a timer interrupt storm in tick_nohz_stop_sched_tick()\")\nSigned-off-by: Anna-Maria Gleixner <anna-maria@linutronix.de>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nReviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nReviewed-by: Daniel Bristot de Oliveira <bristot@redhat.com>\nAcked-by: Frederic Weisbecker <frederic@kernel.org>\nCc: bigeasy@linutronix.de\nCc: peterz@infradead.org\nCc: stable@vger.kernel.org\nLink: https://lkml.kernel.org/r/20180731161358.29472-1-anna-maria@linutronix.de\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/0a022859e2304b21a6cd620c2eb008cc60de0ab8"},{"sha":"52296ab92b66e2a8c932b2a4cb318dd08cb8bd29","author":{"name":"Dmitry Safonov","email":"bed3f98d0a894717be46c58ffa90302af9946688@arista.com"},"message":"netlink: Do not subscribe to non-existent groups\n\n[ Upstream commit 7acf9d4237c46894e0fa0492dd96314a41742e84 ]\n\nMake ABI more strict about subscribing to group > ngroups.\nCode doesn't check for that and it looks bogus.\n(one can subscribe to non-existing group)\nStill, it's possible to bind() to all possible groups with (-1)\n\nCc: \"David S. Miller\" <davem@davemloft.net>\nCc: Herbert Xu <herbert@gondor.apana.org.au>\nCc: Steffen Klassert <steffen.klassert@secunet.com>\nCc: netdev@vger.kernel.org\nSigned-off-by: Dmitry Safonov <dima@arista.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/52296ab92b66e2a8c932b2a4cb318dd08cb8bd29"},{"sha":"bc48f46f117e05af226a4c0dff617218f1c13650","author":{"name":"Dmitry Safonov","email":"bed3f98d0a894717be46c58ffa90302af9946688@arista.com"},"message":"netlink: Don't shift with UB on nlk->ngroups\n\n[ Upstream commit 61f4b23769f0cc72ae62c9a81cf08f0397d40da8 ]\n\nOn i386 nlk->ngroups might be 32 or 0. Which leads to UB, resulting in\nhang during boot.\nCheck for 0 ngroups and use (unsigned long long) as a type to shift.\n\nFixes: 7acf9d4237c4 (\"netlink: Do not subscribe to non-existent groups\").\nReported-by: kernel test robot <rong.a.chen@intel.com>\nSigned-off-by: Dmitry Safonov <dima@arista.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/bc48f46f117e05af226a4c0dff617218f1c13650"},{"sha":"a5928d68418768e3e7ed9c75039060c1e70e047e","author":{"name":"Dmitry Safonov","email":"bed3f98d0a894717be46c58ffa90302af9946688@arista.com"},"message":"netlink: Don't shift on 64 for ngroups\n\ncommit 91874ecf32e41b5d86a4cb9d60e0bee50d828058 upstream.\n\nIt's legal to have 64 groups for netlink_sock.\n\nAs user-supplied nladdr->nl_groups is __u32, it's possible to subscribe\nonly to first 32 groups.\n\nThe check for correctness of .bind() userspace supplied parameter\nis done by applying mask made from ngroups shift. Which broke Android\nas they have 64 groups and the shift for mask resulted in an overflow.\n\nFixes: 61f4b23769f0 (\"netlink: Don't shift with UB on nlk->ngroups\")\nCc: \"David S. Miller\" <davem@davemloft.net>\nCc: Herbert Xu <herbert@gondor.apana.org.au>\nCc: Steffen Klassert <steffen.klassert@secunet.com>\nCc: netdev@vger.kernel.org\nCc: stable@vger.kernel.org\nReported-and-Tested-by: Nathan Chancellor <natechancellor@gmail.com>\nSigned-off-by: Dmitry Safonov <dima@arista.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/a5928d68418768e3e7ed9c75039060c1e70e047e"},{"sha":"310eba0dfc8a7d5423516df7f4be7451505ac6ef","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: fix false negatives *and* false positives in ext4_check_descriptors()\n\ncommit 44de022c4382541cebdd6de4465d1f4f465ff1dd upstream.\n\nExt4_check_descriptors() was getting called before s_gdb_count was\ninitialized.  So for file systems w/o the meta_bg feature, allocation\nbitmaps could overlap the block group descriptors and ext4 wouldn't\nnotice.\n\nFor file systems with the meta_bg feature enabled, there was a\nfencepost error which would cause the ext4_check_descriptors() to\nincorrectly believe that the block allocation bitmap overlaps with the\nblock group descriptor blocks, and it would reject the mount.\n\nFix both of these problems.\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org\nSigned-off-by: Benjamin Gilbert <bgilbert@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/310eba0dfc8a7d5423516df7f4be7451505ac6ef"},{"sha":"fef9866d278ee726b15cf251339660e77ba5488c","author":{"name":"Vitaly Kuznetsov","email":"282517a3cdaae14e79e6d52f012bddb9ec2b7f0e@redhat.com"},"message":"ACPI / PCI: Bail early in acpi_pci_add_bus() if there is no ACPI handle\n\ncommit a0040c0145945d3bd203df8fa97f6dfa819f3f7d upstream.\n\nHyper-V instances support PCI pass-through which is implemented through PV\npci-hyperv driver. When a device is passed through, a new root PCI bus is\ncreated in the guest. The bus sits on top of VMBus and has no associated\ninformation in ACPI. acpi_pci_add_bus() in this case proceeds all the way\nto acpi_evaluate_dsm(), which reports\n\n  ACPI: \\: failed to evaluate _DSM (0x1001)\n\nWhile acpi_pci_slot_enumerate() and acpiphp_enumerate_slots() are protected\nagainst ACPI_HANDLE() being NULL and do nothing, acpi_evaluate_dsm() is not\nand gives us the error. It seems the correct fix is to not do anything in\nacpi_pci_add_bus() in such cases.\n\nSigned-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nCc: Sinan Kaya <okaya@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/fef9866d278ee726b15cf251339660e77ba5488c"},{"sha":"731ccd90b8dc6697fefb62f43ed6f8d253d7fd5b","author":{"name":"Masami Hiramatsu","email":"308c3db2ad395e67f502db11a9ceb1603d4442e0@kernel.org"},"message":"ring_buffer: tracing: Inherit the tracing setting to next ring buffer\n\ncommit 73c8d8945505acdcbae137c2e00a1232e0be709f upstream.\n\nMaintain the tracing on/off setting of the ring_buffer when switching\nto the trace buffer snapshot.\n\nTaking a snapshot is done by swapping the backup ring buffer\n(max_tr_buffer). But since the tracing on/off setting is defined\nby the ring buffer, when swapping it, the tracing on/off setting\ncan also be changed. This causes a strange result like below:\n\n  /sys/kernel/debug/tracing # cat tracing_on\n  1\n  /sys/kernel/debug/tracing # echo 0 > tracing_on\n  /sys/kernel/debug/tracing # cat tracing_on\n  0\n  /sys/kernel/debug/tracing # echo 1 > snapshot\n  /sys/kernel/debug/tracing # cat tracing_on\n  1\n  /sys/kernel/debug/tracing # echo 1 > snapshot\n  /sys/kernel/debug/tracing # cat tracing_on\n  0\n\nWe don't touch tracing_on, but snapshot changes tracing_on\nsetting each time. This is an anomaly, because user doesn't know\nthat each \"ring_buffer\" stores its own tracing-enable state and\nthe snapshot is done by swapping ring buffers.\n\nLink: http://lkml.kernel.org/r/153149929558.11274.11730609978254724394.stgit@devbox\n\nCc: Ingo Molnar <mingo@redhat.com>\nCc: Shuah Khan <shuah@kernel.org>\nCc: Tom Zanussi <tom.zanussi@linux.intel.com>\nCc: Hiraku Toyooka <hiraku.toyooka@cybertrust.co.jp>\nCc: stable@vger.kernel.org\nFixes: debdd57f5145 (\"tracing: Make a snapshot feature available from userspace\")\nSigned-off-by: Masami Hiramatsu <mhiramat@kernel.org>\n[ Updated commit log and comment in the code ]\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/731ccd90b8dc6697fefb62f43ed6f8d253d7fd5b"},{"sha":"a8ec97dbac9027f2f4158aadf86010edc2a9ea5d","author":{"name":"Esben Haabendal","email":"cf68e657b0c4cf2832f46ae230fca76272da41f1@deif.com"},"message":"i2c: imx: Fix reinit_completion() use\n\ncommit 9f9e3e0d4dd3338b3f3dde080789f71901e1e4ff upstream.\n\nMake sure to call reinit_completion() before dma is started to avoid race\ncondition where reinit_completion() is called after complete() and before\nwait_for_completion_timeout().\n\nSigned-off-by: Esben Haabendal <eha@deif.com>\nFixes: ce1a78840ff7 (\"i2c: imx: add DMA support for freescale i2c driver\")\nReviewed-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nCc: stable@kernel.org\nSigned-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/a8ec97dbac9027f2f4158aadf86010edc2a9ea5d"},{"sha":"0749d5b3ec62310b747751ea7d4d5ccca51bc80f","author":{"name":"Shankara Pailoor","email":"441886e34aaa4ed284238e32fdd27abc960c4bb2@gmail.com"},"message":"jfs: Fix inconsistency between memory allocation and ea_buf->max_size\n\ncommit 92d34134193e5b129dc24f8d79cb9196626e8d7a upstream.\n\nThe code is assuming the buffer is max_size length, but we weren't\nallocating enough space for it.\n\nSigned-off-by: Shankara Pailoor <shankarapailoor@gmail.com>\nSigned-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/0749d5b3ec62310b747751ea7d4d5ccca51bc80f"},{"sha":"8404ae6c8c9ff23a06cf38112e83002e1088bfe1","author":{"name":"Greg Kroah-Hartman","email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org"},"message":"Linux 4.4.147","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/8404ae6c8c9ff23a06cf38112e83002e1088bfe1"},{"sha":"a5fc66599b6143999290603a51da11868f7d36a9","author":{"name":"Greg Kroah-Hartman","email":"4645f7897fd33786a2ee1264d590b3c400559d85@google.com"},"message":"Merge 4.4.147 into android-4.4\n\nChanges in 4.4.147\n\tscsi: qla2xxx: Fix ISP recovery on unload\n\tscsi: qla2xxx: Return error when TMF returns\n\tgenirq: Make force irq threading setup more robust\n\tnohz: Fix local_timer_softirq_pending()\n\tnetlink: Do not subscribe to non-existent groups\n\tnetlink: Don't shift with UB on nlk->ngroups\n\tnetlink: Don't shift on 64 for ngroups\n\text4: fix false negatives *and* false positives in ext4_check_descriptors()\n\tACPI / PCI: Bail early in acpi_pci_add_bus() if there is no ACPI handle\n\tring_buffer: tracing: Inherit the tracing setting to next ring buffer\n\ti2c: imx: Fix reinit_completion() use\n\tjfs: Fix inconsistency between memory allocation and ea_buf->max_size\n\tLinux 4.4.147\n\nChange-Id: I067f9844278976dddef8063961a70e189c423de3\nSigned-off-by: Greg Kroah-Hartman <gregkh@google.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/a5fc66599b6143999290603a51da11868f7d36a9"},{"sha":"7736fcede789b412ae1c5c2f12f9bef58903319c","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: fix check to prevent initializing reserved inodes\n\ncommit 5012284700775a4e6e3fbe7eac4c543c4874b559 upstream.\n\nCommit 8844618d8aa7: \"ext4: only look at the bg_flags field if it is\nvalid\" will complain if block group zero does not have the\nEXT4_BG_INODE_ZEROED flag set.  Unfortunately, this is not correct,\nsince a freshly created file system has this flag cleared.  It gets\nalmost immediately after the file system is mounted read-write --- but\nthe following somewhat unlikely sequence will end up triggering a\nfalse positive report of a corrupted file system:\n\n   mkfs.ext4 /dev/vdc\n   mount -o ro /dev/vdc /vdc\n   mount -o remount,rw /dev/vdc\n\nInstead, when initializing the inode table for block group zero, test\nto make sure that itable_unused count is not too large, since that is\nthe case that will result in some or all of the reserved inodes\ngetting cleared.\n\nThis fixes the failures reported by Eric Whiteney when running\ngeneric/230 and generic/231 in the the nojournal test case.\n\nFixes: 8844618d8aa7 (\"ext4: only look at the bg_flags field if it is valid\")\nReported-by: Eric Whitney <enwlinux@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/7736fcede789b412ae1c5c2f12f9bef58903319c"},{"sha":"215f36e128f2b476cd3bfe91339a5e12b79d010c","author":{"name":"Tadeusz Struk","email":"ac7da5bc34fbda078ba4af5ef710d2a59a2316f5@intel.com"},"message":"tpm: fix race condition in tpm_common_write()\n\ncommit 3ab2011ea368ec3433ad49e1b9e1c7b70d2e65df upstream.\n\nThere is a race condition in tpm_common_write function allowing\ntwo threads on the same /dev/tpm<N>, or two different applications\non the same /dev/tpmrm<N> to overwrite each other commands/responses.\nFixed this by taking the priv->buffer_mutex early in the function.\n\nAlso converted the priv->data_pending from atomic to a regular size_t\ntype. There is no need for it to be atomic since it is only touched\nunder the protection of the priv->buffer_mutex.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nCc: stable@vger.kernel.org\nSigned-off-by: Tadeusz Struk <tadeusz.struk@intel.com>\nReviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/215f36e128f2b476cd3bfe91339a5e12b79d010c"},{"sha":"e424bee248c38266c6057d43f3e350072fc41c5d","author":{"name":"Thomas Egerer","email":"99ef75c122afe73dd03e0ee223f77d9a52aa8c0f@gmx.de"},"message":"ipv4+ipv6: Make INET*_ESP select CRYPTO_ECHAINIV\n\ncommit 32b6170ca59ccf07d0e394561e54b2cd9726038c upstream.\n\nThe ESP algorithms using CBC mode require echainiv. Hence INET*_ESP have\nto select CRYPTO_ECHAINIV in order to work properly. This solves the\nissues caused by a misconfiguration as described in [1].\nThe original approach, patching crypto/Kconfig was turned down by\nHerbert Xu [2].\n\n[1] https://lists.strongswan.org/pipermail/users/2015-December/009074.html\n[2] http://marc.info/?l=linux-crypto-vger&m=145224655809562&w=2\n\nSigned-off-by: Thomas Egerer <hakke_007@gmx.de>\nAcked-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nCc: Yongqin Liu <yongqin.liu@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/e424bee248c38266c6057d43f3e350072fc41c5d"},{"sha":"1e4006421429ab672c62ab25afb3c39e6f4aa94f","author":{"name":"Kees Cook","email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org"},"message":"fork: unconditionally clear stack on fork\n\ncommit e01e80634ecdde1dd113ac43b3adad21b47f3957 upstream.\n\nOne of the classes of kernel stack content leaks[1] is exposing the\ncontents of prior heap or stack contents when a new process stack is\nallocated.  Normally, those stacks are not zeroed, and the old contents\nremain in place.  In the face of stack content exposure flaws, those\ncontents can leak to userspace.\n\nFixing this will make the kernel no longer vulnerable to these flaws, as\nthe stack will be wiped each time a stack is assigned to a new process.\nThere's not a meaningful change in runtime performance; it almost looks\nlike it provides a benefit.\n\nPerforming back-to-back kernel builds before:\n\tRun times: 157.86 157.09 158.90 160.94 160.80\n\tMean: 159.12\n\tStd Dev: 1.54\n\nand after:\n\tRun times: 159.31 157.34 156.71 158.15 160.81\n\tMean: 158.46\n\tStd Dev: 1.46\n\nInstead of making this a build or runtime config, Andy Lutomirski\nrecommended this just be enabled by default.\n\n[1] A noisy search for many kinds of stack content leaks can be seen here:\nhttps://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=linux+kernel+stack+leak\n\nI did some more with perf and cycle counts on running 100,000 execs of\n/bin/true.\n\nbefore:\nCycles: 218858861551 218853036130 214727610969 227656844122 224980542841\nMean:  221015379122.60\nStd Dev: 4662486552.47\n\nafter:\nCycles: 213868945060 213119275204 211820169456 224426673259 225489986348\nMean:  217745009865.40\nStd Dev: 5935559279.99\n\nIt continues to look like it's faster, though the deviation is rather\nwide, but I'm not sure what I could do that would be less noisy.  I'm\nopen to ideas!\n\nLink: http://lkml.kernel.org/r/20180221021659.GA37073@beast\nSigned-off-by: Kees Cook <keescook@chromium.org>\nAcked-by: Michal Hocko <mhocko@suse.com>\nReviewed-by: Andrew Morton <akpm@linux-foundation.org>\nCc: Andy Lutomirski <luto@kernel.org>\nCc: Laura Abbott <labbott@redhat.com>\nCc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>\nCc: Mel Gorman <mgorman@techsingularity.net>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[ Srivatsa: Backported to 4.4.y ]\nSigned-off-by: Srivatsa S. Bhat <srivatsa@csail.mit.edu>\nReviewed-by: Srinidhi Rao <srinidhir@vmware.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/1e4006421429ab672c62ab25afb3c39e6f4aa94f"},{"sha":"a9252a70174362912fee1556f8c3a25d66cd7637","author":{"name":"Helge Deller","email":"5b1e7895819cf7d6bc77091b09bbfd6d330a4e74@gmx.de"},"message":"parisc: Enable CONFIG_MLONGCALLS by default\n\ncommit 66509a276c8c1d19ee3f661a41b418d101c57d29 upstream.\n\nEnable the -mlong-calls compiler option by default, because otherwise in most\ncases linking the vmlinux binary fails due to truncations of R_PARISC_PCREL22F\nrelocations. This fixes building the 64-bit defconfig.\n\nCc: stable@vger.kernel.org # 4.0+\nSigned-off-by: Helge Deller <deller@gmx.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/a9252a70174362912fee1556f8c3a25d66cd7637"},{"sha":"277b161b1a1d339985b4c24e796e86eae9511382","author":{"name":"John David Anglin","email":"d3a7a82a6ff309c7c46b71cf01386d84d6ca7c2a@bell.net"},"message":"parisc: Define mb() and add memory barriers to assembler unlock sequences\n\ncommit fedb8da96355f5f64353625bf96dc69423ad1826 upstream.\n\nFor years I thought all parisc machines executed loads and stores in\norder. However, Jeff Law recently indicated on gcc-patches that this is\nnot correct. There are various degrees of out-of-order execution all the\nway back to the PA7xxx processor series (hit-under-miss). The PA8xxx\nseries has full out-of-order execution for both integer operations, and\nloads and stores.\n\nThis is described in the following article:\nhttp://web.archive.org/web/20040214092531/http://www.cpus.hp.com/technical_references/advperf.shtml\n\nFor this reason, we need to define mb() and to insert a memory barrier\nbefore the store unlocking spinlocks. This ensures that all memory\naccesses are complete prior to unlocking. The ldcw instruction performs\nthe same function on entry.\n\nSigned-off-by: John David Anglin <dave.anglin@bell.net>\nCc: stable@vger.kernel.org # 4.0+\nSigned-off-by: Helge Deller <deller@gmx.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.10/commits/277b161b1a1d339985b4c24e796e86eae9511382"}]}
{"actor":{"display_login":"blissgerrit"}}