{"push_id":2737872276,"size":33,"distinct_size":33,"ref":"refs/heads/whyred-o-oss","head":"6b9ba04999078d12daf5cbaf5d905decafcfc854","before":"a1714a915fc285b774a0617b4169d2a83d791948","commits":[{"sha":"f3af03e9c7f06275c3236b08bdcdf561f88fb1fa","author":{"name":"David Rientjes","email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com"},"message":"compiler, clang: suppress warning for unused static inline functions\n\ncommit abb2ea7dfd82451d85ce669b811310c05ab5ca46 upstream.\n\nGCC explicitly does not warn for unused static inline functions for\n-Wunused-function.  The manual states:\n\n\tWarn whenever a static function is declared but not defined or\n\ta non-inline static function is unused.\n\nClang does warn for static inline functions that are unused.\n\nIt turns out that suppressing the warnings avoids potentially complex\n#ifdef directives, which also reduces LOC.\n\nSuppress the warning for clang.\n\nSigned-off-by: David Rientjes <rientjes@google.com>\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/android-linux-stable/whyred/commits/f3af03e9c7f06275c3236b08bdcdf561f88fb1fa"},{"sha":"9acb6600059ffa072a30c221ad784d1ebcea7b42","author":{"name":"Linus Torvalds","email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org"},"message":"compiler, clang: properly override 'inline' for clang\n\ncommit 6d53cefb18e4646fb4bf62ccb6098fb3808486df upstream.\n\nCommit abb2ea7dfd82 (\"compiler, clang: suppress warning for unused\nstatic inline functions\") just caused more warnings due to re-defining\nthe 'inline' macro.\n\nSo undef it before re-defining it, and also add the 'notrace' attribute\nlike the gcc version that this is overriding does.\n\nMaybe this makes clang happier.\n\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/android-linux-stable/whyred/commits/9acb6600059ffa072a30c221ad784d1ebcea7b42"},{"sha":"a2da6af8b5e83268dbeb5b14d85625b50d0d304b","author":{"name":"David Rientjes","email":"d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com"},"message":"compiler, clang: always inline when CONFIG_OPTIMIZE_INLINING is disabled\n\ncommit 9a04dbcfb33b4012d0ce8c0282f1e3ca694675b1 upstream.\n\nThe motivation for commit abb2ea7dfd82 (\"compiler, clang: suppress\nwarning for unused static inline functions\") was to suppress clang's\nwarnings about unused static inline functions.\n\nFor configs without CONFIG_OPTIMIZE_INLINING enabled, such as any non-x86\narchitecture, `inline' in the kernel implies that\n__attribute__((always_inline)) is used.\n\nSome code depends on that behavior, see\n  https://lkml.org/lkml/2017/6/13/918:\n\n  net/built-in.o: In function `__xchg_mb':\n  arch/arm64/include/asm/cmpxchg.h:99: undefined reference to `__compiletime_assert_99'\n  arch/arm64/include/asm/cmpxchg.h:99: undefined reference to `__compiletime_assert_99\n\nThe full fix would be to identify these breakages and annotate the\nfunctions with __always_inline instead of `inline'.  But since we are\nlate in the 4.12-rc cycle, simply carry forward the forced inlining\nbehavior and work toward moving arm64, and other architectures, toward\nCONFIG_OPTIMIZE_INLINING behavior.\n\nLink: http://lkml.kernel.org/r/alpine.DEB.2.10.1706261552200.1075@chino.kir.corp.google.com\nSigned-off-by: David Rientjes <rientjes@google.com>\nReported-by: Sodagudi Prasad <psodagud@codeaurora.org>\nTested-by: Sodagudi Prasad <psodagud@codeaurora.org>\nTested-by: Matthias Kaehlcke <mka@chromium.org>\nCc: Mark Rutland <mark.rutland@arm.com>\nCc: Will Deacon <will.deacon@arm.com>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/a2da6af8b5e83268dbeb5b14d85625b50d0d304b"},{"sha":"bdb0a55ef623532fa58c67a22635d139660b1cfd","author":{"name":"Nick Desaulniers","email":"00198f13417fb2e066da5908d444d839551c0414@google.com"},"message":"compiler-gcc.h: Add __attribute__((gnu_inline)) to all inline declarations\n\ncommit d03db2bc26f0e4a6849ad649a09c9c73fccdc656 upstream.\n\nFunctions marked extern inline do not emit an externally visible\nfunction when the gnu89 C standard is used. Some KBUILD Makefiles\noverwrite KBUILD_CFLAGS. This is an issue for GCC 5.1+ users as without\nan explicit C standard specified, the default is gnu11. Since c99, the\nsemantics of extern inline have changed such that an externally visible\nfunction is always emitted. This can lead to multiple definition errors\nof extern inline functions at link time of compilation units whose build\nfiles have removed an explicit C standard compiler flag for users of GCC\n5.1+ or Clang.\n\nSuggested-by: Arnd Bergmann <arnd@arndb.de>\nSuggested-by: H. Peter Anvin <hpa@zytor.com>\nSuggested-by: Joe Perches <joe@perches.com>\nSigned-off-by: Nick Desaulniers <ndesaulniers@google.com>\nAcked-by: Juergen Gross <jgross@suse.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: acme@redhat.com\nCc: akataria@vmware.com\nCc: akpm@linux-foundation.org\nCc: andrea.parri@amarulasolutions.com\nCc: ard.biesheuvel@linaro.org\nCc: aryabinin@virtuozzo.com\nCc: astrachan@google.com\nCc: boris.ostrovsky@oracle.com\nCc: brijesh.singh@amd.com\nCc: caoj.fnst@cn.fujitsu.com\nCc: geert@linux-m68k.org\nCc: ghackmann@google.com\nCc: gregkh@linuxfoundation.org\nCc: jan.kiszka@siemens.com\nCc: jarkko.sakkinen@linux.intel.com\nCc: jpoimboe@redhat.com\nCc: keescook@google.com\nCc: kirill.shutemov@linux.intel.com\nCc: kstewart@linuxfoundation.org\nCc: linux-efi@vger.kernel.org\nCc: linux-kbuild@vger.kernel.org\nCc: manojgupta@google.com\nCc: mawilcox@microsoft.com\nCc: michal.lkml@markovi.net\nCc: mjg59@google.com\nCc: mka@chromium.org\nCc: pombredanne@nexb.com\nCc: rientjes@google.com\nCc: rostedt@goodmis.org\nCc: sedat.dilek@gmail.com\nCc: thomas.lendacky@amd.com\nCc: tstellar@redhat.com\nCc: tweek@google.com\nCc: virtualization@lists.linux-foundation.org\nCc: will.deacon@arm.com\nCc: yamada.masahiro@socionext.com\nLink: http://lkml.kernel.org/r/20180621162324.36656-2-ndesaulniers@google.com\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/android-linux-stable/whyred/commits/bdb0a55ef623532fa58c67a22635d139660b1cfd"},{"sha":"f15fa075cdff3a5c7321d4fa6f3d733d28ff46e0","author":{"name":"H. Peter Anvin","email":"8a453bad9912ffe59bc0f0b8abe03df9be19379e@linux.intel.com"},"message":"x86/asm: Add _ASM_ARG* constants for argument registers to <asm/asm.h>\n\ncommit 0e2e160033283e20f688d8bad5b89460cc5bfcc4 upstream.\n\ni386 and x86-64 uses different registers for arguments; make them\navailable so we don't have to #ifdef in the actual code.\n\nNative size and specified size (q, l, w, b) versions are provided.\n\nSigned-off-by: H. Peter Anvin <hpa@linux.intel.com>\nSigned-off-by: Nick Desaulniers <ndesaulniers@google.com>\nReviewed-by: Sedat Dilek <sedat.dilek@gmail.com>\nAcked-by: Juergen Gross <jgross@suse.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: acme@redhat.com\nCc: akataria@vmware.com\nCc: akpm@linux-foundation.org\nCc: andrea.parri@amarulasolutions.com\nCc: ard.biesheuvel@linaro.org\nCc: arnd@arndb.de\nCc: aryabinin@virtuozzo.com\nCc: astrachan@google.com\nCc: boris.ostrovsky@oracle.com\nCc: brijesh.singh@amd.com\nCc: caoj.fnst@cn.fujitsu.com\nCc: geert@linux-m68k.org\nCc: ghackmann@google.com\nCc: gregkh@linuxfoundation.org\nCc: jan.kiszka@siemens.com\nCc: jarkko.sakkinen@linux.intel.com\nCc: joe@perches.com\nCc: jpoimboe@redhat.com\nCc: keescook@google.com\nCc: kirill.shutemov@linux.intel.com\nCc: kstewart@linuxfoundation.org\nCc: linux-efi@vger.kernel.org\nCc: linux-kbuild@vger.kernel.org\nCc: manojgupta@google.com\nCc: mawilcox@microsoft.com\nCc: michal.lkml@markovi.net\nCc: mjg59@google.com\nCc: mka@chromium.org\nCc: pombredanne@nexb.com\nCc: rientjes@google.com\nCc: rostedt@goodmis.org\nCc: thomas.lendacky@amd.com\nCc: tstellar@redhat.com\nCc: tweek@google.com\nCc: virtualization@lists.linux-foundation.org\nCc: will.deacon@arm.com\nCc: yamada.masahiro@socionext.com\nLink: http://lkml.kernel.org/r/20180621162324.36656-3-ndesaulniers@google.com\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/android-linux-stable/whyred/commits/f15fa075cdff3a5c7321d4fa6f3d733d28ff46e0"},{"sha":"0b12830665116f90ed795a1a54e2fced083c1a59","author":{"name":"David S. Miller","email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@davemloft.net"},"message":"Revert \"sit: reload iphdr in ipip6_rcv\"\n\ncommit f4eb17e1efe538d4da7d574bedb00a8dafcc26b7 upstream.\n\nThis reverts commit b699d0035836f6712917a41e7ae58d84359b8ff9.\n\nAs per Eric Dumazet, the pskb_may_pull() is a NOP in this\nparticular case, so the 'iph' reload is unnecessary.\n\nSigned-off-by: David S. Miller <davem@davemloft.net>\nCc: Dmitry Tunin <hanipouspilot@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/0b12830665116f90ed795a1a54e2fced083c1a59"},{"sha":"b9e22bd82856a794986d75bb3bb585b8bfbf4d99","author":{"name":"alex chen","email":"4ac5dc52b5921607e5d8c9db7ef74df83bd6110b@huawei.com"},"message":"ocfs2: subsystem.su_mutex is required while accessing the item->ci_parent\n\ncommit 853bc26a7ea39e354b9f8889ae7ad1492ffa28d2 upstream.\n\nThe subsystem.su_mutex is required while accessing the item->ci_parent,\notherwise, NULL pointer dereference to the item->ci_parent will be\ntriggered in the following situation:\n\nadd node                     delete node\nsys_write\n vfs_write\n  configfs_write_file\n   o2nm_node_store\n    o2nm_node_local_write\n                             do_rmdir\n                              vfs_rmdir\n                               configfs_rmdir\n                                mutex_lock(&subsys->su_mutex);\n                                unlink_obj\n                                 item->ci_group = NULL;\n                                 item->ci_parent = NULL;\n\t to_o2nm_cluster_from_node\n\t  node->nd_item.ci_parent->ci_parent\n\t  BUG since of NULL pointer dereference to nd_item.ci_parent\n\nMoreover, the o2nm_cluster also should be protected by the\nsubsystem.su_mutex.\n\n[alex.chen@huawei.com: v2]\n  Link: http://lkml.kernel.org/r/59EEAA69.9080703@huawei.com\nLink: http://lkml.kernel.org/r/59E9B36A.10700@huawei.com\nSigned-off-by: Alex Chen <alex.chen@huawei.com>\nReviewed-by: Jun Piao <piaojun@huawei.com>\nReviewed-by: Joseph Qi <jiangqi903@gmail.com>\nCc: Mark Fasheh <mfasheh@versity.com>\nCc: Joel Becker <jlbec@evilplan.org>\nCc: Junxiao Bi <junxiao.bi@oracle.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Salvatore Bonaccorso <carnil@debian.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/b9e22bd82856a794986d75bb3bb585b8bfbf4d99"},{"sha":"3e18265e43138f685cd78a4b1c92dd788e32e2fa","author":{"name":"Jonas Gorski","email":"9712c064bde5a52658fc87d6454b4956f9bf286b@gmail.com"},"message":"bcm63xx_enet: correct clock usage\n\ncommit 9c86b846ce02f7e35d7234cf090b80553eba5389 upstream.\n\nCheck the return code of prepare_enable and change one last instance of\nenable only to prepare_enable. Also properly disable and release the\nclock in error paths and on remove for enetsw.\n\nSigned-off-by: Jonas Gorski <jonas.gorski@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Amit Pundir <amit.pundir@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/3e18265e43138f685cd78a4b1c92dd788e32e2fa"},{"sha":"3bed835ab1ec95a7a1ea83c02ee21e6e420050b3","author":{"name":"Jonas Gorski","email":"9712c064bde5a52658fc87d6454b4956f9bf286b@gmail.com"},"message":"bcm63xx_enet: do not write to random DMA channel on BCM6345\n\ncommit d6213c1f2ad54a964b77471690264ed685718928 upstream.\n\nThe DMA controller regs actually point to DMA channel 0, so the write to\nENETDMA_CFG_REG will actually modify a random DMA channel.\n\nSince DMA controller registers do not exist on BCM6345, guard the write\nwith the usual check for dma_has_sram.\n\nSigned-off-by: Jonas Gorski <jonas.gorski@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Amit Pundir <amit.pundir@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/3bed835ab1ec95a7a1ea83c02ee21e6e420050b3"},{"sha":"ec9d59be99aa2de6d8c7e9aa38f426830cf94847","author":{"name":"Christian Lamparter","email":"2b86d4915b352c348b09e5d907edf5d041a1585c@googlemail.com"},"message":"crypto: crypto4xx - remove bad list_del\n\ncommit a728a196d253530f17da5c86dc7dfbe58c5f7094 upstream.\n\nalg entries are only added to the list, after the registration\nwas successful. If the registration failed, it was never added\nto the list in the first place.\n\nSigned-off-by: Christian Lamparter <chunkeey@googlemail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Amit Pundir <amit.pundir@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/ec9d59be99aa2de6d8c7e9aa38f426830cf94847"},{"sha":"517340a7ef476a44905fdb001c4a3dd824d99c3b","author":{"name":"Christian Lamparter","email":"2b86d4915b352c348b09e5d907edf5d041a1585c@googlemail.com"},"message":"crypto: crypto4xx - fix crypto4xx_build_pdr, crypto4xx_build_sdr leak\n\ncommit 5d59ad6eea82ef8df92b4109615a0dde9d8093e9 upstream.\n\nIf one of the later memory allocations in rypto4xx_build_pdr()\nfails: dev->pdr (and/or) dev->pdr_uinfo wouldn't be freed.\n\ncrypto4xx_build_sdr() has the same issue with dev->sdr.\n\nSigned-off-by: Christian Lamparter <chunkeey@googlemail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Amit Pundir <amit.pundir@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/517340a7ef476a44905fdb001c4a3dd824d99c3b"},{"sha":"af4bae09386c787fbc2fa9b69a50d65eba4b6e30","author":{"name":"Gustavo A. R. Silva","email":"beac5f8171fcde5e2ec734cc5d25d03e7362e8de@embeddedor.com"},"message":"atm: zatm: Fix potential Spectre v1\n\n[ Upstream commit ced9e191501e52b95e1b57b8e0db00943869eed0 ]\n\npool can be indirectly controlled by user-space, hence leading to\na potential exploitation of the Spectre variant 1 vulnerability.\n\nThis issue was detected with the help of Smatch:\n\ndrivers/atm/zatm.c:1491 zatm_ioctl() warn: potential spectre issue\n'zatm_dev->pool_info' (local cap)\n\nFix this by sanitizing pool before using it to index\nzatm_dev->pool_info\n\nNotice that given that speculation windows are large, the policy is\nto kill the speculation on the first load and not worry if it can be\ncompleted with a dependent load/store [1].\n\n[1] https://marc.info/?l=linux-kernel&m=152449131114778&w=2\n\nSigned-off-by: Gustavo A. R. Silva <gustavo@embeddedor.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/android-linux-stable/whyred/commits/af4bae09386c787fbc2fa9b69a50d65eba4b6e30"},{"sha":"e41074e9ea4181b77ab02394d7c63e7995a800f9","author":{"name":"Eric Dumazet","email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com"},"message":"net: dccp: avoid crash in ccid3_hc_rx_send_feedback()\n\n[ Upstream commit 74174fe5634ffbf645a7ca5a261571f700b2f332 ]\n\nOn fast hosts or malicious bots, we trigger a DCCP_BUG() which\nseems excessive.\n\nsyzbot reported :\n\nBUG: delta (-6195) <= 0 at net/dccp/ccids/ccid3.c:628/ccid3_hc_rx_send_feedback()\nCPU: 1 PID: 18 Comm: ksoftirqd/1 Not tainted 4.18.0-rc1+ #112\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nCall Trace:\n __dump_stack lib/dump_stack.c:77 [inline]\n dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113\n ccid3_hc_rx_send_feedback net/dccp/ccids/ccid3.c:628 [inline]\n ccid3_hc_rx_packet_recv.cold.16+0x38/0x71 net/dccp/ccids/ccid3.c:793\n ccid_hc_rx_packet_recv net/dccp/ccid.h:185 [inline]\n dccp_deliver_input_to_ccids+0xf0/0x280 net/dccp/input.c:180\n dccp_rcv_established+0x87/0xb0 net/dccp/input.c:378\n dccp_v4_do_rcv+0x153/0x180 net/dccp/ipv4.c:654\n sk_backlog_rcv include/net/sock.h:914 [inline]\n __sk_receive_skb+0x3ba/0xd80 net/core/sock.c:517\n dccp_v4_rcv+0x10f9/0x1f58 net/dccp/ipv4.c:875\n ip_local_deliver_finish+0x2eb/0xda0 net/ipv4/ip_input.c:215\n NF_HOOK include/linux/netfilter.h:287 [inline]\n ip_local_deliver+0x1e9/0x750 net/ipv4/ip_input.c:256\n dst_input include/net/dst.h:450 [inline]\n ip_rcv_finish+0x823/0x2220 net/ipv4/ip_input.c:396\n NF_HOOK include/linux/netfilter.h:287 [inline]\n ip_rcv+0xa18/0x1284 net/ipv4/ip_input.c:492\n __netif_receive_skb_core+0x2488/0x3680 net/core/dev.c:4628\n __netif_receive_skb+0x2c/0x1e0 net/core/dev.c:4693\n process_backlog+0x219/0x760 net/core/dev.c:5373\n napi_poll net/core/dev.c:5771 [inline]\n net_rx_action+0x7da/0x1980 net/core/dev.c:5837\n __do_softirq+0x2e8/0xb17 kernel/softirq.c:284\n run_ksoftirqd+0x86/0x100 kernel/softirq.c:645\n smpboot_thread_fn+0x417/0x870 kernel/smpboot.c:164\n kthread+0x345/0x410 kernel/kthread.c:240\n ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:412\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nReported-by: syzbot <syzkaller@googlegroups.com>\nCc: Gerrit Renker <gerrit@erg.abdn.ac.uk>\nCc: dccp@vger.kernel.org\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/android-linux-stable/whyred/commits/e41074e9ea4181b77ab02394d7c63e7995a800f9"},{"sha":"29dbaecd2fbeda3f8dc76d2484807dec5b139aba","author":{"name":"Eric Dumazet","email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com"},"message":"net: dccp: switch rx_tstamp_last_feedback to monotonic clock\n\n[ Upstream commit 0ce4e70ff00662ad7490e545ba0cd8c1fa179fca ]\n\nTo compute delays, better not use time of the day which can\nbe changed by admins or malicious programs.\n\nAlso change ccid3_first_li() to use s64 type for delta variable\nto avoid potential overflows.\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: Gerrit Renker <gerrit@erg.abdn.ac.uk>\nCc: dccp@vger.kernel.org\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/android-linux-stable/whyred/commits/29dbaecd2fbeda3f8dc76d2484807dec5b139aba"},{"sha":"2f3def9a32ce45263c045464ebe3b6f05d0eb9ef","author":{"name":"Alex Vesker","email":"5d97e6ddacbebfbcdda9f8fd242d7d2670aa652a@mellanox.com"},"message":"net/mlx5: Fix incorrect raw command length parsing\n\n[ Upstream commit 603b7bcff824740500ddfa001d7a7168b0b38542 ]\n\nThe NULL character was not set correctly for the string containing\nthe command length, this caused failures reading the output of the\ncommand due to a random length. The fix is to initialize the output\nlength string.\n\nFixes: e126ba97dba9 (\"mlx5: Add driver for Mellanox Connect-IB adapters\")\nSigned-off-by: Alex Vesker <valex@mellanox.com>\nSigned-off-by: Saeed Mahameed <saeedm@mellanox.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/android-linux-stable/whyred/commits/2f3def9a32ce45263c045464ebe3b6f05d0eb9ef"},{"sha":"6ac40d2dc0eb70a99418729fd7c9d5ff90925855","author":{"name":"Eric Dumazet","email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com"},"message":"net: sungem: fix rx checksum support\n\n[ Upstream commit 12b03558cef6d655d0d394f5e98a6fd07c1f6c0f ]\n\nAfter commit 88078d98d1bb (\"net: pskb_trim_rcsum() and CHECKSUM_COMPLETE\nare friends\"), sungem owners reported the infamous \"eth0: hw csum failure\"\nmessage.\n\nCHECKSUM_COMPLETE has in fact never worked for this driver, but this\nwas masked by the fact that upper stacks had to strip the FCS, and\ntherefore skb->ip_summed was set back to CHECKSUM_NONE before\nmy recent change.\n\nDriver configures a number of bytes to skip when the chip computes\nthe checksum, and for some reason only half of the Ethernet header\nwas skipped.\n\nThen a second problem is that we should strip the FCS by default,\nunless the driver is updated to eventually support NETIF_F_RXFCS in\nthe future.\n\nFinally, a driver should check if NETIF_F_RXCSUM feature is enabled\nor not, so that the admin can turn off rx checksum if wanted.\n\nMany thanks to Andreas Schwab and Mathieu Malaterre for their\nhelp in debugging this issue.\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nReported-by: Meelis Roos <mroos@linux.ee>\nReported-by: Mathieu Malaterre <malat@debian.org>\nReported-by: Andreas Schwab <schwab@linux-m68k.org>\nTested-by: Andreas Schwab <schwab@linux-m68k.org>\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/android-linux-stable/whyred/commits/6ac40d2dc0eb70a99418729fd7c9d5ff90925855"},{"sha":"6f6d1452ad16bd35a3f44c4ce67b5075e86e9b18","author":{"name":"Sudarsana Reddy Kalluru","email":"cacd07e51b108deced42f891974e1fbe222245a7@cavium.com"},"message":"qed: Limit msix vectors in kdump kernel to the minimum required count.\n\n[ Upstream commit bb7858ba1102f82470a917e041fd23e6385c31be ]\n\nMemory size is limited in the kdump kernel environment. Allocation of more\nmsix-vectors (or queues) consumes few tens of MBs of memory, which might\nlead to the kdump kernel failure.\nThis patch adds changes to limit the number of MSI-X vectors in kdump\nkernel to minimum required value (i.e., 2 per engine).\n\nFixes: fe56b9e6a (\"qed: Add module with basic common support\")\nSigned-off-by: Sudarsana Reddy Kalluru <Sudarsana.Kalluru@cavium.com>\nSigned-off-by: Michal Kalderon <Michal.Kalderon@cavium.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/android-linux-stable/whyred/commits/6f6d1452ad16bd35a3f44c4ce67b5075e86e9b18"},{"sha":"73852461f8edec6dae90a303bec5f2b212828eb7","author":{"name":"Jiri Slaby","email":"dfbf39eb5bf303a3db5454d815cb8c8888cbadf9@suse.cz"},"message":"r8152: napi hangup fix after disconnect\n\n[ Upstream commit 0ee1f4734967af8321ecebaf9c74221ace34f2d5 ]\n\nWhen unplugging an r8152 adapter while the interface is UP, the NIC\nbecomes unusable.  usb->disconnect (aka rtl8152_disconnect) deletes\nnapi. Then, rtl8152_disconnect calls unregister_netdev and that invokes\nnetdev->ndo_stop (aka rtl8152_close). rtl8152_close tries to\nnapi_disable, but the napi is already deleted by disconnect above. So\nthe first while loop in napi_disable never finishes. This results in\ncomplete deadlock of the network layer as there is rtnl_mutex held by\nunregister_netdev.\n\nSo avoid the call to napi_disable in rtl8152_close when the device is\nalready gone.\n\nThe other calls to usb_kill_urb, cancel_delayed_work_sync,\nnetif_stop_queue etc. seem to be fine. The urb and netdev is not\ndestroyed yet.\n\nSigned-off-by: Jiri Slaby <jslaby@suse.cz>\nCc: linux-usb@vger.kernel.org\nCc: netdev@vger.kernel.org\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/android-linux-stable/whyred/commits/73852461f8edec6dae90a303bec5f2b212828eb7"},{"sha":"84aeeb1af37a86ee6f2eda969e5c63ef89ec4acc","author":{"name":"Yuchung Cheng","email":"5b5a0a360fa35167ac197fe6359c229fde284cf2@google.com"},"message":"tcp: fix Fast Open key endianness\n\n[ Upstream commit c860e997e9170a6d68f9d1e6e2cf61f572191aaf ]\n\nFast Open key could be stored in different endian based on the CPU.\nPreviously hosts in different endianness in a server farm using\nthe same key config (sysctl value) would produce different cookies.\nThis patch fixes it by always storing it as little endian to keep\nsame API for LE hosts.\n\nReported-by: Daniele Iamartino <danielei@google.com>\nSigned-off-by: Yuchung Cheng <ycheng@google.com>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: Neal Cardwell <ncardwell@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/android-linux-stable/whyred/commits/84aeeb1af37a86ee6f2eda969e5c63ef89ec4acc"},{"sha":"61c66cc52d42f78bbdd8f2e40b7c0bb9b936a12d","author":{"name":"Ilpo Järvinen","email":"5801dcaebe162b451612454667e6a167cf0222c1@helsinki.fi"},"message":"tcp: prevent bogus FRTO undos with non-SACK flows\n\n[ Upstream commit 1236f22fbae15df3736ab4a984c64c0c6ee6254c ]\n\nIf SACK is not enabled and the first cumulative ACK after the RTO\nretransmission covers more than the retransmitted skb, a spurious\nFRTO undo will trigger (assuming FRTO is enabled for that RTO).\nThe reason is that any non-retransmitted segment acknowledged will\nset FLAG_ORIG_SACK_ACKED in tcp_clean_rtx_queue even if there is\nno indication that it would have been delivered for real (the\nscoreboard is not kept with TCPCB_SACKED_ACKED bits in the non-SACK\ncase so the check for that bit won't help like it does with SACK).\nHaving FLAG_ORIG_SACK_ACKED set results in the spurious FRTO undo\nin tcp_process_loss.\n\nWe need to use more strict condition for non-SACK case and check\nthat none of the cumulatively ACKed segments were retransmitted\nto prove that progress is due to original transmissions. Only then\nkeep FLAG_ORIG_SACK_ACKED set, allowing FRTO undo to proceed in\nnon-SACK case.\n\n(FLAG_ORIG_SACK_ACKED is planned to be renamed to FLAG_ORIG_PROGRESS\nto better indicate its purpose but to keep this change minimal, it\nwill be done in another patch).\n\nBesides burstiness and congestion control violations, this problem\ncan result in RTO loop: When the loss recovery is prematurely\nundoed, only new data will be transmitted (if available) and\nthe next retransmission can occur only after a new RTO which in case\nof multiple losses (that are not for consecutive packets) requires\none RTO per loss to recover.\n\nSigned-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>\nTested-by: Neal Cardwell <ncardwell@google.com>\nAcked-by: Neal Cardwell <ncardwell@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/android-linux-stable/whyred/commits/61c66cc52d42f78bbdd8f2e40b7c0bb9b936a12d"}]}
{"actor":{"display_login":"nathanchance"}}