{"push_id":2213487065,"size":87,"distinct_size":87,"ref":"refs/heads/master","head":"ead68f216110170ec729e2c4dec0aad6d38259d7","before":"9035a8961b504d0997369509ab8c6b1f0a4ee33d","commits":[{"sha":"4564b187c16327045d87596e8980c65ba7b84c50","author":{"name":"Johannes Berg","email":"9a5936d824e6835dfe162c5611d10d2cf40ffbad@intel.com"},"message":"nl80211: fix nl80211_send_iface() error paths\n\nEvidently I introduced a locking bug in my change here,\nthe nla_put_failure sometimes needs to unlock. Fix it.\n\nFixes: 44905265bc15 (\"nl80211: don't expose wdev->ssid for most interfaces\")\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/4564b187c16327045d87596e8980c65ba7b84c50"},{"sha":"2d17d8d79e77ff3f1b35b87522fc72fa562260ff","author":{"name":"Song Liu","email":"b0209c83577ead4b29882bad91acf99b724edf59@fb.com"},"message":"xdp: linearize skb in netif_receive_generic_xdp()\n\nIn netif_receive_generic_xdp(), it is necessary to linearize all\nnonlinear skb. However, in current implementation, skb with\ntroom <= 0 are not linearized. This patch fixes this by calling\nskb_linearize() for all nonlinear skb.\n\nFixes: de8f3a83b0a0 (\"bpf: add meta pointer for direct access\")\nSigned-off-by: Song Liu <songliubraving@fb.com>\nAcked-by: Martin KaFai Lau <kafai@fb.com>\nCc: Daniel Borkmann <daniel@iogearbox.net>\nCc: Alexei Starovoitov <ast@kernel.org>\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/2d17d8d79e77ff3f1b35b87522fc72fa562260ff"},{"sha":"6d59b7dbf72ed20d0138e2f9b75ca3d4a9d4faca","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf, s390x: do not reload skb pointers in non-skb context\n\nThe assumption of unconditionally reloading skb pointers on\nBPF helper calls where bpf_helper_changes_pkt_data() holds\ntrue is wrong. There can be different contexts where the\nBPF helper would enforce a reload such as in case of XDP.\nHere, we do have a struct xdp_buff instead of struct sk_buff\nas context, thus this will access garbage.\n\nJITs only ever need to deal with cached skb pointer reload\nwhen ld_abs/ind was seen, therefore guard the reload behind\nSEEN_SKB only. Tested on s390x.\n\nFixes: 9db7f2b81880 (\"s390/bpf: recache skb->data/hlen for skb_vlan_push/pop\")\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\nCc: Michael Holzheu <holzheu@linux.vnet.ibm.com>\nSigned-off-by: Alexei Starovoitov <ast@kernel.org>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/6d59b7dbf72ed20d0138e2f9b75ca3d4a9d4faca"},{"sha":"87338c8e2cbb317b5f757e6172f94e2e3799cd20","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf, ppc64: do not reload skb pointers in non-skb context\n\nThe assumption of unconditionally reloading skb pointers on\nBPF helper calls where bpf_helper_changes_pkt_data() holds\ntrue is wrong. There can be different contexts where the helper\nwould enforce a reload such as in case of XDP. Here, we do\nhave a struct xdp_buff instead of struct sk_buff as context,\nthus this will access garbage.\n\nJITs only ever need to deal with cached skb pointer reload\nwhen ld_abs/ind was seen, therefore guard the reload behind\nSEEN_SKB.\n\nFixes: 156d0e290e96 (\"powerpc/ebpf/jit: Implement JIT compiler for extended BPF\")\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nReviewed-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\nTested-by: Sandipan Das <sandipan@linux.vnet.ibm.com>\nSigned-off-by: Alexei Starovoitov <ast@kernel.org>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/87338c8e2cbb317b5f757e6172f94e2e3799cd20"},{"sha":"04514d13222f2c4c91adf0ecb21004cec3388795","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf: guarantee r1 to be ctx in case of bpf_helper_changes_pkt_data\n\nSome JITs don't cache skb context on stack in prologue, so when\nLD_ABS/IND is used and helper calls yield bpf_helper_changes_pkt_data()\nas true, then they temporarily save/restore skb pointer. However,\nthe assumption that skb always has to be in r1 is a bit of a\ngamble. Right now it turned out to be true for all helpers listed\nin bpf_helper_changes_pkt_data(), but lets enforce that from verifier\nside, so that we make this a guarantee and bail out if the func\nproto is misconfigured in future helpers.\n\nIn case of BPF helper calls from cBPF, bpf_helper_changes_pkt_data()\nis completely unrelevant here (since cBPF is context read-only) and\ntherefore always false.\n\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\nSigned-off-by: Alexei Starovoitov <ast@kernel.org>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/04514d13222f2c4c91adf0ecb21004cec3388795"},{"sha":"07aee94394547721ac168cbf4e1c09c14a5fe671","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf, sparc: fix usage of wrong reg for load_skb_regs after call\n\nWhen LD_ABS/IND is used in the program, and we have a BPF helper\ncall that changes packet data (bpf_helper_changes_pkt_data() returns\ntrue), then in case of sparc JIT, we try to reload cached skb data\nfrom bpf2sparc[BPF_REG_6]. However, there is no such guarantee or\nassumption that skb sits in R6 at this point, all helpers changing\nskb data only have a guarantee that skb sits in R1. Therefore,\nstore BPF R1 in L7 temporarily and after procedure call use L7 to\nreload cached skb data. skb sitting in R6 is only true at the time\nwhen LD_ABS/IND is executed.\n\nFixes: 7a12b5031c6b (\"sparc64: Add eBPF JIT.\")\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: David S. Miller <davem@davemloft.net>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\nSigned-off-by: Alexei Starovoitov <ast@kernel.org>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/07aee94394547721ac168cbf4e1c09c14a5fe671"},{"sha":"87ab8194303e73af2898e9e1c8b3b9bcfe91e7a9","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf: add test case for ld_abs and helper changing pkt data\n\nAdd a test that i) uses LD_ABS, ii) zeroing R6 before call, iii) calls\na helper that triggers reload of cached skb data, iv) uses LD_ABS again.\nIt's added for test_bpf in order to do runtime testing after JITing as\nwell as test_verifier to test that the sequence is allowed.\n\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\nSigned-off-by: Alexei Starovoitov <ast@kernel.org>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/87ab8194303e73af2898e9e1c8b3b9bcfe91e7a9"},{"sha":"c1b08ebe5003ae291470cb6e26923628ab19606f","author":{"name":"Alexei Starovoitov","email":"50b16f6527d2958df737674aa9b4293ff06b2058@kernel.org"},"message":"Merge branch 'bpf-jit-fixes'\n\nDaniel Borkmann says:\n\n====================\nTwo fixes that deal with buggy usage of bpf_helper_changes_pkt_data()\nin the sense that they also reload cached skb data when there's no\nskb context but xdp one, for example. A fix where skb meta data is\nreloaded out of the wrong register on helper call, rest is test cases\nand making sure on verifier side that there's always the guarantee\nthat ctx sits in r1. Thanks!\n====================\n\nSigned-off-by: Alexei Starovoitov <ast@kernel.org>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/c1b08ebe5003ae291470cb6e26923628ab19606f"},{"sha":"588753f1eb18978512b1c9b85fddb457d46f9033","author":{"name":"Brendan McGrath","email":"cd51d4f5d4ed894175ae7ee2d8b07621cf7549be@redmandi.dyndns.org"},"message":"ipv6: icmp6: Allow icmp messages to be looped back\n\nOne example of when an ICMPv6 packet is required to be looped back is\nwhen a host acts as both a Multicast Listener and a Multicast Router.\n\nA Multicast Router will listen on address ff02::16 for MLDv2 messages.\n\nCurrently, MLDv2 messages originating from a Multicast Listener running\non the same host as the Multicast Router are not being delivered to the\nMulticast Router. This is due to dst.input being assigned the default\nvalue of dst_discard.\n\nThis results in the packet being looped back but discarded before being\ndelivered to the Multicast Router.\n\nThis patch sets dst.input to ip6_input to ensure a looped back packet\nis delivered to the Multicast Router.\n\nSigned-off-by: Brendan McGrath <redmcg@redmandi.dyndns.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/588753f1eb18978512b1c9b85fddb457d46f9033"},{"sha":"f870c1ff65a6d1f3a083f277280802ee09a5b44d","author":{"name":"Alexey Kodanev","email":"9f3808f0a12da1be5378a18211ea35dc74f98ef4@oracle.com"},"message":"vxlan: restore dev->mtu setting based on lower device\n\nStefano Brivio says:\n    Commit a985343ba906 (\"vxlan: refactor verification and\n    application of configuration\") introduced a change in the\n    behaviour of initial MTU setting: earlier, the MTU for a link\n    created on top of a given lower device, without an initial MTU\n    specification, was set to the MTU of the lower device minus\n    headroom as a result of this path in vxlan_dev_configure():\n\n\tif (!conf->mtu)\n\t\tdev->mtu = lowerdev->mtu -\n\t\t\t   (use_ipv6 ? VXLAN6_HEADROOM : VXLAN_HEADROOM);\n\n    which is now gone. Now, the initial MTU, in absence of a\n    configured value, is simply set by ether_setup() to ETH_DATA_LEN\n    (1500 bytes).\n\n    This breaks userspace expectations in case the MTU of\n    the lower device is higher than 1500 bytes minus headroom.\n\nThis patch restores the previous behaviour on newlink operation. Since\nmax_mtu can be negative and we update dev->mtu directly, also check it\nfor valid minimum.\n\nReported-by: Junhan Yan <juyan@redhat.com>\nFixes: a985343ba906 (\"vxlan: refactor verification and application of configuration\")\nSigned-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>\nAcked-by: Stefano Brivio <sbrivio@redhat.com>\nSigned-off-by: Stefano Brivio <sbrivio@redhat.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/f870c1ff65a6d1f3a083f277280802ee09a5b44d"},{"sha":"b36025b19a2301ba0cac05e6ffad5668013d2c77","author":{"name":"David S. Miller","email":"79caf591e37e1438a2d55ae59670d5cd0d717764@davemloft.net"},"message":"Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf\n\nDaniel Borkmann says:\n\n====================\npull-request: bpf 2017-12-17\n\nThe following pull-request contains BPF updates for your *net* tree.\n\nThe main changes are:\n\n1) Fix a corner case in generic XDP where we have non-linear skbs\n   but enough tailroom in the skb to not miss to linearizing there,\n   from Song.\n\n2) Fix BPF JIT bugs in s390x and ppc64 to not recache skb data when\n   BPF context is not skb, from Daniel.\n\n3) Fix a BPF JIT bug in sparc64 where recaching skb data after helper\n   call would use the wrong register for the skb, from Daniel.\n====================\n\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/b36025b19a2301ba0cac05e6ffad5668013d2c77"},{"sha":"234833991e14681f61cbfd93e65a5c976089cf11","author":{"name":"Jon Maloy","email":"b0012c6b16a2cc61cfde6c8e64b78c583cb9e8a8@ericsson.com"},"message":"tipc: fix lost member events bug\n\nGroup messages are not supposed to be returned to sender when the\ndestination socket disappears. This is done correctly for regular\ntraffic messages, by setting the 'dest_droppable' bit in the header.\nBut we forget to do that in group protocol messages. This has the effect\nthat such messages may sometimes bounce back to the sender, be perceived\nas a legitimate peer message, and wreak general havoc for the rest of\nthe session. In particular, we have seen that a member in state LEAVING\nmay go back to state RECLAIMED or REMITTED, hence causing suppression\nof an otherwise expected 'member down' event to the user.\n\nWe fix this by setting the 'dest_droppable' bit even in group protocol\nmessages.\n\nSigned-off-by: Jon Maloy <jon.maloy@ericsson.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/234833991e14681f61cbfd93e65a5c976089cf11"},{"sha":"3f42f5fe31c8715a34064bfd7b788488d1ea2f7c","author":{"name":"Jon Maloy","email":"b0012c6b16a2cc61cfde6c8e64b78c583cb9e8a8@ericsson.com"},"message":"tipc: remove leaving group member from all lists\n\nA group member going into state LEAVING should never go back to any\nother state before it is finally deleted. However, this might happen\nif the socket needs to send out a RECLAIM message during this interval.\nSince we forget to remove the leaving member from the group's 'active'\nor 'pending' list, the member might be selected for reclaiming, change\nstate to RECLAIMING, and get stuck in this state instead of being\ndeleted. This might lead to suppression of the expected 'member down'\nevent to the receiver.\n\nWe fix this by removing the member from all lists, except the RB tree,\nat the moment it goes into state LEAVING.\n\nSigned-off-by: Jon Maloy <jon.maloy@ericsson.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/3f42f5fe31c8715a34064bfd7b788488d1ea2f7c"},{"sha":"c505873eaece2b4aefd07d339dc7e1400e0235ac","author":{"name":"Zhao Qiang","email":"4a538303ca32c8f62136696f77fa6d3445cf16eb@nxp.com"},"message":"net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.\n\n88E1145 also need this autoneg errata.\n\nFixes: f2899788353c (\"net: phy: marvell: Limit errata to 88m1101\")\nSigned-off-by: Zhao Qiang <qiang.zhao@nxp.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/c505873eaece2b4aefd07d339dc7e1400e0235ac"},{"sha":"ac3241d5c81bf6e85095481435f29a4627ff820e","author":{"name":"Hemanth Puranik","email":"88245aef45ad1a539fece1a78186fdfb400c51d4@codeaurora.org"},"message":"net: qcom/emac: Change the order of mac up and sgmii open\n\nThis patch fixes the order of mac_up and sgmii_open for the\nreasons noted below:\n\n- If open takes more time(if the SGMII block is not responding or\n  if we want to do some delay based task) in this situation we\n  will hit NETDEV watchdog\n- The main reason : We should signal to upper layers that we are\n  ready to receive packets \"only\" when the entire path is initialized\n  not the other way around, this is followed in the reset path where\n  we do mac_down, sgmii_reset and mac_up. This also makes the driver\n  uniform across the reset and open paths.\n- In the future there may be need for delay based tasks to be done in\n  sgmii open which will result in NETDEV watchdog\n- As per the documentation the order of init should be sgmii, mac, rings\n  and DMA\n\nSigned-off-by: Hemanth Puranik <hpuranik@codeaurora.org>\nAcked-by: Timur Tabi <timur@codeaurora.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/ac3241d5c81bf6e85095481435f29a4627ff820e"},{"sha":"5c468674d17056148da06218d4da5d04baf22eac","author":{"name":"Xin Long","email":"0c651f6709819e543c4ca1708bc1021b57131127@gmail.com"},"message":"sctp: fix the issue that a __u16 variable may overflow in sctp_ulpq_renege\n\nNow when reneging events in sctp_ulpq_renege(), the variable freed\ncould be increased by a __u16 value twice while freed is of __u16\ntype. It means freed may overflow at the second addition.\n\nThis patch is to fix it by using __u32 type for 'freed', while at\nit, also to remove 'if (chunk)' check, as all renege commands are\ngenerated in sctp_eat_data and it can't be NULL.\n\nReported-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>\nSigned-off-by: Xin Long <lucien.xin@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/5c468674d17056148da06218d4da5d04baf22eac"},{"sha":"d196975905b2bb227dc54547c03b3d9d0013805c","author":{"name":"Xin Long","email":"0c651f6709819e543c4ca1708bc1021b57131127@gmail.com"},"message":"sctp: add SCTP_CID_RECONF conversion in sctp_cname\n\nWhenever a new type of chunk is added, the corresp conversion in\nsctp_cname should be added. Otherwise, in some places, pr_debug\nwill print it as \"unknown chunk\".\n\nFixes: cc16f00f6529 (\"sctp: add support for generating stream reconf ssn reset request chunk\")\nSigned-off-by: Xin Long <lucien.xin@gmail.com>\nAcked-by: Marcelo R. Leitner <marcelo.leitner@gmail.com>\nAcked-by: Neil Horman <nhorman@tuxdriver.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/d196975905b2bb227dc54547c03b3d9d0013805c"},{"sha":"84aeb437ab98a2bce3d4b2111c79723aedfceb33","author":{"name":"Nikolay Aleksandrov","email":"64c6133501914790fe0371388ffd86301bcc142b@cumulusnetworks.com"},"message":"net: bridge: fix early call to br_stp_change_bridge_id and plug newlink leaks\n\nThe early call to br_stp_change_bridge_id in bridge's newlink can cause\na memory leak if an error occurs during the newlink because the fdb\nentries are not cleaned up if a different lladdr was specified, also\nanother minor issue is that it generates fdb notifications with\nifindex = 0. Another unrelated memory leak is the bridge sysfs entries\nwhich get added on NETDEV_REGISTER event, but are not cleaned up in the\nnewlink error path. To remove this special case the call to\nbr_stp_change_bridge_id is done after netdev register and we cleanup the\nbridge on changelink error via br_dev_delete to plug all leaks.\n\nThis patch makes netlink bridge destruction on newlink error the same as\ndellink and ioctl del which is necessary since at that point we have a\nfully initialized bridge device.\n\nTo reproduce the issue:\n$ ip l add br0 address 00:11:22:33:44:55 type bridge group_fwd_mask 1\nRTNETLINK answers: Invalid argument\n\n$ rmmod bridge\n[ 1822.142525] =============================================================================\n[ 1822.143640] BUG bridge_fdb_cache (Tainted: G           O    ): Objects remaining in bridge_fdb_cache on __kmem_cache_shutdown()\n[ 1822.144821] -----------------------------------------------------------------------------\n\n[ 1822.145990] Disabling lock debugging due to kernel taint\n[ 1822.146732] INFO: Slab 0x0000000092a844b2 objects=32 used=2 fp=0x00000000fef011b0 flags=0x1ffff8000000100\n[ 1822.147700] CPU: 2 PID: 13584 Comm: rmmod Tainted: G    B      O     4.15.0-rc2+ #87\n[ 1822.148578] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140531_083030-gandalf 04/01/2014\n[ 1822.150008] Call Trace:\n[ 1822.150510]  dump_stack+0x78/0xa9\n[ 1822.151156]  slab_err+0xb1/0xd3\n[ 1822.151834]  ? __kmalloc+0x1bb/0x1ce\n[ 1822.152546]  __kmem_cache_shutdown+0x151/0x28b\n[ 1822.153395]  shutdown_cache+0x13/0x144\n[ 1822.154126]  kmem_cache_destroy+0x1c0/0x1fb\n[ 1822.154669]  SyS_delete_module+0x194/0x244\n[ 1822.155199]  ? trace_hardirqs_on_thunk+0x1a/0x1c\n[ 1822.155773]  entry_SYSCALL_64_fastpath+0x23/0x9a\n[ 1822.156343] RIP: 0033:0x7f929bd38b17\n[ 1822.156859] RSP: 002b:00007ffd160e9a98 EFLAGS: 00000202 ORIG_RAX: 00000000000000b0\n[ 1822.157728] RAX: ffffffffffffffda RBX: 00005578316ba090 RCX: 00007f929bd38b17\n[ 1822.158422] RDX: 00007f929bd9ec60 RSI: 0000000000000800 RDI: 00005578316ba0f0\n[ 1822.159114] RBP: 0000000000000003 R08: 00007f929bff5f20 R09: 00007ffd160e8a11\n[ 1822.159808] R10: 00007ffd160e9860 R11: 0000000000000202 R12: 00007ffd160e8a80\n[ 1822.160513] R13: 0000000000000000 R14: 0000000000000000 R15: 00005578316ba090\n[ 1822.161278] INFO: Object 0x000000007645de29 @offset=0\n[ 1822.161666] INFO: Object 0x00000000d5df2ab5 @offset=128\n\nFixes: 30313a3d5794 (\"bridge: Handle IFLA_ADDRESS correctly when creating bridge device\")\nFixes: 5b8d5429daa0 (\"bridge: netlink: register netdevice before executing changelink\")\nSigned-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/84aeb437ab98a2bce3d4b2111c79723aedfceb33"},{"sha":"6623c0fba10ef45b64ca213ad5dec926f37fa9a0","author":{"name":"Russell King","email":"8640768d851c67eb4c0e8bfcf2aabcc8010b9372@armlinux.org.uk"},"message":"net: phy: marvell: avoid pause mode on SGMII-to-Copper for 88e151x\n\nObserved on the 88e1512 in SGMII-to-Copper mode, negotiating pause\nis unreliable.  While the pause bits can be set in the advertisment\nregister, they clear shortly after negotiation with a link partner\ncommences irrespective of the cause of the negotiation.\n\nWhile these bits may be correctly conveyed to the link partner on the\nfirst negotiation, a subsequent negotiation (eg, due to negotiation\nrestart by the link partner, or reconnection of the cable) will result\nin the link partner seeing these bits as zero, while the kernel\nbelieves that it has advertised pause modes.\n\nThis leads to the local kernel evaluating (eg) symmetric pause mode,\nwhile the remote end evaluates that we have no pause mode capability.\n\nSince we can't guarantee the advertisment, disable pause mode support\nwith this PHY when used in SGMII-to-Copper mode.\n\nThe 88e1510 in RGMII-to-Copper mode appears to behave correctly.\n\nReviewed-by: Andrew Lunn <andrew@lunn.ch>\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/6623c0fba10ef45b64ca213ad5dec926f37fa9a0"},{"sha":"ab14436065c8066c265540312742390d6d07ddd2","author":{"name":"Alexey Khoroshilov","email":"ace9a61ddd722b948531d2d4c78db504ebfc9f1b@ispras.ru"},"message":"net: phy: xgene: disable clk on error paths\n\nThere are several error paths in xgene_mdio_probe(),\nwhere clk is left undisabled. The patch fixes them.\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/altera-opensource/linux-socfpga/commits/ab14436065c8066c265540312742390d6d07ddd2"}]}
{"actor":{"display_login":"atull-altera"}}