{"push_id":730724994,"size":60,"distinct_size":0,"ref":"refs/heads/caf/korg/linux-4.1.y","head":"5cf9896dc5c72a6c68c36140568b755f697f7760","before":"6a010c0abd49388a49af3d5a5bfc00e0d5767607","commits":[{"sha":"9bdbb8968e9e7e6b9619076d1867da1c0cfec2c7","author":{"email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com","name":"Hans de Goede"},"message":"ARM: dts: sunxi: Adjust touchscreen compatible for sun5i and later\n\ncommit 8bf1b9b3d90194a174493febc731f7783f2adf1a upstream.\n\nThe touchscreen controller in the A13 and later has a different temperature\ncurve than the one in the original A10, change the compatible for the A13 and\nlater so that the kernel will use the correct curve.\n\nReported-by: Tong Zhang <lovewilliam@gmail.com>\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/9bdbb8968e9e7e6b9619076d1867da1c0cfec2c7"},{"sha":"9d281572f2be11afa36e1534da43890cb9a130cc","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/Rashed97/caf-kernel-msm-3.10/commits/9d281572f2be11afa36e1534da43890cb9a130cc"},{"sha":"aa0b8c72f5c1e0208bfafb383b535bdc9d3b2c6b","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/Rashed97/caf-kernel-msm-3.10/commits/aa0b8c72f5c1e0208bfafb383b535bdc9d3b2c6b"},{"sha":"1a2cddd17ebe5e76a796c25e11cdd5518310eabc","author":{"email":"06a38fb2ed1a2d0a17f4f06761ac2e5ace5a31ab@hartkopp.net","name":"Oliver Hartkopp"},"message":"can: fix loss of CAN frames in raw_rcv\n\ncommit 36c01245eb8046c16eee6431e7dbfbb302635fa8 upstream.\n\nAs reported by Manfred Schlaegl here\n\n   http://marc.info/?l=linux-netdev&m=143482089824232&w=2\n\ncommit 514ac99c64b \"can: fix multiple delivery of a single CAN frame for\noverlapping CAN filters\" requires the skb->tstamp to be set to check for\nidentical CAN skbs.\n\nAs net timestamping is influenced by several players (netstamp_needed and\nnetdev_tstamp_prequeue) Manfred missed a proper timestamp which leads to\nCAN frame loss.\n\nAs skb timestamping became now mandatory for CAN related skbs this patch\nmakes sure that received CAN skbs always have a proper timestamp set.\nMaybe there's a better solution in the future but this patch fixes the\nCAN frame loss so far.\n\nReported-by: Manfred Schlaegl <manfred.schlaegl@gmx.at>\nSigned-off-by: Oliver Hartkopp <socketcan@hartkopp.net>\nSigned-off-by: Marc Kleine-Budde <mkl@pengutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/1a2cddd17ebe5e76a796c25e11cdd5518310eabc"},{"sha":"bd0a0d20ebd08f250af9023530b5de4bc433ebaa","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/Rashed97/caf-kernel-msm-3.10/commits/bd0a0d20ebd08f250af9023530b5de4bc433ebaa"},{"sha":"08be544ef5d8453b7778bd57f3da8eeebcf1cd65","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/Rashed97/caf-kernel-msm-3.10/commits/08be544ef5d8453b7778bd57f3da8eeebcf1cd65"},{"sha":"d7884e43677ba8618ae2f1ead7b96b215b409e20","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/Rashed97/caf-kernel-msm-3.10/commits/d7884e43677ba8618ae2f1ead7b96b215b409e20"},{"sha":"2c330edb4b31fdf18c6a6c4d1d9b482632c3925b","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/Rashed97/caf-kernel-msm-3.10/commits/2c330edb4b31fdf18c6a6c4d1d9b482632c3925b"},{"sha":"914b0ef228c97dfea025091428f6c7809c9d38ad","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/Rashed97/caf-kernel-msm-3.10/commits/914b0ef228c97dfea025091428f6c7809c9d38ad"},{"sha":"80b856db9f9e1dbaf20a24020f8ade95c14f7477","author":{"email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","name":"Johannes Berg"},"message":"mac80211: fix locking in update_vlan_tailroom_need_count()\n\n[ Upstream commit 51f458d9612177f69c2e2c437034ae15f93078e7 ]\n\nUnfortunately, Michal's change to fix AP_VLAN crypto tailroom\ncaused a locking issue that was reported by lockdep, but only\nin a few cases - the issue was a classic ABBA deadlock caused\nby taking the mtx after the key_mtx, where normally they're\ntaken the other way around.\n\nAs the key mutex protects the field in question (I'm adding a\nfew annotations to make that clear) only the iteration needs\nto be protected, but we can also iterate the interface list\nwith just RCU protection while holding the key mutex.\n\nFixes: f9dca80b98ca (\"mac80211: fix AP_VLAN crypto tailroom calculation\")\nSigned-off-by: Johannes Berg <johannes.berg@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/Rashed97/caf-kernel-msm-3.10/commits/80b856db9f9e1dbaf20a24020f8ade95c14f7477"},{"sha":"1bc31b1e80a716b903cf40ae4d679c820f71d518","author":{"email":"5bdb78a8cad883df1b360eae695997a65cec3099@list.ru","name":"Stas Sergeev"},"message":"mvneta: add forgotten initialization of autonegotiation bits\n\n[ Upstream commit 538761b794c1542f1c6e31eadd9d7aae118889f7 ]\n\nThe commit 898b2970e2c9 (\"mvneta: implement SGMII-based in-band link state\nsignaling\")\nchanged mvneta_adjust_link() so that it does not clear the auto-negotiation\nbits in MVNETA_GMAC_AUTONEG_CONFIG register. This was necessary for\nauto-negotiation mode to work.\nUnfortunately I haven't checked if these bits are ever initialized.\nIt appears they are not.\nThis patch adds the missing initialization of the auto-negotiation bits\nin the MVNETA_GMAC_AUTONEG_CONFIG register.\nIt fixes the following regression:\nhttps://www.mail-archive.com/netdev@vger.kernel.org/msg67928.html\n\nSince the patch was tested to fix a regression, it should be applied to\nstable tree.\n\nTested-by: Arnaud Ebalard <arno@natisbad.org>\n\nCC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\nCC: Florian Fainelli <f.fainelli@gmail.com>\nCC: netdev@vger.kernel.org\nCC: linux-kernel@vger.kernel.org\nCC: stable@vger.kernel.org\n\nSigned-off-by: Stas Sergeev <stsp@users.sourceforge.net>\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/Rashed97/caf-kernel-msm-3.10/commits/1bc31b1e80a716b903cf40ae4d679c820f71d518"},{"sha":"c31967d447989b85b631dda39487a319df21e03a","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/Rashed97/caf-kernel-msm-3.10/commits/c31967d447989b85b631dda39487a319df21e03a"},{"sha":"6fc8b947b364ceb6d91e5b6f3e3d22cd9a013ac0","author":{"email":"7afaca84402052a1e3bc753b1373a08c68f6096c@amazon.de","name":"Palik, Imre"},"message":"xen-netback: fix a BUG() during initialization\n\n[ Upstream commit 12b322ac85208de564ecf23aa754d796a91de21f ]\n\nCommit edafc132baac (\"xen-netback: making the bandwidth limiter runtime settable\")\nintroduced the capability to change the bandwidth rate limit at runtime.\nBut it also introduced a possible crashing bug.\n\nIf netback receives two XenbusStateConnected without getting the\nhotplug-status watch firing in between, then it will try to register the\nwatches for the rate limiter again.  But this triggers a BUG() in the watch\nregistration code.\n\nThe fix modifies connect() to remove the possibly existing packet-rate\nwatches before trying to install those watches.  This behaviour is in line\nwith how connect() deals with the hotplug-status watch.\n\nSigned-off-by: Imre Palik <imrep@amazon.de>\nCc: Matt Wilson <msw@amazon.com>\nAcked-by: Wei Liu <wei.liu2@citrix.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/Rashed97/caf-kernel-msm-3.10/commits/6fc8b947b364ceb6d91e5b6f3e3d22cd9a013ac0"},{"sha":"66634bb1c4f1eda70583eddaf8c5e980f05a8fb9","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/Rashed97/caf-kernel-msm-3.10/commits/66634bb1c4f1eda70583eddaf8c5e980f05a8fb9"},{"sha":"f3f6617f6b90f2e27ee7362f8a2f4063c7eac6a7","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/Rashed97/caf-kernel-msm-3.10/commits/f3f6617f6b90f2e27ee7362f8a2f4063c7eac6a7"},{"sha":"7a9aa8ab0c706b3d2770a3996c9e63f08074c855","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/Rashed97/caf-kernel-msm-3.10/commits/7a9aa8ab0c706b3d2770a3996c9e63f08074c855"},{"sha":"1b74080050336e29a82abc2a9b2e1f901485a362","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/Rashed97/caf-kernel-msm-3.10/commits/1b74080050336e29a82abc2a9b2e1f901485a362"},{"sha":"62a9ad17a245002cc611fc4667c2919ef422d8ee","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/Rashed97/caf-kernel-msm-3.10/commits/62a9ad17a245002cc611fc4667c2919ef422d8ee"},{"sha":"6c10c84170c40bf3d4a9953ae5a2ffe59ad736d4","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/Rashed97/caf-kernel-msm-3.10/commits/6c10c84170c40bf3d4a9953ae5a2ffe59ad736d4"},{"sha":"7e2a3d667c4c9ca494c73f5930365240a31c4eb0","author":{"email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com","name":"Eric Dumazet"},"message":"bnx2x: fix lockdep splat\n\n[ Upstream commit d53c66a5b80698620f7c9ba2372fff4017e987b8 ]\n\nMichel reported following lockdep splat\n\n[   44.718117] INFO: trying to register non-static key.\n[   44.723081] the code is fine but needs lockdep annotation.\n[   44.728559] turning off the locking correctness validator.\n[   44.734036] CPU: 8 PID: 5483 Comm: ethtool Not tainted 4.1.0\n[   44.770289] Call Trace:\n[   44.772741]  [<ffffffff816eb1cd>] dump_stack+0x4c/0x65\n[   44.777879]  [<ffffffff8111d921>] ? console_unlock+0x1f1/0x510\n[   44.783708]  [<ffffffff811121f5>] __lock_acquire+0x1d05/0x1f10\n[   44.789538]  [<ffffffff8111370a>] ? mark_held_locks+0x6a/0x90\n[   44.795276]  [<ffffffff81113835>] ? trace_hardirqs_on_caller+0x105/0x1d0\n[   44.801967]  [<ffffffff8111390d>] ? trace_hardirqs_on+0xd/0x10\n[   44.807793]  [<ffffffff811330fa>] ? hrtimer_try_to_cancel+0x4a/0x250\n[   44.814142]  [<ffffffff81112ba6>] lock_acquire+0xb6/0x290\n[   44.819537]  [<ffffffff810d6675>] ? flush_work+0x5/0x280\n[   44.824844]  [<ffffffff810d66ad>] flush_work+0x3d/0x280\n[   44.830061]  [<ffffffff810d6675>] ? flush_work+0x5/0x280\n[   44.835366]  [<ffffffff816f3c43>] ? schedule_hrtimeout_range+0x13/0x20\n[   44.841889]  [<ffffffff8112ec9b>] ? usleep_range+0x4b/0x50\n[   44.847365]  [<ffffffff8111370a>] ? mark_held_locks+0x6a/0x90\n[   44.853102]  [<ffffffff810d8585>] ? __cancel_work_timer+0x105/0x1c0\n[   44.859359]  [<ffffffff81113835>] ? trace_hardirqs_on_caller+0x105/0x1d0\n[   44.866045]  [<ffffffff810d851f>] __cancel_work_timer+0x9f/0x1c0\n[   44.872048]  [<ffffffffa0010982>] ? bnx2x_func_stop+0x42/0x90 [bnx2x]\n[   44.878481]  [<ffffffff810d8670>] cancel_work_sync+0x10/0x20\n[   44.884134]  [<ffffffffa00259e5>] bnx2x_chip_cleanup+0x245/0x730 [bnx2x]\n[   44.890829]  [<ffffffff8110ce02>] ? up+0x32/0x50\n[   44.895439]  [<ffffffff811306b5>] ? del_timer_sync+0x5/0xd0\n[   44.901005]  [<ffffffffa005596d>] bnx2x_nic_unload+0x20d/0x8e0 [bnx2x]\n[   44.907527]  [<ffffffff811f1aef>] ? might_fault+0x5f/0xb0\n[   44.912921]  [<ffffffffa005851c>] bnx2x_reload_if_running+0x2c/0x50 [bnx2x]\n[   44.919879]  [<ffffffffa005a3c5>] bnx2x_set_ringparam+0x2b5/0x460 [bnx2x]\n[   44.926664]  [<ffffffff815d498b>] dev_ethtool+0x55b/0x1c40\n[   44.932148]  [<ffffffff815dfdc7>] ? rtnl_lock+0x17/0x20\n[   44.937364]  [<ffffffff815e7f8b>] dev_ioctl+0x17b/0x630\n[   44.942582]  [<ffffffff815abf8d>] sock_do_ioctl+0x5d/0x70\n[   44.947972]  [<ffffffff815ac013>] sock_ioctl+0x73/0x280\n[   44.953192]  [<ffffffff8124c1c8>] do_vfs_ioctl+0x88/0x5b0\n[   44.958587]  [<ffffffff8110d0b3>] ? up_read+0x23/0x40\n[   44.963631]  [<ffffffff812584cc>] ? __fget_light+0x6c/0xa0\n[   44.969105]  [<ffffffff8124c781>] SyS_ioctl+0x91/0xb0\n[   44.974149]  [<ffffffff816f4dd7>] system_call_fastpath+0x12/0x6f\n\nAs bnx2x_init_ptp() is only called if bp->flags contains PTP_SUPPORTED,\nwe also need to guard bnx2x_stop_ptp() with same condition, otherwise\nptp_task workqueue is not initialized and kernel barfs on\ncancel_work_sync()\n\nFixes: eeed018cbfa30 (\"bnx2x: Add timestamping and PTP hardware clock support\")\nReported-by: Michel Lespinasse <walken@google.com>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: Michal Kalderon <Michal.Kalderon@qlogic.com>\nCc: Ariel Elior <Ariel.Elior@qlogic.com>\nCc: Yuval Mintz <Yuval.Mintz@qlogic.com>\nCc: David Decotigny <decot@google.com>\nAcked-by: Sony Chacko <sony.chacko@qlogic.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/Rashed97/caf-kernel-msm-3.10/commits/7e2a3d667c4c9ca494c73f5930365240a31c4eb0"}]}