{"push_id":1934871383,"size":66,"distinct_size":0,"ref":"refs/heads/caf/korg/linux-4.12.y","head":"a0fb6543b40f216f72ef57ff3f61df918047c0fc","before":"1ea1c41db9839e56eb0f41dfffc7c6dd80bf7a64","commits":[{"sha":"10df347170c39961ef93efb070213b68fc674202","author":{"name":"Jonathan Toppins","email":"64ad6e3c9989bac74e1739fe883c0e29c18b94ff@redhat.com"},"message":"mm: ratelimit PFNs busy info message\n\ncommit 75dddef32514f7aa58930bde6a1263253bc3d4ba upstream.\n\nThe RDMA subsystem can generate several thousand of these messages per\nsecond eventually leading to a kernel crash.  Ratelimit these messages\nto prevent this crash.\n\nDoug said:\n \"I've been carrying a version of this for several kernel versions. I\n  don't remember when they started, but we have one (and only one) class\n  of machines: Dell PE R730xd, that generate these errors. When it\n  happens, without a rate limit, we get rcu timeouts and kernel oopses.\n  With the rate limit, we just get a lot of annoying kernel messages but\n  the machine continues on, recovers, and eventually the memory\n  operations all succeed\"\n\nAnd:\n \"> Well... why are all these EBUSY's occurring? It sounds inefficient\n  > (at least) but if it is expected, normal and unavoidable then\n  > perhaps we should just remove that message altogether?\n\n  I don't have an answer to that question. To be honest, I haven't\n  looked real hard. We never had this at all, then it started out of the\n  blue, but only on our Dell 730xd machines (and it hits all of them),\n  but no other classes or brands of machines. And we have our 730xd\n  machines loaded up with different brands and models of cards (for\n  instance one dedicated to mlx4 hardware, one for qib, one for mlx5, an\n  ocrdma/cxgb4 combo, etc), so the fact that it hit all of the machines\n  meant it wasn't tied to any particular brand/model of RDMA hardware.\n  To me, it always smelled of a hardware oddity specific to maybe the\n  CPUs or mainboard chipsets in these machines, so given that I'm not an\n  mm expert anyway, I never chased it down.\n\n  A few other relevant details: it showed up somewhere around 4.8/4.9 or\n  thereabouts. It never happened before, but the prinkt has been there\n  since the 3.18 days, so possibly the test to trigger this message was\n  changed, or something else in the allocator changed such that the\n  situation started happening on these machines?\n\n  And, like I said, it is specific to our 730xd machines (but they are\n  all identical, so that could mean it's something like their specific\n  ram configuration is causing the allocator to hit this on these\n  machine but not on other machines in the cluster, I don't want to say\n  it's necessarily the model of chipset or CPU, there are other bits of\n  identicalness between these machines)\"\n\nLink: http://lkml.kernel.org/r/499c0f6cc10d6eb829a67f2a4d75b4228a9b356e.1501695897.git.jtoppins@redhat.com\nSigned-off-by: Jonathan Toppins <jtoppins@redhat.com>\nReviewed-by: Doug Ledford <dledford@redhat.com>\nTested-by: Doug Ledford <dledford@redhat.com>\nCc: Michal Hocko <mhocko@suse.com>\nCc: Vlastimil Babka <vbabka@suse.cz>\nCc: Mel Gorman <mgorman@techsingularity.net>\nCc: Hillf Danton <hillf.zj@alibaba-inc.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/10df347170c39961ef93efb070213b68fc674202"},{"sha":"5f064f8a0d4b4a3d17eda6444a9f06437e34fbe0","author":{"name":"Cong Wang","email":"3f5d79d28d6d48052800caba9df0b30e06fefe41@gmail.com"},"message":"mm: fix list corruptions on shmem shrinklist\n\ncommit d041353dc98a6339182cd6f628b4c8f111278cb3 upstream.\n\nWe saw many list corruption warnings on shmem shrinklist:\n\n  WARNING: CPU: 18 PID: 177 at lib/list_debug.c:59 __list_del_entry+0x9e/0xc0\n  list_del corruption. prev->next should be ffff9ae5694b82d8, but was ffff9ae5699ba960\n  Modules linked in: intel_rapl sb_edac edac_core x86_pkg_temp_thermal coretemp iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul ghash_clmulni_intel raid0 dcdbas shpchp wmi hed i2c_i801 ioatdma lpc_ich i2c_smbus acpi_cpufreq tcp_diag inet_diag sch_fq_codel ipmi_si ipmi_devintf ipmi_msghandler igb ptp crc32c_intel pps_core i2c_algo_bit i2c_core dca ipv6 crc_ccitt\n  CPU: 18 PID: 177 Comm: kswapd1 Not tainted 4.9.34-t3.el7.twitter.x86_64 #1\n  Hardware name: Dell Inc. PowerEdge C6220/0W6W6G, BIOS 2.2.3 11/07/2013\n  Call Trace:\n    dump_stack+0x4d/0x66\n    __warn+0xcb/0xf0\n    warn_slowpath_fmt+0x4f/0x60\n    __list_del_entry+0x9e/0xc0\n    shmem_unused_huge_shrink+0xfa/0x2e0\n    shmem_unused_huge_scan+0x20/0x30\n    super_cache_scan+0x193/0x1a0\n    shrink_slab.part.41+0x1e3/0x3f0\n    shrink_slab+0x29/0x30\n    shrink_node+0xf9/0x2f0\n    kswapd+0x2d8/0x6c0\n    kthread+0xd7/0xf0\n    ret_from_fork+0x22/0x30\n\n  WARNING: CPU: 23 PID: 639 at lib/list_debug.c:33 __list_add+0x89/0xb0\n  list_add corruption. prev->next should be next (ffff9ae5699ba960), but was ffff9ae5694b82d8. (prev=ffff9ae5694b82d8).\n  Modules linked in: intel_rapl sb_edac edac_core x86_pkg_temp_thermal coretemp iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul ghash_clmulni_intel raid0 dcdbas shpchp wmi hed i2c_i801 ioatdma lpc_ich i2c_smbus acpi_cpufreq tcp_diag inet_diag sch_fq_codel ipmi_si ipmi_devintf ipmi_msghandler igb ptp crc32c_intel pps_core i2c_algo_bit i2c_core dca ipv6 crc_ccitt\n  CPU: 23 PID: 639 Comm: systemd-udevd Tainted: G        W       4.9.34-t3.el7.twitter.x86_64 #1\n  Hardware name: Dell Inc. PowerEdge C6220/0W6W6G, BIOS 2.2.3 11/07/2013\n  Call Trace:\n    dump_stack+0x4d/0x66\n    __warn+0xcb/0xf0\n    warn_slowpath_fmt+0x4f/0x60\n    __list_add+0x89/0xb0\n    shmem_setattr+0x204/0x230\n    notify_change+0x2ef/0x440\n    do_truncate+0x5d/0x90\n    path_openat+0x331/0x1190\n    do_filp_open+0x7e/0xe0\n    do_sys_open+0x123/0x200\n    SyS_open+0x1e/0x20\n    do_syscall_64+0x61/0x170\n    entry_SYSCALL64_slow_path+0x25/0x25\n\nThe problem is that shmem_unused_huge_shrink() moves entries from the\nglobal sbinfo->shrinklist to its local lists and then releases the\nspinlock.  However, a parallel shmem_setattr() could access one of these\nentries directly and add it back to the global shrinklist if it is\nremoved, with the spinlock held.\n\nThe logic itself looks solid since an entry could be either in a local\nlist or the global list, otherwise it is removed from one of them by\nlist_del_init().  So probably the race condition is that, one CPU is in\nthe middle of INIT_LIST_HEAD() but the other CPU calls list_empty()\nwhich returns true too early then the following list_add_tail() sees a\ncorrupted entry.\n\nlist_empty_careful() is designed to fix this situation.\n\n[akpm@linux-foundation.org: add comments]\nLink: http://lkml.kernel.org/r/20170803054630.18775-1-xiyou.wangcong@gmail.com\nFixes: 779750d20b93 (\"shmem: split huge pages beyond i_size under memory pressure\")\nSigned-off-by: Cong Wang <xiyou.wangcong@gmail.com>\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nAcked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>\nCc: Hugh Dickins <hughd@google.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/5f064f8a0d4b4a3d17eda6444a9f06437e34fbe0"},{"sha":"5c1d458de22bfde86efb8f59fbd318166961376d","author":{"name":"Mel Gorman","email":"7e4a4144b35252848d9a801e3e6fca62e0cbe9e6@suse.de"},"message":"futex: Remove unnecessary warning from get_futex_key\n\ncommit 48fb6f4db940e92cfb16cd878cddd59ea6120d06 upstream.\n\nCommit 65d8fc777f6d (\"futex: Remove requirement for lock_page() in\nget_futex_key()\") removed an unnecessary lock_page() with the\nside-effect that page->mapping needed to be treated very carefully.\n\nTwo defensive warnings were added in case any assumption was missed and\nthe first warning assumed a correct application would not alter a\nmapping backing a futex key.  Since merging, it has not triggered for\nany unexpected case but Mark Rutland reported the following bug\ntriggering due to the first warning.\n\n  kernel BUG at kernel/futex.c:679!\n  Internal error: Oops - BUG: 0 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 0 PID: 3695 Comm: syz-executor1 Not tainted 4.13.0-rc3-00020-g307fec773ba3 #3\n  Hardware name: linux,dummy-virt (DT)\n  task: ffff80001e271780 task.stack: ffff000010908000\n  PC is at get_futex_key+0x6a4/0xcf0 kernel/futex.c:679\n  LR is at get_futex_key+0x6a4/0xcf0 kernel/futex.c:679\n  pc : [<ffff00000821ac14>] lr : [<ffff00000821ac14>] pstate: 80000145\n\nThe fact that it's a bug instead of a warning was due to an unrelated\narm64 problem, but the warning itself triggered because the underlying\nmapping changed.\n\nThis is an application issue but from a kernel perspective it's a\nrecoverable situation and the warning is unnecessary so this patch\nremoves the warning.  The warning may potentially be triggered with the\nfollowing test program from Mark although it may be necessary to adjust\nNR_FUTEX_THREADS to be a value smaller than the number of CPUs in the\nsystem.\n\n    #include <linux/futex.h>\n    #include <pthread.h>\n    #include <stdio.h>\n    #include <stdlib.h>\n    #include <sys/mman.h>\n    #include <sys/syscall.h>\n    #include <sys/time.h>\n    #include <unistd.h>\n\n    #define NR_FUTEX_THREADS 16\n    pthread_t threads[NR_FUTEX_THREADS];\n\n    void *mem;\n\n    #define MEM_PROT  (PROT_READ | PROT_WRITE)\n    #define MEM_SIZE  65536\n\n    static int futex_wrapper(int *uaddr, int op, int val,\n                             const struct timespec *timeout,\n                             int *uaddr2, int val3)\n    {\n        syscall(SYS_futex, uaddr, op, val, timeout, uaddr2, val3);\n    }\n\n    void *poll_futex(void *unused)\n    {\n        for (;;) {\n            futex_wrapper(mem, FUTEX_CMP_REQUEUE_PI, 1, NULL, mem + 4, 1);\n        }\n    }\n\n    int main(int argc, char *argv[])\n    {\n        int i;\n\n        mem = mmap(NULL, MEM_SIZE, MEM_PROT,\n               MAP_SHARED | MAP_ANONYMOUS, -1, 0);\n\n        printf(\"Mapping @ %p\\n\", mem);\n\n        printf(\"Creating futex threads...\\n\");\n\n        for (i = 0; i < NR_FUTEX_THREADS; i++)\n            pthread_create(&threads[i], NULL, poll_futex, NULL);\n\n        printf(\"Flipping mapping...\\n\");\n        for (;;) {\n            mmap(mem, MEM_SIZE, MEM_PROT,\n                 MAP_FIXED | MAP_SHARED | MAP_ANONYMOUS, -1, 0);\n        }\n\n        return 0;\n    }\n\nReported-and-tested-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Mel Gorman <mgorman@suse.de>\nAcked-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/5c1d458de22bfde86efb8f59fbd318166961376d"},{"sha":"5e96389b3adc71ded6075bfad5d179c3ace8b138","author":{"name":"Max Filippov","email":"d74404602d9677d809facc4c4eac9231fee6b605@gmail.com"},"message":"xtensa: fix cache aliasing handling code for WT cache\n\ncommit 6d0f581d1768d3eaba15776e7dd1fdfec10cfe36 upstream.\n\nCurrently building kernel for xtensa core with aliasing WT cache fails\nwith the following messages:\n\n  mm/memory.c:2152: undefined reference to `flush_dcache_page'\n  mm/memory.c:2332: undefined reference to `local_flush_cache_page'\n  mm/memory.c:1919: undefined reference to `local_flush_cache_range'\n  mm/memory.c:4179: undefined reference to `copy_to_user_page'\n  mm/memory.c:4183: undefined reference to `copy_from_user_page'\n\nThis happens because implementation of these functions is only compiled\nwhen data cache is WB, which looks wrong: even when data cache doesn't\nneed flushing it still needs invalidation. The functions like\n__flush_[invalidate_]dcache_* are correctly defined for both WB and WT\ncaches (and even if they weren't that'd still be ok, just slower).\n\nFix this by providing the same implementation of the above functions for\nboth WB and WT cache.\n\nSigned-off-by: Max Filippov <jcmvbkbc@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/5e96389b3adc71ded6075bfad5d179c3ace8b138"},{"sha":"094849d602a0e8bbe90464b209521159cbd8ecea","author":{"name":"Max Filippov","email":"d74404602d9677d809facc4c4eac9231fee6b605@gmail.com"},"message":"xtensa: mm/cache: add missing EXPORT_SYMBOLs\n\ncommit bc652eb6a0d5cffaea7dc8e8ad488aab2a1bf1ed upstream.\n\nFunctions clear_user_highpage, copy_user_highpage, flush_dcache_page,\nlocal_flush_cache_range and local_flush_cache_page may be used from\nmodules. Export them.\n\nSigned-off-by: Max Filippov <jcmvbkbc@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/094849d602a0e8bbe90464b209521159cbd8ecea"},{"sha":"0af6995672cb78c527661f4c5f6ce9931d96e100","author":{"name":"Max Filippov","email":"d74404602d9677d809facc4c4eac9231fee6b605@gmail.com"},"message":"xtensa: don't limit csum_partial export by CONFIG_NET\n\ncommit 7f81e55c737a8fa82c71f290945d729a4902f8d2 upstream.\n\ncsum_partial and csum_partial_copy_generic are defined unconditionally\nand are available even when CONFIG_NET is disabled. They are used not\nonly by the network drivers, but also by scsi and media.\nDon't limit these functions export by CONFIG_NET.\n\nSigned-off-by: Max Filippov <jcmvbkbc@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/0af6995672cb78c527661f4c5f6ce9931d96e100"},{"sha":"8452494828f74b72b230fd84b8ebc2ca95397716","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"xfs: Fix leak of discard bio\n\ncommit ea7bd56fa309d10a41b1041827a63c0746c47554 upstream.\n\nThe bio describing discard operation is allocated by\n__blkdev_issue_discard() which returns us a reference to it. That\nreference is never released and thus we leak this bio. Drop the bio\nreference once it completes in xlog_discard_endio().\n\nFixes: 4560e78f40cb55bd2ea8f1ef4001c5baa88531c7\nSigned-off-by: Jan Kara <jack@suse.cz>\nReviewed-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/8452494828f74b72b230fd84b8ebc2ca95397716"},{"sha":"0eda7e0bf2389a4dd5e752dcaa4a8d48bb799172","author":{"name":"Gregory CLEMENT","email":"4264d285b3ce9b577917b36d034b4cf25ea4fe85@free-electrons.com"},"message":"pinctrl: armada-37xx: Fix number of pin in south bridge\n\ncommit 6b67c3906cd74d88da4f6717b4b294bd52fce56a upstream.\n\nOn the south bridge we have pin from to 29, so it gives 30 pins (and not\n29).\n\nWithout this patch the kernel complain with the following traces:\ncat /sys/kernel/debug/pinctrl/d0018800.pinctrl/pingroups\n[  154.530205] armada-37xx-pinctrl d0018800.pinctrl: failed to get pin(29) name\n[  154.537567] ------------[ cut here ]------------\n[  154.542348] WARNING: CPU: 1 PID: 1347 at /home/gclement/open/kernel/marvell-mainline-linux/drivers/pinctrl/core.c:1610 pinctrl_groups_show+0x15c/0x1a0\n[  154.555918] Modules linked in:\n[  154.558890] CPU: 1 PID: 1347 Comm: cat Tainted: G        W       4.13.0-rc1-00001-g19e1b9fa219d #525\n[  154.568316] Hardware name: Marvell Armada 3720 Development Board DB-88F3720-DDR3 (DT)\n[  154.576311] task: ffff80001d32d100 task.stack: ffff80001bdc0000\n[  154.583048] PC is at pinctrl_groups_show+0x15c/0x1a0\n[  154.587816] LR is at pinctrl_groups_show+0x148/0x1a0\n[  154.592847] pc : [<ffff0000083e3adc>] lr : [<ffff0000083e3ac8>] pstate: 00000145\n[  154.600840] sp : ffff80001bdc3c80\n[  154.604255] x29: ffff80001bdc3c80 x28: 00000000f7750000\n[  154.609825] x27: ffff80001d05d198 x26: 0000000000000009\n[  154.615224] x25: ffff0000089ead20 x24: 0000000000000002\n[  154.620705] x23: ffff000008c8e1d0 x22: ffff80001be55700\n[  154.626187] x21: ffff80001d05d100 x20: 0000000000000005\n[  154.631667] x19: 0000000000000006 x18: 0000000000000010\n[  154.637238] x17: 0000000000000000 x16: ffff0000081fc4b8\n[  154.642726] x15: 0000000000000006 x14: ffff0000899e537f\n[  154.648214] x13: ffff0000099e538d x12: 206f742064656c69\n[  154.653613] x11: 6166203a6c727463 x10: 0000000005f5e0ff\n[  154.659094] x9 : ffff80001bdc38c0 x8 : 286e697020746567\n[  154.664576] x7 : ffff000008551870 x6 : 000000000000011b\n[  154.670146] x5 : 0000000000000000 x4 : 0000000000000000\n[  154.675544] x3 : 0000000000000000 x2 : 0000000000000000\n[  154.681025] x1 : ffff000008c8e1d0 x0 : ffff80001be55700\n[  154.686507] Call trace:\n[  154.688668] Exception stack(0xffff80001bdc3ab0 to 0xffff80001bdc3be0)\n[  154.695224] 3aa0:                                   0000000000000006 0001000000000000\n[  154.703310] 3ac0: ffff80001bdc3c80 ffff0000083e3adc ffff80001bdc3bb0 00000000ffffffd8\n[  154.711304] 3ae0: 4554535953425553 6f6674616c703d4d 4349564544006d72 6674616c702b3d45\n[  154.719478] 3b00: 313030643a6d726f 6e69702e30303838 ffff80006c727463 ffff0000089635d8\n[  154.727562] 3b20: ffff80001d1ca0cb ffff000008af0fa4 ffff80001bdc3b40 ffff000008c8e1dc\n[  154.735648] 3b40: ffff80001bdc3bc0 ffff000008223174 ffff80001be55700 ffff000008c8e1d0\n[  154.743731] 3b60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000\n[  154.752354] 3b80: 000000000000011b ffff000008551870 286e697020746567 ffff80001bdc38c0\n[  154.760446] 3ba0: 0000000005f5e0ff 6166203a6c727463 206f742064656c69 ffff0000099e538d\n[  154.767910] 3bc0: ffff0000899e537f 0000000000000006 ffff0000081fc4b8 0000000000000000\n[  154.776085] [<ffff0000083e3adc>] pinctrl_groups_show+0x15c/0x1a0\n[  154.782823] [<ffff000008222abc>] seq_read+0x184/0x460\n[  154.787505] [<ffff000008344120>] full_proxy_read+0x60/0xa8\n[  154.793431] [<ffff0000081f9bec>] __vfs_read+0x1c/0x110\n[  154.799001] [<ffff0000081faff4>] vfs_read+0x84/0x140\n[  154.803860] [<ffff0000081fc4fc>] SyS_read+0x44/0xa0\n[  154.808983] [<ffff000008082f30>] el0_svc_naked+0x24/0x28\n[  154.814459] ---[ end trace 4cbb00a92d616b95 ]---\n\nFixes: 87466ccd9401 (\"pinctrl: armada-37xx: Add pin controller support\nfor Armada 37xx\")\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/0eda7e0bf2389a4dd5e752dcaa4a8d48bb799172"},{"sha":"a34d48d5ca47c7ba740783ed8490b93499e0f870","author":{"name":"Boris Brezillon","email":"d3686c1eb756201cacdf5983212dc6c4a5a469fe@free-electrons.com"},"message":"mtd: nand: atmel: Fix DT backward compatibility in pmecc.c\n\ncommit 3aa0907675a38498d8f2d343e94207ad28a117cf upstream.\n\nPMECC caps extraction from old DT bindings is broken, thus leading to\nerroneous EL registers offset, which in turn make HW ECC unusable on\nsama5d2 when old bindings are in use.\n\nPassing the NAND dev node instead of the NFC node to of_match_node()\nsolves the problem.\n\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nFixes: f88fc122cc34 (\"mtd: nand: Cleanup/rework the atmel_nand driver\")\nTested-by: Romain Izard <romain.izard.pro@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/a34d48d5ca47c7ba740783ed8490b93499e0f870"},{"sha":"867c07788e9764cee324bbe1193ba93febe08e3c","author":{"name":"Boris Brezillon","email":"d3686c1eb756201cacdf5983212dc6c4a5a469fe@free-electrons.com"},"message":"mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES\n\ncommit a11bf5ed951f8900d244d09eb03a888b59c7fc82 upstream.\n\nSome ONFI NANDs do not support the SET/GET FEATURES commands, which,\naccording to the spec, is perfectly valid.\n\nOn these NANDs we can't set a specific timing mode using the \"timing\nmode\" feature, and we should assume the NAND does not require any setup\nto enter a specific timing mode.\n\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nFixes: d8e725dd8311 (\"mtd: nand: automate NAND timings selection\")\nReported-by: Alexander Dahl <ada@thorsis.com>\nTested-by: Alexander Dahl <ada@thorsis.com>\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/867c07788e9764cee324bbe1193ba93febe08e3c"},{"sha":"a0e1953e0310ad79c9aa6ff019b5425d342566aa","author":{"name":"Boris Brezillon","email":"d3686c1eb756201cacdf5983212dc6c4a5a469fe@free-electrons.com"},"message":"mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow\n\ncommit 6d29231000bbe0fb9e4893a9c68151ffdd3b5469 upstream.\n\nAll timings in nand_sdr_timings are expressed in picoseconds but some\nof them may not fit in an u32.\n\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nFixes: 204e7ecd47e2 (\"mtd: nand: Add a few more timings to nand_sdr_timings\")\nReported-by: Alexander Dahl <ada@thorsis.com>\nReviewed-by: Alexander Dahl <ada@thorsis.com>\nTested-by: Alexander Dahl <ada@thorsis.com>\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/a0e1953e0310ad79c9aa6ff019b5425d342566aa"},{"sha":"f838bd1752be732c6c9e0ff50935be5dc4fef48f","author":{"name":"Varun Prakash","email":"0a39a72a518d11a6e025ca556cbb1a5b965e4cea@chelsio.com"},"message":"iscsi-target: fix memory leak in iscsit_setup_text_cmd()\n\ncommit ea8dc5b4cd2195ee582cae28afa4164c6dea1738 upstream.\n\nOn receiving text request iscsi-target allocates buffer for\npayload in iscsit_handle_text_cmd() and assigns buffer pointer\nto cmd->text_in_ptr, this buffer is currently freed in\niscsit_release_cmd(), if iscsi-target sets 'C' bit in text\nresponse then it will receive another text request from the\ninitiator with ttt != 0xffffffff in this case iscsi-target\nwill find cmd using itt and call iscsit_setup_text_cmd()\nwhich will set cmd->text_in_ptr to NULL without freeing\npreviously allocated buffer.\n\nThis patch fixes this issue by calling kfree(cmd->text_in_ptr)\nin iscsit_setup_text_cmd() before assigning NULL to it.\n\nFor the first text request cmd->text_in_ptr is NULL as\ncmd is memset to 0 in iscsit_allocate_cmd().\n\nSigned-off-by: Varun Prakash <varun@chelsio.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/f838bd1752be732c6c9e0ff50935be5dc4fef48f"},{"sha":"428048128bf08766ffddb3571fd5040951dfc8c9","author":{"name":"Nicholas Bellinger","email":"79a5e6cd70ccff08412e5a88129ccc53c0a7b045@linux-iscsi.org"},"message":"iscsi-target: Fix iscsi_np reset hung task during parallel delete\n\ncommit 978d13d60c34818a41fc35962602bdfa5c03f214 upstream.\n\nThis patch fixes a bug associated with iscsit_reset_np_thread()\nthat can occur during parallel configfs rmdir of a single iscsi_np\nused across multiple iscsi-target instances, that would result in\nhung task(s) similar to below where configfs rmdir process context\nwas blocked indefinately waiting for iscsi_np->np_restart_comp\nto finish:\n\n[ 6726.112076] INFO: task dcp_proxy_node_:15550 blocked for more than 120 seconds.\n[ 6726.119440]       Tainted: G        W  O     4.1.26-3321 #2\n[ 6726.125045] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 6726.132927] dcp_proxy_node_ D ffff8803f202bc88     0 15550      1 0x00000000\n[ 6726.140058]  ffff8803f202bc88 ffff88085c64d960 ffff88083b3b1ad0 ffff88087fffeb08\n[ 6726.147593]  ffff8803f202c000 7fffffffffffffff ffff88083f459c28 ffff88083b3b1ad0\n[ 6726.155132]  ffff88035373c100 ffff8803f202bca8 ffffffff8168ced2 ffff8803f202bcb8\n[ 6726.162667] Call Trace:\n[ 6726.165150]  [<ffffffff8168ced2>] schedule+0x32/0x80\n[ 6726.170156]  [<ffffffff8168f5b4>] schedule_timeout+0x214/0x290\n[ 6726.176030]  [<ffffffff810caef2>] ? __send_signal+0x52/0x4a0\n[ 6726.181728]  [<ffffffff8168d7d6>] wait_for_completion+0x96/0x100\n[ 6726.187774]  [<ffffffff810e7c80>] ? wake_up_state+0x10/0x10\n[ 6726.193395]  [<ffffffffa035d6e2>] iscsit_reset_np_thread+0x62/0xe0 [iscsi_target_mod]\n[ 6726.201278]  [<ffffffffa0355d86>] iscsit_tpg_disable_portal_group+0x96/0x190 [iscsi_target_mod]\n[ 6726.210033]  [<ffffffffa0363f7f>] lio_target_tpg_store_enable+0x4f/0xc0 [iscsi_target_mod]\n[ 6726.218351]  [<ffffffff81260c5a>] configfs_write_file+0xaa/0x110\n[ 6726.224392]  [<ffffffff811ea364>] vfs_write+0xa4/0x1b0\n[ 6726.229576]  [<ffffffff811eb111>] SyS_write+0x41/0xb0\n[ 6726.234659]  [<ffffffff8169042e>] system_call_fastpath+0x12/0x71\n\nIt would happen because each iscsit_reset_np_thread() sets state\nto ISCSI_NP_THREAD_RESET, sends SIGINT, and then blocks waiting\nfor completion on iscsi_np->np_restart_comp.\n\nHowever, if iscsi_np was active processing a login request and\nmore than a single iscsit_reset_np_thread() caller to the same\niscsi_np was blocked on iscsi_np->np_restart_comp, iscsi_np\nkthread process context in __iscsi_target_login_thread() would\nflush pending signals and only perform a single completion of\nnp->np_restart_comp before going back to sleep within transport\nspecific iscsit_transport->iscsi_accept_np code.\n\nTo address this bug, add a iscsi_np->np_reset_count and update\n__iscsi_target_login_thread() to keep completing np->np_restart_comp\nuntil ->np_reset_count has reached zero.\n\nReported-by: Gary Guo <ghg@datera.io>\nTested-by: Gary Guo <ghg@datera.io>\nCc: Mike Christie <mchristi@redhat.com>\nCc: Hannes Reinecke <hare@suse.de>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/428048128bf08766ffddb3571fd5040951dfc8c9"},{"sha":"7b0d44e25fdbf7aa786538cbe2d41f9cae0c5947","author":{"name":"Alan Stern","email":"5c4cbde65af01ad64f5b2177d0cd78ab5b01e5a1@rowland.harvard.edu"},"message":"usb-storage: fix deadlock involving host lock and scsi_done\n\ncommit 8b52291a0743fc4db4a7495c846a6f31ee84d282 upstream.\n\nChristoph Hellwig says that since version 4.12, the kernel switched to\nusing blk-mq by default.  The old code used a softirq for handling\nrequest completions, but blk-mq can handle completions in the caller's\ncontext.  This may cause a problem for usb-storage, because it invokes\nthe ->scsi_done callback while holding the host lock, and the\ncompletion routine sometimes tries to acquire the same lock (when\nrunning the error handler, for example).\n\nThe consequence is that the existing code will sometimes deadlock upon\nerror completion of a SCSI command (with a lockdep warning).\n\nThis is easy enough to fix, since usb-storage doesn't really need to\nhold the host lock while the callback runs.  It was simpler to write\nit that way, but moving the call outside the locked region is pretty\neasy and there's no downside.  That's what this patch does.\n\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nReported-and-tested-by: Arthur Marsh <arthur.marsh@internode.on.net>\nCC: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/7b0d44e25fdbf7aa786538cbe2d41f9cae0c5947"},{"sha":"59c74236092d7bf6581dfc9c3b29315d26f6a5eb","author":{"name":"Nicholas Bellinger","email":"79a5e6cd70ccff08412e5a88129ccc53c0a7b045@linux-iscsi.org"},"message":"target: Fix node_acl demo-mode + uncached dynamic shutdown regression\n\ncommit 6f48655facfd7f7ccfe6d252ac0fe319ab02e4dd upstream.\n\nThis patch fixes a generate_node_acls = 1 + cache_dynamic_acls = 0\nregression, that was introduced by\n\n  commit 01d4d673558985d9a118e1e05026633c3e2ade9b\n  Author: Nicholas Bellinger <nab@linux-iscsi.org>\n  Date:   Wed Dec 7 12:55:54 2016 -0800\n\nwhich originally had the proper list_del_init() usage, but was\ndropped during list review as it was thought unnecessary by HCH.\n\nHowever, list_del_init() usage is required during the special\ngenerate_node_acls = 1 + cache_dynamic_acls = 0 case when\ntransport_free_session() does a list_del(&se_nacl->acl_list),\nfollowed by target_complete_nacl() doing the same thing.\n\nThis was manifesting as a general protection fault as reported\nby Justin:\n\nkernel: general protection fault: 0000 [#1] SMP\nkernel: Modules linked in:\nkernel: CPU: 0 PID: 11047 Comm: iscsi_ttx Not tainted 4.13.0-rc2.x86_64.1+ #20\nkernel: Hardware name: Intel Corporation S5500BC/S5500BC, BIOS S5500.86B.01.00.0064.050520141428 05/05/2014\nkernel: task: ffff88026939e800 task.stack: ffffc90007884000\nkernel: RIP: 0010:target_put_nacl+0x49/0xb0\nkernel: RSP: 0018:ffffc90007887d70 EFLAGS: 00010246\nkernel: RAX: dead000000000200 RBX: ffff8802556ca000 RCX: 0000000000000000\nkernel: RDX: dead000000000100 RSI: 0000000000000246 RDI: ffff8802556ce028\nkernel: RBP: ffffc90007887d88 R08: 0000000000000001 R09: 0000000000000000\nkernel: R10: ffffc90007887df8 R11: ffffea0009986900 R12: ffff8802556ce020\nkernel: R13: ffff8802556ce028 R14: ffff8802556ce028 R15: ffffffff88d85540\nkernel: FS:  0000000000000000(0000) GS:ffff88027fc00000(0000) knlGS:0000000000000000\nkernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nkernel: CR2: 00007fffe36f5f94 CR3: 0000000009209000 CR4: 00000000003406f0\nkernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nkernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nkernel: Call Trace:\nkernel:  transport_free_session+0x67/0x140\nkernel:  transport_deregister_session+0x7a/0xc0\nkernel:  iscsit_close_session+0x92/0x210\nkernel:  iscsit_close_connection+0x5f9/0x840\nkernel:  iscsit_take_action_for_connection_exit+0xfe/0x110\nkernel:  iscsi_target_tx_thread+0x140/0x1e0\nkernel:  ? wait_woken+0x90/0x90\nkernel:  kthread+0x124/0x160\nkernel:  ? iscsit_thread_get_cpumask+0x90/0x90\nkernel:  ? kthread_create_on_node+0x40/0x40\nkernel:  ret_from_fork+0x22/0x30\nkernel: Code: 00 48 89 fb 4c 8b a7 48 01 00 00 74 68 4d 8d 6c 24 08 4c\n89 ef e8 e8 28 43 00 48 8b 93 20 04 00 00 48 8b 83 28 04 00 00 4c 89\nef <48> 89 42 08 48 89 10 48 b8 00 01 00 00 00 00 ad de 48 89 83 20\nkernel: RIP: target_put_nacl+0x49/0xb0 RSP: ffffc90007887d70\nkernel: ---[ end trace f12821adbfd46fed ]---\n\nTo address this, go ahead and use proper list_del_list() for all\ncases of se_nacl->acl_list deletion.\n\nReported-by: Justin Maggard <jmaggard01@gmail.com>\nTested-by: Justin Maggard <jmaggard01@gmail.com>\nCc: Justin Maggard <jmaggard01@gmail.com>\nSigned-off-by: Nicholas Bellinger <nab@linux-iscsi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/59c74236092d7bf6581dfc9c3b29315d26f6a5eb"},{"sha":"cfea0422a154cd45de0ff1a8146d2e303647a5cf","author":{"name":"Mateusz Jurczyk","email":"9dac9dbf3523a1dbbeccf3b117c6bed38acdab89@google.com"},"message":"fuse: initialize the flock flag in fuse_file on allocation\n\ncommit 68227c03cba84a24faf8a7277d2b1a03c8959c2c upstream.\n\nBefore the patch, the flock flag could remain uninitialized for the\nlifespan of the fuse_file allocation. Unless set to true in\nfuse_file_flock(), it would remain in an indeterminate state until read in\nan if statement in fuse_release_common(). This could consequently lead to\ntaking an unexpected branch in the code.\n\nThe bug was discovered by a runtime instrumentation designed to detect use\nof uninitialized memory in the kernel.\n\nSigned-off-by: Mateusz Jurczyk <mjurczyk@google.com>\nFixes: 37fb3a30b462 (\"fuse: fix flock\")\nSigned-off-by: Miklos Szeredi <mszeredi@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/cfea0422a154cd45de0ff1a8146d2e303647a5cf"},{"sha":"1f2f0f1a75bda5776c5d5aba015fc9b3d1fd82cb","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz\n\ncommit 682c6c2188f39d13548ccdc89c9888fbcb547889 upstream.\n\nAt least the Acer Iconia Tab8 / aka W1-810 uses 1MiHz instead of\n1MHz for one of its busses, fix this up to 1MHz instead of failing\nthe probe of that bus.\n\nThis fixes the accelerometer on the Acer Iconia Tab8 not working.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nReviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/1f2f0f1a75bda5776c5d5aba015fc9b3d1fd82cb"},{"sha":"3329fe0e05f8eb1a82b04d921b07c2ece0e3c802","author":{"name":"Miquel Raynal","email":"a7767255b3edc7e6f3fcad603d168d8a229ae75e@free-electrons.com"},"message":"nand: fix wrong default oob layout for small pages using soft ecc\n\ncommit f7f8c1756e9a5f1258a7cc6b663f8451b724900f upstream.\n\nWhen using soft ecc, if no ooblayout is given, the core automatically\nuses one of the nand_ooblayout_{sp,lp}*() functions to determine the\nlayout inside the out of band data.\n\nUntil kernel version 4.6, struct nand_ecclayout was used for that\npurpose. During the migration from 4.6 to 4.7, an error shown up in the\nsmall page layout, in the case oob section is only 8 bytes long.\n\nThe layout was using three bytes (0, 1, 2) for ecc, two bytes (3, 4)\nas free bytes, one byte (5) for bad block marker and finally\ntwo bytes (6, 7) as free bytes, as shown there:\n\n[linux-4.6] drivers/mtd/nand/nand_base.c:52\nstatic struct nand_ecclayout nand_oob_8 = {\n\t.eccbytes = 3,\n\t.eccpos = {0, 1, 2},\n\t.oobfree = {\n\t\t{.offset = 3,\n\t\t .length = 2},\n\t\t{.offset = 6,\n\t\t .length = 2} }\n};\n\nThis fixes the current implementation which is incoherent. It\nreferences bit 3 at the same time as an ecc byte and a free byte.\n\nFurthermore, it is clear with the previous implementation that there\nis only one ecc section with 8 bytes oob sections. We shall return\n-ERANGE in the nand_ooblayout_ecc_sp() function when asked for the\nsecond section.\n\nSigned-off-by: Miquel Raynal <miquel.raynal@free-electrons.com>\nFixes: 41b207a70d3a (\"mtd: nand: implement the default mtd_ooblayout_ops\")\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/3329fe0e05f8eb1a82b04d921b07c2ece0e3c802"},{"sha":"8d189f60407f878aff3bc782e109edd713da9655","author":{"name":"Haibo Chen","email":"f3d60692cc41c2832ca99a7adf6c7d33a1612bb1@nxp.com"},"message":"mmc: mmc: correct the logic for setting HS400ES signal voltage\n\ncommit 92ddd95919466de5d34f3cb43635da9a7f9ab814 upstream.\n\nChange the default err value to -EINVAL, make sure the card only\nhas type EXT_CSD_CARD_TYPE_HS400_1_8V also do the signal voltage\nsetting when select hs400es mode.\n\nFixes: commit 1720d3545b77 (\"mmc: core: switch to 1V8 or 1V2 for hs400es mode\")\nSigned-off-by: Haibo Chen <haibo.chen@nxp.com>\nReviewed-by: Shawn Lin <shawn.lin@rock-chips.com>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/8d189f60407f878aff3bc782e109edd713da9655"},{"sha":"1cc5cd5b97b51a19cbc0a918787b5a9b63aa7140","author":{"name":"Weston Andros Adamson","email":"1869113a08a13c4d6d16e6ceb63bee6d2bb0c217@monkey.org"},"message":"nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays\n\ncommit 1feb26162bee7b2f110facfec71b5c7bdbc7d14d upstream.\n\nThe client was freeing the nfs4_ff_layout_ds, but not the contained\nnfs4_ff_ds_version array.\n\nSigned-off-by: Weston Andros Adamson <dros@primarydata.com>\nSigned-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/1cc5cd5b97b51a19cbc0a918787b5a9b63aa7140"}]}
{"actor":{"display_login":"akhilnarang"}}