{"push_id":972872680,"size":34,"distinct_size":34,"ref":"refs/heads/master","head":"721675fcf277cfd345117d3abae1c5590c5fdfd4","before":"2178cbc68f3602dc0b5949b9be2c8383ad3d93ef","commits":[{"sha":"e93ad19d05648397ef3bcb838d26aec06c245dc0","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"cpuset: make mm migration asynchronous\n\nIf \"cpuset.memory_migrate\" is set, when a process is moved from one\ncpuset to another with a different memory node mask, pages in used by\nthe process are migrated to the new set of nodes.  This was performed\nsynchronously in the ->attach() callback, which is synchronized\nagainst process management.  Recently, the synchronization was changed\nfrom per-process rwsem to global percpu rwsem for simplicity and\noptimization.\n\nCombined with the synchronous mm migration, this led to deadlocks\nbecause mm migration could schedule a work item which may in turn try\nto create a new worker blocking on the process management lock held\nfrom cgroup process migration path.\n\nThis heavy an operation shouldn't be performed synchronously from that\ndeep inside cgroup migration in the first place.  This patch punts the\nactual migration to an ordered workqueue and updates cgroup process\nmigration and cpuset config update paths to flush the workqueue after\nall locks are released.  This way, the operations still seem\nsynchronous to userland without entangling mm migration with process\nmanagement synchronization.  CPU hotplug can also invoke mm migration\nbut there's no reason for it to wait for mm migrations and thus\ndoesn't synchronize against their completions.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-and-tested-by: Christian Borntraeger <borntraeger@de.ibm.com>\nCc: stable@vger.kernel.org # v4.4+","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/e93ad19d05648397ef3bcb838d26aec06c245dc0"},{"sha":"aa226ff4a1ce79f229c6b7a4c0a14e17fececd01","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"cgroup: make sure a parent css isn't offlined before its children\n\nThere are three subsystem callbacks in css shutdown path -\ncss_offline(), css_released() and css_free().  Except for\ncss_released(), cgroup core didn't guarantee the order of invocation.\ncss_offline() or css_free() could be called on a parent css before its\nchildren.  This behavior is unexpected and led to bugs in cpu and\nmemory controller.\n\nThis patch updates offline path so that a parent css is never offlined\nbefore its children.  Each css keeps online_cnt which reaches zero iff\nitself and all its children are offline and offline_css() is invoked\nonly after online_cnt reaches zero.\n\nThis fixes the memory controller bug and allows the fix for cpu\ncontroller.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-and-tested-by: Christian Borntraeger <borntraeger@de.ibm.com>\nReported-by: Brian Christiansen <brian.o.christiansen@gmail.com>\nLink: http://lkml.kernel.org/g/5698A023.9070703@de.ibm.com\nLink: http://lkml.kernel.org/g/CAKB58ikDkzc8REt31WBkD99+hxNzjK4+FBmhkgS+NVrC9vjMSg@mail.gmail.com\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/aa226ff4a1ce79f229c6b7a4c0a14e17fececd01"},{"sha":"8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"cgroup: make sure a parent css isn't freed before its children\n\nThere are three subsystem callbacks in css shutdown path -\ncss_offline(), css_released() and css_free().  Except for\ncss_released(), cgroup core didn't guarantee the order of invocation.\ncss_offline() or css_free() could be called on a parent css before its\nchildren.  This behavior is unexpected and led to bugs in cpu and\nmemory controller.\n\nThe previous patch updated ordering for css_offline() which fixes the\ncpu controller issue.  While there currently isn't a known bug caused\nby misordering of css_free() invocations, let's fix it too for\nconsistency.\n\ncss_free() ordering can be trivially fixed by moving putting of the\nparent css below css_free() invocation.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4"},{"sha":"fb3296335500aaff61333df8eabbccf28761c79d","author":{"email":"08e19e96e5a6ac61790e54f6ea8bc3b1fdb92d4d@broadcom.com","name":"Danesh Petigara"},"message":"drivers: ata: wake port before DMA stop for ALPM\n\nThe AHCI driver code stops and starts port DMA engines at will\nwithout considering the power state of the particular port. The\nAHCI specification isn't very clear on how to handle this scenario,\nleaving implementation open to interpretation.\n\nBroadcom's STB SATA host controller is unable to handle port DMA\ncontroller restarts when the port in question is in low power mode.\nWhen a port enters partial or slumber mode, its PHY is powered down.\nWhen a controller restart is requested, the controller's internal\nstate machine expects the PHY to be brought back up by software which\nnever happens in this case, resulting in failures.\n\nTo avoid this situation, logic is added to manually wake up the port\njust before its DMA engine is stopped, if the port happens to be in\na low power state. HBA initiated power management ensures that the port\neventually returns to its configured low power state, when the link is\nidle (as per the conditions listed in the spec). A new host flag is also\nadded to ensure this logic is only exercised for hosts with the above\nlimitation.\n\ntj: Formatting changes.\n\nSigned-off-by: Danesh Petigara <dpetigara@broadcom.com>\nReviewed-by: Markus Mayer <mmayer@broadcom.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/fb3296335500aaff61333df8eabbccf28761c79d"},{"sha":"b00622fc34e9d45069bd6e328dfd47ea2ef61468","author":{"email":"47253168cf85700675d267e3faa36db3fb600ea3@cisco.com","name":"Shikha Jain"},"message":"libata: blacklist a Viking flash model for MWDMA corruption\n\nViking flash model VRFDFC22048UCHC-TE causes data corruption in MWDMA mode.\n\nCc: xe-kernel@external.cisco.com\nSigned-off-by: Shikha Jain <shikjain@cisco.com>\nSigned-off-by: Anil Veliyankara Madam <aveliyan@cisco.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/b00622fc34e9d45069bd6e328dfd47ea2ef61468"},{"sha":"566d1827df2ef0cbe921d3d6946ac3007b1a6938","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"libata: disable forced PORTS_IMPL for >= AHCI 1.3\n\nSome early controllers incorrectly reported zero ports in PORTS_IMPL\nregister and the ahci driver fabricates PORTS_IMPL from the number of\nports in those cases.  This hasn't mattered but with the new nvme\ncontrollers there are cases where zero PORTS_IMPL is valid and should\nbe honored.\n\nDisable the workaround for >= AHCI 1.3.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-by: Andy Lutomirski <luto@amacapital.net>\nLink: http://lkml.kernel.org/g/CALCETrU7yMvXEDhjAUShoHEhDwifJGapdw--BKxsP0jmjKGmRw@mail.gmail.com\nCc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/566d1827df2ef0cbe921d3d6946ac3007b1a6938"},{"sha":"a6ed4a18ba6a6f5a01e024b9d221d6439bf6ca4c","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Input: xpad - remove unused function\n\nThere are two definitions of xpad_identify_controller(), one is used\nwhen CONFIG_JOYSTICK_XPAD_LEDS is set, but the other one is empty\nand never used, and we get a gcc warning about it:\n\ndrivers/input/joystick/xpad.c:1210:13: warning: 'xpad_identify_controller' defined but not used [-Wunused-function]\n\nThis removes the second definition.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nFixes: cae705baa40b (\"Input: xpad - re-send LED command on present event\")\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/a6ed4a18ba6a6f5a01e024b9d221d6439bf6ca4c"},{"sha":"af6e94634d0a77aa42a9fdee35abd00a95b4ca54","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Input: sirfsoc-onkey - allow modular build\n\nCONFIG_INPUT may itself be a loadable module, but the sirf power key\ndriver is listed as 'bool', which makes it possible to select\na broken configuration with the driver built-in but the subsystem\nnot loaded. In this configuration, we get a link error:\n\ndrivers/input/built-in.o: In function `sirfsoc_pwrc_isr':\ndrivers/input/misc/sirfsoc-onkey.c:63: undefined reference to `input_event'\ndrivers/input/built-in.o: In function `sirfsoc_pwrc_isr':\ninclude/linux/input.h:414: undefined reference to `input_event'\ndrivers/input/built-in.o: In function `sirfsoc_pwrc_probe':\ndrivers/input/misc/sirfsoc-onkey.c:132: undefined reference to `devm_input_allocate_device'\ndrivers/input/misc/sirfsoc-onkey.c:139: undefined reference to `input_set_capability'\ndrivers/input/misc/sirfsoc-onkey.c:161: undefined reference to `input_register_device'\ndrivers/input/built-in.o: In function `sirfsoc_pwrc_report_event':\ndrivers/input/misc/sirfsoc-onkey.c:48: undefined reference to `input_event'\ndrivers/input/built-in.o: In function `sirfsoc_pwrc_report_event':\ninclude/linux/input.h:414: undefined reference to `input_event'\ndrivers/input/built-in.o:(.debug_addr+0x24): undefined reference to `input_event'\ndrivers/input/built-in.o:(.debug_addr+0xbc): undefined reference to `devm_input_allocate_device'\ndrivers/input/built-in.o:(.debug_addr+0x104): undefined reference to `input_set_capability'\ndrivers/input/built-in.o:(.debug_addr+0x128): undefined reference to `input_register_device'\n\nThis marks the driver as 'tristate' so it becomes possible to have\nit in a loadable module, mainly to help with randconfig builds.\n\nWe also have to add a missing semicolon here, which ended up not\nbeing needed in built-in mode because the following MODULE_DEVICE_TABLE\nis an empty macro followed by another semicolon then.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/af6e94634d0a77aa42a9fdee35abd00a95b4ca54"},{"sha":"497e1b3f6b6d3cf2206d15687eb7bfa0ab0e968d","author":{"email":"4515e699e2ac78ad2253451343b05f644c855b8c@gmail.com","name":"Amitoj Kaur Chawla"},"message":"Input: cap11xx - add missing of_node_put\n\nfor_each_child_of_node performs an of_node_get on each iteration, so\nto break out of the loop an of_node_put is required.\n\nFound using Coccinelle.\n\nSigned-off-by: Amitoj Kaur Chawla <amitoj1606@gmail.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/497e1b3f6b6d3cf2206d15687eb7bfa0ab0e968d"},{"sha":"015bb5e134544492d840cee17d7442194cfb0fe4","author":{"email":"bfa0a1520768723a1c60e18250fb841c342eb8d8@ti.com","name":"Grygorii Strashko"},"message":"Input: serio - drop warnings in case of EPROBE_DEFER from serio_find_driver()\n\nNow serio_find_driver() will print warnings in case device_attach()\nreturns -EPROBE_DEFER. Those warnings are obsolete, in genral, because:\n- DD core can report the same if required\n- since commit 013c074f8642 (\"PM / sleep: prohibit devices probing\nduring suspend/hibernation\") the devices probing is prohibited during\nSystem suspend and deferred device will be carefully reprobed once\nResume is finished.\n\nHence, drop warnings in case of EPROBE_DEFER from serio_find_driver().\n\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nAcked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/015bb5e134544492d840cee17d7442194cfb0fe4"},{"sha":"d4f1b06d685d11ebdaccf11c0db1cb3c78736862","author":{"email":"6b8646d310837fed93a129ed3c979b90c7f2674f@gmail.com","name":"Dmitry Torokhov"},"message":"Input: vmmouse - fix absolute device registration\n\nWe should set device's capabilities first, and then register it,\notherwise various handlers already present in the kernel will not be\nable to connect to the device.\n\nReported-by: Lauri Kasanen <cand@gmx.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/d4f1b06d685d11ebdaccf11c0db1cb3c78736862"},{"sha":"9a2ddda572a002633a64b1ae5f4bc49cfcbf495f","author":{"email":"f75897670c17327c42ab201733fb8a81ff9f4c34@tremily.us","name":"W. Trevor King"},"message":"Documentation: cgroup: Fix 'cgroup-legacy' -> 'cgroup-v1'\n\nThis should have happened in 6255c46f (cgroup: rename cgroup\ndocumentations, 2016-01-11).\n\nSigned-off-by: W. Trevor King <wking@tremily.us>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/9a2ddda572a002633a64b1ae5f4bc49cfcbf495f"},{"sha":"a588afc920bc50e894f6ae2874c4281c795e0979","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"libata-sff: use WARN instead of BUG on illegal host state machine state\n\nata_sff_hsm_move() triggers BUG if it sees a host state machine state\nthat it dind't expect.  The risk for data corruption when the\ncondition occurs is low as it's highly unlikely that it would lead to\nspurious completion of commands.  The BUG occasionally triggered for\nsubtle race conditions in the driver.  Let's downgrade it to WARN so\nthat it doesn't kill the machine unnecessarily.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nCc: Dmitry Vyukov <dvyukov@google.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/a588afc920bc50e894f6ae2874c4281c795e0979"},{"sha":"23d11a58a9a60dcb52c8fc6494efce908b24c295","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"workqueue: skip flush dependency checks for legacy workqueues\n\nfca839c00a12 (\"workqueue: warn if memory reclaim tries to flush\n!WQ_MEM_RECLAIM workqueue\") implemented flush dependency warning which\ntriggers if a PF_MEMALLOC task or WQ_MEM_RECLAIM workqueue tries to\nflush a !WQ_MEM_RECLAIM workquee.\n\nThis assumes that workqueues marked with WQ_MEM_RECLAIM sit in memory\nreclaim path and making it depend on something which may need more\nmemory to make forward progress can lead to deadlocks.  Unfortunately,\nworkqueues created with the legacy create*_workqueue() interface\nalways have WQ_MEM_RECLAIM regardless of whether they are depended\nupon memory reclaim or not.  These spurious WQ_MEM_RECLAIM markings\ncause spurious triggering of the flush dependency checks.\n\n  WARNING: CPU: 0 PID: 6 at kernel/workqueue.c:2361 check_flush_dependency+0x138/0x144()\n  workqueue: WQ_MEM_RECLAIM deferwq:deferred_probe_work_func is flushing !WQ_MEM_RECLAIM events:lru_add_drain_per_cpu\n  ...\n  Workqueue: deferwq deferred_probe_work_func\n  [<c0017acc>] (unwind_backtrace) from [<c0013134>] (show_stack+0x10/0x14)\n  [<c0013134>] (show_stack) from [<c0245f18>] (dump_stack+0x94/0xd4)\n  [<c0245f18>] (dump_stack) from [<c0026f9c>] (warn_slowpath_common+0x80/0xb0)\n  [<c0026f9c>] (warn_slowpath_common) from [<c0026ffc>] (warn_slowpath_fmt+0x30/0x40)\n  [<c0026ffc>] (warn_slowpath_fmt) from [<c00390b8>] (check_flush_dependency+0x138/0x144)\n  [<c00390b8>] (check_flush_dependency) from [<c0039ca0>] (flush_work+0x50/0x15c)\n  [<c0039ca0>] (flush_work) from [<c00c51b0>] (lru_add_drain_all+0x130/0x180)\n  [<c00c51b0>] (lru_add_drain_all) from [<c00f728c>] (migrate_prep+0x8/0x10)\n  [<c00f728c>] (migrate_prep) from [<c00bfbc4>] (alloc_contig_range+0xd8/0x338)\n  [<c00bfbc4>] (alloc_contig_range) from [<c00f8f18>] (cma_alloc+0xe0/0x1ac)\n  [<c00f8f18>] (cma_alloc) from [<c001cac4>] (__alloc_from_contiguous+0x38/0xd8)\n  [<c001cac4>] (__alloc_from_contiguous) from [<c001ceb4>] (__dma_alloc+0x240/0x278)\n  [<c001ceb4>] (__dma_alloc) from [<c001cf78>] (arm_dma_alloc+0x54/0x5c)\n  [<c001cf78>] (arm_dma_alloc) from [<c0355ea4>] (dmam_alloc_coherent+0xc0/0xec)\n  [<c0355ea4>] (dmam_alloc_coherent) from [<c039cc4c>] (ahci_port_start+0x150/0x1dc)\n  [<c039cc4c>] (ahci_port_start) from [<c0384734>] (ata_host_start.part.3+0xc8/0x1c8)\n  [<c0384734>] (ata_host_start.part.3) from [<c03898dc>] (ata_host_activate+0x50/0x148)\n  [<c03898dc>] (ata_host_activate) from [<c039d558>] (ahci_host_activate+0x44/0x114)\n  [<c039d558>] (ahci_host_activate) from [<c039f05c>] (ahci_platform_init_host+0x1d8/0x3c8)\n  [<c039f05c>] (ahci_platform_init_host) from [<c039e6bc>] (tegra_ahci_probe+0x448/0x4e8)\n  [<c039e6bc>] (tegra_ahci_probe) from [<c0347058>] (platform_drv_probe+0x50/0xac)\n  [<c0347058>] (platform_drv_probe) from [<c03458cc>] (driver_probe_device+0x214/0x2c0)\n  [<c03458cc>] (driver_probe_device) from [<c0343cc0>] (bus_for_each_drv+0x60/0x94)\n  [<c0343cc0>] (bus_for_each_drv) from [<c03455d8>] (__device_attach+0xb0/0x114)\n  [<c03455d8>] (__device_attach) from [<c0344ab8>] (bus_probe_device+0x84/0x8c)\n  [<c0344ab8>] (bus_probe_device) from [<c0344f48>] (deferred_probe_work_func+0x68/0x98)\n  [<c0344f48>] (deferred_probe_work_func) from [<c003b738>] (process_one_work+0x120/0x3f8)\n  [<c003b738>] (process_one_work) from [<c003ba48>] (worker_thread+0x38/0x55c)\n  [<c003ba48>] (worker_thread) from [<c0040f14>] (kthread+0xdc/0xf4)\n  [<c0040f14>] (kthread) from [<c000f778>] (ret_from_fork+0x14/0x3c)\n\nFix it by marking workqueues created via create*_workqueue() with\n__WQ_LEGACY and disabling flush dependency checks on them.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-and-tested-by: Thierry Reding <thierry.reding@gmail.com>\nLink: http://lkml.kernel.org/g/20160126173843.GA11115@ulmo.nvidia.com\nFixes: fca839c00a12 (\"workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue\")","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/23d11a58a9a60dcb52c8fc6494efce908b24c295"},{"sha":"8eee1d3ed5b6fc8e14389567c9a6f53f82bb7224","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"libata: fix sff host state machine locking while polling\n\nThe bulk of ATA host state machine is implemented by\nata_sff_hsm_move().  The function is called from either the interrupt\nhandler or, if polling, a work item.  Unlike from the interrupt path,\nthe polling path calls the function without holding the host lock and\nata_sff_hsm_move() selectively grabs the lock.\n\nThis is completely broken.  If an IRQ triggers while polling is in\nprogress, the two can easily race and end up accessing the hardware\nand updating state machine state at the same time.  This can put the\nstate machine in an illegal state and lead to a crash like the\nfollowing.\n\n  kernel BUG at drivers/ata/libata-sff.c:1302!\n  invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN\n  Modules linked in:\n  CPU: 1 PID: 10679 Comm: syz-executor Not tainted 4.5.0-rc1+ #300\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011\n  task: ffff88002bd00000 ti: ffff88002e048000 task.ti: ffff88002e048000\n  RIP: 0010:[<ffffffff83a83409>]  [<ffffffff83a83409>] ata_sff_hsm_move+0x619/0x1c60\n  ...\n  Call Trace:\n   <IRQ>\n   [<ffffffff83a84c31>] __ata_sff_port_intr+0x1e1/0x3a0 drivers/ata/libata-sff.c:1584\n   [<ffffffff83a85611>] ata_bmdma_port_intr+0x71/0x400 drivers/ata/libata-sff.c:2877\n   [<     inline     >] __ata_sff_interrupt drivers/ata/libata-sff.c:1629\n   [<ffffffff83a85bf3>] ata_bmdma_interrupt+0x253/0x580 drivers/ata/libata-sff.c:2902\n   [<ffffffff81479f98>] handle_irq_event_percpu+0x108/0x7e0 kernel/irq/handle.c:157\n   [<ffffffff8147a717>] handle_irq_event+0xa7/0x140 kernel/irq/handle.c:205\n   [<ffffffff81484573>] handle_edge_irq+0x1e3/0x8d0 kernel/irq/chip.c:623\n   [<     inline     >] generic_handle_irq_desc include/linux/irqdesc.h:146\n   [<ffffffff811a92bc>] handle_irq+0x10c/0x2a0 arch/x86/kernel/irq_64.c:78\n   [<ffffffff811a7e4d>] do_IRQ+0x7d/0x1a0 arch/x86/kernel/irq.c:240\n   [<ffffffff86653d4c>] common_interrupt+0x8c/0x8c arch/x86/entry/entry_64.S:520\n   <EOI>\n   [<     inline     >] rcu_lock_acquire include/linux/rcupdate.h:490\n   [<     inline     >] rcu_read_lock include/linux/rcupdate.h:874\n   [<ffffffff8164b4a1>] filemap_map_pages+0x131/0xba0 mm/filemap.c:2145\n   [<     inline     >] do_fault_around mm/memory.c:2943\n   [<     inline     >] do_read_fault mm/memory.c:2962\n   [<     inline     >] do_fault mm/memory.c:3133\n   [<     inline     >] handle_pte_fault mm/memory.c:3308\n   [<     inline     >] __handle_mm_fault mm/memory.c:3418\n   [<ffffffff816efb16>] handle_mm_fault+0x2516/0x49a0 mm/memory.c:3447\n   [<ffffffff8127dc16>] __do_page_fault+0x376/0x960 arch/x86/mm/fault.c:1238\n   [<ffffffff8127e358>] trace_do_page_fault+0xe8/0x420 arch/x86/mm/fault.c:1331\n   [<ffffffff8126f514>] do_async_page_fault+0x14/0xd0 arch/x86/kernel/kvm.c:264\n   [<ffffffff86655578>] async_page_fault+0x28/0x30 arch/x86/entry/entry_64.S:986\n\nFix it by ensuring that the polling path is holding the host lock\nbefore entering ata_sff_hsm_move() so that all hardware accesses and\nstate updates are performed under the host lock.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-and-tested-by: Dmitry Vyukov <dvyukov@google.com>\nLink: http://lkml.kernel.org/g/CACT4Y+b_JsOxJu2EZyEf+mOXORc_zid5V1-pLZSroJVxyWdSpw@mail.gmail.com\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/8eee1d3ed5b6fc8e14389567c9a6f53f82bb7224"},{"sha":"bb6a777369449d15a4a890306d2f925cae720e1c","author":{"email":"85eaff3c03d4b4d3d601e96c3e1c7f9e58a5538d@linux.vnet.ibm.com","name":"Carol L Soto"},"message":"IB/IPoIB: Do not set skb truesize since using one linearskb\n\nWe are seeing this warning: at net/core/skbuff.c:4174\nand before commit a44878d10063 (\"IB/ipoib: Use one linear skb in RX flow\")\nskb truesize was not being set when ipoib was using just one skb.\nRemoving this line avoids the warning when running tcp tests like iperf.\n\nFixes: a44878d10063 (\"IB/ipoib: Use one linear skb in RX flow\")\nSigned-off-by: Carol L Soto <clsoto@linux.vnet.ibm.com>\nSigned-off-by: Doug Ledford <dledford@redhat.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/bb6a777369449d15a4a890306d2f925cae720e1c"},{"sha":"9f780dab7fb5618ee8bacbf6f91832374231c30c","author":{"email":"d100aa70785e45ee8deab668147d941941915c21@canonical.com","name":"Colin Ian King"},"message":"IB/sysfs: remove unused va_list args\n\n_show_port_gid_attr performs a va_end on some unused va_list args.\nClean this up by removing the args completely.\n\nFixes: 470be516a226e8 (\"IB/core: Add gid attributes to sysfs\")\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nReviewed-by: Ira Weiny <ira.weiny@intel.com>\nReviewed-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>\nSigned-off-by: Doug Ledford <dledford@redhat.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/9f780dab7fb5618ee8bacbf6f91832374231c30c"},{"sha":"fd98d89698855f6cf5650c014e5d3fca38783c8b","author":{"email":"be5a419d60e6c52df4f7ab8e6b65ac3b9455f961@broadcom.com","name":"Selvin Xavier"},"message":"RDMA/ocrdma: Initialize stats resources in the driver before ib device registration.\n\nIn the latest kernel, process_mad hook of the driver can be invoked as\nsoon as device is registered. In this hook, ocrdma driver is issuing a\ncommand to get the stats counters from the HW. This is triggering system\ncrash since the statistics command resources are not allocated by the driver.\nChanging the sequence of initialization to avoid this crash.\n\nSigned-off-by: Selvin Xavier <selvin.xavier@broadcom.com>\nSigned-off-by: Doug Ledford <dledford@redhat.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/fd98d89698855f6cf5650c014e5d3fca38783c8b"},{"sha":"7d82df1663e8a66961954258f3a99701f0126e73","author":{"email":"be5a419d60e6c52df4f7ab8e6b65ac3b9455f961@broadcom.com","name":"Selvin Xavier"},"message":"RDMA/ocrdma: populate max_sge_rd in device attributes\n\nmax_sge_rd is used by some of the ULPs to calculate the maximum\nnumber of SGEs that can be used for RDMA READ. Populating this\nvalue in the response of query_device verb. Also, avoid checking\nthe max_srq_sge while populating max_sge.\n\nSigned-off-by: Selvin Xavier <selvin.xavier@broadcom.com>\nSigned-off-by: Doug Ledford <dledford@redhat.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/7d82df1663e8a66961954258f3a99701f0126e73"},{"sha":"aff3ead9fa25b2a472d1a894365f66b28e1e2787","author":{"email":"be5a419d60e6c52df4f7ab8e6b65ac3b9455f961@broadcom.com","name":"Selvin Xavier"},"message":"RDMA/ocrdma: Fix pkey_index returned by driver in rq work completion\n\nCurrently returning the pkey value instead of pkey index.\npkey index is always zero since ocrdma supports only default\npkey.\n\nSigned-off-by: Selvin Xavier <selvin.xavier@broadcom.com>\nSigned-off-by: Doug Ledford <dledford@redhat.com>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/aff3ead9fa25b2a472d1a894365f66b28e1e2787"}]}