{"push_id":620797552,"size":292,"distinct_size":292,"ref":"refs/heads/linux-3.14.y","head":"bdcec2cf3acd0d9ef24c653b722596f49ef6a040","before":"4ccf212fb84d79b75fc66a2e26ac6bdbab0aedbf","commits":[{"sha":"3adca859271e324203be08f2db54f0f685a66f9a","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"gpio: sysfs: fix memory leak in gpiod_export_link\n\ncommit 0f303db08df0df9bd0966443ad6001e63960af16 upstream.\n\nFix memory leak in the gpio sysfs interface due to failure to drop\nreference to device returned by class_find_device when creating a link.\n\nFixes: a4177ee7f1a8 (\"gpiolib: allow exported GPIO nodes to be named using sysfs links\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/3adca859271e324203be08f2db54f0f685a66f9a"},{"sha":"2739bb7a0087d57dc75f897fee2ef1407f2c3f08","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"gpio: sysfs: fix memory leak in gpiod_sysfs_set_active_low\n\ncommit 49d2ca84e433dab854c7a866bc6add09cfab682d upstream.\n\nFix memory leak in the gpio sysfs interface due to failure to drop\nreference to device returned by class_find_device when setting the\ngpio-line polarity.\n\nFixes: 0769746183ca (\"gpiolib: add support for changing value polarity in sysfs\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/2739bb7a0087d57dc75f897fee2ef1407f2c3f08"},{"sha":"65456b7b5e4ca49d5c8e5832a182ecd18b5cbbb4","author":{"email":"21a30bf11a11606e7a4fa755860c630f59961dc8@stratus.com","name":"Charlotte Richardson"},"message":"PCI: Add NEC variants to Stratus ftServer PCIe DMI check\n\ncommit 51ac3d2f0c505ca36ffc9715ffd518d756589ef8 upstream.\n\nNEC OEMs the same platforms as Stratus does, which have multiple devices on\nsome PCIe buses under downstream ports.\n\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=51331\nFixes: 1278998f8ff6 (\"PCI: Work around Stratus ftServer broken PCIe hierarchy (fix DMI check)\")\nSigned-off-by: Charlotte Richardson <charlotte.richardson@stratus.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nCC: Myron Stowe <myron.stowe@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/65456b7b5e4ca49d5c8e5832a182ecd18b5cbbb4"},{"sha":"f939ec038379751495a433f4e3d9e9d0bc73e845","author":{"email":"118ed6118e893d16e8c6e0776e0ebc290952c897@openwrt.org","name":"Felix Fietkau"},"message":"MIPS: IRQ: Fix disable_irq on CPU IRQs\n\ncommit a3e6c1eff54878506b2dddcc202df9cc8180facb upstream.\n\nIf the irq_chip does not define .irq_disable, any call to disable_irq\nwill defer disabling the IRQ until it fires while marked as disabled.\nThis assumes that the handler function checks for this condition, which\nhandle_percpu_irq does not. In this case, calling disable_irq leads to\nan IRQ storm, if the interrupt fires while disabled.\n\nThis optimization is only useful when disabling the IRQ is slow, which\nis not true for the MIPS CPU IRQ.\n\nDisable this optimization by implementing .irq_disable and .irq_enable\n\nSigned-off-by: Felix Fietkau <nbd@openwrt.org>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/8949/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/f939ec038379751495a433f4e3d9e9d0bc73e845"},{"sha":"1d594605fd5b38d6124e3f46b16ae50703d19a72","author":{"email":"13423a3f3006b5859cfceae66d59451f5eb4e205@iki.fi","name":"Aaro Koskinen"},"message":"MIPS: OCTEON: fix kernel crash when offlining a CPU\n\ncommit 63a87fe0d0de2ce126a8cec9a299a133cfd5658e upstream.\n\nocteon_cpu_disable() will unconditionally enable interrupts when called.\nWe can assume that the routine is always called with interrupts disabled,\nso just delete the incorrect local_irq_disable/enable().\n\nThe patch fixes the following crash when offlining a CPU:\n\n[   93.818785] ------------[ cut here ]------------\n[   93.823421] WARNING: CPU: 1 PID: 10 at kernel/smp.c:231 flush_smp_call_function_queue+0x1c4/0x1d0()\n[   93.836215] Modules linked in:\n[   93.839287] CPU: 1 PID: 10 Comm: migration/1 Not tainted 3.19.0-rc4-octeon-los_b5f0 #1\n[   93.847212] Stack : 0000000000000001 ffffffff81b2cf90 0000000000000004 ffffffff81630000\n\t  0000000000000000 0000000000000000 0000000000000000 000000000000004a\n\t  0000000000000006 ffffffff8117e550 0000000000000000 0000000000000000\n\t  ffffffff81b30000 ffffffff81b26808 8000000032c77748 ffffffff81627e07\n\t  ffffffff81595ec8 ffffffff81b26808 000000000000000a 0000000000000001\n\t  0000000000000001 0000000000000003 0000000010008ce1 ffffffff815030c8\n\t  8000000032cbbb38 ffffffff8113d42c 0000000010008ce1 ffffffff8117f36c\n\t  8000000032c77300 8000000032cbba50 0000000000000001 ffffffff81503984\n\t  0000000000000000 0000000000000000 0000000000000000 0000000000000000\n\t  0000000000000000 ffffffff81121668 0000000000000000 0000000000000000\n\t  ...\n[   93.912819] Call Trace:\n[   93.915273] [<ffffffff81121668>] show_stack+0x68/0x80\n[   93.920335] [<ffffffff81503984>] dump_stack+0x6c/0x90\n[   93.925395] [<ffffffff8113d58c>] warn_slowpath_common+0x94/0xd8\n[   93.931324] [<ffffffff811a402c>] flush_smp_call_function_queue+0x1c4/0x1d0\n[   93.938208] [<ffffffff811a4128>] hotplug_cfd+0xf0/0x108\n[   93.943444] [<ffffffff8115bacc>] notifier_call_chain+0x5c/0xb8\n[   93.949286] [<ffffffff8113d704>] cpu_notify+0x24/0x60\n[   93.954348] [<ffffffff81501738>] take_cpu_down+0x38/0x58\n[   93.959670] [<ffffffff811b343c>] multi_cpu_stop+0x154/0x180\n[   93.965250] [<ffffffff811b3768>] cpu_stopper_thread+0xd8/0x160\n[   93.971093] [<ffffffff8115ea4c>] smpboot_thread_fn+0x1ec/0x1f8\n[   93.976936] [<ffffffff8115ab04>] kthread+0xd4/0xf0\n[   93.981735] [<ffffffff8111c4f0>] ret_from_kernel_thread+0x14/0x1c\n[   93.987835]\n[   93.989326] ---[ end trace c9e3815ee655bda9 ]---\n[   93.993951] Kernel bug detected[#1]:\n[   93.997533] CPU: 1 PID: 10 Comm: migration/1 Tainted: G        W      3.19.0-rc4-octeon-los_b5f0 #1\n[   94.006591] task: 8000000032c77300 ti: 8000000032cb8000 task.ti: 8000000032cb8000\n[   94.014081] $ 0   : 0000000000000000 0000000010000ce1 0000000000000001 ffffffff81620000\n[   94.022146] $ 4   : 8000000002c72ac0 0000000000000000 00000000000001a7 ffffffff813b06f0\n[   94.030210] $ 8   : ffffffff813b20d8 0000000000000000 0000000000000000 ffffffff81630000\n[   94.038275] $12   : 0000000000000087 0000000000000000 0000000000000086 0000000000000000\n[   94.046339] $16   : ffffffff81623168 0000000000000001 0000000000000000 0000000000000008\n[   94.054405] $20   : 0000000000000001 0000000000000001 0000000000000001 0000000000000003\n[   94.062470] $24   : 0000000000000038 ffffffff813b7f10\n[   94.070536] $28   : 8000000032cb8000 8000000032cbbc20 0000000010008ce1 ffffffff811bcaf4\n[   94.078601] Hi    : 0000000000f188e8\n[   94.082179] Lo    : d4fdf3b646c09d55\n[   94.085760] epc   : ffffffff811bc9d0 irq_work_run_list+0x8/0xf8\n[   94.091686]     Tainted: G        W\n[   94.095613] ra    : ffffffff811bcaf4 irq_work_run+0x34/0x60\n[   94.101192] Status: 10000ce3\tKX SX UX KERNEL EXL IE\n[   94.106235] Cause : 40808034\n[   94.109119] PrId  : 000d9301 (Cavium Octeon II)\n[   94.113653] Modules linked in:\n[   94.116721] Process migration/1 (pid: 10, threadinfo=8000000032cb8000, task=8000000032c77300, tls=0000000000000000)\n[   94.127168] Stack : 8000000002c74c80 ffffffff811a4128 0000000000000001 ffffffff81635720\n\t  fffffffffffffff2 ffffffff8115bacc 80000000320fbce0 80000000320fbca4\n\t  80000000320fbc80 0000000000000002 0000000000000004 ffffffff8113d704\n\t  80000000320fbce0 ffffffff81501738 0000000000000003 ffffffff811b343c\n\t  8000000002c72aa0 8000000002c72aa8 ffffffff8159cae8 ffffffff8159caa0\n\t  ffffffff81650000 80000000320fbbf0 80000000320fbc80 ffffffff811b32e8\n\t  0000000000000000 ffffffff811b3768 ffffffff81622b80 ffffffff815148a8\n\t  8000000032c77300 8000000002c73e80 ffffffff815148a8 8000000032c77300\n\t  ffffffff81622b80 ffffffff815148a8 8000000032c77300 ffffffff81503f48\n\t  ffffffff8115ea0c ffffffff81620000 0000000000000000 ffffffff81174d64\n\t  ...\n[   94.192771] Call Trace:\n[   94.195222] [<ffffffff811bc9d0>] irq_work_run_list+0x8/0xf8\n[   94.200802] [<ffffffff811bcaf4>] irq_work_run+0x34/0x60\n[   94.206036] [<ffffffff811a4128>] hotplug_cfd+0xf0/0x108\n[   94.211269] [<ffffffff8115bacc>] notifier_call_chain+0x5c/0xb8\n[   94.217111] [<ffffffff8113d704>] cpu_notify+0x24/0x60\n[   94.222171] [<ffffffff81501738>] take_cpu_down+0x38/0x58\n[   94.227491] [<ffffffff811b343c>] multi_cpu_stop+0x154/0x180\n[   94.233072] [<ffffffff811b3768>] cpu_stopper_thread+0xd8/0x160\n[   94.238914] [<ffffffff8115ea4c>] smpboot_thread_fn+0x1ec/0x1f8\n[   94.244757] [<ffffffff8115ab04>] kthread+0xd4/0xf0\n[   94.249555] [<ffffffff8111c4f0>] ret_from_kernel_thread+0x14/0x1c\n[   94.255654]\n[   94.257146]\nCode: a2423c40  40026000  30420001 <00020336> dc820000  10400037  00000000  0000010f  0000010f\n[   94.267183] ---[ end trace c9e3815ee655bdaa ]---\n[   94.271804] Fatal exception: panic in 5 seconds\n\nReported-by: Hemmo Nieminen <hemmo.nieminen@iki.fi>\nSigned-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nAcked-by: David Daney <david.daney@cavium.com>\nCc: linux-mips@linux-mips.org\nCc: linux-kernel@vger.kernel.org\nPatchwork: https://patchwork.linux-mips.org/patch/8952/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/1d594605fd5b38d6124e3f46b16ae50703d19a72"},{"sha":"d7eb804c0bf631664b4157702ddbfa233e3086fd","author":{"email":"7da9702eed642c2e82fcf6b2f4145d9c11c095ec@iki.fi","name":"Hemmo Nieminen"},"message":"MIPS: Fix kernel lockup or crash after CPU offline/online\n\ncommit c7754e75100ed5e3068ac5085747f2bfc386c8d6 upstream.\n\nAs printk() invocation can cause e.g. a TLB miss, printk() cannot be\ncalled before the exception handlers have been properly initialized.\nThis can happen e.g. when netconsole has been loaded as a kernel module\nand the TLB table has been cleared when a CPU was offline.\n\nCall cpu_report() in start_secondary() only after the exception handlers\nhave been initialized to fix this.\n\nWithout the patch the kernel will randomly either lockup or crash\nafter a CPU is onlined and the console driver is a module.\n\nSigned-off-by: Hemmo Nieminen <hemmo.nieminen@iki.fi>\nSigned-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nCc: David Daney <david.daney@cavium.com>\nCc: linux-mips@linux-mips.org\nCc: linux-kernel@vger.kernel.org\nPatchwork: https://patchwork.linux-mips.org/patch/8953/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/d7eb804c0bf631664b4157702ddbfa233e3086fd"},{"sha":"95f61468e717054c464df5a3c8778e7c418258c4","author":{"email":"b913f13ef92ac157955c954ccaaff7be065faba4@arm.com","name":"Will Deacon"},"message":"ARM: 8299/1: mm: ensure local active ASID is marked as allocated on rollover\n\ncommit 8e64806672466392acf19e14427d1c29df3e58b9 upstream.\n\nCommit e1a5848e3398 (\"ARM: 7924/1: mm: don't bother with reserved ttbr0\nwhen running with LPAE\") removed the use of the reserved TTBR0 value\nfor LPAE systems, since the ASID is held in the TTBR and can be updated\natomicly with the pgd of the next mm.\n\nUnfortunately, this patch forgot to update flush_context, which\ndeliberately avoids marking the local active ASID as allocated, since we\nused to switch via ASID zero and didn't need to allocate the ASID of\nthe previous mm. The side-effect of this is that we can allocate the\nsame ASID to the next mm and, between flushing the local TLB and updating\nTTBR0, we can perform speculative TLB fills for userspace nG mappings\nusing the page table of the previous mm.\n\nThe consequence of this is that the next mm can erroneously hit some\nmappings of the previous mm. Note that this was made significantly\nharder to hit by a391263cd84e (\"ARM: 8203/1: mm: try to re-use old ASID\nassignments following a rollover\") but is still theoretically possible.\n\nThis patch fixes the problem by removing the code from flush_context\nthat forces the allocated ASID to zero for the local CPU. Many thanks\nto the Broadcom guys for tracking this one down.\n\nFixes: e1a5848e3398 (\"ARM: 7924/1: mm: don't bother with reserved ttbr0 when running with LPAE\")\n\nReported-by: Raymond Ngun <rngun@broadcom.com>\nTested-by: Raymond Ngun <rngun@broadcom.com>\nReviewed-by: Gregory Fong <gregory.0xf0@gmail.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/95f61468e717054c464df5a3c8778e7c418258c4"},{"sha":"7af7e9a4520845a95e43f2867f20050a12546716","author":{"email":"fe031bd268e574c3e649d0fd7ef4a978e9d7c1cd@redhat.com","name":"Sachin Prabhu"},"message":"Complete oplock break jobs before closing file handle\n\ncommit ca7df8e0bb2a5ec79691de8a1a4c0e611fe04e60 upstream.\n\nCommit\nc11f1df5003d534fd067f0168bfad7befffb3b5c\nrequires writers to wait for any pending oplock break handler to\ncomplete before proceeding to write. This is done by waiting on bit\nCIFS_INODE_PENDING_OPLOCK_BREAK in cifsFileInfo->flags. This bit is\ncleared by the oplock break handler job queued on the workqueue once it\nhas completed handling the oplock break allowing writers to proceed with\nwriting to the file.\n\nWhile testing, it was noticed that the filehandle could be closed while\nthere is a pending oplock break which results in the oplock break\nhandler on the cifsiod workqueue being cancelled before it has had a\nchance to execute and clear the CIFS_INODE_PENDING_OPLOCK_BREAK bit.\nAny subsequent attempt to write to this file hangs waiting for the\nCIFS_INODE_PENDING_OPLOCK_BREAK bit to be cleared.\n\nWe fix this by ensuring that we also clear the bit\nCIFS_INODE_PENDING_OPLOCK_BREAK when we remove the oplock break handler\nfrom the workqueue.\n\nThe bug was found by Red Hat QA while testing using ltp's fsstress\ncommand.\n\nSigned-off-by: Sachin Prabhu <sprabhu@redhat.com>\nAcked-by: Shirish Pargaonkar <shirishpargaonkar@gmail.com>\nSigned-off-by: Jeff Layton <jlayton@samba.org>\nSigned-off-by: Steve French <steve.french@primarydata.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/7af7e9a4520845a95e43f2867f20050a12546716"},{"sha":"75a94c278e5cca705c56d6e2308b68dda3788db6","author":{"email":"a62d066fcbab732c2ebe9cb02e2d29694a514faf@codeaurora.org","name":"Shiraz Hashim"},"message":"mm: pagewalk: call pte_hole() for VM_PFNMAP during walk_page_range\n\ncommit 23aaed6659df9adfabe9c583e67a36b54e21df46 upstream.\n\nwalk_page_range() silently skips vma having VM_PFNMAP set, which leads\nto undesirable behaviour at client end (who called walk_page_range).\nUserspace applications get the wrong data, so the effect is like just\nconfusing users (if the applications just display the data) or sometimes\nkilling the processes (if the applications do something with\nmisunderstanding virtual addresses due to the wrong data.)\n\nFor example for pagemap_read, when no callbacks are called against\nVM_PFNMAP vma, pagemap_read may prepare pagemap data for next virtual\naddress range at wrong index.\n\nEventually userspace may get wrong pagemap data for a task.\nCorresponding to a VM_PFNMAP marked vma region, kernel may report\nmappings from subsequent vma regions.  User space in turn may account\nmore pages (than really are) to the task.\n\nIn my case I was using procmem, procrack (Android utility) which uses\npagemap interface to account RSS pages of a task.  Due to this bug it\nwas giving a wrong picture for vmas (with VM_PFNMAP set).\n\nFixes: a9ff785e4437 (\"mm/pagewalk.c: walk_page_range should avoid VM_PFNMAP areas\")\nSigned-off-by: Shiraz Hashim <shashim@codeaurora.org>\nAcked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.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":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/75a94c278e5cca705c56d6e2308b68dda3788db6"},{"sha":"1ff733ae2347f93a20376defe1e6af77ede4da52","author":{"email":"5c8455eb353959a2a7e266fcc4f76fb65342dc20@gmail.com","name":"karl beldan"},"message":"lib/checksum.c: fix carry in csum_tcpudp_nofold\n\ncommit 150ae0e94634714b23919f0c333fee28a5b199d5 upstream.\n\nThe carry from the 64->32bits folding was dropped, e.g with:\nsaddr=0xFFFFFFFF daddr=0xFF0000FF len=0xFFFF proto=0 sum=1,\ncsum_tcpudp_nofold returned 0 instead of 1.\n\nSigned-off-by: Karl Beldan <karl.beldan@rivierawaves.com>\nCc: Al Viro <viro@ZenIV.linux.org.uk>\nCc: Eric Dumazet <eric.dumazet@gmail.com>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Mike Frysinger <vapier@gentoo.org>\nCc: netdev@vger.kernel.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/1ff733ae2347f93a20376defe1e6af77ede4da52"},{"sha":"52e87609d9d3ea34cadb5676e8ea85d025ac9632","author":{"email":"f414f2bdd839fdc054376382fa67e9bc2fbf206f@lab.ntt.co.jp","name":"Ryusuke Konishi"},"message":"nilfs2: fix deadlock of segment constructor over I_SYNC flag\n\ncommit 7ef3ff2fea8bf5e4a21cef47ad87710a3d0fdb52 upstream.\n\nNilfs2 eventually hangs in a stress test with fsstress program.  This\nissue was caused by the following deadlock over I_SYNC flag between\nnilfs_segctor_thread() and writeback_sb_inodes():\n\n  nilfs_segctor_thread()\n    nilfs_segctor_thread_construct()\n      nilfs_segctor_unlock()\n        nilfs_dispose_list()\n          iput()\n            iput_final()\n              evict()\n                inode_wait_for_writeback()  * wait for I_SYNC flag\n\n  writeback_sb_inodes()\n     * set I_SYNC flag on inode->i_state\n    __writeback_single_inode()\n      do_writepages()\n        nilfs_writepages()\n          nilfs_construct_dsync_segment()\n            nilfs_segctor_sync()\n               * wait for completion of segment constructor\n    inode_sync_complete()\n       * clear I_SYNC flag after __writeback_single_inode() completed\n\nwriteback_sb_inodes() calls do_writepages() for dirty inodes after\nsetting I_SYNC flag on inode->i_state.  do_writepages() in turn calls\nnilfs_writepages(), which can run segment constructor and wait for its\ncompletion.  On the other hand, segment constructor calls iput(), which\ncan call evict() and wait for the I_SYNC flag on\ninode_wait_for_writeback().\n\nSince segment constructor doesn't know when I_SYNC will be set, it\ncannot know whether iput() will block or not unless inode->i_nlink has a\nnon-zero count.  We can prevent evict() from being called in iput() by\nimplementing sop->drop_inode(), but it's not preferable to leave inodes\nwith i_nlink == 0 for long periods because it even defers file\ntruncation and inode deallocation.  So, this instead resolves the\ndeadlock by calling iput() asynchronously with a workqueue for inodes\nwith i_nlink == 0.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nTested-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>\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":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/52e87609d9d3ea34cadb5676e8ea85d025ac9632"},{"sha":"7b823e82af87ae951a957d241934fc807a76fe8e","author":{"email":"c0ce8600dd827d60b78832d91910a4aff4385d56@gmx.net","name":"Peter Kümmel"},"message":"kconfig: Fix warning \"‘jump’ may be used uninitialized\"\n\ncommit 2d560306096739e2251329ab5c16059311a151b0 upstream.\n\nWarning:\nIn file included from scripts/kconfig/zconf.tab.c:2537:0:\nscripts/kconfig/menu.c: In function ‘get_symbol_str’:\nscripts/kconfig/menu.c:590:18: warning: ‘jump’ may be used uninitialized in this function [-Wmaybe-uninitialized]\n     jump->offset = strlen(r->s);\n\nSimplifies the test logic because (head && local) means (jump != 0)\nand makes GCC happy when checking if the jump pointer was initialized.\n\nSigned-off-by: Peter Kümmel <syntheticpp@gmx.net>\nSigned-off-by: Michal Marek <mmarek@suse.cz>\nCc: Sedat Dilek <sedat.dilek@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/7b823e82af87ae951a957d241934fc807a76fe8e"},{"sha":"42b34c73ae40e3158779a5d47dcd514702804613","author":{"email":"1db9dd262beaa64f35756dd39531d9747b7778bb@arm.com","name":"Mark Rutland"},"message":"arm64: Fix up /proc/cpuinfo\n\ncommit 44b82b7700d05a52cd983799d3ecde1a976b3bed upstream.\n\nCommit d7a49086f263164a (arm64: cpuinfo: print info for all CPUs)\nattempted to clean up /proc/cpuinfo, but due to concerns regarding\nfurther changes was reverted in commit 5e39977edf6500fd (Revert \"arm64:\ncpuinfo: print info for all CPUs\").\n\nThere are two major issues with the arm64 /proc/cpuinfo format\ncurrently:\n\n* The \"Features\" line describes (only) the 64-bit hwcaps, which is\n  problematic for some 32-bit applications which attempt to parse it. As\n  the same names are used for analogous ISA features (e.g. aes) despite\n  these generally being architecturally unrelated, it is not possible to\n  simply append the 64-bit and 32-bit hwcaps in a manner that might not\n  be misleading to some applications.\n\n  Various potential solutions have appeared in vendor kernels. Typically\n  the format of the Features line varies depending on whether the task\n  is 32-bit.\n\n* Information is only printed regarding a single CPU. This does not\n  match the ARM format, and does not provide sufficient information in\n  big.LITTLE systems where CPUs are heterogeneous. The CPU information\n  printed is queried from the current CPU's registers, which is racy\n  w.r.t. cross-cpu migration.\n\nThis patch attempts to solve these issues. The following changes are\nmade:\n\n* When a task with a LINUX32 personality attempts to read /proc/cpuinfo,\n  the \"Features\" line contains the decoded 32-bit hwcaps, as with the\n  arm port. Otherwise, the decoded 64-bit hwcaps are shown. This aligns\n  with the behaviour of COMPAT_UTS_MACHINE and COMPAT_ELF_PLATFORM. In\n  the absense of compat support, the Features line is empty.\n\n  The set of hwcaps injected into a task's auxval are unaffected.\n\n* Properties are printed per-cpu, as with the ARM port. The per-cpu\n  information is queried from pre-recorded cpu information (as used by\n  the sanity checks).\n\n* As with the previous attempt at fixing up /proc/cpuinfo, the hardware\n  field is removed. The only users so far are 32-bit applications tied\n  to particular boards, so no portable applications should be affected,\n  and this should prevent future tying to particular boards.\n\nThe following differences remain:\n\n* No model_name is printed, as this cannot be queried from the hardware\n  and cannot be provided in a stable fashion. Use of the CPU\n  {implementor,variant,part,revision} fields is sufficient to identify a\n  CPU and is portable across arm and arm64.\n\n* The following system-wide properties are not provided, as they are not\n  possible to provide generally. Programs relying on these are already\n  tied to particular (32-bit only) boards:\n  - Hardware\n  - Revision\n  - Serial\n\nNo software has yet been identified for which these remaining\ndifferences are problematic.\n\nCc: Greg Hackmann <ghackmann@google.com>\nCc: Ian Campbell <ijc@hellion.org.uk>\nCc: Serban Constantinescu <serban.constantinescu@arm.com>\nCc: Will Deacon <will.deacon@arm.com>\nCc: cross-distro@lists.linaro.org\nCc: linux-api@vger.kernel.org\nCc: linux-arm-kernel@lists.infradead.org\nCc: linux-kernel@vger.kernel.org\nAcked-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/42b34c73ae40e3158779a5d47dcd514702804613"},{"sha":"07110343605adc3f8ddfc0dde38d29d2e0e210a2","author":{"email":"eecfa5af1016ca9db755569d9919e212ab6a1c94@openvz.org","name":"Dmitry Monakhov"},"message":"ext4: prevent bugon on race between write/fcntl\n\ncommit a41537e69b4aa43f0fea02498c2595a81267383b upstream.\n\nO_DIRECT flags can be toggeled via fcntl(F_SETFL). But this value checked\ntwice inside ext4_file_write_iter() and __generic_file_write() which\nresult in BUG_ON inside ext4_direct_IO.\n\nLet's initialize iocb->private unconditionally.\n\nTESTCASE: xfstest:generic/036  https://patchwork.ozlabs.org/patch/402445/\n\n#TYPICAL STACK TRACE:\nkernel BUG at fs/ext4/inode.c:2960!\ninvalid opcode: 0000 [#1] SMP\nModules linked in: brd iTCO_wdt lpc_ich mfd_core igb ptp dm_mirror dm_region_hash dm_log dm_mod\nCPU: 6 PID: 5505 Comm: aio-dio-fcntl-r Not tainted 3.17.0-rc2-00176-gff5c017 #161\nHardware name: Intel Corporation W2600CR/W2600CR, BIOS SE5C600.86B.99.99.x028.061320111235 06/13/2011\ntask: ffff88080e95a7c0 ti: ffff88080f908000 task.ti: ffff88080f908000\nRIP: 0010:[<ffffffff811fabf2>]  [<ffffffff811fabf2>] ext4_direct_IO+0x162/0x3d0\nRSP: 0018:ffff88080f90bb58  EFLAGS: 00010246\nRAX: 0000000000000400 RBX: ffff88080fdb2a28 RCX: 00000000a802c818\nRDX: 0000040000080000 RSI: ffff88080d8aeb80 RDI: 0000000000000001\nRBP: ffff88080f90bbc8 R08: 0000000000000000 R09: 0000000000001581\nR10: 0000000000000000 R11: 0000000000000000 R12: ffff88080d8aeb80\nR13: ffff88080f90bbf8 R14: ffff88080fdb28c8 R15: ffff88080fdb2a28\nFS:  00007f23b2055700(0000) GS:ffff880818400000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f23b2045000 CR3: 000000080cedf000 CR4: 00000000000407e0\nStack:\n ffff88080f90bb98 0000000000000000 7ffffffffffffffe ffff88080fdb2c30\n 0000000000000200 0000000000000200 0000000000000001 0000000000000200\n ffff88080f90bbc8 ffff88080fdb2c30 ffff88080f90be08 0000000000000200\nCall Trace:\n [<ffffffff8112ca9d>] generic_file_direct_write+0xed/0x180\n [<ffffffff8112f2b2>] __generic_file_write_iter+0x222/0x370\n [<ffffffff811f495b>] ext4_file_write_iter+0x34b/0x400\n [<ffffffff811bd709>] ? aio_run_iocb+0x239/0x410\n [<ffffffff811bd709>] ? aio_run_iocb+0x239/0x410\n [<ffffffff810990e5>] ? local_clock+0x25/0x30\n [<ffffffff810abd94>] ? __lock_acquire+0x274/0x700\n [<ffffffff811f4610>] ? ext4_unwritten_wait+0xb0/0xb0\n [<ffffffff811bd756>] aio_run_iocb+0x286/0x410\n [<ffffffff810990e5>] ? local_clock+0x25/0x30\n [<ffffffff810ac359>] ? lock_release_holdtime+0x29/0x190\n [<ffffffff811bc05b>] ? lookup_ioctx+0x4b/0xf0\n [<ffffffff811bde3b>] do_io_submit+0x55b/0x740\n [<ffffffff811bdcaa>] ? do_io_submit+0x3ca/0x740\n [<ffffffff811be030>] SyS_io_submit+0x10/0x20\n [<ffffffff815ce192>] system_call_fastpath+0x16/0x1b\nCode: 01 48 8b 80 f0 01 00 00 48 8b 18 49 8b 45 10 0f 85 f1 01 00 00 48 03 45 c8 48 3b 43 48 0f 8f e3 01 00 00 49 83 7c\n24 18 00 75 04 <0f> 0b eb fe f0 ff 83 ec 01 00 00 49 8b 44 24 18 8b 00 85 c0 89\nRIP  [<ffffffff811fabf2>] ext4_direct_IO+0x162/0x3d0\n RSP <ffff88080f90bb58>\n\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Dmitry Monakhov <dmonakhov@openvz.org>\n[hujianyang: Backported to 3.10\n - Move initialization of iocb->private to ext4_file_write() as we don't\n   have ext4_file_write_iter(), which is introduced by commit 9b884164.\n - Adjust context to make 'overwrite' changes apply to ext4_file_dio_write()\n   as ext4_file_dio_write() is not move into ext4_file_write()]\nSigned-off-by: hujianyang <hujianyang@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/07110343605adc3f8ddfc0dde38d29d2e0e210a2"},{"sha":"52e81bd56fa4bc2c424dc3ac8283821839c5a329","author":{"email":"5c8455eb353959a2a7e266fcc4f76fb65342dc20@gmail.com","name":"karl beldan"},"message":"lib/checksum.c: fix build for generic csum_tcpudp_nofold\n\ncommit 9ce357795ef208faa0d59894d9d119a7434e37f3 upstream.\n\nFixed commit added from64to32 under _#ifndef do_csum_ but used it\nunder _#ifndef csum_tcpudp_nofold_, breaking some builds (Fengguang's\nrobot reported TILEGX's). Move from64to32 under the latter.\n\nFixes: 150ae0e94634 (\"lib/checksum.c: fix carry in csum_tcpudp_nofold\")\nReported-by: kbuild test robot <fengguang.wu@intel.com>\nSigned-off-by: Karl Beldan <karl.beldan@rivierawaves.com>\nCc: Eric Dumazet <edumazet@google.com>\nCc: David S. Miller <davem@davemloft.net>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/52e81bd56fa4bc2c424dc3ac8283821839c5a329"},{"sha":"e23daf1c3a2215e95b7c57c6e20beb4c7a08b599","author":{"email":"b3e6a3251704a94eee1cf08e0adc382e6cb535ee@atmel.com","name":"Bo Shen"},"message":"ASoC: atmel_ssc_dai: fix start event for I2S mode\n\ncommit a43bd7e125143b875caae6d4f9938855b440faaf upstream.\n\nAccording to the I2S specification information as following:\n  - WS = 0, channel 1 (left)\n  - WS = 1, channel 2 (right)\nSo, the start event should be TF/RF falling edge.\n\nReported-by: Songjun Wu <songjun.wu@atmel.com>\nSigned-off-by: Bo Shen <voice.shen@atmel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/e23daf1c3a2215e95b7c57c6e20beb4c7a08b599"},{"sha":"48e81ac2e37ec765f0885c0acc7b63f91f21da24","author":{"email":"3613bade79ee1cd4cc74802f4c7c26501a46456e@boundarydevices.com","name":"Eric Nelson"},"message":"ASoC: sgtl5000: add delay before first I2C access\n\ncommit 58cc9c9a175885bbf6bae3acf18233d0a8229a84 upstream.\n\nTo quote from section 1.3.1 of the data sheet:\n\tThe SGTL5000 has an internal reset that is deasserted\n\t8 SYS_MCLK cycles after all power rails have been brought\n\tup. After this time, communication can start\n\n\t...\n\t1.0us represents 8 SYS_MCLK cycles at the minimum 8.0 MHz SYS_MCLK.\n\nSigned-off-by: Eric Nelson <eric.nelson@boundarydevices.com>\nReviewed-by: Fabio Estevam <fabio.estevam@freescale.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/48e81ac2e37ec765f0885c0acc7b63f91f21da24"},{"sha":"2451dcefc2bcd083460b0e39118a00d940ca6a8a","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: ak411x: Fix stall in work callback\n\ncommit 4161b4505f1690358ac0a9ee59845a7887336b21 upstream.\n\nWhen ak4114 work calls its callback and the callback invokes\nak4114_reinit(), it stalls due to flush_delayed_work().  For avoiding\nthis, control the reentrance by introducing a refcount.  Also\nflush_delayed_work() is replaced with cancel_delayed_work_sync().\n\nThe exactly same bug is present in ak4113.c and fixed as well.\n\nReported-by: Pavel Hofman <pavel.hofman@ivitera.com>\nAcked-by: Jaroslav Kysela <perex@perex.cz>\nTested-by: Pavel Hofman <pavel.hofman@ivitera.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/2451dcefc2bcd083460b0e39118a00d940ca6a8a"},{"sha":"4748a404df64c684505af382ab9d8d6607289be3","author":{"email":"4c9eb49378914b743bdd32292c04df29b820d73e@cn.fujitsu.com","name":"Lai Jiangshan"},"message":"smpboot: Add missing get_online_cpus() in smpboot_register_percpu_thread()\n\ncommit 4bee96860a65c3a62d332edac331b3cf936ba3ad upstream.\n\nThe following race exists in the smpboot percpu threads management:\n\nCPU0\t      \t   \t     CPU1\ncpu_up(2)\n  get_online_cpus();\n  smpboot_create_threads(2);\n\t\t\t     smpboot_register_percpu_thread();\n\t\t\t     for_each_online_cpu();\n\t\t\t       __smpboot_create_thread();\n  __cpu_up(2);\n\nThis results in a missing per cpu thread for the newly onlined cpu2 and\nin a NULL pointer dereference on a consecutive offline of that cpu.\n\nProctect smpboot_register_percpu_thread() with get_online_cpus() to\nprevent that.\n\n[ tglx: Massaged changelog and removed the change in\n        smpboot_unregister_percpu_thread() because that's an\n        optimization and therefor not stable material. ]\n\nSigned-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Rusty Russell <rusty@rustcorp.com.au>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nCc: David Rientjes <rientjes@google.com>\nLink: http://lkml.kernel.org/r/1406777421-12830-1-git-send-email-laijs@cn.fujitsu.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/4748a404df64c684505af382ab9d8d6607289be3"},{"sha":"5fb88e88031daf17e29ba5c679fe5ec4b8047e1a","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@amacapital.net","name":"Andy Lutomirski"},"message":"x86,kvm,vmx: Preserve CR4 across VM entry\n\ncommit d974baa398f34393db76be45f7d4d04fbdbb4a0a upstream.\n\nCR4 isn't constant; at least the TSD and PCE bits can vary.\n\nTBH, treating CR0 and CR3 as constant scares me a bit, too, but it looks\nlike it's correct.\n\nThis adds a branch and a read from cr4 to each vm entry.  Because it is\nextremely likely that consecutive entries into the same vcpu will have\nthe same host cr4 value, this fixes up the vmcs instead of restoring cr4\nafter the fact.  A subsequent patch will add a kernel-wide cr4 shadow,\nreducing the overhead in the common case to just two memory reads and a\nbranch.\n\nSigned-off-by: Andy Lutomirski <luto@amacapital.net>\nAcked-by: Paolo Bonzini <pbonzini@redhat.com>\nCc: Petr Matousek <pmatouse@redhat.com>\nCc: Gleb Natapov <gleb@kernel.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[wangkai: Backport to 3.10: adjust context]\nSigned-off-by: Wang Kai <morgan.wang@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/5fb88e88031daf17e29ba5c679fe5ec4b8047e1a"}]}