{"push_id":722889938,"size":60,"distinct_size":0,"ref":"refs/heads/grsec-4.0","head":"12a795b8de41068c8614ef5e51cee18b66412252","before":"7872d2c5b23bdc440850a4e36c098424f22e3158","commits":[{"sha":"7e1f3f490900b479f88bf38be7317f98ed754369","author":{"email":"da3a51b335cef0eb0e2c329c5ef6bcd6acef687a@oracle.com","name":"Konrad Rzeszutek Wilk"},"message":"config: Enable NEED_DMA_MAP_STATE by default when SWIOTLB is selected\n\ncommit a6dfa128ce5c414ab46b1d690f7a1b8decb8526d upstream.\n\nA huge amount of NIC drivers use the DMA API, however if\ncompiled under 32-bit an very important part of the DMA API can\nbe ommitted leading to the drivers not working at all\n(especially if used with 'swiotlb=force iommu=soft').\n\nAs Prashant Sreedharan explains it: \"the driver [tg3] uses\nDEFINE_DMA_UNMAP_ADDR(), dma_unmap_addr_set() to keep a copy of\nthe dma \"mapping\" and dma_unmap_addr() to get the \"mapping\"\nvalue. On most of the platforms this is a no-op, but ... with\n\"iommu=soft and swiotlb=force\" this house keeping is required,\n... otherwise we pass 0 while calling pci_unmap_/pci_dma_sync_\ninstead of the DMA address.\"\n\nAs such enable this even when using 32-bit kernels.\n\nReported-by: Ian Jackson <Ian.Jackson@eu.citrix.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nAcked-by: David S. Miller <davem@davemloft.net>\nAcked-by: Prashant Sreedharan <prashant@broadcom.com>\nCc: Borislav Petkov <bp@alien8.de>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Michael Chan <mchan@broadcom.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: boris.ostrovsky@oracle.com\nCc: cascardo@linux.vnet.ibm.com\nCc: david.vrabel@citrix.com\nCc: sanjeevb@broadcom.com\nCc: siva.kallam@broadcom.com\nCc: vyasevich@gmail.com\nCc: xen-devel@lists.xensource.com\nLink: http://lkml.kernel.org/r/20150417190448.GA9462@l.oracle.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nCc: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/7e1f3f490900b479f88bf38be7317f98ed754369"},{"sha":"14ff2e37d00e3de44983826b49ea8d52c77e5f47","author":{"email":"3a4d625ce225e891399f98db96a382ac4a84080b@trash.net","name":"Patrick McHardy"},"message":"netfilter: nft_rbtree: fix locking\n\ncommit 16c45eda96038aae848b6cfd42e2bf4b5e80f365 upstream.\n\nFix a race condition and unnecessary locking:\n\n* the root rb_node must only be accessed under the lock in nft_rbtree_lookup()\n* the lock is not needed in lookup functions in netlink context\n\nSigned-off-by: Patrick McHardy <kaber@trash.net>\nSigned-off-by: Pablo Neira Ayuso <pablo@netfilter.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/14ff2e37d00e3de44983826b49ea8d52c77e5f47"},{"sha":"8d0ecc1067d80ede2798259b38b937c7185af738","author":{"email":"df6bdf20a159eda54db82d97e15e3f2b8626ef27@armadeus.com","name":"Sebastien Szymanski"},"message":"ARM: clk-imx6q: refine sata's parent\n\ncommit da946aeaeadcd24ff0cda9984c6fb8ed2bfd462a upstream.\n\nAccording to IMX6D/Q RM, table 18-3, sata clock's parent is ahb, not ipg.\n\nSigned-off-by: Sebastien Szymanski <sebastien.szymanski@armadeus.com>\nReviewed-by: Fabio Estevam <fabio.estevam@freescale.com>\nSigned-off-by: Shawn Guo <shawn.guo@linaro.org>\n[dirk.behme: Adjust moved file]\nSigned-off-by: Dirk Behme <dirk.behme@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/8d0ecc1067d80ede2798259b38b937c7185af738"},{"sha":"933c41149c32b722d0ae48206bdd150d2be40591","author":{"email":"48f3f89ac3fac5337b47faa8a2f93eb8b298844e@redhat.com","name":"Bandan Das"},"message":"KVM: nSVM: Check for NRIPS support before updating control field\n\ncommit f104765b4f81fd74d69e0eb161e89096deade2db upstream.\n\nIf hardware doesn't support DecodeAssist - a feature that provides\nmore information about the intercept in the VMCB, KVM decodes the\ninstruction and then updates the next_rip vmcb control field.\nHowever, NRIP support itself depends on cpuid Fn8000_000A_EDX[NRIPS].\nSince skip_emulated_instruction() doesn't verify nrip support\nbefore accepting control.next_rip as valid, avoid writing this\nfield if support isn't present.\n\nSigned-off-by: Bandan Das <bsd@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/933c41149c32b722d0ae48206bdd150d2be40591"},{"sha":"34fb78dc42350e12645436a2e5f93b23a05b3b8a","author":{"email":"1a53202f7826b15a582486d4ea9c371e05720251@oracle.com","name":"Sowmini Varadhan"},"message":"sparc: Use GFP_ATOMIC in ldc_alloc_exp_dring() as it can be called in softirq context\n\nUpstream commit 671d773297969bebb1732e1cdc1ec03aa53c6be2\n\nSince it is possible for vnet_event_napi to end up doing\nvnet_control_pkt_engine -> ... -> vnet_send_attr ->\nvnet_port_alloc_tx_ring -> ldc_alloc_exp_dring -> kzalloc()\n(i.e., in softirq context), kzalloc() should be called with\nGFP_ATOMIC from ldc_alloc_exp_dring.\n\nSigned-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/34fb78dc42350e12645436a2e5f93b23a05b3b8a"},{"sha":"d0031aa36070aadb5cfb492d629a81e833e32bbd","author":{"email":"966b74740c67c4df944e25f0a65bfdba363503f7@blackwall.org","name":"Nikolay Aleksandrov"},"message":"bridge: fix multicast router rlist endless loop\n\n[ Upstream commit 1a040eaca1a22f8da8285ceda6b5e4a2cb704867 ]\n\nSince the addition of sysfs multicast router support if one set\nmulticast_router to \"2\" more than once, then the port would be added to\nthe hlist every time and could end up linking to itself and thus causing an\nendless loop for rlist walkers.\nSo to reproduce just do:\necho 2 > multicast_router; echo 2 > multicast_router;\nin a bridge port and let some igmp traffic flow, for me it hangs up\nin br_multicast_flood().\nFix this by adding a check in br_multicast_add_router() if the port is\nalready linked.\nThe reason this didn't happen before the addition of multicast_router\nsysfs entries is because there's a !hlist_unhashed check that prevents\nit.\n\nSigned-off-by: Nikolay Aleksandrov <razor@blackwall.org>\nFixes: 0909e11758bd (\"bridge: Add multicast_router sysfs entries\")\nAcked-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/d0031aa36070aadb5cfb492d629a81e833e32bbd"},{"sha":"81dd711eddff5f6dbe5e10f55c946cf5834f075f","author":{"email":"e27030aebe9cad8817d34b8c31dbaf301fb798b9@gmail.com","name":"Richard Cochran"},"message":"net: igb: fix the start time for periodic output signals\n\n[ Upstream commit 58c98be137830d34b79024cc5dc95ef54fcd7ffe ]\n\nWhen programming the start of a periodic output, the code wrongly places\nthe seconds value into the \"low\" register and the nanoseconds into the\n\"high\" register.  Even though this is backwards, it slipped through my\ntesting, because the re-arming code in the interrupt service routine is\ncorrect, and the signal does appear starting with the second edge.\n\nThis patch fixes the issue by programming the registers correctly.\n\nSigned-off-by: Richard Cochran <richardcochran@gmail.com>\nReviewed-by: Jacob Keller <jacob.e.keller@intel.com>\nAcked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/81dd711eddff5f6dbe5e10f55c946cf5834f075f"},{"sha":"8c58ea8cb458d57e94655d0ddbeb462864b744fc","author":{"email":"c0c0c8857ed6ec93282de3ee9d47e224acf995af@fb.com","name":"Shaohua Li"},"message":"net: don't wait for order-3 page allocation\n\n[ Upstream commit fb05e7a89f500cfc06ae277bdc911b281928995d ]\n\nWe saw excessive direct memory compaction triggered by skb_page_frag_refill.\nThis causes performance issues and add latency. Commit 5640f7685831e0\nintroduces the order-3 allocation. According to the changelog, the order-3\nallocation isn't a must-have but to improve performance. But direct memory\ncompaction has high overhead. The benefit of order-3 allocation can't\ncompensate the overhead of direct memory compaction.\n\nThis patch makes the order-3 page allocation atomic. If there is no memory\npressure and memory isn't fragmented, the alloction will still success, so we\ndon't sacrifice the order-3 benefit here. If the atomic allocation fails,\ndirect memory compaction will not be triggered, skb_page_frag_refill will\nfallback to order-0 immediately, hence the direct memory compaction overhead is\navoided. In the allocation failure case, kswapd is waken up and doing\ncompaction, so chances are allocation could success next time.\n\nalloc_skb_with_frags is the same.\n\nThe mellanox driver does similar thing, if this is accepted, we must fix\nthe driver too.\n\nV3: fix the same issue in alloc_skb_with_frags as pointed out by Eric\nV2: make the changelog clearer\n\nCc: Eric Dumazet <edumazet@google.com>\nCc: Chris Mason <clm@fb.com>\nCc: Debabrata Banerjee <dbavatar@gmail.com>\nSigned-off-by: Shaohua Li <shli@fb.com>\nAcked-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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/8c58ea8cb458d57e94655d0ddbeb462864b744fc"},{"sha":"1f70e491e8287b345e9859486aeb7cca2885ff2a","author":{"email":"7fc7fc98bf391a9b9f95a773bac29e7d60cc65b5@gmail.com","name":"Marcelo Ricardo Leitner"},"message":"sctp: fix ASCONF list handling\n\n[ Upstream commit 2d45a02d0166caf2627fe91897c6ffc3b19514c4 ]\n\n->auto_asconf_splist is per namespace and mangled by functions like\nsctp_setsockopt_auto_asconf() which doesn't guarantee any serialization.\n\nAlso, the call to inet_sk_copy_descendant() was backuping\n->auto_asconf_list through the copy but was not honoring\n->do_auto_asconf, which could lead to list corruption if it was\ndifferent between both sockets.\n\nThis commit thus fixes the list handling by using ->addr_wq_lock\nspinlock to protect the list. A special handling is done upon socket\ncreation and destruction for that. Error handlig on sctp_init_sock()\nwill never return an error after having initialized asconf, so\nsctp_destroy_sock() can be called without addrq_wq_lock. The lock now\nwill be take on sctp_close_sock(), before locking the socket, so we\ndon't do it in inverse order compared to sctp_addr_wq_timeout_handler().\n\nInstead of taking the lock on sctp_sock_migrate() for copying and\nrestoring the list values, it's preferred to avoid rewritting it by\nimplementing sctp_copy_descendant().\n\nIssue was found with a test application that kept flipping sysctl\ndefault_auto_asconf on and off, but one could trigger it by issuing\nsimultaneous setsockopt() calls on multiple sockets or by\ncreating/destroying sockets fast enough. This is only triggerable\nlocally.\n\nFixes: 9f7d653b67ae (\"sctp: Add Auto-ASCONF support (core).\")\nReported-by: Ji Jianwen <jiji@redhat.com>\nSuggested-by: Neil Horman <nhorman@tuxdriver.com>\nSuggested-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nSigned-off-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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/1f70e491e8287b345e9859486aeb7cca2885ff2a"},{"sha":"4ab5e4c2b831ae15c92efa17c10ff1544ff25af0","author":{"email":"966b74740c67c4df944e25f0a65bfdba363503f7@blackwall.org","name":"Nikolay Aleksandrov"},"message":"bridge: fix br_stp_set_bridge_priority race conditions\n\n[ Upstream commit 2dab80a8b486f02222a69daca6859519e05781d9 ]\n\nAfter the ->set() spinlocks were removed br_stp_set_bridge_priority\nwas left running without any protection when used via sysfs. It can\nrace with port add/del and could result in use-after-free cases and\ncorrupted lists. Tested by running port add/del in a loop with stp\nenabled while setting priority in a loop, crashes are easily\nreproducible.\nThe spinlocks around sysfs ->set() were removed in commit:\n14f98f258f19 (\"bridge: range check STP parameters\")\nThere's also a race condition in the netlink priority support that is\nfixed by this change, but it was introduced recently and the fixes tag\ncovers it, just in case it's needed the commit is:\naf615762e972 (\"bridge: add ageing_time, stp_state, priority over netlink\")\n\nSigned-off-by: Nikolay Aleksandrov <razor@blackwall.org>\nFixes: 14f98f258f19 (\"bridge: range check STP parameters\")\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/4ab5e4c2b831ae15c92efa17c10ff1544ff25af0"},{"sha":"2163a99fd06efb376c86a108cb610086bc51e332","author":{"email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com","name":"Eric Dumazet"},"message":"packet: read num_members once in packet_rcv_fanout()\n\n[ Upstream commit f98f4514d07871da7a113dd9e3e330743fd70ae4 ]\n\nWe need to tell compiler it must not read f->num_members multiple\ntimes. Otherwise testing if num is not zero is flaky, and we could\nattempt an invalid divide by 0 in fanout_demux_cpu()\n\nNote bug was present in packet_rcv_fanout_hash() and\npacket_rcv_fanout_lb() but final 3.1 had a simple location\nafter commit 95ec3eb417115fb (\"packet: Add 'cpu' fanout policy.\")\n\nFixes: dc99f600698dc (\"packet: Add fanout support.\")\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: 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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/2163a99fd06efb376c86a108cb610086bc51e332"},{"sha":"d68fec2ac4339ea7d5bd56139f12f4c0e200c7fa","author":{"email":"1ee125182537a91f90180f97fc3b3cb011bdf78a@google.com","name":"Willem de Bruijn"},"message":"packet: avoid out of bounds read in round robin fanout\n\n[ Upstream commit 468479e6043c84f5a65299cc07cb08a22a28c2b1 ]\n\nPACKET_FANOUT_LB computes f->rr_cur such that it is modulo\nf->num_members. It returns the old value unconditionally, but\nf->num_members may have changed since the last store. Ensure\nthat the return value is always < num.\n\nWhen modifying the logic, simplify it further by replacing the loop\nwith an unconditional atomic increment.\n\nFixes: dc99f600698d (\"packet: Add fanout support.\")\nSuggested-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: Willem de Bruijn <willemb@google.com>\nAcked-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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/d68fec2ac4339ea7d5bd56139f12f4c0e200c7fa"},{"sha":"3126c3a665a5a0c99dec474d3429813ac3b18cf6","author":{"email":"84572ef2253ef81e2d8cd8c65849f4d9a3881f47@ssi.bg","name":"Julian Anastasov"},"message":"neigh: do not modify unlinked entries\n\n[ Upstream commit 2c51a97f76d20ebf1f50fef908b986cb051fdff9 ]\n\nThe lockless lookups can return entry that is unlinked.\nSometimes they get reference before last neigh_cleanup_and_release,\nsometimes they do not need reference. Later, any\nmodification attempts may result in the following problems:\n\n1. entry is not destroyed immediately because neigh_update\ncan start the timer for dead entry, eg. on change to NUD_REACHABLE\nstate. As result, entry lives for some time but is invisible\nand out of control.\n\n2. __neigh_event_send can run in parallel with neigh_destroy\nwhile refcnt=0 but if timer is started and expired refcnt can\nreach 0 for second time leading to second neigh_destroy and\npossible crash.\n\nThanks to Eric Dumazet and Ying Xue for their work and analyze\non the __neigh_event_send change.\n\nFixes: 767e97e1e0db (\"neigh: RCU conversion of struct neighbour\")\nFixes: a263b3093641 (\"ipv4: Make neigh lookups directly in output packet path.\")\nFixes: 6fd6ce2056de (\"ipv6: Do not depend on rt->n in ip6_finish_output2().\")\nCc: Eric Dumazet <eric.dumazet@gmail.com>\nCc: Ying Xue <ying.xue@windriver.com>\nSigned-off-by: Julian Anastasov <ja@ssi.bg>\nAcked-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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/3126c3a665a5a0c99dec474d3429813ac3b18cf6"},{"sha":"bb5dc87a95f3c4a2874238bfe64d0d1e474cf8d3","author":{"email":"76034b3b6d3b031435cc9968b738d3b7190d594f@apple.com","name":"Christoph Paasch"},"message":"tcp: Do not call tcp_fastopen_reset_cipher from interrupt context\n\n[ Upstream commit dfea2aa654243f70dc53b8648d0bbdeec55a7df1 ]\n\ntcp_fastopen_reset_cipher really cannot be called from interrupt\ncontext. It allocates the tcp_fastopen_context with GFP_KERNEL and\ncalls crypto_alloc_cipher, which allocates all kind of stuff with\nGFP_KERNEL.\n\nThus, we might sleep when the key-generation is triggered by an\nincoming TFO cookie-request which would then happen in interrupt-\ncontext, as shown by enabling CONFIG_DEBUG_ATOMIC_SLEEP:\n\n[   36.001813] BUG: sleeping function called from invalid context at mm/slub.c:1266\n[   36.003624] in_atomic(): 1, irqs_disabled(): 0, pid: 1016, name: packetdrill\n[   36.004859] CPU: 1 PID: 1016 Comm: packetdrill Not tainted 4.1.0-rc7 #14\n[   36.006085] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5-0-ge51488c-20140602_164612-nilsson.home.kraxel.org 04/01/2014\n[   36.008250]  00000000000004f2 ffff88007f8838a8 ffffffff8171d53a ffff880075a084a8\n[   36.009630]  ffff880075a08000 ffff88007f8838c8 ffffffff810967d3 ffff88007f883928\n[   36.011076]  0000000000000000 ffff88007f8838f8 ffffffff81096892 ffff88007f89be00\n[   36.012494] Call Trace:\n[   36.012953]  <IRQ>  [<ffffffff8171d53a>] dump_stack+0x4f/0x6d\n[   36.014085]  [<ffffffff810967d3>] ___might_sleep+0x103/0x170\n[   36.015117]  [<ffffffff81096892>] __might_sleep+0x52/0x90\n[   36.016117]  [<ffffffff8118e887>] kmem_cache_alloc_trace+0x47/0x190\n[   36.017266]  [<ffffffff81680d82>] ? tcp_fastopen_reset_cipher+0x42/0x130\n[   36.018485]  [<ffffffff81680d82>] tcp_fastopen_reset_cipher+0x42/0x130\n[   36.019679]  [<ffffffff81680f01>] tcp_fastopen_init_key_once+0x61/0x70\n[   36.020884]  [<ffffffff81680f2c>] __tcp_fastopen_cookie_gen+0x1c/0x60\n[   36.022058]  [<ffffffff816814ff>] tcp_try_fastopen+0x58f/0x730\n[   36.023118]  [<ffffffff81671788>] tcp_conn_request+0x3e8/0x7b0\n[   36.024185]  [<ffffffff810e3872>] ? __module_text_address+0x12/0x60\n[   36.025327]  [<ffffffff8167b2e1>] tcp_v4_conn_request+0x51/0x60\n[   36.026410]  [<ffffffff816727e0>] tcp_rcv_state_process+0x190/0xda0\n[   36.027556]  [<ffffffff81661f97>] ? __inet_lookup_established+0x47/0x170\n[   36.028784]  [<ffffffff8167c2ad>] tcp_v4_do_rcv+0x16d/0x3d0\n[   36.029832]  [<ffffffff812e6806>] ? security_sock_rcv_skb+0x16/0x20\n[   36.030936]  [<ffffffff8167cc8a>] tcp_v4_rcv+0x77a/0x7b0\n[   36.031875]  [<ffffffff816af8c3>] ? iptable_filter_hook+0x33/0x70\n[   36.032953]  [<ffffffff81657d22>] ip_local_deliver_finish+0x92/0x1f0\n[   36.034065]  [<ffffffff81657f1a>] ip_local_deliver+0x9a/0xb0\n[   36.035069]  [<ffffffff81657c90>] ? ip_rcv+0x3d0/0x3d0\n[   36.035963]  [<ffffffff81657569>] ip_rcv_finish+0x119/0x330\n[   36.036950]  [<ffffffff81657ba7>] ip_rcv+0x2e7/0x3d0\n[   36.037847]  [<ffffffff81610652>] __netif_receive_skb_core+0x552/0x930\n[   36.038994]  [<ffffffff81610a57>] __netif_receive_skb+0x27/0x70\n[   36.040033]  [<ffffffff81610b72>] process_backlog+0xd2/0x1f0\n[   36.041025]  [<ffffffff81611482>] net_rx_action+0x122/0x310\n[   36.042007]  [<ffffffff81076743>] __do_softirq+0x103/0x2f0\n[   36.042978]  [<ffffffff81723e3c>] do_softirq_own_stack+0x1c/0x30\n\nThis patch moves the call to tcp_fastopen_init_key_once to the places\nwhere a listener socket creates its TFO-state, which always happens in\nuser-context (either from the setsockopt, or implicitly during the\nlisten()-call)\n\nCc: Eric Dumazet <eric.dumazet@gmail.com>\nCc: Hannes Frederic Sowa <hannes@stressinduktion.org>\nFixes: 222e83d2e0ae (\"tcp: switch tcp_fastopen key generation to net_get_random_once\")\nSigned-off-by: Christoph Paasch <cpaasch@apple.com>\nAcked-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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/bb5dc87a95f3c4a2874238bfe64d0d1e474cf8d3"},{"sha":"12f8020c4e75057d0aa648ba7d8702ab447fa78b","author":{"email":"84572ef2253ef81e2d8cd8c65849f4d9a3881f47@ssi.bg","name":"Julian Anastasov"},"message":"ip: report the original address of ICMP messages\n\n[ Upstream commit 34b99df4e6256ddafb663c6de0711dceceddfe0e ]\n\nICMP messages can trigger ICMP and local errors. In this case\nserr->port is 0 and starting from Linux 4.0 we do not return\nthe original target address to the error queue readers.\nAdd function to define which errors provide addr_offset.\nWith this fix my ping command is not silent anymore.\n\nFixes: c247f0534cc5 (\"ip: fix error queue empty skb handling\")\nSigned-off-by: Julian Anastasov <ja@ssi.bg>\nAcked-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":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/12f8020c4e75057d0aa648ba7d8702ab447fa78b"},{"sha":"36ff50393e0434727794af730128df4ed1694e72","author":{"email":"e758e9d459928adc5685f935ae8d8ff9fe60a5ba@mellanox.com","name":"Eran Ben Elisha"},"message":"net/mlx4_en: Release TX QP when destroying TX ring\n\n[ Upstream commit 0eb08514fdbdcd16fd6870680cd638f203662e9d ]\n\nTX ring QP wasn't released at mlx4_en_destroy_tx_ring. Instead, the code\nused the deprecated base_tx_qpn field. Move TX QP release to\nmlx4_en_destroy_tx_ring and remove the base_tx_qpn field.\n\nFixes: ddae0349fdb7 ('net/mlx4: Change QP allocation scheme')\nSigned-off-by: Eran Ben Elisha <eranbe@mellanox.com>\nSigned-off-by: Or Gerlitz <ogerlitz@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/36ff50393e0434727794af730128df4ed1694e72"},{"sha":"9c6dc1096617880c9ef6f3b45e3d9d3309f4cd37","author":{"email":"c55d109aa4fa626d00b3c6a0adc354c70612f8d6@mellanox.com","name":"Ido Shamay"},"message":"net/mlx4_en: Wake TX queues only when there's enough room\n\n[ Upstream commit 488a9b48e398b157703766e2cd91ea45ac6997c5 ]\n\nIndication of a single completed packet, marked by txbbs_skipped\nbeing bigger then zero, in not enough in order to wake up a\nstopped TX queue. The completed packet may contain a single TXBB,\nwhile next packet to be sent (after the wake up) may have multiple\nTXBBs (LSO/TSO packets for example), causing overflow in queue followed\nby WQE corruption and TX queue timeout.\nInstead, wake the stopped queue only when there's enough room for the\nworst case (maximum sized WQE) packet that we should need to handle after\nthe queue is opened again.\n\nAlso created an helper routine - mlx4_en_is_tx_ring_full, which checks\nif the current TX ring is full or not. It provides better code readability\nand removes code duplication.\n\nSigned-off-by: Ido Shamay <idos@mellanox.com>\nSigned-off-by: Or Gerlitz <ogerlitz@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/9c6dc1096617880c9ef6f3b45e3d9d3309f4cd37"},{"sha":"f8975e1fd5aef2b07b8b016ce2b1c19b078ac7d8","author":{"email":"c55d109aa4fa626d00b3c6a0adc354c70612f8d6@mellanox.com","name":"Ido Shamay"},"message":"net/mlx4_en: Fix wrong csum complete report when rxvlan offload is disabled\n\n[ Upstream commit 79a258526ce1051cb9684018c25a89d51ac21be8 ]\n\nThe check_csum() function relied on hwtstamp_rx_filter to know if rxvlan\noffload is disabled. This is wrong since rxvlan offload can be switched\non/off regardless of hwtstamp_rx_filter.\n\nAlso moved check_csum to query CQE information to identify VLAN packets\nand removed the check of IP packets, since it has been validated before.\n\nFixes: f8c6455bb04b ('net/mlx4_en: Extend checksum offloading by CHECKSUM COMPLETE')\nSigned-off-by: Ido Shamay <idos@mellanox.com>\nSigned-off-by: Or Gerlitz <ogerlitz@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/f8975e1fd5aef2b07b8b016ce2b1c19b078ac7d8"},{"sha":"a821d6db7447bf3d878f6718381e954f9b4d80d7","author":{"email":"de1b678a59344538ef9f2ddb34a5f9486544e2f9@mellanox.com","name":"Or Gerlitz"},"message":"mlx4: Disable HA for SRIOV PF RoCE devices\n\n[ Upstream commit 7254acffeeec3c0a75b9c5364c29a6eb00014930 ]\n\nWhen in HA mode, the driver exposes an IB (RoCE) device instance with only\none port. Under SRIOV, the existing implementation doesn't go well with\nthe PF RoCE driver's role of Special QPs Para-Virtualization, etc.\n\nAs such, disable HA for the mlx4 PF RoCE device in SRIOV mode.\n\nFixes: a57500903093 ('IB/mlx4: Add port aggregation support')\nSigned-off-by: Or Gerlitz <ogerlitz@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/a821d6db7447bf3d878f6718381e954f9b4d80d7"},{"sha":"a3040359e1c3a20d2eefb5d364faf616fdcd6ce7","author":{"email":"c5344daf2e7bda9dbffd8e6718db2d989f7f4819@ti.com","name":"Mugunthan V N"},"message":"net: phy: fix phy link up when limiting speed via device tree\n\n[ Upstream commit eb686231fce3770299760f24fdcf5ad041f44153 ]\n\nWhen limiting phy link speed using \"max-speed\" to 100mbps or less on a\ngiga bit phy, phy never completes auto negotiation and phy state\nmachine is held in PHY_AN. Fixing this issue by comparing the giga\nbit advertise though phydev->supported doesn't have it but phy has\nBMSR_ESTATEN set. So that auto negotiation is restarted as old and\nnew advertise are different and link comes up fine.\n\nSigned-off-by: Mugunthan V N <mugunthanvnm@ti.com>\nReviewed-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/a3040359e1c3a20d2eefb5d364faf616fdcd6ce7"}]}