{"push_id":1424244341,"size":28,"distinct_size":28,"ref":"refs/heads/for-linust","head":"5405dcc8abb7db3791a9776e5e06a36e5c07c675","before":"b369a14f1586411ca847c74f51e62b038b2f6db8","commits":[{"sha":"39385cb5f3274735b03ed1f8e7ff517b02a0beed","author":{"name":"Johan Hedberg","email":"96898026c3f4a50ee66f26e7291d450d5b98554a@intel.com"},"message":"Bluetooth: Fix using the correct source address type\n\nThe hci_get_route() API is used to look up local HCI devices, however\nso far it has been incapable of dealing with anything else than the\npublic address of HCI devices. This completely breaks with LE-only HCI\ndevices that do not come with a public address, but use a static\nrandom address instead.\n\nThis patch exteds the hci_get_route() API with a src_type parameter\nthat's used for comparing with the right address of each HCI device.\n\nSigned-off-by: Johan Hedberg <johan.hedberg@intel.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/39385cb5f3274735b03ed1f8e7ff517b02a0beed"},{"sha":"5499a6b22e5508b921c447757685b0a5e40a07ed","author":{"name":"Oliver Hartkopp","email":"4a7aeae382a9ad981c684b504c17442f359c4ede@hartkopp.net"},"message":"can: bcm: fix support for CAN FD frames\n\nSince commit 6f3b911d5f29b98 (\"can: bcm: add support for CAN FD frames\") the\nCAN broadcast manager supports CAN and CAN FD data frames.\n\nAs these data frames are embedded in struct can[fd]_frames which have a\ndifferent length the access to the provided array of CAN frames became\ndependend of op->cfsiz. By using a struct canfd_frame pointer for the array of\nCAN frames the new offset calculation based on op->cfsiz was accidently applied\nto CAN FD frame element lengths.\n\nThis fix makes the pointer to the arrays of the different CAN frame types a\nvoid pointer so that the offset calculation in bytes accesses the correct CAN\nframe elements.\n\nReference: http://marc.info/?l=linux-netdev&m=147980658909653\n\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Oliver Hartkopp <socketcan@hartkopp.net>\nTested-by: Andrey Konovalov <andreyknvl@google.com>\nCc: linux-stable <stable@vger.kernel.org>\nSigned-off-by: Marc Kleine-Budde <mkl@pengutronix.de>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/5499a6b22e5508b921c447757685b0a5e40a07ed"},{"sha":"764d3be6e415b40056834bfd29b994dc3f837606","author":{"name":"Paolo Abeni","email":"760d0d6fcadb77e1b4c1d3c7879788c2b4ed8bbe@redhat.com"},"message":"ipv6: bump genid when the IFA_F_TENTATIVE flag is clear\n\nWhen an ipv6 address has the tentative flag set, it can't be\nused as source for egress traffic, while the associated route,\nif any, can be looked up and even stored into some dst_cache.\n\nIn the latter scenario, the source ipv6 address selected and\nstored in the cache is most probably wrong (e.g. with\nlink-local scope) and the entity using the dst_cache will\nexperience lack of ipv6 connectivity until said cache is\ncleared or invalidated.\n\nOverall this may cause lack of connectivity over most IPv6 tunnels\n(comprising geneve and vxlan), if the first egress packet reaches\nthe tunnel before the DaD is completed for the used ipv6\naddress.\n\nThis patch bumps a new genid after that the IFA_F_TENTATIVE flag\nis cleared, so that dst_cache will be invalidated on\nnext lookup and ipv6 connectivity restored.\n\nFixes: 0c1d70af924b (\"net: use dst_cache for vxlan device\")\nFixes: 468dfffcd762 (\"geneve: add dst caching support\")\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nSigned-off-by: Paolo Abeni <pabeni@redhat.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/764d3be6e415b40056834bfd29b994dc3f837606"},{"sha":"30c7be26fd3587abcb69587f781098e3ca2d565b","author":{"name":"Eric Dumazet","email":"b3d77ad2db30f558882cc0c038be5a3cf96611f9@google.com"},"message":"udplite: call proper backlog handlers\n\nIn commits 93821778def10 (\"udp: Fix rcv socket locking\") and\nf7ad74fef3af (\"net/ipv6/udp: UDP encapsulation: break backlog_rcv into\n__udpv6_queue_rcv_skb\") UDP backlog handlers were renamed, but UDPlite\nwas forgotten.\n\nThis leads to crashes if UDPlite header is pulled twice, which happens\nstarting from commit e6afc8ace6dd (\"udp: remove headers from UDP packets\nbefore queueing\")\n\nBug found by syzkaller team, thanks a lot guys !\n\nNote that backlog use in UDP/UDPlite is scheduled to be removed starting\nfrom linux-4.10, so this patch is only needed up to linux-4.9\n\nFixes: 93821778def1 (\"udp: Fix rcv socket locking\")\nFixes: f7ad74fef3af (\"net/ipv6/udp: UDP encapsulation: break backlog_rcv into __udpv6_queue_rcv_skb\")\nFixes: e6afc8ace6dd (\"udp: remove headers from UDP packets before queueing\")\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nCc: Benjamin LaHaise <bcrl@kvack.org>\nCc: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/30c7be26fd3587abcb69587f781098e3ca2d565b"},{"sha":"867d1212bf3c53dc057f7bca72155048cc51d18c","author":{"name":"Andy Gospodarek","email":"d5bb94bfe4a4a4ee479b7ab07f2b90ec80fb30eb@broadcom.com"},"message":"bnxt: do not busy-poll when link is down\n\nWhen busy polling while a link is down (during a link-flap test), TX\ntimeouts were observed as well as the following messages in the ring\nbuffer:\n\nbnxt_en 0008:01:00.2 enP8p1s0f2d2: Resp cmpl intr err msg: 0x51\nbnxt_en 0008:01:00.2 enP8p1s0f2d2: hwrm_ring_free tx failed. rc:-1\nbnxt_en 0008:01:00.2 enP8p1s0f2d2: Resp cmpl intr err msg: 0x51\nbnxt_en 0008:01:00.2 enP8p1s0f2d2: hwrm_ring_free rx failed. rc:-1\n\nThese were resolved by checking for link status and returning if link\nwas not up.\n\nSigned-off-by: Andy Gospodarek <gospo@broadcom.com>\nSigned-off-by: Michael Chan <michael.chan@broadcom.com>\nTested-by: Rob Miller <rob.miller@broadcom.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/867d1212bf3c53dc057f7bca72155048cc51d18c"},{"sha":"76da8706d90d8641eeb9b8e579942ed80b6c0880","author":{"name":"Florian Fainelli","email":"244da8ca84c0b82369d8dd3f15015e61f28f6fe5@gmail.com"},"message":"net: dsa: bcm_sf2: Ensure we re-negotiate EEE during after link change\n\nIn case the link change and EEE is enabled or disabled, always try to\nre-negotiate this with the link partner.\n\nFixes: 450b05c15f9c (\"net: dsa: bcm_sf2: add support for controlling EEE\")\nSigned-off-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/76da8706d90d8641eeb9b8e579942ed80b6c0880"},{"sha":"19a8bb28d1c66670a2aebf9c78ec21c0b942f4b8","author":{"name":"Roman Mashak","email":"438d91077537574f04f08925e5c7563caa8f6290@mojatatu.com"},"message":"net sched filters: fix filter handle ID in tfilter_notify_chain()\n\nShould pass valid filter handle, not the netlink flags.\n\nFixes: 30a391a13ab92 (\"net sched filters: pass netlink message flags in event notification\")\nSigned-off-by: Roman Mashak <mrv@mojatatu.com>\nSigned-off-by: Jamal Hadi Salim <jhs@mojatatu.com>\nReported-by: Cong Wang <xiyou.wangcong@gmail.com>\nAcked-by: Daniel Borkmann <daniel@iogearbox.net>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/19a8bb28d1c66670a2aebf9c78ec21c0b942f4b8"},{"sha":"f9e154a0e6730218c222d95af22784b0a53e3f58","author":{"name":"David S. Miller","email":"79caf591e37e1438a2d55ae59670d5cd0d717764@davemloft.net"},"message":"Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth\n\nJohan Hedberg says:\n\n====================\npull request: bluetooth 2016-11-23\n\nSorry about the late pull request for 4.9, but we have one more\nimportant Bluetooth patch that should make it to the release. It fixes\nconnection creation for Bluetooth LE controllers that do not have a\npublic address (only a random one).\n\nPlease let me know if there are any issues pulling. Thanks.\n====================\n\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/f9e154a0e6730218c222d95af22784b0a53e3f58"},{"sha":"f7db0ec9572f66b36c0d4d6bc4b564da53c8b35d","author":{"name":"Geliang Tang","email":"bd74e8ca27341f584803a5a1f60187557a0aa095@gmail.com"},"message":"dwc_eth_qos: drop duplicate headers\n\nDrop duplicate headers types.h and delay.h from dwc_eth_qos.c.\n\nSigned-off-by: Geliang Tang <geliangtang@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/f7db0ec9572f66b36c0d4d6bc4b564da53c8b35d"},{"sha":"fb09c8c524dae2b893aacc9348e876a87b45b697","author":{"name":"David S. Miller","email":"79caf591e37e1438a2d55ae59670d5cd0d717764@davemloft.net"},"message":"Merge tag 'linux-can-fixes-for-4.9-20161123' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can\n\nMarc Kleine-Budde says:\n\n====================\npull-request: can 2016-11-23\n\nthis is a pull request for net/master.\n\nThe patch by Oliver Hartkopp for the broadcast manager (bcm) fixes the\nCAN-FD support, which may cause an out-of-bounds access otherwise.\n====================\n\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/fb09c8c524dae2b893aacc9348e876a87b45b697"},{"sha":"97db8afa2ab919fc400fe982f5054060868bdf07","author":{"name":"Andrew Lunn","email":"6b7c097d961f68685fc978cf91eeae17be6cbb45@lunn.ch"},"message":"net: ethernet: mvneta: Remove IFF_UNICAST_FLT which is not implemented\n\nThe mvneta driver advertises it supports IFF_UNICAST_FLT. However, it\nactually does not. The hardware probably does support it, but there is\nno code to configure the filter. As a quick and simple fix, remove the\nflag. This will cause the core to fall back to promiscuous mode.\n\nSigned-off-by: Andrew Lunn <andrew@lunn.ch>\nFixes: b50b72de2f2f (\"net: mvneta: enable features before registering the driver\")\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/97db8afa2ab919fc400fe982f5054060868bdf07"},{"sha":"f79675563a6bbfc2ff85684bbbaea9ef092664d2","author":{"name":"Jon Paul Maloy","email":"b0012c6b16a2cc61cfde6c8e64b78c583cb9e8a8@ericsson.com"},"message":"tipc: fix compatibility bug in link monitoring\n\ncommit 817298102b0b (\"tipc: fix link priority propagation\") introduced a\ncompatibility problem between TIPC versions newer than Linux 4.6 and\nthose older than Linux 4.4. In versions later than 4.4, link STATE\nmessages only contain a non-zero link priority value when the sender\nwants the receiver to change its priority. This has the effect that the\nreceiver resets itself in order to apply the new priority. This works\nwell, and is consistent with the said commit.\n\nHowever, in versions older than 4.4 a valid link priority is present in\nall sent link STATE messages, leading to cyclic link establishment and\nreset on the 4.6+ node.\n\nWe fix this by adding a test that the received value should not only\nbe valid, but also differ from the current value in order to cause the\nreceiving link endpoint to reset.\n\nReported-by: Amar Nv <amar.nv005@gmail.com>\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/alaahl/linux/commits/f79675563a6bbfc2ff85684bbbaea9ef092664d2"},{"sha":"d876a4d2afecacf4b4d8b11479e9f1ed0080bb2e","author":{"name":"Jon Paul Maloy","email":"b0012c6b16a2cc61cfde6c8e64b78c583cb9e8a8@ericsson.com"},"message":"tipc: improve sanity check for received domain records\n\nIn commit 35c55c9877f8 (\"tipc: add neighbor monitoring framework\") we\nadded a data area to the link monitor STATE messages under the\nassumption that previous versions did not use any such data area.\n\nFor versions older than Linux 4.3 this assumption is not correct. In\nthose version, all STATE messages sent out from a node inadvertently\ncontain a 16 byte data area containing a string; -a leftover from\nprevious RESET messages which were using this during the setup phase.\nThis string serves no purpose in STATE messages, and should no be there.\n\nUnfortunately, this data area is delivered to the link monitor\nframework, where a sanity check catches that it is not a correct domain\nrecord, and drops it. It also issues a rate limited warning about the\nevent.\n\nSince such events occur much more frequently than anticipated, we now\nchoose to remove the warning in order to not fill the kernel log with\nuseless contents. We also make the sanity check stricter, to further\nreduce the risk that such data is inavertently admitted.\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/alaahl/linux/commits/d876a4d2afecacf4b4d8b11479e9f1ed0080bb2e"},{"sha":"8006f6bf5e39f11c697f48df20382b81d2f2f8b8","author":{"name":"Miroslav Lichvar","email":"dff4e058f2aa89d1c9e462ceed29e4a5f113691a@redhat.com"},"message":"net: ethtool: don't require CAP_NET_ADMIN for ETHTOOL_GLINKSETTINGS\n\nThe ETHTOOL_GLINKSETTINGS command is deprecating the ETHTOOL_GSET\ncommand and likewise it shouldn't require the CAP_NET_ADMIN capability.\n\nSigned-off-by: Miroslav Lichvar <mlichvar@redhat.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/8006f6bf5e39f11c697f48df20382b81d2f2f8b8"},{"sha":"1f1e70efe53c01844ce76d77c3383c2bcb6beb49","author":{"name":"Dan Carpenter","email":"60b2bf2bc0bec4ca4a4b046ca7ef9255248abff8@oracle.com"},"message":"fsl/fman: fix a leak in tgec_free()\n\nWe set \"tgec->cfg\" to NULL before passing it to kfree().  There is no\nneed to set it to NULL at all.  Let's just delete it.\n\nFixes: 57ba4c9b56d8 (\"fsl/fman: Add FMan MAC support\")\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/1f1e70efe53c01844ce76d77c3383c2bcb6beb49"},{"sha":"4ee12efa2dbf949d72ef2f7ef2e044af5a67b515","author":{"name":"Geliang Tang","email":"bd74e8ca27341f584803a5a1f60187557a0aa095@gmail.com"},"message":"ibmvnic: drop duplicate header seq_file.h\n\nDrop duplicate header seq_file.h from ibmvnic.c.\n\nSigned-off-by: Geliang Tang <geliangtang@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/4ee12efa2dbf949d72ef2f7ef2e044af5a67b515"},{"sha":"8f8a8b13b447842b147539ae2cab6699897539b9","author":{"name":"Geliang Tang","email":"bd74e8ca27341f584803a5a1f60187557a0aa095@gmail.com"},"message":"net: ieee802154: drop duplicate header delay.h\n\nDrop duplicate header delay.h from adf7242.c.\n\nSigned-off-by: Geliang Tang <geliangtang@gmail.com>\nAcked-by: Stefan Schmidt <stefan@osg.samsung.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/8f8a8b13b447842b147539ae2cab6699897539b9"},{"sha":"5e7dfeb758663391ec721e6a4519d3df874f9b1f","author":{"name":"Geliang Tang","email":"bd74e8ca27341f584803a5a1f60187557a0aa095@gmail.com"},"message":"net/mlx5: drop duplicate header delay.h\n\nDrop duplicate header delay.h from mlx5/core/main.c.\n\nSigned-off-by: Geliang Tang <geliangtang@gmail.com>\nAcked-by: Matan Barak <matanb@mellanox.com>\nAcked-by: Saeed Mahameed <saeedm@mellanox.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/5e7dfeb758663391ec721e6a4519d3df874f9b1f"},{"sha":"e8f967c3d88489fc1562a31d4e44d905ac1d3aff","author":{"name":"Arnd Bergmann","email":"72a0f6d3b182607e6d5c44b93e1abb7b23ee18f3@arndb.de"},"message":"mvpp2: use correct size for memset\n\ngcc-7 detects a short memset in mvpp2, introduced in the original\nmerge of the driver:\n\ndrivers/net/ethernet/marvell/mvpp2.c: In function 'mvpp2_cls_init':\ndrivers/net/ethernet/marvell/mvpp2.c:3296:2: error: 'memset' used with length equal to number of elements without multiplication by element size [-Werror=memset-elt-size]\n\nThe result seems to be that we write uninitialized data into the\nflow table registers, although we did not get any warning about\nthat uninitialized data usage.\n\nUsing sizeof() lets us initialize then entire array instead.\n\nFixes: 3f518509dedc (\"ethernet: Add new driver for Marvell Armada 375 network unit\")\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/alaahl/linux/commits/e8f967c3d88489fc1562a31d4e44d905ac1d3aff"},{"sha":"6998cc6ec23740347670da13186d2979c5401903","author":{"name":"Jon Paul Maloy","email":"b0012c6b16a2cc61cfde6c8e64b78c583cb9e8a8@ericsson.com"},"message":"tipc: resolve connection flow control compatibility problem\n\nIn commit 10724cc7bb78 (\"tipc: redesign connection-level flow control\")\nwe replaced the previous message based flow control with one based on\n1k blocks. In order to ensure backwards compatibility the mechanism\nfalls back to using message as base unit when it senses that the peer\ndoesn't support the new algorithm. The default flow control window,\ni.e., how many units can be sent before the sender blocks and waits\nfor an acknowledge (aka advertisement) is 512. This was tested against\nthe previous version, which uses an acknowledge frequency of on ack per\n256 received message, and found to work fine.\n\nHowever, we missed the fact that versions older than Linux 3.15 use an\nacknowledge frequency of 512, which is exactly the limit where a 4.6+\nsender will stop and wait for acknowledge. This would also work fine if\nit weren't for the fact that if the first sent message on a 4.6+ server\nside is an empty SYNACK, this one is also is counted as a sent message,\nwhile it is not counted as a received message on a legacy 3.15-receiver.\nThis leads to the sender always being one step ahead of the receiver, a\nscenario causing the sender to block after 512 sent messages, while the\nreceiver only has registered 511 read messages. Hence, the legacy\nreceiver is not trigged to send an acknowledge, with a permanently\nblocked sender as result.\n\nWe solve this deadlock by simply allowing the sender to send one more\nmessage before it blocks, i.e., by a making minimal change to the\ncondition used for determining connection congestion.\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/alaahl/linux/commits/6998cc6ec23740347670da13186d2979c5401903"}]}
{"actor":{"display_login":"alaahl"}}