{"push_id":2758579779,"size":1000,"distinct_size":4315,"ref":"refs/heads/lineage-15.1","head":"b48d27391757c0f9780fe0c13edf54a08fec82ce","before":"13de117a066b00e75881ea71268d78349dd7d216","commits":[{"sha":"cd59b55080f5fa48a9cf7049dd3dcccb492a50d7","author":{"name":"Heiner Kallweit","email":"688f3b22cb68c85c90f972acb3bbdba2c5ca2ae1@gmail.com"},"message":"r8169: fix powering up RTL8168h\n\n[ Upstream commit 3148dedfe79e422f448a10250d3e2cdf8b7ee617 ]\n\nSince commit a92a08499b1f \"r8169: improve runtime pm in general and\nsuspend unused ports\" interfaces w/o link are runtime-suspended after\n10s. On systems where drivers take longer to load this can lead to the\nsituation that the interface is runtime-suspended already when it's\ninitially brought up.\nThis shouldn't be a problem because rtl_open() resumes MAC/PHY.\nHowever with at least one chip version the interface doesn't properly\ncome up, as reported here:\nhttps://bugzilla.kernel.org/show_bug.cgi?id=199549\n\nThe vendor driver uses a delay to give certain chip versions some\ntime to resume before starting the PHY configuration. So let's do\nthe same. I don't know which chip versions may be affected,\ntherefore apply this delay always.\n\nThis patch was reported to fix the issue for RTL8168h.\nI was able to reproduce the issue on an Asus H310I-Plus which also\nuses a RTL8168h. Also in my case the patch fixed the issue.\n\nReported-by: Slava Kardakov <ojab@ojab.ru>\nTested-by: Slava Kardakov <ojab@ojab.ru>\nSigned-off-by: Heiner Kallweit <hkallweit1@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/cd59b55080f5fa48a9cf7049dd3dcccb492a50d7"},{"sha":"9982c6090d7e23782542f919ebbfdb2f72c1c1d1","author":{"name":"Xin Long","email":"ed9bd6f22d2a1e0b1507d3ddc300dc248265d19a@gmail.com"},"message":"sctp: handle two v4 addrs comparison in sctp_inet6_cmp_addr\n\n[ Upstream commit d625329b06e46bd20baf9ee40847d11982569204 ]\n\nSince sctp ipv6 socket also supports v4 addrs, it's possible to\ncompare two v4 addrs in pf v6 .cmp_addr, sctp_inet6_cmp_addr.\n\nHowever after Commit 1071ec9d453a (\"sctp: do not check port in\nsctp_inet6_cmp_addr\"), it no longer calls af1->cmp_addr, which\nin this case is sctp_v4_cmp_addr, but calls __sctp_v6_cmp_addr\nwhere it handles them as two v6 addrs. It would cause a out of\nbounds crash.\n\nsyzbot found this crash when trying to bind two v4 addrs to a\nv6 socket.\n\nThis patch fixes it by adding the process for two v4 addrs in\nsctp_inet6_cmp_addr.\n\nFixes: 1071ec9d453a (\"sctp: do not check port in sctp_inet6_cmp_addr\")\nReported-by: syzbot+cd494c1dd681d4d93ebb@syzkaller.appspotmail.com\nSigned-off-by: Xin Long <lucien.xin@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nAcked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/9982c6090d7e23782542f919ebbfdb2f72c1c1d1"},{"sha":"00002fa69ffdfc0038e7277bf9de1662098f85cc","author":{"name":"Xin Long","email":"ed9bd6f22d2a1e0b1507d3ddc300dc248265d19a@gmail.com"},"message":"sctp: use the old asoc when making the cookie-ack chunk in dupcook_d\n\n[ Upstream commit 46e16d4b956867013e0bbd7f2bad206f4aa55752 ]\n\nWhen processing a duplicate cookie-echo chunk, for case 'D', sctp will\nnot process the param from this chunk. It means old asoc has nothing\nto be updated, and the new temp asoc doesn't have the complete info.\n\nSo there's no reason to use the new asoc when creating the cookie-ack\nchunk. Otherwise, like when auth is enabled for cookie-ack, the chunk\ncan not be set with auth, and it will definitely be dropped by peer.\n\nThis issue is there since very beginning, and we fix it by using the\nold asoc instead.\n\nSigned-off-by: Xin Long <lucien.xin@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nAcked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/00002fa69ffdfc0038e7277bf9de1662098f85cc"},{"sha":"afad8f840026e7011d58f75a0c2c30772b27ed96","author":{"name":"Michael Chan","email":"3f2e970908f19805ed8a131f8c48f96300c6323e@broadcom.com"},"message":"tg3: Fix vunmap() BUG_ON() triggered from tg3_free_consistent().\n\n[ Upstream commit d89a2adb8bfe6f8949ff389acdb9fa298b6e8e12 ]\n\ntg3_free_consistent() calls dma_free_coherent() to free tp->hw_stats\nunder spinlock and can trigger BUG_ON() in vunmap() because vunmap()\nmay sleep.  Fix it by removing the spinlock and relying on the\nTG3_FLAG_INIT_COMPLETE flag to prevent race conditions between\ntg3_get_stats64() and tg3_free_consistent().  TG3_FLAG_INIT_COMPLETE\nis always cleared under tp->lock before tg3_free_consistent()\nand therefore tg3_get_stats64() can safely access tp->hw_stats\nunder tp->lock if TG3_FLAG_INIT_COMPLETE is set.\n\nFixes: f5992b72ebe0 (\"tg3: Fix race condition in tg3_get_stats64().\")\nReported-by: Zumeng Chen <zumeng.chen@gmail.com>\nSigned-off-by: Michael Chan <michael.chan@broadcom.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/afad8f840026e7011d58f75a0c2c30772b27ed96"},{"sha":"8ff936814817daeefceeb1ce26e80b46439a137d","author":{"name":"Debabrata Banerjee","email":"8416239a43cab9c6f46deec338e1a206a5c77021@akamai.com"},"message":"bonding: do not allow rlb updates to invalid mac\n\n[ Upstream commit 4fa8667ca3989ce14cf66301fa251544fbddbdd0 ]\n\nMake sure multicast, broadcast, and zero mac's cannot be the output of rlb\nupdates, which should all be directed arps. Receive load balancing will be\ncollapsed if any of these happen, as the switch will broadcast.\n\nSigned-off-by: Debabrata Banerjee <dbanerje@akamai.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/8ff936814817daeefceeb1ce26e80b46439a137d"},{"sha":"fc36a2a38f1e87ad0c1d753bbb00bd03ceb75bf1","author":{"name":"Yuchung Cheng","email":"5b5a0a360fa35167ac197fe6359c229fde284cf2@google.com"},"message":"tcp: ignore Fast Open on repair mode\n\n[ Upstream commit 16ae6aa1705299789f71fdea59bfb119c1fbd9c0 ]\n\nThe TCP repair sequence of operation is to first set the socket in\nrepair mode, then inject the TCP stats into the socket with repair\nsocket options, then call connect() to re-activate the socket. The\nconnect syscall simply returns and set state to ESTABLISHED\nmode. As a result Fast Open is meaningless for TCP repair.\n\nHowever allowing sendto() system call with MSG_FASTOPEN flag half-way\nduring the repair operation could unexpectedly cause data to be\nsent, before the operation finishes changing the internal TCP stats\n(e.g. MSS).  This in turn triggers TCP warnings on inconsistent\npacket accounting.\n\nThe fix is to simply disallow Fast Open operation once the socket\nis in the repair mode.\n\nReported-by: syzbot <syzkaller@googlegroups.com>\nSigned-off-by: Yuchung Cheng <ycheng@google.com>\nReviewed-by: Neal Cardwell <ncardwell@google.com>\nReviewed-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/fc36a2a38f1e87ad0c1d753bbb00bd03ceb75bf1"},{"sha":"e0a532d3d4562da65cac8bf74bac3f4190d73a57","author":{"name":"Xin Long","email":"ed9bd6f22d2a1e0b1507d3ddc300dc248265d19a@gmail.com"},"message":"sctp: fix the issue that the cookie-ack with auth can't get processed\n\n[ Upstream commit ce402f044e4e432c296f90eaabb8dbe8f3624391 ]\n\nWhen auth is enabled for cookie-ack chunk, in sctp_inq_pop, sctp\nprocesses auth chunk first, then continues to the next chunk in\nthis packet if chunk_end + chunk_hdr size < skb_tail_pointer().\nOtherwise, it will go to the next packet or discard this chunk.\n\nHowever, it missed the fact that cookie-ack chunk's size is equal\nto chunk_hdr size, which couldn't match that check, and thus this\nchunk would not get processed.\n\nThis patch fixes it by changing the check to chunk_end + chunk_hdr\nsize <= skb_tail_pointer().\n\nFixes: 26b87c788100 (\"net: sctp: fix remote memory pressure from excessive queueing\")\nSigned-off-by: Xin Long <lucien.xin@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nAcked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/e0a532d3d4562da65cac8bf74bac3f4190d73a57"},{"sha":"957adaae7d228f5be44ed0e4ea926dc8e3d45caf","author":{"name":"Xin Long","email":"ed9bd6f22d2a1e0b1507d3ddc300dc248265d19a@gmail.com"},"message":"sctp: delay the authentication for the duplicated cookie-echo chunk\n\n[ Upstream commit 59d8d4434f429b4fa8a346fd889058bda427a837 ]\n\nNow sctp only delays the authentication for the normal cookie-echo\nchunk by setting chunk->auth_chunk in sctp_endpoint_bh_rcv(). But\nfor the duplicated one with auth, in sctp_assoc_bh_rcv(), it does\nauthentication first based on the old asoc, which will definitely\nfail due to the different auth info in the old asoc.\n\nThe duplicated cookie-echo chunk will create a new asoc with the\nauth info from this chunk, and the authentication should also be\ndone with the new asoc's auth info for all of the collision 'A',\n'B' and 'D'. Otherwise, the duplicated cookie-echo chunk with auth\nwill never pass the authentication and create the new connection.\n\nThis issue exists since very beginning, and this fix is to make\nsctp_assoc_bh_rcv() follow the way sctp_endpoint_bh_rcv() does\nfor the normal cookie-echo chunk to delay the authentication.\n\nWhile at it, remove the unused params from sctp_sf_authenticate()\nand define sctp_auth_chunk_verify() used for all the places that\ndo the delayed authentication.\n\nv1->v2:\n  fix the typo in changelog as Marcelo noticed.\n\nAcked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>\nSigned-off-by: Xin Long <lucien.xin@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/957adaae7d228f5be44ed0e4ea926dc8e3d45caf"},{"sha":"bea8a671cee74232bbeef3980354cb9b305f6a9f","author":{"name":"Takashi Iwai","email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de"},"message":"ALSA: timer: Call notifier in the same spinlock\n\ncommit f65e0d299807d8a11812845c972493c3f9a18e10 upstream.\n\nsnd_timer_notify1() is called outside the spinlock and it retakes the\nlock after the unlock.  This is rather racy, and it's safer to move\nsnd_timer_notify() call inside the main spinlock.\n\nThe patch also contains a slight refactoring / cleanup of the code.\nNow all start/stop/continue/pause look more symmetric and a bit better\nreadable.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/bea8a671cee74232bbeef3980354cb9b305f6a9f"},{"sha":"9bb698bedebf437ae3de8bae8e1aa8bca02664da","author":{"name":"Richard Guy Briggs","email":"eb4b5bbb4a6cbf3468229148f167a307303eeb1f@redhat.com"},"message":"audit: move calcs after alloc and check when logging set loginuid\n\ncommit 76a658c20efd541a62838d9ff68ce94170d7a549 upstream.\n\nMove the calculations of values after the allocation in case the\nallocation fails.  This avoids wasting effort in the rare case that it\nfails, but more importantly saves us extra logic to release the tty\nref.\n\nSigned-off-by: Richard Guy Briggs <rgb@redhat.com>\nSigned-off-by: Paul Moore <paul@paul-moore.com>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/9bb698bedebf437ae3de8bae8e1aa8bca02664da"},{"sha":"45eecfb9c5f5bc2f7c254c8bcc4219fa4b31008c","author":{"name":"Ard Biesheuvel","email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org"},"message":"arm64: introduce mov_q macro to move a constant into a 64-bit register\n\ncommit 30b5ba5cf333cc650e474eaf2cc1ae91bc7cf89f upstream.\n\nImplement a macro mov_q that can be used to move an immediate constant\ninto a 64-bit register, using between 2 and 4 movz/movk instructions\n(depending on the operand)\n\nAcked-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/45eecfb9c5f5bc2f7c254c8bcc4219fa4b31008c"},{"sha":"348f043ab6c6ab15f9e49b7905ba932dd260cf93","author":{"name":"Suzuki K Poulose","email":"25f0e69a3d23ed1d9a060214a9ff1a9504ba3f49@arm.com"},"message":"arm64: Add work around for Arm Cortex-A55 Erratum 1024718\n\ncommit ece1397cbc89c51914fae1aec729539cfd8bd62b upstream.\n\nSome variants of the Arm Cortex-55 cores (r0p0, r0p1, r1p0) suffer\nfrom an erratum 1024718, which causes incorrect updates when DBM/AP\nbits in a page table entry is modified without a break-before-make\nsequence. The work around is to skip enabling the hardware DBM feature\non the affected cores. The hardware Access Flag management features\nis not affected. There are some other cores suffering from this\nerrata, which could be added to the midr_list to trigger the work\naround.\n\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: ckadabi@codeaurora.org\nReviewed-by: Dave Martin <dave.martin@arm.com>\nSigned-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/348f043ab6c6ab15f9e49b7905ba932dd260cf93"},{"sha":"2fc127737e300bba00d4ed878dac4c78be42522b","author":{"name":"Mel Gorman","email":"39ea6a09710987173e32e37c86918024a0f441c1@suse.de"},"message":"futex: Remove unnecessary warning from get_futex_key\n\ncommit 48fb6f4db940e92cfb16cd878cddd59ea6120d06 upstream.\n\nCommit 65d8fc777f6d (\"futex: Remove requirement for lock_page() in\nget_futex_key()\") removed an unnecessary lock_page() with the\nside-effect that page->mapping needed to be treated very carefully.\n\nTwo defensive warnings were added in case any assumption was missed and\nthe first warning assumed a correct application would not alter a\nmapping backing a futex key.  Since merging, it has not triggered for\nany unexpected case but Mark Rutland reported the following bug\ntriggering due to the first warning.\n\n  kernel BUG at kernel/futex.c:679!\n  Internal error: Oops - BUG: 0 [#1] PREEMPT SMP\n  Modules linked in:\n  CPU: 0 PID: 3695 Comm: syz-executor1 Not tainted 4.13.0-rc3-00020-g307fec773ba3 #3\n  Hardware name: linux,dummy-virt (DT)\n  task: ffff80001e271780 task.stack: ffff000010908000\n  PC is at get_futex_key+0x6a4/0xcf0 kernel/futex.c:679\n  LR is at get_futex_key+0x6a4/0xcf0 kernel/futex.c:679\n  pc : [<ffff00000821ac14>] lr : [<ffff00000821ac14>] pstate: 80000145\n\nThe fact that it's a bug instead of a warning was due to an unrelated\narm64 problem, but the warning itself triggered because the underlying\nmapping changed.\n\nThis is an application issue but from a kernel perspective it's a\nrecoverable situation and the warning is unnecessary so this patch\nremoves the warning.  The warning may potentially be triggered with the\nfollowing test program from Mark although it may be necessary to adjust\nNR_FUTEX_THREADS to be a value smaller than the number of CPUs in the\nsystem.\n\n    #include <linux/futex.h>\n    #include <pthread.h>\n    #include <stdio.h>\n    #include <stdlib.h>\n    #include <sys/mman.h>\n    #include <sys/syscall.h>\n    #include <sys/time.h>\n    #include <unistd.h>\n\n    #define NR_FUTEX_THREADS 16\n    pthread_t threads[NR_FUTEX_THREADS];\n\n    void *mem;\n\n    #define MEM_PROT  (PROT_READ | PROT_WRITE)\n    #define MEM_SIZE  65536\n\n    static int futex_wrapper(int *uaddr, int op, int val,\n                             const struct timespec *timeout,\n                             int *uaddr2, int val3)\n    {\n        syscall(SYS_futex, uaddr, op, val, timeout, uaddr2, val3);\n    }\n\n    void *poll_futex(void *unused)\n    {\n        for (;;) {\n            futex_wrapper(mem, FUTEX_CMP_REQUEUE_PI, 1, NULL, mem + 4, 1);\n        }\n    }\n\n    int main(int argc, char *argv[])\n    {\n        int i;\n\n        mem = mmap(NULL, MEM_SIZE, MEM_PROT,\n               MAP_SHARED | MAP_ANONYMOUS, -1, 0);\n\n        printf(\"Mapping @ %p\\n\", mem);\n\n        printf(\"Creating futex threads...\\n\");\n\n        for (i = 0; i < NR_FUTEX_THREADS; i++)\n            pthread_create(&threads[i], NULL, poll_futex, NULL);\n\n        printf(\"Flipping mapping...\\n\");\n        for (;;) {\n            mmap(mem, MEM_SIZE, MEM_PROT,\n                 MAP_FIXED | MAP_SHARED | MAP_ANONYMOUS, -1, 0);\n        }\n\n        return 0;\n    }\n\nReported-and-tested-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Mel Gorman <mgorman@suse.de>\nAcked-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: stable@vger.kernel.org # 4.7+\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/2fc127737e300bba00d4ed878dac4c78be42522b"},{"sha":"177a981885cf9588ca5cbcaf2ce65ab0d4b4abb3","author":{"name":"Jiri Slaby","email":"dfbf39eb5bf303a3db5454d815cb8c8888cbadf9@suse.cz"},"message":"futex: Remove duplicated code and fix undefined behaviour\n\ncommit 30d6e0a4190d37740e9447e4e4815f06992dd8c3 upstream.\n\nThere is code duplicated over all architecture's headers for\nfutex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr,\nand comparison of the result.\n\nRemove this duplication and leave up to the arches only the needed\nassembly which is now in arch_futex_atomic_op_inuser.\n\nThis effectively distributes the Will Deacon's arm64 fix for undefined\nbehaviour reported by UBSAN to all architectures. The fix was done in\ncommit 5f16a046f8e1 (arm64: futex: Fix undefined behaviour with\nFUTEX_OP_OPARG_SHIFT usage). Look there for an example dump.\n\nAnd as suggested by Thomas, check for negative oparg too, because it was\nalso reported to cause undefined behaviour report.\n\nNote that s390 removed access_ok check in d12a29703 (\"s390/uaccess:\nremove pointless access_ok() checks\") as access_ok there returns true.\nWe introduce it back to the helper for the sake of simplicity (it gets\noptimized away anyway).\n\nSigned-off-by: Jiri Slaby <jslaby@suse.cz>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Russell King <rmk+kernel@armlinux.org.uk>\nAcked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)\nAcked-by: Heiko Carstens <heiko.carstens@de.ibm.com> [s390]\nAcked-by: Chris Metcalf <cmetcalf@mellanox.com> [for tile]\nReviewed-by: Darren Hart (VMware) <dvhart@infradead.org>\nReviewed-by: Will Deacon <will.deacon@arm.com> [core/arm64]\nCc: linux-mips@linux-mips.org\nCc: Rich Felker <dalias@libc.org>\nCc: linux-ia64@vger.kernel.org\nCc: linux-sh@vger.kernel.org\nCc: peterz@infradead.org\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Max Filippov <jcmvbkbc@gmail.com>\nCc: Paul Mackerras <paulus@samba.org>\nCc: sparclinux@vger.kernel.org\nCc: Jonas Bonn <jonas@southpole.se>\nCc: linux-s390@vger.kernel.org\nCc: linux-arch@vger.kernel.org\nCc: Yoshinori Sato <ysato@users.sourceforge.jp>\nCc: linux-hexagon@vger.kernel.org\nCc: Helge Deller <deller@gmx.de>\nCc: \"James E.J. Bottomley\" <jejb@parisc-linux.org>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: Matt Turner <mattst88@gmail.com>\nCc: linux-snps-arc@lists.infradead.org\nCc: Fenghua Yu <fenghua.yu@intel.com>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: linux-xtensa@linux-xtensa.org\nCc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>\nCc: openrisc@lists.librecores.org\nCc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>\nCc: Stafford Horne <shorne@gmail.com>\nCc: linux-arm-kernel@lists.infradead.org\nCc: Richard Henderson <rth@twiddle.net>\nCc: Chris Zankel <chris@zankel.net>\nCc: Michal Simek <monstr@monstr.eu>\nCc: Tony Luck <tony.luck@intel.com>\nCc: linux-parisc@vger.kernel.org\nCc: Vineet Gupta <vgupta@synopsys.com>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: Richard Kuo <rkuo@codeaurora.org>\nCc: linux-alpha@vger.kernel.org\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: linuxppc-dev@lists.ozlabs.org\nCc: \"David S. Miller\" <davem@davemloft.net>\nLink: http://lkml.kernel.org/r/20170824073105.3901-1-jslaby@suse.cz\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/177a981885cf9588ca5cbcaf2ce65ab0d4b4abb3"},{"sha":"ee551b8e00b0368cb1188dbf0238a3a8989e9845","author":{"name":"Antony Antony","email":"1799296195846afeef14df836a5db11994803780@phenome.org"},"message":"xfrm: fix xfrm_do_migrate() with AEAD e.g(AES-GCM)\n\ncommit 75bf50f4aaa1c78d769d854ab3d975884909e4fb upstream.\n\ncopy geniv when cloning the xfrm state.\n\nx->geniv was not copied to the new state and migration would fail.\n\nxfrm_do_migrate\n  ..\n  xfrm_state_clone()\n   ..\n   ..\n   esp_init_aead()\n   crypto_alloc_aead()\n    crypto_alloc_tfm()\n     crypto_find_alg() return EAGAIN and failed\n\nSigned-off-by: Antony Antony <antony@phenome.org>\nSigned-off-by: Steffen Klassert <steffen.klassert@secunet.com>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/ee551b8e00b0368cb1188dbf0238a3a8989e9845"},{"sha":"415a85ce93fdc114b0ca37577882569481d11c4e","author":{"name":"Vasily Averin","email":"92a5505f10e70d6be04c6ea75cda66fdd7decf37@virtuozzo.com"},"message":"lockd: lost rollback of set_grace_period() in lockd_down_net()\n\ncommit 3a2b19d1ee5633f76ae8a88da7bc039a5d1732aa upstream.\n\nCommit efda760fe95ea (\"lockd: fix lockd shutdown race\") is incorrect,\nit removes lockd_manager and disarm grace_period_end for init_net only.\n\nIf nfsd was started from another net namespace lockd_up_net() calls\nset_grace_period() that adds lockd_manager into per-netns list\nand queues grace_period_end delayed work.\n\nThese action should be reverted in lockd_down_net().\nOtherwise it can lead to double list_add on after restart nfsd in netns,\nand to use-after-free if non-disarmed delayed work will be executed after netns destroy.\n\nFixes: efda760fe95e (\"lockd: fix lockd shutdown race\")\nCc: stable@vger.kernel.org\nSigned-off-by: Vasily Averin <vvs@virtuozzo.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/415a85ce93fdc114b0ca37577882569481d11c4e"},{"sha":"59d96688ed7c62f71b881ece31efe89a0c3fe664","author":{"name":"Greg Kroah-Hartman","email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org"},"message":"Revert \"ARM: dts: imx6qdl-wandboard: Fix audio channel swap\"\n\nThis reverts commit 9de3a3bfed892608dc30a6bc3fd8bdbeae5b51a5 which was\ncommit 79935915300c5eb88a0e94fa9148a7505c14a02a upstream.\n\nAs Ben points out:\n\tThis depends on:\n\n\tcommit 570c70a60f53ca737ead4e5966c446bf0d39fac9\n\tAuthor: Fabio Estevam <fabio.estevam@nxp.com>\n\tDate:   Wed Apr 5 11:32:34 2017 -0300\n\n\t    ASoC: sgtl5000: Allow LRCLK pad drive strength to be changed\n\nwhich did not show up until 4.13, so this makes no sense to have in this\nstable branch.\n\nReported-by: Ben Hutchings <ben.hutchings@codethink.co.uk>\nCc: Fabio Estevam <fabio.estevam@nxp.com>\nCc: Shawn Guo <shawnguo@kernel.org>\nCc: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/59d96688ed7c62f71b881ece31efe89a0c3fe664"},{"sha":"e28debec24f5c40ac5752bd2fc3b2e686e9010d0","author":{"name":"James Chapman","email":"d87d459960487ecb1b999dfc309f5d5f521df082@katalix.com"},"message":"l2tp: revert \"l2tp: fix missing print session offset info\"\n\ncommit de3b58bc359a861d5132300f53f95e83f71954b3 upstream.\n\nRevert commit 820da5357572 (\"l2tp: fix missing print session offset\ninfo\").  The peer_offset parameter is removed.\n\nSigned-off-by: James Chapman <jchapman@katalix.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nCc: Guillaume Nault <g.nault@alphalink.fr>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/e28debec24f5c40ac5752bd2fc3b2e686e9010d0"},{"sha":"7d56aed52b52450181c7ba58cb680739cb7e5737","author":{"name":"Michael Kerrisk (man-pages)","email":"cc9a9bf9e3f3b546e69143652ae261619ab7ca78@gmail.com"},"message":"pipe: cap initial pipe capacity according to pipe-max-size limit\n\ncommit 086e774a57fba4695f14383c0818994c0b31da7c upstream.\n\nThis is a patch that provides behavior that is more consistent, and\nprobably less surprising to users. I consider the change optional, and\nwelcome opinions about whether it should be applied.\n\nBy default, pipes are created with a capacity of 64 kiB.  However,\n/proc/sys/fs/pipe-max-size may be set smaller than this value.  In this\nscenario, an unprivileged user could thus create a pipe whose initial\ncapacity exceeds the limit. Therefore, it seems logical to cap the\ninitial pipe capacity according to the value of pipe-max-size.\n\nThe test program shown earlier in this patch series can be used to\ndemonstrate the effect of the change brought about with this patch:\n\n    # cat /proc/sys/fs/pipe-max-size\n    1048576\n    # sudo -u mtk ./test_F_SETPIPE_SZ 1\n    Initial pipe capacity: 65536\n    # echo 10000 > /proc/sys/fs/pipe-max-size\n    # cat /proc/sys/fs/pipe-max-size\n    16384\n    # sudo -u mtk ./test_F_SETPIPE_SZ 1\n    Initial pipe capacity: 16384\n    # ./test_F_SETPIPE_SZ 1\n    Initial pipe capacity: 65536\n\nThe last two executions of 'test_F_SETPIPE_SZ' show that pipe-max-size\ncaps the initial allocation for a new pipe for unprivileged users, but\nnot for privileged users.\n\nLink: http://lkml.kernel.org/r/31dc7064-2a17-9c5b-1df1-4e3012ee992c@gmail.com\nSigned-off-by: Michael Kerrisk <mtk.manpages@gmail.com>\nReviewed-by: Vegard Nossum <vegard.nossum@oracle.com>\nCc: Willy Tarreau <w@1wt.eu>\nCc: <socketpair@gmail.com>\nCc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>\nCc: Jens Axboe <axboe@fb.com>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/7d56aed52b52450181c7ba58cb680739cb7e5737"},{"sha":"cde6d68b1a4f67b8b1c7f71c710fd8590ef725a3","author":{"name":"Jiri Slaby","email":"dfbf39eb5bf303a3db5454d815cb8c8888cbadf9@suse.cz"},"message":"futex: futex_wake_op, fix sign_extend32 sign bits\n\ncommit d70ef22892ed6c066e51e118b225923c9b74af34 upstream.\n\nsign_extend32 counts the sign bit parameter from 0, not from 1.  So we\nhave to use \"11\" for 12th bit, not \"12\".\n\nThis mistake means we have not allowed negative op and cmp args since\ncommit 30d6e0a4190d (\"futex: Remove duplicated code and fix undefined\nbehaviour\") till now.\n\nFixes: 30d6e0a4190d (\"futex: Remove duplicated code and fix undefined behaviour\")\nSigned-off-by: Jiri Slaby <jslaby@suse.cz>\nCc: Ingo Molnar <mingo@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Darren Hart <dvhart@infradead.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/X00TD/android_kernel_asus_sdm660/commits/cde6d68b1a4f67b8b1c7f71c710fd8590ef725a3"}]}
{"actor":{"display_login":"ShivamKumarJha"}}