{"push_id":1198176566,"size":35,"distinct_size":35,"ref":"refs/heads/pf-4.4","head":"54a8dfca8eeb10359f5b650d0f8dfb9478132ff4","before":"9256a1e80a704012aeae53095dc0ba0c2001f080","commits":[{"sha":"95e727af08b60284e2617296f07c794a1566f99e","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"net_sched: fix pfifo_head_drop behavior vs backlog\n\n[ Upstream commit 6c0d54f1897d229748d4f41ef919078db6db2123 ]\n\nWhen the qdisc is full, we drop a packet at the head of the queue,\nqueue the current skb and return NET_XMIT_CN\n\nNow we track backlog on upper qdiscs, we need to call\nqdisc_tree_reduce_backlog(), even if the qlen did not change.\n\nFixes: 2ccccf5fb43f (\"net_sched: update hierarchical backlog too\")\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: WANG Cong <xiyou.wangcong@gmail.com>\nCc: Jamal Hadi Salim <jhs@mojatatu.com>\nAcked-by: Cong Wang <xiyou.wangcong@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/pfactum/pf-kernel/commits/95e727af08b60284e2617296f07c794a1566f99e"},{"sha":"36292ca2f2918d4b34d05053bfec5c8c97aaed09","author":{"name":"Jason A. Donenfeld","email":"99e030c4305a4e4b1828d232b8797d3ca296d80a@zx2c4.com"},"message":"net: Don't forget pr_fmt on net_dbg_ratelimited for CONFIG_DYNAMIC_DEBUG\n\n[ Upstream commit daddef76c3deaaa7922f9d7b18edbf0a061215c3 ]\n\nThe implementation of net_dbg_ratelimited in the CONFIG_DYNAMIC_DEBUG\ncase was added with 2c94b5373 (\"net: Implement net_dbg_ratelimited() for\nCONFIG_DYNAMIC_DEBUG case\"). The implementation strategy was to take the\nusual definition of the dynamic_pr_debug macro, but alter it by adding a\ncall to \"net_ratelimit()\" in the if statement. This is, in fact, the\ncorrect approach.\n\nHowever, while doing this, the author of the commit forgot to surround\nfmt by pr_fmt, resulting in unprefixed log messages appearing in the\nconsole. So, this commit adds back the pr_fmt(fmt) invocation, making\nnet_dbg_ratelimited properly consistent across DEBUG, no DEBUG, and\nDYNAMIC_DEBUG cases, and bringing parity with the behavior of\ndynamic_pr_debug as well.\n\nFixes: 2c94b5373 (\"net: Implement net_dbg_ratelimited() for CONFIG_DYNAMIC_DEBUG case\")\nSigned-off-by: Jason A. Donenfeld <Jason@zx2c4.com>\nCc: Tim Bingham <tbingham@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/pfactum/pf-kernel/commits/36292ca2f2918d4b34d05053bfec5c8c97aaed09"},{"sha":"9d6814d7aecf58a2a91d5992b678568b07b62ad7","author":{"name":"Simon Horman","email":"f7123f56b775f32434663a1d9bc86525ea0b75ec@netronome.com"},"message":"sit: correct IP protocol used in ipip6_err\n\n[ Upstream commit d5d8760b78d0cfafe292f965f599988138b06a70 ]\n\nSince 32b8a8e59c9c (\"sit: add IPv4 over IPv4 support\")\nipip6_err() may be called for packets whose IP protocol is\nIPPROTO_IPIP as well as those whose IP protocol is IPPROTO_IPV6.\n\nIn the case of IPPROTO_IPIP packets the correct protocol value is not\npassed to ipv4_update_pmtu() or ipv4_redirect().\n\nThis patch resolves this problem by using the IP protocol of the packet\nrather than a hard-coded value. This appears to be consistent\nwith the usage of the protocol of a packet by icmp_socket_deliver()\nthe caller of ipip6_err().\n\nI was able to exercise the redirect case by using a setup where an ICMP\nredirect was received for the destination of the encapsulated packet.\nHowever, it appears that although incorrect the protocol field is not used\nin this case and thus no problem manifests.  On inspection it does not\nappear that a problem will manifest in the fragmentation needed/update pmtu\ncase either.\n\nIn short I believe this is a cosmetic fix. None the less, the use of\nIPPROTO_IPV6 seems wrong and confusing.\n\nReviewed-by: Dinan Gunawardena <dinan.gunawardena@netronome.com>\nSigned-off-by: Simon Horman <simon.horman@netronome.com>\nAcked-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.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/pfactum/pf-kernel/commits/9d6814d7aecf58a2a91d5992b678568b07b62ad7"},{"sha":"da7da39bdf3193188bad098c90427eac5210de13","author":{"name":"Herbert Xu","email":"b06c1e85ee1d40a691f7eaf317640579555a220e@gondor.apana.org.au"},"message":"esp: Fix ESN generation under UDP encapsulation\n\n[ Upstream commit 962fcef33b03395051367181a0549d29d109d9a4 ]\n\nBlair Steven noticed that ESN in conjunction with UDP encapsulation\nis broken because we set the temporary ESP header to the wrong spot.\n\nThis patch fixes this by first of all using the right spot, i.e.,\n4 bytes off the real ESP header, and then saving this information\nso that after encryption we can restore it properly.\n\nFixes: 7021b2e1cddd (\"esp4: Switch to new AEAD interface\")\nReported-by: Blair Steven <Blair.Steven@alliedtelesis.co.nz>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nAcked-by: Steffen Klassert <steffen.klassert@secunet.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/pfactum/pf-kernel/commits/da7da39bdf3193188bad098c90427eac5210de13"},{"sha":"6fb6914d5b459aefefafb19c57b3903ee4ad8b61","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"netem: fix a use after free\n\n[ Upstream commit 21de12ee5568fd1aec47890c72967abf791ac80a ]\n\nIf the packet was dropped by lower qdisc, then we must not\naccess it later.\n\nSave qdisc_pkt_len(skb) in a temp variable.\n\nFixes: 2ccccf5fb43f (\"net_sched: update hierarchical backlog too\")\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: WANG Cong <xiyou.wangcong@gmail.com>\nCc: Jamal Hadi Salim <jhs@mojatatu.com>\nCc: Stephen Hemminger <stephen@networkplumber.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/pfactum/pf-kernel/commits/6fb6914d5b459aefefafb19c57b3903ee4ad8b61"},{"sha":"d05916086fa3e797b3806f1ec3c5a923adb3070e","author":{"name":"Tom Goff","email":"72896b2edf5b5cac022bcdde0c63fc907e6e6328@ll.mit.edu"},"message":"ipmr/ip6mr: Initialize the last assert time of mfc entries.\n\n[ Upstream commit 70a0dec45174c976c64b4c8c1d0898581f759948 ]\n\nThis fixes wrong-interface signaling on 32-bit platforms for entries\ncreated when jiffies > 2^31 + MFC_ASSERT_THRESH.\n\nSigned-off-by: Tom Goff <thomas.goff@ll.mit.edu>\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/pfactum/pf-kernel/commits/d05916086fa3e797b3806f1ec3c5a923adb3070e"},{"sha":"688feac4897c2a613d730e48b83e3ba4084953be","author":{"name":"daniel","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@dd-wrt.com"},"message":"Bridge: Fix ipv6 mc snooping if bridge has no ipv6 address\n\n[ Upstream commit 0888d5f3c0f183ea6177355752ada433d370ac89 ]\n\nThe bridge is falsly dropping ipv6 mulitcast packets if there is:\n 1. No ipv6 address assigned on the brigde.\n 2. No external mld querier present.\n 3. The internal querier enabled.\n\nWhen the bridge fails to build mld queries, because it has no\nipv6 address, it slilently returns, but keeps the local querier enabled.\nThis specific case causes confusing packet loss.\n\nIpv6 multicast snooping can only work if:\n a) An external querier is present\n OR\n b) The bridge has an ipv6 address an is capable of sending own queries\n\nOtherwise it has to forward/flood the ipv6 multicast traffic,\nbecause snooping cannot work.\n\nThis patch fixes the issue by adding a flag to the bridge struct that\nindicates that there is currently no ipv6 address assinged to the bridge\nand returns a false state for the local querier in\n__br_multicast_querier_exists().\n\nSpecial thanks to Linus Lüssing.\n\nFixes: d1d81d4c3dd8 (\"bridge: check return value of ipv6_dev_get_saddr()\")\nSigned-off-by: Daniel Danzberger <daniel@dd-wrt.com>\nAcked-by: Linus Lüssing <linus.luessing@c0d3.blue>\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/pfactum/pf-kernel/commits/688feac4897c2a613d730e48b83e3ba4084953be"},{"sha":"348a1cd82cfc4c4b4f7b6775aae398c337cc03b8","author":{"name":"Willem de Bruijn","email":"86b583cfb6b08f85a219d9441a0068d5b14d5476@google.com"},"message":"sock_diag: do not broadcast raw socket destruction\n\n[ Upstream commit 9a0fee2b552b1235fb1706ae1fc664ae74573be8 ]\n\nDiag intends to broadcast tcp_sk and udp_sk socket destruction.\nTesting sk->sk_protocol for IPPROTO_TCP/IPPROTO_UDP alone is not\nsufficient for this. Raw sockets can have the same type.\n\nAdd a test for sk->sk_type.\n\nFixes: eb4cb008529c (\"sock_diag: define destruction multicast groups\")\nSigned-off-by: Willem de Bruijn <willemb@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/pfactum/pf-kernel/commits/348a1cd82cfc4c4b4f7b6775aae398c337cc03b8"},{"sha":"11bef1439d07f1f7bcee109606f432bdd178c6da","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf, perf: delay release of BPF prog after grace period\n\n[ Upstream commit ceb56070359b7329b5678b5d95a376fcb24767be ]\n\nCommit dead9f29ddcc (\"perf: Fix race in BPF program unregister\") moved\ndestruction of BPF program from free_event_rcu() callback to __free_event(),\nwhich is problematic if used with tail calls: if prog A is attached as\ntrace event directly, but at the same time present in a tail call map used\nby another trace event program elsewhere, then we need to delay destruction\nvia RCU grace period since it can still be in use by the program doing the\ntail call (the prog first needs to be dropped from the tail call map, then\ntrace event with prog A attached destroyed, so we get immediate destruction).\n\nFixes: dead9f29ddcc (\"perf: Fix race in BPF program unregister\")\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\nCc: Jann Horn <jann@thejh.net>\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/pfactum/pf-kernel/commits/11bef1439d07f1f7bcee109606f432bdd178c6da"},{"sha":"f4de1e74580acbc3a2b4cfd7d257e6ad2f8734ec","author":{"name":"David Barroso","email":"d7c4a6c8a9833b5f49cd0a38b8e0e0e6a45642bf@fastly.com"},"message":"neigh: Explicitly declare RCU-bh read side critical section in neigh_xmit()\n\n[ Upstream commit b560f03ddfb072bca65e9440ff0dc4f9b1d1f056 ]\n\nneigh_xmit() expects to be called inside an RCU-bh read side critical\nsection, and while one of its two current callers gets this right, the\nother one doesn't.\n\nMore specifically, neigh_xmit() has two callers, mpls_forward() and\nmpls_output(), and while both callers call neigh_xmit() under\nrcu_read_lock(), this provides sufficient protection for neigh_xmit()\nonly in the case of mpls_forward(), as that is always called from\nsoftirq context and therefore doesn't need explicit BH protection,\nwhile mpls_output() can be called from process context with softirqs\nenabled.\n\nWhen mpls_output() is called from process context, with softirqs\nenabled, we can be preempted by a softirq at any time, and RCU-bh\nconsiders the completion of a softirq as signaling the end of any\npending read-side critical sections, so if we do get a softirq\nwhile we are in the part of neigh_xmit() that expects to be run inside\nan RCU-bh read side critical section, we can end up with an unexpected\nRCU grace period running right in the middle of that critical section,\nmaking things go boom.\n\nThis patch fixes this impedance mismatch in the callee, by making\nneigh_xmit() always take rcu_read_{,un}lock_bh() around the code that\nexpects to be treated as an RCU-bh read side critical section, as this\nseems a safer option than fixing it in the callers.\n\nFixes: 4fd3d7d9e868f (\"neigh: Add helper function neigh_xmit\")\nSigned-off-by: David Barroso <dbarroso@fastly.com>\nSigned-off-by: Lennert Buytenhek <lbuytenhek@fastly.com>\nAcked-by: David Ahern <dsa@cumulusnetworks.com>\nAcked-by: Robert Shearman <rshearma@brocade.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/pfactum/pf-kernel/commits/f4de1e74580acbc3a2b4cfd7d257e6ad2f8734ec"},{"sha":"779fb6074843a685c241874a5b308fd56cbdb35f","author":{"name":"Nicolas Ferre","email":"2228eb5b44b639b9fdcb84cba702bf0f82db4179@atmel.com"},"message":"net: macb: fix default configuration for GMAC on AT91\n\n[ Upstream commit 6bdaa5e9ed39b3b3328f35d218e8ad5a99cfc4d2 ]\n\nOn AT91 SoCs, the User Register (USRIO) exposes a switch to configure the\n\"Reduced\" or \"Traditional\" version of the Media Independent Interface\n(RMII vs. MII or RGMII vs. GMII).\nAs on the older EMAC version, on GMAC, this switch is set by default to the\nnon-reduced type of interface, so use the existing capability and extend it to\nGMII as well. We then keep the current logic in the macb_init() function.\n\nThe capabilities of sama5d2, sama5d4 and sama5d3 GEM interface are updated in\nthe macb_config structure to be able to properly enable them with a traditional\ninterface (GMII or MII).\n\nReported-by: Romain HENRIET <romain.henriet@l-acoustics.com>\nSigned-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\n[cyrille.pitchen@atmel.com: backported to 4.4.y]\nSigned-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/779fb6074843a685c241874a5b308fd56cbdb35f"},{"sha":"999e0d18786192faf8240a5048dd1a08cf5d4bd0","author":{"name":"Feng Tang","email":"320c16bf83d224bd756b9e900985944544ab52dd@intel.com"},"message":"net: alx: Work around the DMA RX overflow issue\n\n[ Upstream commit 881d0327db37ad917a367c77aff1afa1ee41e0a9 ]\n\nNote: This is a verified backported patch for stable 4.4 kernel, and it\ncould also be applied to 4.3/4.2/4.1/3.18/3.16\n\nThere is a problem with alx devices, that the network link will be\nlost in 1-5 minutes after the device is up.\n\n>From debugging without datasheet, we found the error always\nhappen when the DMA RX address is set to 0x....fc0, which is very\nlikely to be a HW/silicon problem.\n\nThis patch will apply rx skb with 64 bytes longer space, and if the\nallocated skb has a 0x...fc0 address, it will use skb_resever(skb, 64)\nto advance the address, so that the RX overflow can be avoided.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=70761\nSigned-off-by: Feng Tang <feng.tang@intel.com>\nSuggested-by: Eric Dumazet <edumazet@google.com>\nTested-by: Ole Lukoie <olelukoie@mail.ru>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/999e0d18786192faf8240a5048dd1a08cf5d4bd0"},{"sha":"b30cc5b14fc0981a613969bfa048aa706347d1c3","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf: try harder on clones when writing into skb\n\n[ Upstream commit 3697649ff29e0f647565eed04b27a7779c646a22 ]\n\nWhen we're dealing with clones and the area is not writeable, try\nharder and get a copy via pskb_expand_head(). Replace also other\noccurences in tc actions with the new skb_try_make_writable().\n\nReported-by: Ashhad Sheikh <ashhadsheikh394@gmail.com>\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Alexei Starovoitov <ast@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/pfactum/pf-kernel/commits/b30cc5b14fc0981a613969bfa048aa706347d1c3"},{"sha":"eda89513103abe73ec650256e445c8515bc688b5","author":{"name":"Basil Gunn","email":"4464ab7a1a4c9b7f5d330cc380504397b116c130@pacabunga.com"},"message":"AX.25: Close socket connection on session completion\n\n[ Upstream commit 4a7d99ea1b27734558feb6833f180cd38a159940 ]\n\nA socket connection made in ax.25 is not closed when session is\ncompleted.  The heartbeat timer is stopped prematurely and this is\nwhere the socket gets closed. Allow heatbeat timer to run to close\nsocket. Symptom occurs in kernels >= 4.2.0\n\nOriginally sent 6/15/2016. Resend with distribution list matching\nscripts/maintainer.pl output.\n\nSigned-off-by: Basil Gunn <basil@pacabunga.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/pfactum/pf-kernel/commits/eda89513103abe73ec650256e445c8515bc688b5"},{"sha":"f6d06f1de8b796339a52550976650ab9f991d24c","author":{"name":"Anton Blanchard","email":"ce1a3ad8ea491e2355699b412ffe6d0f9ccbd22e@samba.org"},"message":"crypto: vmx - Increase priority of aes-cbc cipher\n\ncommit 12d3f49e1ffbbf8cbbb60acae5a21103c5c841ac upstream.\n\nAll of the VMX AES ciphers (AES, AES-CBC and AES-CTR) are set at\npriority 1000. Unfortunately this means we never use AES-CBC and\nAES-CTR, because the base AES-CBC cipher that is implemented on\ntop of AES inherits its priority.\n\nTo fix this, AES-CBC and AES-CTR have to be a higher priority. Set\nthem to 2000.\n\nTesting on a POWER8 with:\n\ncryptsetup benchmark --cipher aes --key-size 256\n\nShows decryption speed increase from 402.4 MB/s to 3069.2 MB/s,\nover 7x faster. Thanks to Mike Strosaker for helping me debug\nthis issue.\n\nFixes: 8c755ace357c (\"crypto: vmx - Adding CBC routines for VMX module\")\nSigned-off-by: Anton Blanchard <anton@samba.org>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/f6d06f1de8b796339a52550976650ab9f991d24c"},{"sha":"5ae68873134c30bf83159b6d335b2f996c60346b","author":{"name":"Linus Walleij","email":"b0d9e537b6c72323d8ac72352e58c452d7c4fc88@linaro.org"},"message":"crypto: ux500 - memmove the right size\n\ncommit 19ced623db2fe91604d69f7d86b03144c5107739 upstream.\n\nThe hash buffer is really HASH_BLOCK_SIZE bytes, someone\nmust have thought that memmove takes n*u32 words by mistake.\nTests work as good/bad as before after this patch.\n\nCc: Joakim Bech <joakim.bech@linaro.org>\nReported-by: David Binderman <linuxdev.baldrick@gmail.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/5ae68873134c30bf83159b6d335b2f996c60346b"},{"sha":"ce1abd2563d07c1042a6e156fdbaa73e1e70b75f","author":{"name":"Mathias Krause","email":"c0f5a800b69cdfd927790b9eec175d77c6a1b20d@googlemail.com"},"message":"crypto: user - re-add size check for CRYPTO_MSG_GETALG\n\ncommit 055ddaace03580455a7b7dbea8e93d62acee61fc upstream.\n\nCommit 9aa867e46565 (\"crypto: user - Add CRYPTO_MSG_DELRNG\")\naccidentally removed the minimum size check for CRYPTO_MSG_GETALG\nnetlink messages. This allows userland to send a truncated\nCRYPTO_MSG_GETALG message as short as a netlink header only making\ncrypto_report() operate on uninitialized memory by accessing data\nbeyond the end of the netlink message.\n\nFix this be re-adding the minimum required size of CRYPTO_MSG_GETALG\nmessages to the crypto_msg_min[] array.\n\nFixes: 9aa867e46565 (\"crypto: user - Add CRYPTO_MSG_DELRNG\")\nSigned-off-by: Mathias Krause <minipli@googlemail.com>\nCc: Steffen Klassert <steffen.klassert@secunet.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/ce1abd2563d07c1042a6e156fdbaa73e1e70b75f"},{"sha":"b66baf41d0474bd5c46959767428ec36b43962f0","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"USB: uas: Fix slave queue_depth not being set\n\ncommit 593224ea77b1ca842f45cf76f4deeef44dfbacd1 upstream.\n\nCommit 198de51dbc34 (\"USB: uas: Limit qdepth at the scsi-host level\")\nremoved the scsi_change_queue_depth() call from uas_slave_configure()\nassuming that the slave would inherit the host's queue_depth, which\nthat commit sets to the same value.\n\nThis is incorrect, without the scsi_change_queue_depth() call the slave's\nqueue_depth defaults to 1, introducing a performance regression.\n\nThis commit restores the call, fixing the performance regression.\n\nFixes: 198de51dbc34 (\"USB: uas: Limit qdepth at the scsi-host level\")\nReported-by: Tom Yan <tom.ty89@gmail.com>\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/b66baf41d0474bd5c46959767428ec36b43962f0"},{"sha":"c56eeffc23f389347d47a486c8d7368b15ba8ceb","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"usb: quirks: Fix sorting\n\ncommit 81099f97bd31e25ff2719a435b1860fc3876122f upstream.\n\nProperly sort all the entries by vendor id.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/c56eeffc23f389347d47a486c8d7368b15ba8ceb"},{"sha":"4fe6d4b48d7213f441e119256f245d8903bc8ac5","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"usb: quirks: Add no-lpm quirk for Acer C120 LED Projector\n\ncommit 32cb0b37098f4beeff5ad9e325f11b42a6ede56c upstream.\n\nThe Acer C120 LED Projector is a USB-3 connected pico projector which\ntakes both its power and video data from USB-3.\n\nIn combination with some hubs this device does not play well with\nlpm, so disable lpm for it.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/pfactum/pf-kernel/commits/4fe6d4b48d7213f441e119256f245d8903bc8ac5"}]}
{"actor":{"display_login":"pfactum"}}