{"push_id":1932911821,"size":42,"distinct_size":0,"ref":"refs/heads/caf/3.10/caf/korg/linux-4.9.y","head":"a97a16f18c4895e41951a44d27af8af0b8f1d897","before":"6da35f43acde8f718b53f6f05fc865bffa709fc5","commits":[{"sha":"b56cd77c1205fae6c92a519bd11cc26e78292bfe","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.18/commits/b56cd77c1205fae6c92a519bd11cc26e78292bfe"},{"sha":"e2286916ac078728949163d7cbd5d4875a57dbfb","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.18/commits/e2286916ac078728949163d7cbd5d4875a57dbfb"},{"sha":"0041042de554cbcaa73163747d7179be715923fc","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.18/commits/0041042de554cbcaa73163747d7179be715923fc"},{"sha":"03973c57e1a27de080ed06a3961f1d6afec27539","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.18/commits/03973c57e1a27de080ed06a3961f1d6afec27539"},{"sha":"a3ab0f069f466acb7da4f960d8e1bc3cfdf1309e","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.18/commits/a3ab0f069f466acb7da4f960d8e1bc3cfdf1309e"},{"sha":"a311810903c700ff7411be16489df09ad6f3faee","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.18/commits/a311810903c700ff7411be16489df09ad6f3faee"},{"sha":"ced271b814e441ac5ce079427c14860f9534b57a","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.18/commits/ced271b814e441ac5ce079427c14860f9534b57a"},{"sha":"e6a0599b746427682df1e8d444eee9e0641b4c09","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.18/commits/e6a0599b746427682df1e8d444eee9e0641b4c09"},{"sha":"b51a71635576ddd2f30597c148ca4b0d62cec288","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.18/commits/b51a71635576ddd2f30597c148ca4b0d62cec288"},{"sha":"1da30c23b63b3ed426880ac11179dbc2d2bbf368","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.18/commits/1da30c23b63b3ed426880ac11179dbc2d2bbf368"},{"sha":"227559e6233c9af382efcfd4c9ac87e090bb4853","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.18/commits/227559e6233c9af382efcfd4c9ac87e090bb4853"},{"sha":"160c365b5879e6d4ea1c299b68c9702e8c783298","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.18/commits/160c365b5879e6d4ea1c299b68c9702e8c783298"},{"sha":"0a205d8145c22d83e24ada019b599a33f7bf68ed","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.18/commits/0a205d8145c22d83e24ada019b599a33f7bf68ed"},{"sha":"00f3c2a253f752948c5cac9f3a554407ab43d9c2","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.18/commits/00f3c2a253f752948c5cac9f3a554407ab43d9c2"},{"sha":"4381e2c30008fa5ceb28957cb186a25871b09bf1","author":{"name":"Wladimir J. van der Laan","email":"c34e7a7f54ce6bae7e557bf240ec1aad7766c5ce@gmail.com"},"message":"drm/etnaviv: Fix off-by-one error in reloc checking\n\ncommit d6f756e09f01ea7a0efbbcef269a1e384a35d824 upstream.\n\nA relocation pointing to the last four bytes of a buffer can\nlegitimately happen in the case of small vertex buffers.\n\nSigned-off-by: Wladimir J. van der Laan <laanwj@gmail.com>\nReviewed-by: Philipp Zabel <p.zabel@pengutronix.de>\nReviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>\nSigned-off-by: Lucas Stach <l.stach@pengutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/4381e2c30008fa5ceb28957cb186a25871b09bf1"},{"sha":"2b3bf207b2a2465115d2bded0eef8a3c4ee0c6c2","author":{"name":"Maarten Lankhorst","email":"31963d7fed19f3420ff638ec3d8fbadfee1a8e5f@linux.intel.com"},"message":"drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut\n\ncommit 5279fc7724ae3a82c9cfe5b09c1fb07ff0e41056 upstream.\n\nbdw_load_gamma_lut is writing beyond the array to the maximum value.\nThe intend of the function is to clamp values > 1 to 1, so write\nthe intended color to the max register.\n\nThis fixes the following KASAN warning:\n\n[  197.020857] [IGT] kms_pipe_color: executing\n[  197.063434] [IGT] kms_pipe_color: starting subtest ctm-0-25-pipe0\n[  197.078989] ==================================================================\n[  197.079127] BUG: KASAN: slab-out-of-bounds in bdw_load_gamma_lut.isra.2+0x3b9/0x570 [i915]\n[  197.079188] Read of size 2 at addr ffff8800d38db150 by task kms_pipe_color/1839\n[  197.079208] CPU: 2 PID: 1839 Comm: kms_pipe_color Tainted: G     U 4.13.0-rc1-patser+ #5211\n[  197.079215] Hardware name: NUC5i7RYB, BIOS RYBDWi35.86A.0246.2015.0309.1355 03/09/2015\n[  197.079220] Call Trace:\n[  197.079230]  dump_stack+0x68/0x9e\n[  197.079239]  print_address_description+0x6f/0x250\n[  197.079251]  kasan_report+0x216/0x370\n[  197.079374]  ? bdw_load_gamma_lut.isra.2+0x3b9/0x570 [i915]\n[  197.079451]  ? gen8_write16+0x4e0/0x4e0 [i915]\n[  197.079460]  __asan_report_load2_noabort+0x14/0x20\n[  197.079535]  bdw_load_gamma_lut.isra.2+0x3b9/0x570 [i915]\n[  197.079612]  broadwell_load_luts+0x1df/0x550 [i915]\n[  197.079690]  intel_color_load_luts+0x7b/0x80 [i915]\n[  197.079764]  intel_begin_crtc_commit+0x138/0x760 [i915]\n[  197.079783]  drm_atomic_helper_commit_planes_on_crtc+0x1a3/0x820 [drm_kms_helper]\n[  197.079859]  ? intel_pre_plane_update+0x571/0x580 [i915]\n[  197.079937]  intel_update_crtc+0x238/0x330 [i915]\n[  197.080016]  intel_update_crtcs+0x10f/0x210 [i915]\n[  197.080092]  intel_atomic_commit_tail+0x1552/0x3340 [i915]\n[  197.080101]  ? _raw_spin_unlock+0x3c/0x40\n[  197.080110]  ? __queue_work+0xb40/0xbf0\n[  197.080188]  ? skl_update_crtcs+0xc00/0xc00 [i915]\n[  197.080195]  ? trace_hardirqs_on+0xd/0x10\n[  197.080269]  ? intel_atomic_commit_ready+0x128/0x13c [i915]\n[  197.080329]  ? __i915_sw_fence_complete+0x5b8/0x6d0 [i915]\n[  197.080336]  ? debug_object_activate+0x39e/0x580\n[  197.080397]  ? i915_sw_fence_await+0x30/0x30 [i915]\n[  197.080409]  ? __might_sleep+0x15b/0x180\n[  197.080483]  intel_atomic_commit+0x944/0xa70 [i915]\n[  197.080490]  ? refcount_dec_and_test+0x11/0x20\n[  197.080567]  ? intel_atomic_commit_tail+0x3340/0x3340 [i915]\n[  197.080597]  ? drm_atomic_crtc_set_property+0x303/0x580 [drm]\n[  197.080674]  ? intel_atomic_commit_tail+0x3340/0x3340 [i915]\n[  197.080704]  drm_atomic_commit+0xd7/0xe0 [drm]\n[  197.080722]  drm_atomic_helper_crtc_set_property+0xec/0x130 [drm_kms_helper]\n[  197.080749]  drm_mode_crtc_set_obj_prop+0x7d/0xb0 [drm]\n[  197.080775]  drm_mode_obj_set_property_ioctl+0x50b/0x5d0 [drm]\n[  197.080783]  ? __might_fault+0x104/0x180\n[  197.080809]  ? drm_mode_obj_find_prop_id+0x160/0x160 [drm]\n[  197.080838]  ? drm_mode_obj_find_prop_id+0x160/0x160 [drm]\n[  197.080861]  drm_ioctl_kernel+0x154/0x1a0 [drm]\n[  197.080885]  drm_ioctl+0x624/0x8f0 [drm]\n[  197.080910]  ? drm_mode_obj_find_prop_id+0x160/0x160 [drm]\n[  197.080934]  ? drm_getunique+0x210/0x210 [drm]\n[  197.080943]  ? __handle_mm_fault+0x1bd0/0x1ce0\n[  197.080949]  ? lock_downgrade+0x610/0x610\n[  197.080957]  ? __lru_cache_add+0x15a/0x180\n[  197.080967]  do_vfs_ioctl+0xd92/0xe40\n[  197.080975]  ? ioctl_preallocate+0x1b0/0x1b0\n[  197.080982]  ? selinux_capable+0x20/0x20\n[  197.080991]  ? __do_page_fault+0x7b7/0x9a0\n[  197.080997]  ? lock_downgrade+0x5bb/0x610\n[  197.081007]  ? security_file_ioctl+0x57/0x90\n[  197.081016]  SyS_ioctl+0x4e/0x80\n[  197.081024]  entry_SYSCALL_64_fastpath+0x18/0xad\n[  197.081030] RIP: 0033:0x7f61f287a987\n[  197.081035] RSP: 002b:00007fff7d44d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\n[  197.081043] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f61f287a987\n[  197.081048] RDX: 00007fff7d44d1c0 RSI: 00000000c01864ba RDI: 0000000000000003\n[  197.081053] RBP: 00007f61f2b3eb00 R08: 0000000000000059 R09: 0000000000000000\n[  197.081058] R10: 0000002ea5c4a290 R11: 0000000000000246 R12: 00007f61f2b3eb58\n[  197.081063] R13: 0000000000001010 R14: 00007f61f2b3eb58 R15: 0000000000002702\n\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101659\nSigned-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>\nReported-by: Martin Peres <martin.peres@linux.intel.com>\nCc: Martin Peres <martin.peres@linux.intel.com>\nFixes: 82cf435b3134 (\"drm/i915: Implement color management on bdw/skl/bxt/kbl\")\nCc: Shashank Sharma <shashank.sharma@intel.com>\nCc: Kiran S Kumar <kiran.s.kumar@intel.com>\nCc: Kausal Malladi <kausalmalladi@gmail.com>\nCc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>\nCc: Matt Roper <matthew.d.roper@intel.com>\nCc: Daniel Vetter <daniel.vetter@intel.com>\nCc: Jani Nikula <jani.nikula@linux.intel.com>\nCc: intel-gfx@lists.freedesktop.org\nLink: https://patchwork.freedesktop.org/patch/msgid/20170724091431.24251-1-maarten.lankhorst@linux.intel.com\nReviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>\n(cherry picked from commit 09a92bc8773b4314e02b478e003fe5936ce85adb)\nSigned-off-by: Jani Nikula <jani.nikula@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/2b3bf207b2a2465115d2bded0eef8a3c4ee0c6c2"},{"sha":"e27f58cd130bae882e6bd66e094c036056a03278","author":{"name":"Hector Martin","email":"003a4d79549d2811c83ec2080fcc1026ef6c363d@marcan.st"},"message":"USB: serial: option: add D-Link DWM-222 device ID\n\ncommit fd1b8668af59a11bb754a6c9b0051c6c5ce73b74 upstream.\n\nAdd device id for D-Link DWM-222.\n\nSigned-off-by: Hector Martin <marcan@marcan.st>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/e27f58cd130bae882e6bd66e094c036056a03278"},{"sha":"5665164015017a8abeb4b401656db678b43dafac","author":{"name":"Stefan Triller","email":"f27a17fc90c00d8c248d8510a1084221738b492b@stefantriller.de"},"message":"USB: serial: cp210x: add support for Qivicon USB ZigBee dongle\n\ncommit 9585e340db9f6cc1c0928d82c3a23cc4460f0a3f upstream.\n\nThe German Telekom offers a ZigBee USB Stick under the brand name Qivicon\nfor their SmartHome Home Base in its 1. Generation. The productId is not\nknown by the according kernel module, this patch adds support for it.\n\nSigned-off-by: Stefan Triller <github@stefantriller.de>\nReviewed-by: Frans Klaver <fransklaver@gmail.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/5665164015017a8abeb4b401656db678b43dafac"},{"sha":"4fd8c366acac7a888b83a25d349476a111e49ac7","author":{"name":"Greg Kroah-Hartman","email":"4931344b09d7a7d3573e8b1ebec918e229ead9bf@linuxfoundation.org"},"message":"USB: serial: pl2303: add new ATEN device id\n\ncommit 3b6bcd3d093c698d32e93d4da57679b8fbc5e01e upstream.\n\nThis adds a new ATEN device id for a new pl2303-based device.\n\nReported-by: Peter Kuo <PeterKuo@aten.com.tw>\nCc: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/4fd8c366acac7a888b83a25d349476a111e49ac7"},{"sha":"821ccbe2937ece265dfc087c4fe272242b70350a","author":{"name":"Bin Liu","email":"a72059919660980379dd6f250450bdd11bed73d1@ti.com"},"message":"usb: musb: fix tx fifo flush handling again\n\ncommit 45d73860530a14c608f410b91c6c341777bfa85d upstream.\n\ncommit 68fe05e2a451 (\"usb: musb: fix tx fifo flush handling\") drops the\n1ms delay trying to solve the long disconnect time issue when\napplication queued many tx urbs. However, the 1ms delay is needed for\nsome use cases, for example, without the delay, reconnecting AR9271 WIFI\ndongle no longer works if the connection is dropped from the AP.\n\nSo let's add back the 1ms delay in musb_h_tx_flush_fifo(), and solve the\nlong disconnect time problem with a separate patch for\nusb_hcd_flush_endpoint().\n\nSigned-off-by: Bin Liu <b-liu@ti.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/821ccbe2937ece265dfc087c4fe272242b70350a"}]}
{"actor":{"display_login":"akhilnarang"}}