{"push_id":1259608223,"size":1000,"distinct_size":1006,"ref":"refs/heads/linux-4.4.y","head":"85184740541c2b80b72ebfa46cfe065ec1d1058f","before":"8c9aef03d3b540b6885e7534a885ea25f62dd9ed","commits":[{"sha":"c6cf3b71df047f61b568795fe926f107806eae82","author":{"name":"Patrick Uiterwijk","email":"38df6a931a205814ca498263d467ca19b4fbd715@puiterwijk.org"},"message":"ARM: mvebu: Correct unit address for linksys\n\ncommit 199831c77c50e6913e893b6bc268ba9f4a9a2bf8 upstream.\n\nThe USB2 port for Armada 38x is defined to be at 58000, not at\n50000.\n\nFixes: 2d0a7addbd10 (\"ARM: Kirkwood: Add support for many Synology NAS devices\")\nSigned-off-by: Patrick Uiterwijk <patrick@puiterwijk.org>\nAcked-by: Imre Kaloz <kaloz@openwrt.org>\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/c6cf3b71df047f61b568795fe926f107806eae82"},{"sha":"81b5ed00246258100df11c87f118a27f0ebceba3","author":{"name":"Nishanth Menon","email":"22045716eebdf63edb645da8b757687137dffbf9@ti.com"},"message":"ARM: OMAP2: Fix up interconnect barrier initialization for DRA7\n\ncommit 456e8d53482537616899a146b706eccd095404e6 upstream.\n\nThe following commits:\ncommit 3fa609755c11 (\"ARM: omap2: restore OMAP4 barrier behaviour\")\ncommit f746929ffdc8 (\"Revert \"ARM: OMAP4: remove dead kconfig option OMAP4_ERRATA_I688\"\")\nand\ncommit ea827ad5ffbb (\"ARM: DRA7: Provide proper IO map table\")\ncame in around the same time, unfortunately this seem to have missed\ninitializing the barrier for DRA7 platforms - omap5_map_io was reused\nfor dra7 till it was split out by the last patch. barrier_init\nneeds to be hence carried forward as it is valid for DRA7 family of\nprocessors as they are for OMAP5.\n\nFixes: ea827ad5ffbb7 (\"ARM: DRA7: Provide proper IO map table\")\nReported-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nReported-by: Tomi Valkeinen <tomi.valkeinen@ti.com>\nCc: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Nishanth Menon <nm@ti.com>\nReviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/81b5ed00246258100df11c87f118a27f0ebceba3"},{"sha":"882e790b572a7dadf5323e373d0139bfbc6dce15","author":{"name":"Lokesh Vutla","email":"d569bcfb48ad30e36af736a1b765de6031c428c4@ti.com"},"message":"ARM: OMAP2+: hwmod: Fix updating of sysconfig register\n\ncommit 3ca4a238106dedc285193ee47f494a6584b6fd2f upstream.\n\nCommit 127500ccb766f (\"ARM: OMAP2+: Only write the sysconfig on idle\nwhen necessary\") talks about verification of sysconfig cache value before\nupdating it, only during idle path. But the patch is adding the\nverification in the enable path. So, adding the check in a proper place\nas per the commit description.\n\nNot keeping this check during enable path as there is a chance of losing\ncontext and it is safe to do on idle as the context of the register will\nnever be lost while the device is active.\n\nSigned-off-by: Lokesh Vutla <lokeshvutla@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nCc: Jon Hunter <jonathanh@nvidia.com>\nFixes: commit 127500ccb766 \"ARM: OMAP2+: Only write the sysconfig on idle when necessary\"\n[paul@pwsan.com: appears to have been caused by my own mismerge of the\n originally posted patch]\nSigned-off-by: Paul Walmsley <paul@pwsan.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/882e790b572a7dadf5323e373d0139bfbc6dce15"},{"sha":"6905c7a4aa1ef675825bc2ab56fd965a573ffb74","author":{"name":"Jerome Marchand","email":"dc2f8179cebe372cf7ded5d10edf58cc1936d348@redhat.com"},"message":"assoc_array: don't call compare_object() on a node\n\ncommit 8d4a2ec1e0b41b0cf9a0c5cd4511da7f8e4f3de2 upstream.\n\nChanges since V1: fixed the description and added KASan warning.\n\nIn assoc_array_insert_into_terminal_node(), we call the\ncompare_object() method on all non-empty slots, even when they're\nnot leaves, passing a pointer to an unexpected structure to\ncompare_object(). Currently it causes an out-of-bound read access\nin keyring_compare_object detected by KASan (see below). The issue\nis easily reproduced with keyutils testsuite.\nOnly call compare_object() when the slot is a leave.\n\nKASan warning:\n==================================================================\nBUG: KASAN: slab-out-of-bounds in keyring_compare_object+0x213/0x240 at addr ffff880060a6f838\nRead of size 8 by task keyctl/1655\n=============================================================================\nBUG kmalloc-192 (Not tainted): kasan: bad access detected\n-----------------------------------------------------------------------------\n\nDisabling lock debugging due to kernel taint\nINFO: Allocated in assoc_array_insert+0xfd0/0x3a60 age=69 cpu=1 pid=1647\n\t___slab_alloc+0x563/0x5c0\n\t__slab_alloc+0x51/0x90\n\tkmem_cache_alloc_trace+0x263/0x300\n\tassoc_array_insert+0xfd0/0x3a60\n\t__key_link_begin+0xfc/0x270\n\tkey_create_or_update+0x459/0xaf0\n\tSyS_add_key+0x1ba/0x350\n\tentry_SYSCALL_64_fastpath+0x12/0x76\nINFO: Slab 0xffffea0001829b80 objects=16 used=8 fp=0xffff880060a6f550 flags=0x3fff8000004080\nINFO: Object 0xffff880060a6f740 @offset=5952 fp=0xffff880060a6e5d1\n\nBytes b4 ffff880060a6f730: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f740: d1 e5 a6 60 00 88 ff ff 0e 00 00 00 00 00 00 00  ...`............\nObject ffff880060a6f750: 02 cf 8e 60 00 88 ff ff 02 c0 8e 60 00 88 ff ff  ...`.......`....\nObject ffff880060a6f760: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f770: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f790: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f7a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f7b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f7c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f7d0: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f7e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffff880060a6f7f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nCPU: 0 PID: 1655 Comm: keyctl Tainted: G    B           4.5.0-rc4-kasan+ #291\nHardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n 0000000000000000 000000001b2800b4 ffff880060a179e0 ffffffff81b60491\n ffff88006c802900 ffff880060a6f740 ffff880060a17a10 ffffffff815e2969\n ffff88006c802900 ffffea0001829b80 ffff880060a6f740 ffff880060a6e650\nCall Trace:\n [<ffffffff81b60491>] dump_stack+0x85/0xc4\n [<ffffffff815e2969>] print_trailer+0xf9/0x150\n [<ffffffff815e9454>] object_err+0x34/0x40\n [<ffffffff815ebe50>] kasan_report_error+0x230/0x550\n [<ffffffff819949be>] ? keyring_get_key_chunk+0x13e/0x210\n [<ffffffff815ec62d>] __asan_report_load_n_noabort+0x5d/0x70\n [<ffffffff81994cc3>] ? keyring_compare_object+0x213/0x240\n [<ffffffff81994cc3>] keyring_compare_object+0x213/0x240\n [<ffffffff81bc238c>] assoc_array_insert+0x86c/0x3a60\n [<ffffffff81bc1b20>] ? assoc_array_cancel_edit+0x70/0x70\n [<ffffffff8199797d>] ? __key_link_begin+0x20d/0x270\n [<ffffffff8199786c>] __key_link_begin+0xfc/0x270\n [<ffffffff81993389>] key_create_or_update+0x459/0xaf0\n [<ffffffff8128ce0d>] ? trace_hardirqs_on+0xd/0x10\n [<ffffffff81992f30>] ? key_type_lookup+0xc0/0xc0\n [<ffffffff8199e19d>] ? lookup_user_key+0x13d/0xcd0\n [<ffffffff81534763>] ? memdup_user+0x53/0x80\n [<ffffffff819983ea>] SyS_add_key+0x1ba/0x350\n [<ffffffff81998230>] ? key_get_type_from_user.constprop.6+0xa0/0xa0\n [<ffffffff828bcf4e>] ? retint_user+0x18/0x23\n [<ffffffff8128cc7e>] ? trace_hardirqs_on_caller+0x3fe/0x580\n [<ffffffff81004017>] ? trace_hardirqs_on_thunk+0x17/0x19\n [<ffffffff828bc432>] entry_SYSCALL_64_fastpath+0x12/0x76\nMemory state around the buggy address:\n ffff880060a6f700: fc fc fc fc fc fc fc fc 00 00 00 00 00 00 00 00\n ffff880060a6f780: 00 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc\n>ffff880060a6f800: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n                                        ^\n ffff880060a6f880: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n ffff880060a6f900: fc fc fc fc fc fc 00 00 00 00 00 00 00 00 00 00\n==================================================================\n\nSigned-off-by: Jerome Marchand <jmarchan@redhat.com>\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/6905c7a4aa1ef675825bc2ab56fd965a573ffb74"},{"sha":"6a20c0a043a73e39b5cd952d7eaf7fd7831e73ac","author":{"name":"Rafal Redzimski","email":"43bdb90049aa825db44acf39bcec8689c8641fb4@intel.com"},"message":"usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host\n\ncommit 0d46faca6f887a849efb07c1655b5a9f7c288b45 upstream.\n\nBroxton B0 also requires XHCI_PME_STUCK_QUIRK.\nAdding PCI device ID for Broxton B and adding to quirk.\n\nSigned-off-by: Rafal Redzimski <rafal.f.redzimski@intel.com>\nSigned-off-by: Robert Dobrowolski <robert.dobrowolski@linux.intel.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/6a20c0a043a73e39b5cd952d7eaf7fd7831e73ac"},{"sha":"ba7aa9a970dc12054252042e2b30e1dedcdc5968","author":{"name":"Mathias Nyman","email":"6f76a2d91b00c1a813d5588fd87cc784fe96486e@linux.intel.com"},"message":"xhci: resume USB 3 roothub first\n\ncommit 671ffdff5b13314b1fc65d62cf7604b873fb5dc4 upstream.\n\nGive USB3 devices a better chance to enumerate at USB 3 speeds if\nthey are connected to a suspended host.\nSolves an issue with NEC uPD720200 host hanging when partially\nenumerating a USB3 device as USB2 after host controller runtime resume.\n\nTested-by: Mike Murdoch <main.haarp@gmail.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/ba7aa9a970dc12054252042e2b30e1dedcdc5968"},{"sha":"bb6adb50beb03da007c63e86866f6be81d671075","author":{"name":"Lu Baolu","email":"aa0cb55c2120fe06ddbb364d78cace89fc49cea8@linux.intel.com"},"message":"usb: xhci: fix wild pointers in xhci_mem_cleanup\n\ncommit 71504062a7c34838c3fccd92c447f399d3cb5797 upstream.\n\nThis patch fixes some wild pointers produced by xhci_mem_cleanup.\nThese wild pointers will cause system crash if xhci_mem_cleanup()\nis called twice.\n\nReported-and-tested-by: Pengcheng Li <lpc.li@hisilicon.com>\nSigned-off-by: Lu Baolu <baolu.lu@linux.intel.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/bb6adb50beb03da007c63e86866f6be81d671075"},{"sha":"0eb1e16bf9feb36441440b0bd9fb0ced0fcdfdb6","author":{"name":"Mathias Nyman","email":"6f76a2d91b00c1a813d5588fd87cc784fe96486e@linux.intel.com"},"message":"xhci: fix 10 second timeout on removal of PCI hotpluggable xhci controllers\n\ncommit 98d74f9ceaefc2b6c4a6440050163a83be0abede upstream.\n\nPCI hotpluggable xhci controllers such as some Alpine Ridge solutions will\nremove the xhci controller from the PCI bus when the last USB device is\ndisconnected.\n\nAdd a flag to indicate that the host is being removed to avoid queueing\nconfigure_endpoint commands for the dropped endpoints.\nFor PCI hotplugged controllers this will prevent 5 second command timeouts\nFor static xhci controllers the configure_endpoint command is not needed\nin the removal case as everything will be returned, freed, and the\ncontroller is reset.\n\nFor now the flag is only set for PCI connected host controllers.\n\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/0eb1e16bf9feb36441440b0bd9fb0ced0fcdfdb6"},{"sha":"95b9219e05dafdb76b0707e815e5314cc0cf91af","author":{"name":"Robert Dobrowolski","email":"fd17761d00bae904377d6e7eabc3569d2c4d3c2a@linux.intel.com"},"message":"usb: hcd: out of bounds access in for_each_companion\n\ncommit e86103a75705c7c530768f4ffaba74cf382910f2 upstream.\n\nOn BXT platform Host Controller and Device Controller figure as\nsame PCI device but with different device function. HCD should\nnot pass data to Device Controller but only to Host Controllers.\nChecking if companion device is Host Controller, otherwise skip.\n\nSigned-off-by: Robert Dobrowolski <robert.dobrowolski@linux.intel.com>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/95b9219e05dafdb76b0707e815e5314cc0cf91af"},{"sha":"e4c7ab76586146820b394e0176f286f5a2e70cb3","author":{"name":"Lars-Peter Clausen","email":"7f698333860e9f21dcc513102ebee3bcaf8d683e@metafoo.de"},"message":"usb: gadget: f_fs: Fix use-after-free\n\ncommit 38740a5b87d53ceb89eb2c970150f6e94e00373a upstream.\n\nWhen using asynchronous read or write operations on the USB endpoints the\nissuer of the IO request is notified by calling the ki_complete() callback\nof the submitted kiocb when the URB has been completed.\n\nCalling this ki_complete() callback will free kiocb. Make sure that the\nstructure is no longer accessed beyond that point, otherwise undefined\nbehaviour might occur.\n\nFixes: 2e4c7553cd6f (\"usb: gadget: f_fs: add aio support\")\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/e4c7ab76586146820b394e0176f286f5a2e70cb3"},{"sha":"9d58f322ee18ffaca1e0b67d90ab811ad75e62a6","author":{"name":"Mike Snitzer","email":"ad2d170babf82633487ab777fab07770fbdc5ac8@redhat.com"},"message":"dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros\n\ncommit 9567366fefddeaea4ed1d713270535d93a3b3c76 upstream.\n\nThe READ_LOCK macro was incorrectly returning -EINVAL if\ndm_bm_is_read_only() was true -- it will always be true once the cache\nmetadata transitions to read-only by dm_cache_metadata_set_read_only().\n\nWrap READ_LOCK and WRITE_LOCK multi-statement macros in do {} while(0).\nAlso, all accesses of the 'cmd' argument passed to these related macros\nare now encapsulated in parenthesis.\n\nA follow-up patch can be developed to eliminate the use of macros in\nfavor of pure C code.  Avoiding that now given that this needs to apply\nto stable@.\n\nReported-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nFixes: d14fcf3dd79 (\"dm cache: make sure every metadata function checks fail_io\")\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/9d58f322ee18ffaca1e0b67d90ab811ad75e62a6"},{"sha":"be5cbaf31cd318f8aaeeff901f6d27232dfa965f","author":{"name":"Ahmed Samy","email":"0fc7df5e8a5950635f6ed8178e844907d3ae09ea@gmail.com"},"message":"dm cache metadata: fix cmd_read_lock() acquiring write lock\n\ncommit 6545b60baaf880b0cd29a5e89dbe745a06027e89 upstream.\n\nCommit 9567366fefdd (\"dm cache metadata: fix READ_LOCK macros and\ncleanup WRITE_LOCK macros\") uses down_write() instead of down_read() in\ncmd_read_lock(), yet up_read() is used to release the lock in\nREAD_UNLOCK().  Fix it.\n\nFixes: 9567366fefdd (\"dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros\")\nSigned-off-by: Ahmed Samy <f.fallen45@gmail.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/be5cbaf31cd318f8aaeeff901f6d27232dfa965f"},{"sha":"ed643d220692bfc2bfec9fe618d102f13a5dae9f","author":{"name":"Rui Salvaterra","email":"2c25f904254294707dd192a2f0046e9931ac0f52@gmail.com"},"message":"lib: lz4: fixed zram with lz4 on big endian machines\n\ncommit 3e26a691fe3fe1e02a76e5bab0c143ace4b137b4 upstream.\n\nBased on Sergey's test patch [1], this fixes zram with lz4 compression\non big endian cpus.\n\nNote that the 64-bit preprocessor test is not a cleanup, it's part of\nthe fix, since those identifiers are bogus (for example, __ppc64__\nisn't defined anywhere else in the kernel, which means we'd fall into\nthe 32-bit definitions on ppc64).\n\nTested on ppc64 with no regression on x86_64.\n\n[1] http://marc.info/?l=linux-kernel&m=145994470805853&w=4\n\nSuggested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nSigned-off-by: Rui Salvaterra <rsalvaterra@gmail.com>\nReviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/ed643d220692bfc2bfec9fe618d102f13a5dae9f"},{"sha":"9b3bd581a0492bdfe788539ca65a14da570faad1","author":{"name":"Seth Forshee","email":"7eef0d67708f72385bb42d10e516f71c5f708675@canonical.com"},"message":"debugfs: Make automount point inodes permanently empty\n\ncommit 87243deb88671f70def4c52dfa7ca7830707bd31 upstream.\n\nStarting with 4.1 the tracing subsystem has its own filesystem\nwhich is automounted in the tracing subdirectory of debugfs.\nPrior to this debugfs could be bind mounted in a cloned mount\nnamespace, but if tracefs has been mounted under debugfs this\nnow fails because there is a locked child mount. This creates\na regression for container software which bind mounts debugfs\nto satisfy the assumption of some userspace software.\n\nIn other pseudo filesystems such as proc and sysfs we're already\ncreating mountpoints like this in such a way that no dirents can\nbe created in the directories, allowing them to be exceptions to\nsome MNT_LOCKED tests. In fact we're already do this for the\ntracefs mountpoint in sysfs.\n\nDo the same in debugfs_create_automount(), since the intention\nhere is clearly to create a mountpoint. This fixes the regression,\nas locked child mounts on permanently empty directories do not\ncause a bind mount to fail.\n\nSigned-off-by: Seth Forshee <seth.forshee@canonical.com>\nAcked-by: Serge Hallyn <serge.hallyn@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/9b3bd581a0492bdfe788539ca65a14da570faad1"},{"sha":"42e6f01a44fe4aab28819b5efa48fbe9da3059e5","author":{"name":"Andy Shevchenko","email":"81dea222a65099eed47626c53d6f56bdfbcbb7bf@linux.intel.com"},"message":"dmaengine: dw: fix master selection\n\ncommit 3fe6409c23e2bee4b2b1b6d671d2da8daa15271c upstream.\n\nThe commit 895005202987 (\"dmaengine: dw: apply both HS interfaces and remove\nslave_id usage\") cleaned up the code to avoid usage of depricated slave_id\nmember of generic slave configuration.\n\nMeanwhile it broke the master selection by removing important call to\ndwc_set_masters() in ->device_alloc_chan_resources() which copied masters from\ncustom slave configuration to the internal channel structure.\n\nEverything works until now since there is no customized connection of\nDesignWare DMA IP to the bus, i.e. one bus and one or more masters are in use.\nThe configurations where 2 masters are connected to the different masters are\nnot working anymore. We are expecting one user of such configuration and need\nto select masters properly. Besides that it is obviously a performance\nregression since only one master is in use in multi-master configuration.\n\nSelect masters in accordance with what user asked for. Keep this patch in a form\nmore suitable for back porting.\n\nWe are safe to take necessary data in ->device_alloc_chan_resources() because\nwe don't support generic slave configuration embedded into custom one, and thus\nthe only way to provide such is to use the parameter to a filter function which\nis called exactly before channel resource allocation.\n\nWhile here, replase BUG_ON to less noisy dev_warn() and prevent channel\nallocation in case of error.\n\nFixes: 895005202987 (\"dmaengine: dw: apply both HS interfaces and remove slave_id usage\")\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Vinod Koul <vinod.koul@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/42e6f01a44fe4aab28819b5efa48fbe9da3059e5"},{"sha":"34c1b030296c6815c05e416c7a647b68e695004a","author":{"name":"Andy Shevchenko","email":"81dea222a65099eed47626c53d6f56bdfbcbb7bf@linux.intel.com"},"message":"dmaengine: hsu: correct use of channel status register\n\ncommit 4f4bc0abff79dc9d7ccbd3143adbf8ad1f4fe6ab upstream.\n\nThere is a typo in documentation regarding to descriptor empty bit (DESCE)\nwhich is set to 1 when descriptor is empty. Thus, status register at the end of\na transfer usually returns all DESCE bits set and thus it will never be zero.\n\nMoreover, there are 2 bits (CDESC) that encode current descriptor, on which\ninterrupt has been asserted. In case when we have few descriptors programmed we\nmight have non-zero value.\n\nRemove DESCE and CDESC bits from DMA channel status register (HSU_CH_SR) when\nreading it.\n\nFixes: 2b49e0c56741 (\"dmaengine: append hsu DMA driver\")\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Vinod Koul <vinod.koul@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/34c1b030296c6815c05e416c7a647b68e695004a"},{"sha":"94d75e190f199dfce1094496927418cb00810683","author":{"name":"Robert Jarzmik","email":"2f72d08aa3acdbc7400d1200b3d58e5e6d8b635f@free.fr"},"message":"dmaengine: pxa_dma: fix the maximum requestor line\n\ncommit 6bab1c6afdca0371cfa957079b36b78d12dd2cf5 upstream.\n\nThe current number of requestor lines is limited to 31. This was an\nerror of a previous commit, as this number is platform dependent, and is\nactually :\n - for pxa25x: 40 requestor lines\n - for pxa27x: 75 requestor lines\n - for pxa3xx: 100 requestor lines\n\nThe previous testing did not reveal the faulty constant as on pxa[23]xx\nplatforms, only camera, MSL and USB are above requestor 32, and in these\nonly the camera has a driver using dma.\n\nFixes: e87ffbdf0697 (\"dmaengine: pxa_dma: fix the no-requestor case\")\nSigned-off-by: Robert Jarzmik <robert.jarzmik@free.fr>\nAcked-by: Vinod Koul <vinod.koul@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/94d75e190f199dfce1094496927418cb00810683"},{"sha":"c0944355a74bc9c2b5b3cc5b627efe0c73e30bd9","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/cgroup: Fix/cleanup cgroup teardown/init\n\ncommit 2f5177f0fd7e531b26d54633be62d1d4cb94621c upstream.\n\nThe CPU controller hasn't kept up with the various changes in the whole\ncgroup initialization / destruction sequence, and commit:\n\n  2e91fa7f6d45 (\"cgroup: keep zombies associated with their original cgroups\")\n\ncaused it to explode.\n\nThe reason for this is that zombies do not inhibit css_offline() from\nbeing called, but do stall css_released(). Now we tear down the cfs_rq\nstructures on css_offline() but zombies can run after that, leading to\nuse-after-free issues.\n\nThe solution is to move the tear-down to css_released(), which\nguarantees nobody (including no zombies) is still using our cgroup.\n\nFurthermore, a few simple cleanups are possible too. There doesn't\nappear to be any point to us using css_online() (anymore?) so fold that\nin css_alloc().\n\nAnd since cgroup code guarantees an RCU grace period between\ncss_released() and css_free() we can forgo using call_rcu() and free the\nstuff immediately.\n\nSuggested-by: Tejun Heo <tj@kernel.org>\nReported-by: Kazuki Yamaguchi <k@rhe.jp>\nReported-by: Niklas Cassel <niklas.cassel@axis.com>\nTested-by: Niklas Cassel <niklas.cassel@axis.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nAcked-by: Tejun Heo <tj@kernel.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: 2e91fa7f6d45 (\"cgroup: keep zombies associated with their original cgroups\")\nLink: http://lkml.kernel.org/r/20160316152245.GY6344@twins.programming.kicks-ass.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/c0944355a74bc9c2b5b3cc5b627efe0c73e30bd9"},{"sha":"bdb0618ad1b9ea6ec6926450c687d133ccddf28c","author":{"name":"Catalin Marinas","email":"6aa257b0f6444d48b36b727fdf3f5c1074b85fd0@arm.com"},"message":"arm64: Honour !PTE_WRITE in set_pte_at() for kernel mappings\n\ncommit ac15bd63bbb24238f763ec5b24ee175ec301e8cd upstream.\n\nCurrently, set_pte_at() only checks the software PTE_WRITE bit for user\nmappings when it sets or clears the hardware PTE_RDONLY accordingly. The\nkernel ptes are written directly without any modification, relying\nsolely on the protection bits in macros like PAGE_KERNEL. However,\nmodifying kernel pte attributes via pte_wrprotect() would be ignored by\nset_pte_at(). Since pte_wrprotect() does not set PTE_RDONLY (it only\nclears PTE_WRITE), the new permission is not taken into account.\n\nThis patch changes set_pte_at() to adjust the read-only permission for\nkernel ptes as well. As a side effect, existing PROT_* definitions used\nfor kernel ioremap*() need to include PTE_DIRTY | PTE_WRITE.\n\n(additionally, white space fix for PTE_KERNEL_ROX)\n\nAcked-by: Andrey Ryabinin <aryabinin@virtuozzo.com>\nTested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>\nReported-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\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/bas-t/linux-stable/commits/bdb0618ad1b9ea6ec6926450c687d133ccddf28c"},{"sha":"70d65587f0a82f50952cb29af133a5b6b8538611","author":{"name":"Catalin Marinas","email":"6aa257b0f6444d48b36b727fdf3f5c1074b85fd0@arm.com"},"message":"arm64: Update PTE_RDONLY in set_pte_at() for PROT_NONE permission\n\ncommit fdc69e7df3cb24f18a93192641786e5b7ecd1dfe upstream.\n\nThe set_pte_at() function must update the hardware PTE_RDONLY bit\ndepending on the state of the PTE_WRITE and PTE_DIRTY bits of the given\nentry value. However, it currently only performs this for pte_valid()\nentries, ignoring PTE_PROT_NONE. The side-effect is that PROT_NONE\nmappings would not have the PTE_RDONLY bit set. Without\nCONFIG_ARM64_HW_AFDBM, this is not an issue since such PROT_NONE pages\nare not accessible anyway.\n\nWith commit 2f4b829c625e (\"arm64: Add support for hardware updates of\nthe access and dirty pte bits\"), the ptep_set_wrprotect() function was\nre-written to cope with automatic hardware updates of the dirty state.\nAs an optimisation, only PTE_RDONLY is checked to assess the \"dirty\"\nstatus. Since set_pte_at() does not set this bit for PROT_NONE mappings,\nsuch pages may be considered \"dirty\" as a result of\nptep_set_wrprotect().\n\nThis patch updates the pte_valid() check to pte_present() in\nset_pte_at(). It also adds PTE_PROT_NONE to the swap entry bits comment.\n\nFixes: 2f4b829c625e (\"arm64: Add support for hardware updates of the access and dirty pte bits\")\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>\nReported-by: Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>\nTested-by: Ganapatrao Kulkarni <gkulkarni@cavium.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/bas-t/linux-stable/commits/70d65587f0a82f50952cb29af133a5b6b8538611"}]}
{"actor":{"display_login":"bas-t"}}