{"push_id":2424013539,"size":132,"distinct_size":1,"ref":"refs/heads/oneplus/QC8998_O_8.1","head":"04e8acfa35e3fa5106cda760f8686c0ae67aa9ec","before":"05599ac46fd1ccaf33b29b10fca5b884d491c283","commits":[{"sha":"633a5a5235d697b145171ca1e702d3a4f6778131","author":{"name":"Hou Tao","email":"3e98258678d766fc8032de731347d0f5060ad78c@huawei.com"},"message":"blkcg: fix double free of new_blkg in blkcg_init_queue\n\ncommit 9b54d816e00425c3a517514e0d677bb3cec49258 upstream.\n\nIf blkg_create fails, new_blkg passed as an argument will\nbe freed by blkg_create, so there is no need to free it again.\n\nSigned-off-by: Hou Tao <houtao1@huawei.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>\nCc: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/633a5a5235d697b145171ca1e702d3a4f6778131"},{"sha":"3389b386139d79b5eb8bb023e9ca603d6245a8fa","author":{"name":"H. Nikolaus Schaller","email":"a5299c95093d4bfc163918beb0c47fe6fef836c8@goldelico.com"},"message":"Input: tsc2007 - check for presence and power down tsc2007 during probe\n\n\n[ Upstream commit 934df23171e7c5b71d937104d4957891c39748ff ]\n\n1. check if chip is really present and don't succeed if it isn't.\n2. if it succeeds, power down the chip until accessed\n\nSigned-off-by: H. Nikolaus Schaller <hns@goldelico.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/3389b386139d79b5eb8bb023e9ca603d6245a8fa"},{"sha":"c2e4c685b3c97bbf6210602cbe5791c468a31fdd","author":{"name":"Varsha Rao","email":"8eda5dd8042c27de8cc0226241a2faf36b596ba8@gmail.com"},"message":"staging: speakup: Replace BUG_ON() with WARN_ON().\n\n\n[ Upstream commit d351c2db5420bb17dcd2d9aac7ddb5f64c6d04b3 ]\n\nBUG_ON() is replaced with WARN_ON() and EINVAL is returned, when\nWARN_ON() is true. This fixes the following checkpatch issue:\n\nAvoid crashing the kernel - try using WARN_ON & recovery code rather\nthan BUG() or BUG_ON().\n\nSigned-off-by: Varsha Rao <rvarsha016@gmail.com>\nReviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/c2e4c685b3c97bbf6210602cbe5791c468a31fdd"},{"sha":"e6e7ba9d76af6ae8b223e7e8a68c2daaa3ffb789","author":{"name":"Colin Ian King","email":"61b69653f478c16de27cbf2a77617b5a614a704a@canonical.com"},"message":"staging: wilc1000: add check for kmalloc allocation failure.\n\n\n[ Upstream commit 6cc0c259d034c6ab48f4e12f505213988e73d380 ]\n\nAdd a sanity check that wid.val has been allocated, fixes a null\npointer deference on stamac when calling ether_add_copy.\n\nDetected by CoverityScan, CID#1369537 (\"Dereference null return value\")\n\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/e6e7ba9d76af6ae8b223e7e8a68c2daaa3ffb789"},{"sha":"9b7940be33211e6f26ca129b8aaf53ea6e0f176b","author":{"name":"Valtteri Heikkilä","email":"d35705a43fba4c07a1e06629cd63aec22da91e6b@nic.fi"},"message":"HID: reject input outside logical range only if null state is set\n\n\n[ Upstream commit 3f3752705dbd50b66b66ad7b4d54fe33d2f746ed ]\n\nThis patch fixes an issue in drivers/hid/hid-input.c where USB HID\ncontrol null state flag is not checked upon rejecting inputs outside\nlogical minimum-maximum range. The check should be made according to USB\nHID specification 1.11, section 6.2.2.5, p.31. The fix will resolve\nissues with some game controllers, such as:\nhttps://bugzilla.kernel.org/show_bug.cgi?id=68621\n\n[tk@the-tk.com: shortened and fixed spelling in commit message]\nSigned-off-by: Valtteri Heikkilä <rnd@nic.fi>\nSigned-off-by: Tomasz Kramkowski <tk@the-tk.com>\nAcked-By: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/9b7940be33211e6f26ca129b8aaf53ea6e0f176b"},{"sha":"e1a3bc45832dedcee6137f048bbc3e49b8a657fb","author":{"name":"Gabriel Krisman Bertazi","email":"70c508657631d6f248acc0b255cbde9f133e6554@collabora.co.uk"},"message":"drm: qxl: Don't alloc fbdev if emulation is not supported\n\n\n[ Upstream commit 861078381ba56b56808113736000d9e7ead349c8 ]\n\nIf fbdev emulation is disabled, the QXL shutdown path will try to clean\na framebuffer that wasn't initialized, hitting the Oops below.  The\nproblem is that even when FBDEV_EMULATION is disabled we allocate the\nqfbdev strutucture, but we don't initialize it.  The fix is to stop\nallocating the memory, since it won't be used.  This allows the existing\nverification in the cleanup hook to do it's job preventing the oops.\n\nNow that we don't allocate the unused fbdev structure, we need to be\ncareful when dereferencing it in the PM suspend hook.\n\n[   24.284684] BUG: unable to handle kernel NULL pointer dereference at 00000000000002e0\n[   24.285627] IP: mutex_lock+0x18/0x30\n[   24.286049] PGD 78cdf067\n[   24.286050] PUD 7940f067\n[   24.286344] PMD 0\n[   24.286649]\n[   24.287072] Oops: 0002 [#1] SMP\n[   24.287422] Modules linked in: qxl\n[   24.287806] CPU: 0 PID: 2328 Comm: bash Not tainted 4.10.0-rc5+ #97\n[   24.288515] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014\n[   24.289681] task: ffff88007c4c0000 task.stack: ffffc90001b58000\n[   24.290354] RIP: 0010:mutex_lock+0x18/0x30\n[   24.290812] RSP: 0018:ffffc90001b5bcb0 EFLAGS: 00010246\n[   24.291401] RAX: 0000000000000000 RBX: 00000000000002e0 RCX: 0000000000000000\n[   24.292209] RDX: ffff88007c4c0000 RSI: 0000000000000001 RDI: 00000000000002e0\n[   24.292987] RBP: ffffc90001b5bcb8 R08: fffffffffffffffe R09: 0000000000000001\n[   24.293797] R10: ffff880078d80b80 R11: 0000000000011400 R12: 0000000000000000\n[   24.294601] R13: 00000000000002e0 R14: ffffffffa0009c28 R15: 0000000000000060\n[   24.295439] FS:  00007f30e3acbb40(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000\n[   24.296364] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   24.296997] CR2: 00000000000002e0 CR3: 0000000078c7b000 CR4: 00000000000006f0\n[   24.297813] Call Trace:\n[   24.298097]  drm_framebuffer_cleanup+0x1f/0x70\n[   24.298612]  qxl_fbdev_fini+0x68/0x90 [qxl]\n[   24.299074]  qxl_modeset_fini+0xd/0x30 [qxl]\n[   24.299562]  qxl_pci_remove+0x22/0x50 [qxl]\n[   24.300025]  pci_device_remove+0x34/0xb0\n[   24.300507]  device_release_driver_internal+0x150/0x200\n[   24.301082]  device_release_driver+0xd/0x10\n[   24.301587]  unbind_store+0x108/0x150\n[   24.301993]  drv_attr_store+0x20/0x30\n[   24.302402]  sysfs_kf_write+0x32/0x40\n[   24.302827]  kernfs_fop_write+0x108/0x190\n[   24.303269]  __vfs_write+0x23/0x120\n[   24.303678]  ? security_file_permission+0x36/0xb0\n[   24.304193]  ? rw_verify_area+0x49/0xb0\n[   24.304636]  vfs_write+0xb0/0x190\n[   24.305004]  SyS_write+0x41/0xa0\n[   24.305362]  entry_SYSCALL_64_fastpath+0x1a/0xa9\n[   24.305887] RIP: 0033:0x7f30e31d9620\n[   24.306285] RSP: 002b:00007ffc54b47e68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\n[   24.307128] RAX: ffffffffffffffda RBX: 00007f30e3497600 RCX: 00007f30e31d9620\n[   24.307928] RDX: 000000000000000d RSI: 0000000000da2008 RDI: 0000000000000001\n[   24.308727] RBP: 000000000070bc60 R08: 00007f30e3498760 R09: 00007f30e3acbb40\n[   24.309504] R10: 0000000000000073 R11: 0000000000000246 R12: 0000000000000001\n[   24.310295] R13: 0000000000000000 R14: 0000000000000000 R15: 00007ffc54b47f34\n[   24.311095] Code: 0e 01 e9 7b fe ff ff 66 90 66 2e 0f 1f 84 00 00 00 00 00\n55 48 89 e5 53 48 89 fb e8 83 e8 ff ff 65 48 8b 14 25 40 c4 00 00 31 c0 <3e>\n48 0f b1 13 48 85 c0 74 08 48 89 df e8 66 fd ff ff 5b 5d c3\n[   24.313182] RIP: mutex_lock+0x18/0x30 RSP: ffffc90001b5bcb0\n[   24.313811] CR2: 00000000000002e0\n[   24.314208] ---[ end trace 29669c1593cae14b ]---\n\nSigned-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>\nLink: http://patchwork.freedesktop.org/patch/msgid/20170227203330.18542-1-krisman@collabora.co.uk\nSigned-off-by: Gerd Hoffmann <kraxel@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/e1a3bc45832dedcee6137f048bbc3e49b8a657fb"},{"sha":"d676ed9c0467494c9bfeb977d0fb26005546c82b","author":{"name":"Mohammed Shafi Shajakhan","email":"4abf9d4e9fb909a6b0c1689ab80ea0e519567492@qti.qualcomm.com"},"message":"ath10k: fix a warning during channel switch with multiple vaps\n\n\n[ Upstream commit c73f8c00330f59ce9b1ace9ff698aca83390d358 ]\n\nDoing a channel switch via hostapd_cli seems to update\nthe new channel context for each VAP's appropriately as below\nin 'ath10k_mac_update_vif_chan', hence we can safely suppress the\nwarning that shows up during this operation and dump the warning only\nif no vaps are available for channel switch\n\nhostapd_cli -i wlan0 chan_switch 5 5200\nOK\n\nath10k_pci : mac chanctx switch n_vifs 3 mode 1\nath10k_pci : mac chanctx switch vdev_id 2 freq 5180->5200 width 0->0\nath10k_pci : mac chanctx switch vdev_id 1 freq 5180->5200 width 0->0\nath10k_pci : mac chanctx switch vdev_id 0 freq 5180->5200 width 0->0\n\nCall Trace:\n\nWARNING: backports-20161201-3.14.77-9ab3068/drivers/net/wireless/ath/ath10k/mac.c:7126\n[<c022f2d4>] (warn_slowpath_null) from [<bf7f150c>]\n(ath10k_reconfig_complete+0xe4/0x25c [ath10k_core])\n[<bf7f150c>] (ath10k_reconfig_complete [ath10k_core])\n[<bf7f35f0>] (ath10k_mac_vif_ap_csa_work+0x214/0x370 [ath10k_core])\n[<bf7f38b8>] (ath10k_mac_op_change_chanctx+0x108/0x128 [ath10k_core])\n[<bf782ac0>] (ieee80211_recalc_chanctx_min_def+0x30c/0x430 [mac80211])\n[<bf7830a4>] (ieee80211_recalc_smps_chanctx+0x2ec/0x840 [mac80211])\n[<bf7843e8>] (ieee80211_vif_use_reserved_context+0x7c/0xf8 [mac80211])\n[<bf7843e8>] (ieee80211_vif_use_reserved_context [mac80211])\n[<bf76e5d4>] (ieee80211_csa_finalize_work+0x5c/0x88 [mac80211])\n\nFixes: d7bf4b4aba05 (\"ath10k: fix ar->rx_channel updating logic\")\nSigned-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/d676ed9c0467494c9bfeb977d0fb26005546c82b"},{"sha":"4fbe422076d36615ec6fe8648d1aecfa460bc67d","author":{"name":"Prarit Bhargava","email":"57afa0c35fd38a11b51d30edc3a65ab805a2449c@redhat.com"},"message":"PCI/MSI: Stop disabling MSI/MSI-X in pci_device_shutdown()\n\n\n[ Upstream commit fda78d7a0ead144f4b2cdb582dcba47911f4952c ]\n\nThe pci_bus_type .shutdown method, pci_device_shutdown(), is called from\ndevice_shutdown() in the kernel restart and shutdown paths.\n\nPreviously, pci_device_shutdown() called pci_msi_shutdown() and\npci_msix_shutdown().  This disables MSI and MSI-X, which causes the device\nto fall back to raising interrupts via INTx.  But the driver is still bound\nto the device, it doesn't know about this change, and it likely doesn't\nhave an INTx handler, so these INTx interrupts cause \"nobody cared\"\nwarnings like this:\n\n  irq 16: nobody cared (try booting with the \"irqpoll\" option)\n  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.8.2-1.el7_UNSUPPORTED.x86_64 #1\n  Hardware name: Hewlett-Packard HP Z820 Workstation/158B, BIOS J63 v03.90 06/\n  ...\n\nThe MSI disabling code was added by d52877c7b1af (\"pci/irq: let\npci_device_shutdown to call pci_msi_shutdown v2\") because a driver left MSI\nenabled and kdump failed because the kexeced kernel wasn't prepared to\nreceive the MSI interrupts.\n\nSubsequent commits 1851617cd2da (\"PCI/MSI: Disable MSI at enumeration even\nif kernel doesn't support MSI\") and  e80e7edc55ba (\"PCI/MSI: Initialize MSI\ncapability for all architectures\") changed the kexeced kernel to disable\nall MSIs itself so it no longer depends on the crashed kernel to clean up\nafter itself.\n\nStop disabling MSI/MSI-X in pci_device_shutdown().  This resolves the\n\"nobody cared\" unhandled IRQ issue above.  It also allows PCI serial\ndevices, which may rely on the MSI interrupts, to continue outputting\nmessages during reboot/shutdown.\n\n[bhelgaas: changelog, drop pci_msi_shutdown() and pci_msix_shutdown() calls\naltogether]\nFixes: https://bugzilla.kernel.org/show_bug.cgi?id=187351\nSigned-off-by: Prarit Bhargava <prarit@redhat.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nCC: Alex Williamson <alex.williamson@redhat.com>\nCC: David Arcari <darcari@redhat.com>\nCC: Myron Stowe <mstowe@redhat.com>\nCC: Lukas Wunner <lukas@wunner.de>\nCC: Keith Busch <keith.busch@intel.com>\nCC: Mika Westerberg <mika.westerberg@linux.intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/4fbe422076d36615ec6fe8648d1aecfa460bc67d"},{"sha":"89aadbc66e41aee339979f5b86c8bd6354c6ceac","author":{"name":"Alexander Potapenko","email":"8a652d6e37d449a8e8c8989569d8839dd1bfdb29@google.com"},"message":"selinux: check for address length in selinux_socket_bind()\n\n\n[ Upstream commit e2f586bd83177d22072b275edd4b8b872daba924 ]\n\nKMSAN (KernelMemorySanitizer, a new error detection tool) reports use of\nuninitialized memory in selinux_socket_bind():\n\n==================================================================\nBUG: KMSAN: use of unitialized memory\ninter: 0\nCPU: 3 PID: 1074 Comm: packet2 Tainted: G    B           4.8.0-rc6+ #1916\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011\n 0000000000000000 ffff8800882ffb08 ffffffff825759c8 ffff8800882ffa48\n ffffffff818bf551 ffffffff85bab870 0000000000000092 ffffffff85bab550\n 0000000000000000 0000000000000092 00000000bb0009bb 0000000000000002\nCall Trace:\n [<     inline     >] __dump_stack lib/dump_stack.c:15\n [<ffffffff825759c8>] dump_stack+0x238/0x290 lib/dump_stack.c:51\n [<ffffffff818bdee6>] kmsan_report+0x276/0x2e0 mm/kmsan/kmsan.c:1008\n [<ffffffff818bf0fb>] __msan_warning+0x5b/0xb0 mm/kmsan/kmsan_instr.c:424\n [<ffffffff822dae71>] selinux_socket_bind+0xf41/0x1080 security/selinux/hooks.c:4288\n [<ffffffff8229357c>] security_socket_bind+0x1ec/0x240 security/security.c:1240\n [<ffffffff84265d98>] SYSC_bind+0x358/0x5f0 net/socket.c:1366\n [<ffffffff84265a22>] SyS_bind+0x82/0xa0 net/socket.c:1356\n [<ffffffff81005678>] do_syscall_64+0x58/0x70 arch/x86/entry/common.c:292\n [<ffffffff8518217c>] entry_SYSCALL64_slow_path+0x25/0x25 arch/x86/entry/entry_64.o:?\nchained origin: 00000000ba6009bb\n [<ffffffff810bb7a7>] save_stack_trace+0x27/0x50 arch/x86/kernel/stacktrace.c:67\n [<     inline     >] kmsan_save_stack_with_flags mm/kmsan/kmsan.c:322\n [<     inline     >] kmsan_save_stack mm/kmsan/kmsan.c:337\n [<ffffffff818bd2b8>] kmsan_internal_chain_origin+0x118/0x1e0 mm/kmsan/kmsan.c:530\n [<ffffffff818bf033>] __msan_set_alloca_origin4+0xc3/0x130 mm/kmsan/kmsan_instr.c:380\n [<ffffffff84265b69>] SYSC_bind+0x129/0x5f0 net/socket.c:1356\n [<ffffffff84265a22>] SyS_bind+0x82/0xa0 net/socket.c:1356\n [<ffffffff81005678>] do_syscall_64+0x58/0x70 arch/x86/entry/common.c:292\n [<ffffffff8518217c>] return_from_SYSCALL_64+0x0/0x6a arch/x86/entry/entry_64.o:?\norigin description: ----address@SYSC_bind (origin=00000000b8c00900)\n==================================================================\n\n(the line numbers are relative to 4.8-rc6, but the bug persists upstream)\n\n, when I run the following program as root:\n\n=======================================================\n  #include <string.h>\n  #include <sys/socket.h>\n  #include <netinet/in.h>\n\n  int main(int argc, char *argv[]) {\n    struct sockaddr addr;\n    int size = 0;\n    if (argc > 1) {\n      size = atoi(argv[1]);\n    }\n    memset(&addr, 0, sizeof(addr));\n    int fd = socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP);\n    bind(fd, &addr, size);\n    return 0;\n  }\n=======================================================\n\n(for different values of |size| other error reports are printed).\n\nThis happens because bind() unconditionally copies |size| bytes of\n|addr| to the kernel, leaving the rest uninitialized. Then\nsecurity_socket_bind() reads the IP address bytes, including the\nuninitialized ones, to determine the port, or e.g. pass them further to\nsel_netnode_find(), which uses them to calculate a hash.\n\nSigned-off-by: Alexander Potapenko <glider@google.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\n[PM: fixed some whitespace damage]\nSigned-off-by: Paul Moore <paul@paul-moore.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/89aadbc66e41aee339979f5b86c8bd6354c6ceac"},{"sha":"ecabc4777cf0918eb5e0ad2e0842bb4b1faab59e","author":{"name":"Changbin Du","email":"5f6b755b7a1cb5f1a44f6ef41b5dc943725490e0@intel.com"},"message":"perf sort: Fix segfault with basic block 'cycles' sort dimension\n\n\n[ Upstream commit 4b0b3aa6a2756e6115fdf275c521e4552a7082f3 ]\n\nSkip the sample which doesn't have branch_info to avoid segmentation\nfault:\n\nThe fault can be reproduced by:\n\n  perf record -a\n  perf report -F cycles\n\nSigned-off-by: Changbin Du <changbin.du@intel.com>\nTested-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Andi Kleen <ak@linux.intel.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nFixes: 0e332f033a82 (\"perf tools: Add support for cycles, weight branch_info field\")\nLink: http://lkml.kernel.org/r/20170313083148.23568-1-changbin.du@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/ecabc4777cf0918eb5e0ad2e0842bb4b1faab59e"},{"sha":"8d6455c5f59f1445ceafc68ac6e51ed9eb6dd1a6","author":{"name":"Aaron Salter","email":"fa58239d05b02fa8485155bde76f38df6dd58790@intel.com"},"message":"i40e: Acquire NVM lock before reads on all devices\n\n\n[ Upstream commit 96a39aed25e6559b160786117df124084feb9080 ]\n\nAcquire NVM lock before reads on all devices.  Previously, locks were\nonly used for X722 and later.  Fixes an issue where simultaneous X710\nNVM accesses were interfering with each other.\n\nChange-ID: If570bb7acf958cef58725ec2a2011cead6f80638\nSigned-off-by: Aaron Salter <aaron.k.salter@intel.com>\nTested-by: Andrew Bowers <andrewx.bowers@intel.com>\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/8d6455c5f59f1445ceafc68ac6e51ed9eb6dd1a6"},{"sha":"f18637f909ad2e12de3ada8329deb1e4b30880e8","author":{"name":"Lihong Yang","email":"d2558fa6731bc996879564bf9fd7398318c62c8e@intel.com"},"message":"i40e: fix ethtool to get EEPROM data from X722 interface\n\n\n[ Upstream commit c271dd6c391b535226cf1a81aaad9f33cb5899d3 ]\n\nCurrently ethtool -e will error out with a X722 interface\nas its EEPROM has a scope limit at offset 0x5B9FFF.\nThis patch fixes the issue by setting the EEPROM length to\nthe scope limit to avoid NVM read failure beyond that.\n\nChange-ID: I0b7d4dd6c7f2a57cace438af5dffa0f44c229372\nSigned-off-by: Lihong Yang <lihong.yang@intel.com>\nTested-by: Andrew Bowers <andrewx.bowers@intel.com>\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/f18637f909ad2e12de3ada8329deb1e4b30880e8"},{"sha":"a7bb9f33452f06da2e114cf154fa729963399414","author":{"name":"Stephane Eranian","email":"6af721cad58040b3048c3e3443075fb31c49e8ff@google.com"},"message":"perf tools: Make perf_event__synthesize_mmap_events() scale\n\n\n[ Upstream commit 88b897a30c525c2eee6e7f16e1e8d0f18830845e ]\n\nThis patch significantly improves the execution time of\nperf_event__synthesize_mmap_events() when running perf record on systems\nwhere processes have lots of threads.\n\nIt just happens that cat /proc/pid/maps support uses a O(N^2) algorithm to\ngenerate each map line in the maps file.  If you have 1000 threads, then you\nhave necessarily 1000 stacks.  For each vma, you need to check if it\ncorresponds to a thread's stack.  With a large number of threads, this can take\na very long time. I have seen latencies >> 10mn.\n\nAs of today, perf does not use the fact that a mapping is a stack, therefore we\ncan work around the issue by using /proc/pid/tasks/pid/maps.  This entry does\nnot try to map a vma to stack and is thus much faster with no loss of\nfunctonality.\n\nThe proc-map-timeout logic is kept in case users still want some upper limit.\n\nIn V2, we fix the file path from /proc/pid/tasks/pid/maps to actual\n/proc/pid/task/pid/maps, tasks -> task.  Thanks Arnaldo for catching this.\n\nCommitter note:\n\nThis problem seems to have been elliminated in the kernel since commit :\nb18cb64ead40 (\"fs/proc: Stop trying to report thread stacks\").\n\nSigned-off-by: Stephane Eranian <eranian@google.com>\nAcked-by: Jiri Olsa <jolsa@redhat.com>\nCc: Andy Lutomirski <luto@kernel.org>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/20170315135059.GC2177@redhat.com\nLink: http://lkml.kernel.org/r/1489598233-25586-1-git-send-email-eranian@google.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/a7bb9f33452f06da2e114cf154fa729963399414"},{"sha":"f51536fff7b7c2a054b9dee487fec4eb55fe2d2e","author":{"name":"Quan Nguyen","email":"81659e9f1d76e3796e782a8b71512bfcb94cf33e@apm.com"},"message":"drivers: net: xgene: Fix hardware checksum setting\n\n\n[ Upstream commit e026e700d940a1ea3d3bc84d92ac668b1f015462 ]\n\nThis patch fixes the hardware checksum settings by properly program\nthe classifier. Otherwise, packet may be received with checksum error\non X-Gene1 SoC.\n\nSigned-off-by: Quan Nguyen <qnguyen@apm.com>\nSigned-off-by: Iyappan Subramanian <isubramanian@apm.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/f51536fff7b7c2a054b9dee487fec4eb55fe2d2e"},{"sha":"1b3ec39d3b6d1d252e03a86fcdcc8f8a2970258e","author":{"name":"Chris Wilson","email":"4181b934c2715a2bba60cdb3cc1b35b2777d1c23@chris-wilson.co.uk"},"message":"drm: Defer disabling the vblank IRQ until the next interrupt (for instant-off)\n\n\n[ Upstream commit 608b20506941969ea30d8c08dc9ae02bb87dbf7d ]\n\nOn vblank instant-off systems, we can get into a situation where the cost\nof enabling and disabling the vblank IRQ around a drmWaitVblank query\ndominates. And with the advent of even deeper hardware sleep state,\ntouching registers becomes ever more expensive.  However, we know that if\nthe user wants the current vblank counter, they are also very likely to\nimmediately queue a vblank wait and so we can keep the interrupt around\nand only turn it off if we have no further vblank requests queued within\nthe interrupt interval.\n\nAfter vblank event delivery, this patch adds a shadow of one vblank where\nthe interrupt is kept alive for the user to query and queue another vblank\nevent. Similarly, if the user is using blocking drmWaitVblanks, the\ninterrupt will be disabled on the IRQ following the wait completion.\nHowever, if the user is simply querying the current vblank counter and\ntimestamp, the interrupt will be disabled after every IRQ and the user\nwill enabled it again on the first query following the IRQ.\n\nv2: Mario Kleiner -\nAfter testing this, one more thing that would make sense is to move\nthe disable block at the end of drm_handle_vblank() instead of at the\ntop.\n\nTurns out that if high precision timestaming is disabled or doesn't\nwork for some reason (as can be simulated by echo 0 >\n/sys/module/drm/parameters/timestamp_precision_usec), then with your\ndelayed disable code at its current place, the vblank counter won't\nincrement anymore at all for instant queries, ie. with your other\n\"instant query\" patches. Clients which repeatedly query the counter\nand wait for it to progress will simply hang, spinning in an endless\nquery loop. There's that comment in vblank_disable_and_save:\n\n\"* Skip this step if there isn't any high precision timestamp\n * available. In that case we can't account for this and just\n * hope for the best.\n */\n\nWith the disable happening after leading edge of vblank (== hw counter\nincrement already happened) but before the vblank counter/timestamp\nhandling in drm_handle_vblank, that step is needed to keep the counter\nprogressing, so skipping it is bad.\n\nNow without high precision timestamping support, a kms driver must not\nset dev->vblank_disable_immediate = true, as this would cause problems\nfor clients, so this shouldn't matter, but it would be good to still\nmake this robust against a future kms driver which might have\nunreliable high precision timestamping, e.g., high precision\ntimestamping that intermittently doesn't work.\n\nv3: Patch before coffee needs extra coffee.\n\nTestcase: igt/kms_vblank\nSigned-off-by: Chris Wilson <chris@chris-wilson.co.uk>\nCc: Ville Syrjälä <ville.syrjala@linux.intel.com>\nCc: Daniel Vetter <daniel@ffwll.ch>\nCc: Michel Dänzer <michel@daenzer.net>\nCc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nCc: Dave Airlie <airlied@redhat.com>,\nCc: Mario Kleiner <mario.kleiner.de@gmail.com>\nReviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nLink: http://patchwork.freedesktop.org/patch/msgid/20170315204027.20160-1-chris@chris-wilson.co.uk\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/1b3ec39d3b6d1d252e03a86fcdcc8f8a2970258e"},{"sha":"f2393b51e235875e79b15bb0dc751e4afdca55e9","author":{"name":"Mohammed Shafi Shajakhan","email":"4abf9d4e9fb909a6b0c1689ab80ea0e519567492@qti.qualcomm.com"},"message":"ath10k: disallow DFS simulation if DFS channel is not enabled\n\n\n[ Upstream commit ca07baab0b1e627ae1d4a55d190fb1c9d32a3445 ]\n\nIf DFS is not enabled in hostapd (ieee80211h=0) DFS channels shall\nnot be available for use even though the hardware may have the capability\nto support DFS. With this configuration (DFS disabled in hostapd) trying to\nbring up ath10k device in DFS channel for AP mode fails and trying to\nsimulate DFS in ath10k debugfs results in a warning in cfg80211 complaining\ninvalid channel and this should be avoided in the driver itself rather than\nfalse propogating RADAR detection to mac80211/cfg80211. Fix this by\nchecking for the first vif 'is_started' state(should work for client mode\nas well) as all the vifs shall be configured for the same channel\n\nsys/kernel/debug/ieee80211/phy1/ath10k# echo 1 > dfs_simulate_radar\n\nWARNING: at net/wireless/chan.c:265 cfg80211_radar_event+0x24/0x60\nWorkqueue: phy0 ieee80211_dfs_radar_detected_work [mac80211]\n[<c022f2d4>] (warn_slowpath_null) from\n[<bf72dab8>] (cfg80211_radar_event+0x24/0x60 [cfg80211])\n[<bf72dab8>] (cfg80211_radar_event [cfg80211]) from\n[<bf7813e0>] (ieee80211_dfs_radar_detected_work+0x94/0xa0 [mac80211])\n[<bf7813e0>] (ieee80211_dfs_radar_detected_work [mac80211]) from\n[<c0242320>] (process_one_work+0x20c/0x32c)\n\nWARNING: at net/wireless/nl80211.c:2488 nl80211_get_mpath+0x13c/0x4cc\n Workqueue: phy0 ieee80211_dfs_radar_detected_work [mac80211]\n[<c022f2d4>] (warn_slowpath_null) from\n[<bf72dab8>] (cfg80211_radar_event+0x24/0x60 [cfg80211])\n[<bf72dab8>] (cfg80211_radar_event [cfg80211]) from\n[<bf7813e0>] (ieee80211_dfs_radar_detected_work+0x94/0xa0 [mac80211])\n[<bf7813e0>] (ieee80211_dfs_radar_detected_work [mac80211]) from\n[<c0242320>] (process_one_work+0x20c/0x32c)\n\nSigned-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/f2393b51e235875e79b15bb0dc751e4afdca55e9"},{"sha":"7acee5659b2008481d500b3299545a74f0cb78e1","author":{"name":"Kefeng Wang","email":"1ff0a8e70a0d22cd78c773803bf266a3b2e64dfe@huawei.com"},"message":"perf probe: Return errno when not hitting any event\n\n\n[ Upstream commit 70946723eeb859466f026274b29c6196e39149c4 ]\n\nOn old perf, when using 'perf probe -d' to delete an inexistent event,\nit returns errno, eg,\n\n  -bash-4.3# perf probe -d xxx  || echo $?\n  Info: Event \"*:xxx\" does not exist.\n    Error: Failed to delete events.\n  255\n\nBut now perf_del_probe_events() will always set ret = 0, different from\nprevious del_perf_probe_events(). After this, it returns errno again,\neg,\n\n  -bash-4.3# ./perf probe -d xxx  || echo $?\n  \"xxx\" does not hit any event.\n    Error: Failed to delete events.\n  254\n\nAnd it is more appropriate to return -ENOENT instead of -EPERM.\n\nSigned-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>\nAcked-by: Masami Hiramatsu <mhiramat@kernel.org>\nCc: Hanjun Guo <guohanjun@huawei.com>\nCc: Jiri Olsa <jolsa@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Wang Nan <wangnan0@huawei.com>\nFixes: dddc7ee32fa1 (\"perf probe: Fix an error when deleting probes successfully\")\nLink: http://lkml.kernel.org/r/1489738592-61011-1-git-send-email-wangkefeng.wang@huawei.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/7acee5659b2008481d500b3299545a74f0cb78e1"},{"sha":"aa4b0ac7c16942717370b704869a72c383b0508a","author":{"name":"Tomasz Kramkowski","email":"528479d158dcd5d1b9a6a6984af40758cf7e2a93@the-tk.com"},"message":"HID: clamp input to logical range if no null state\n\n\n[ Upstream commit c3883fe06488a483658ba5d849b70e49bee15e7c ]\n\nThis patch fixes an issue in drivers/hid/hid-input.c where values\noutside of the logical range are not clamped when \"null state\" bit of\nthe input control is not set.\n\nThis was discussed on the lists [1] and this change stems from the fact\ndue to the ambiguity of the HID specification it might be appropriate to\nfollow Microsoft's own interpretation of the specification. As noted in\nMicrosoft's documentation [2] in the section titled \"Required HID usages\nfor digitizers\" it is noted that values reported outside the logical\nrange \"will be considered as invalid data and the value will be changed\nto the nearest boundary value (logical min/max).\"\n\nThis patch fixes an issue where the (1292:4745) Innomedia INNEX\nGENESIS/ATARI reports out of range values for its X and Y axis of the\nDPad which, due to the null state bit being unset, are forwarded to\nuserspace as is. Now these values will get clamped to the logical range\nbefore being forwarded to userspace. This device was also used to test\nthis patch.\n\nThis patch expands on commit 3f3752705dbd (\"HID: reject input outside\nlogical range only if null state is set\").\n\n[1]: http://lkml.kernel.org/r/20170307131036.GA853@gaia.local\n[2]: https://msdn.microsoft.com/en-us/library/windows/hardware/dn672278(v=vs.85).asp\n\nSigned-off-by: Tomasz Kramkowski <tk@the-tk.com>\nAcked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/aa4b0ac7c16942717370b704869a72c383b0508a"},{"sha":"d813b4903ff6d10f362dee6a33fa2ec052949f30","author":{"name":"Andrey Vagin","email":"94e0a78365855762efb4dc69e66e1b9e1db47c59@openvz.org"},"message":"net/8021q: create device with all possible features in wanted_features\n\n\n[ Upstream commit 88997e4208aea117627898e5f6f9801cf3cd42d2 ]\n\nwanted_features is a set of features which have to be enabled if a\nhardware allows that.\n\nCurrently when a vlan device is created, its wanted_features is set to\ncurrent features of its base device.\n\nThe problem is that the base device can get new features and they are\nnot propagated to vlan-s of this device.\n\nIf we look at bonding devices, they doesn't have this problem and this\npatch suggests to fix this issue by the same way how it works for bonding\ndevices.\n\nWe meet this problem, when we try to create a vlan device over a bonding\ndevice. When a system are booting, real devices require time to be\ninitialized, so bonding devices created without slaves, then vlan\ndevices are created and only then ethernet devices are added to the\nbonding device. As a result we have vlan devices with disabled\nscatter-gather.\n\n* create a bonding device\n  $ ip link add bond0 type bond\n  $ ethtool -k bond0 | grep scatter\n  scatter-gather: off\n\ttx-scatter-gather: off [requested on]\n\ttx-scatter-gather-fraglist: off [requested on]\n\n* create a vlan device\n  $ ip link add link bond0 name bond0.10 type vlan id 10\n  $ ethtool -k bond0.10 | grep scatter\n  scatter-gather: off\n\ttx-scatter-gather: off\n\ttx-scatter-gather-fraglist: off\n\n* Add a slave device to bond0\n  $ ip link set dev eth0 master bond0\n\nAnd now we can see that the bond0 device has got the scatter-gather\nfeature, but the bond0.10 hasn't got it.\n[root@laptop linux-task-diag]# ethtool -k bond0 | grep scatter\nscatter-gather: on\n\ttx-scatter-gather: on\n\ttx-scatter-gather-fraglist: on\n[root@laptop linux-task-diag]# ethtool -k bond0.10 | grep scatter\nscatter-gather: off\n\ttx-scatter-gather: off\n\ttx-scatter-gather-fraglist: off\n\nWith this patch the vlan device will get all new features from the\nbonding device.\n\nHere is a call trace how features which are set in this patch reach\ndev->wanted_features.\n\nregister_netdevice\n   vlan_dev_init\n\t...\n\tdev->hw_features = NETIF_F_HW_CSUM | NETIF_F_SG |\n\t\t       NETIF_F_FRAGLIST | NETIF_F_GSO_SOFTWARE |\n\t\t       NETIF_F_HIGHDMA | NETIF_F_SCTP_CRC |\n\t\t       NETIF_F_ALL_FCOE;\n\n\tdev->features |= dev->hw_features;\n\t...\n    dev->wanted_features = dev->features & dev->hw_features;\n    __netdev_update_features(dev);\n        vlan_dev_fix_features\n\t   ...\n\nCc: Alexey Kuznetsov <kuznet@virtuozzo.com>\nCc: Patrick McHardy <kaber@trash.net>\nCc: \"David S. Miller\" <davem@davemloft.net>\nSigned-off-by: Andrei Vagin <avagin@openvz.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/d813b4903ff6d10f362dee6a33fa2ec052949f30"},{"sha":"182b1a9332536d824380d3d49ff6ed97686d885e","author":{"name":"Linus Walleij","email":"b0d9e537b6c72323d8ac72352e58c452d7c4fc88@linaro.org"},"message":"ARM: dts: Adjust moxart IRQ controller and flags\n\n\n[ Upstream commit c2a736b698008d296c5010ec39077eeb5796109f ]\n\nThe moxart interrupt line flags were not respected in previous\ndriver: instead of assigning them per-consumer, a fixes mask\nwas set in the controller.\n\nWith the migration to a standard Faraday driver we need to\nset up and handle the consumer flags correctly. Also remove\nthe Moxart-specific flags when switching to using real consumer\nflags.\n\nExtend the register window to 0x100 bytes as we may have a few\nmore registers in there and it doesn't hurt.\n\nTested-by: Jonas Jensen <jonas.jensen@gmail.com>\nSigned-off-by: Jonas Jensen <jonas.jensen@gmail.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Olof Johansson <olof@lixom.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/android-linux-stable/op5/commits/182b1a9332536d824380d3d49ff6ed97686d885e"}]}
{"actor":{"display_login":"nathanchance"}}