)]}' { "log": [ { "commit": "a7ff77de9ab8694ac1c0648a623f6916c000d35e", "tree": "ec18a448198d1a60e6360ff6e26b4b8168b3deab", "parents": [ "953a18aa4eaed3637050422156cb6ffbe6554156" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Wed Apr 15 10:51:36 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Mon May 04 15:00:58 2020 +0200" }, "message": "net: macb: Add WoL interrupt support for MACB type of Ethernet controller\n\nHandle the Wake-on-Lan interrupt for the Cadence MACB Ethernet\ncontroller.\nAs we do for the GEM version, we handle of WoL interrupt in a\nspecialized interrupt handler for MACB version that is positionned\njust between suspend() and resume() calls.\n\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "953a18aa4eaed3637050422156cb6ffbe6554156", "tree": "eb5345da90ac0291ed67a25f5f312c52fb55007e", "parents": [ "e985e9247478205d66507cd1bd74b6f8fb6c829f" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 03 12:04:34 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Mon May 04 15:00:57 2020 +0200" }, "message": "net: macb: WoL support for GEM type of Ethernet controller\n\nAdapt the Wake-on-Lan feature to the Cadence GEM Ethernet controller.\nThis controller has different register layout and cannot be handled by\nprevious code.\nWe disable completely interrupts on all the queues but the queue 0.\nHandling of WoL interrupt is done in another interrupt handler\npositioned depending on the controller version used, just between\nsuspend() and resume() calls.\nIt allows to lower pressure on the generic interrupt hot path by\nremoving the need to handle 2 tests for each IRQ: the first figuring out\nthe controller revision, the second for actually knowing if the WoL bit\nis set.\n\nQueue management in suspend()/resume() functions inspired from RFC patch\nby Harini Katakam \u003charinik@xilinx.com\u003e, thanks!\n\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "e985e9247478205d66507cd1bd74b6f8fb6c829f", "tree": "78e036d4d0a2737c010da6fa1bc295bc3e87b87a", "parents": [ "2b377e5705ced4b0171e07642a891f2416b94945" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Mon Apr 20 17:44:04 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Thu Apr 30 15:36:10 2020 +0200" }, "message": "net: macb: fix call to pm_runtime in the suspend/resume functions\n\nThe calls to pm_runtime_force_suspend/resume() functions are only\nrelevant if the device is not configured to act as a WoL wakeup source.\nAdd the device_may_wakeup() test before calling them.\n\nFixes: 3e2a5e153906 (\"net: macb: add wake-on-lan support via magic packet\")\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nCc: Sergio Prado \u003csergio.prado@e-labworks.com\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "2b377e5705ced4b0171e07642a891f2416b94945", "tree": "32f42021b03ec26c7d0f83cb73c4dcbe2d978c3d", "parents": [ "77a2227ac02b432f42ed454e1ad94e15863ae2ff" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Mon Apr 20 17:39:18 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Thu Apr 30 15:36:00 2020 +0200" }, "message": "net: macb: fix macb_suspend() by removing call to netif_carrier_off()\n\nAs we now use the phylink call to phylink_stop() in the non-WoL path,\nthere is no need for this call to netif_carrier_off() anymore. It can\ndisturb the underlying phylink FSM.\n\nFixes: 7897b071ac3b (\"net: macb: convert to phylink\")\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nCc: Antoine Tenart \u003cantoine.tenart@bootlin.com\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "77a2227ac02b432f42ed454e1ad94e15863ae2ff", "tree": "079d76a290c416386cac8ecee1ec6a336952885f", "parents": [ "b01c5d9e5e112c8620e28e538109efa70d566509" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 03 12:33:52 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Tue Apr 21 12:04:54 2020 +0200" }, "message": "net: macb: fix macb_get/set_wol() when moving to phylink\n\nKeep previous function goals and integrate phylink actions to them.\n\nphylink_ethtool_get_wol() is not enough to figure out if Ethernet driver\nsupports Wake-on-Lan.\nInitialization of \"supported\" and \"wolopts\" members is done in phylink\nfunction, no need to keep them in calling function.\n\nphylink_ethtool_set_wol() return value is not enough to determine\nif WoL is enabled for the calling Ethernet driver. Call it first\nbut don\u0027t rely on its return value as most of simple PHY drivers\ndon\u0027t implement a set_wol() function.\n\nFixes: 7897b071ac3b (\"net: macb: convert to phylink\")\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nCc: Antoine Tenart \u003cantoine.tenart@bootlin.com\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "b01c5d9e5e112c8620e28e538109efa70d566509", "tree": "e732b9b7cf60fe210066d1bda20c94589855541b", "parents": [ "760ececd082c834c1ab4b1b410c605cc10bb6224" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 03 11:52:16 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Tue Apr 21 12:04:48 2020 +0200" }, "message": "net: macb: mark device wake capable when \"magic-packet\" property present\n\nChange the way the \"magic-packet\" DT property is handled in the\nmacb_probe() function, matching DT binding documentation.\nNow we mark the device as \"wakeup capable\" instead of calling the\ndevice_init_wakeup() function that would enable the wakeup source.\n\nFor Ethernet WoL, enabling the wakeup_source is done by\nusing ethtool and associated macb_set_wol() function that\nalready calls device_set_wakeup_enable() for this purpose.\n\nThat would reduce power consumption by cutting more clocks if\n\"magic-packet\" property is set but WoL is not configured by ethtool.\n\nFixes: 3e2a5e153906 (\"net: macb: add wake-on-lan support via magic packet\")\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nCc: Sergio Prado \u003csergio.prado@e-labworks.com\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "760ececd082c834c1ab4b1b410c605cc10bb6224", "tree": "ee229fb58e8a5234392a84aec79a0b1fee794b0b", "parents": [ "4be7c35d6905e070a88adb4e247031128486fc79" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Thu Apr 02 11:12:20 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Tue Apr 21 12:04:41 2020 +0200" }, "message": "net: macb: fix wakeup test in runtime suspend/resume routines\n\nUse the proper struct device pointer to check if the wakeup flag\nand wakeup source are positioned.\nUse the one passed by function call which is equivalent to\n\u0026bp-\u003edev-\u003edev.parent.\n\nIt\u0027s preventing the trigger of a spurious interrupt in case the\nWake-on-Lan feature is used.\n\nFixes: bc1109d04c39 (\"net: macb: Add pm runtime support\")\nCc: Claudiu Beznea \u003cclaudiu.beznea@microchip.com\u003e\nCc: Harini Katakam \u003charini.katakam@xilinx.com\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "4be7c35d6905e070a88adb4e247031128486fc79", "tree": "19864245a42aec5ab8d6bf6162a983e9b603df2c", "parents": [ "069ba4704df3072a249d0463d02fd24ca86e645e" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Wed Apr 08 14:46:33 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 17 18:25:46 2020 +0200" }, "message": "ARM: dts: sama5d2 xplained: don\u0027t use DMA for console USART\n\nWas adding characters to the output. Particularly visible while\nusing suspend/resume PM commands.\n\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "069ba4704df3072a249d0463d02fd24ca86e645e", "tree": "bd6eaccf08aaaf0f8f23a12eaaa17a979567e8ca", "parents": [ "4459f8522df821f6498b18245828f3bb995b7849" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Wed Apr 08 17:20:17 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 17 18:25:46 2020 +0200" }, "message": "ARM: dts: sama5d2 xplained: remove phy interrupt\n\nRemove the interrupt from the PHY as it was causing spurious\ninterrupt while testing WoL.\n\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "4459f8522df821f6498b18245828f3bb995b7849", "tree": "f4e560c20d6bfd58ed4fbfa6efbdfb67d59dde83", "parents": [ "911ce428a64a64811321ce5f569095c56e93ce3a" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Thu Apr 02 10:21:27 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 17 18:25:45 2020 +0200" }, "message": "ARM: dts: at91: sam9x60ek: add magic packet WoL to Ethernet node\n\nAdd the \"magic-packet;\" property to Ethernet node to enable\nWake-on-Lan for this interface.\n\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "911ce428a64a64811321ce5f569095c56e93ce3a", "tree": "3a18387443a0a54bab32e6253dcfd30d38177c70", "parents": [ "7a56db0299f9d43b4fe076838150c5cc293df131" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 03 11:42:53 2020 +0200" }, "committer": { "name": "Nicolas Ferre", "email": "nicolas.ferre@microchip.com", "time": "Fri Apr 17 18:25:45 2020 +0200" }, "message": "ARM: dts: at91: sama5d2 xplained: add magic packet WoL to Ethernet node\n\nAdd the \"magic-packet;\" property to Ethernet node to enable\nWake-on-Lan for this interface.\n\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@microchip.com\u003e\n" }, { "commit": "7a56db0299f9d43b4fe076838150c5cc293df131", "tree": "b8c0507100ff2f65a88ec867e142c3196f4ca574", "parents": [ "2fcd80144b93ff90836a44f2054b4d82133d3a85", "fbf4bcc9a8373122881909331f2f9566a128126e" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 18:14:13 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 18:14:13 2020 -0700" }, "message": "Merge tag \u0027nfs-for-5.7-3\u0027 of git://git.linux-nfs.org/projects/trondmy/linux-nfs\n\nPull NFS client bugfix from Trond Myklebust:\n \"Fix an ABBA spinlock issue in pnfs_update_layout()\"\n\n* tag \u0027nfs-for-5.7-3\u0027 of git://git.linux-nfs.org/projects/trondmy/linux-nfs:\n NFS: Fix an ABBA spinlock issue in pnfs_update_layout()\n" }, { "commit": "2fcd80144b93ff90836a44f2054b4d82133d3a85", "tree": "55457c798c088ae7b6cbcf4a653cc5c597ea35a1", "parents": [ "c8372665b4b96d6a818b2693dd49236d5f9c8bc2", "538b8471fee89eaf18f6bfbbc0576473f952b83e" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 15:00:57 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 15:00:57 2020 -0700" }, "message": "Merge tag \u0027tag-chrome-platform-fixes-for-v5.7-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux\n\nPull chrome-platform fixes from Benson Leung:\n \"Two small fixes for cros_ec_sensorhub_ring.c, addressing issues\n introduced in the cros_ec_sensorhub FIFO support commit\"\n\n* tag \u0027tag-chrome-platform-fixes-for-v5.7-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux:\n platform/chrome: cros_ec_sensorhub: Add missing \u0027\\n\u0027 in log messages\n platform/chrome: cros_ec_sensorhub: Off by one in cros_sensorhub_send_sample()\n" }, { "commit": "c8372665b4b96d6a818b2693dd49236d5f9c8bc2", "tree": "f96f2a2510f6abe52ead6a2c4e1adbd9e0de5d8d", "parents": [ "9786cab674574239b04df638f825ee0e7d76a48c", "d518691cbd3be3dae218e05cca3f3fc9b2f1aa77" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 14:52:29 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 14:52:29 2020 -0700" }, "message": "Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net\n\nPull networking fixes from David Miller:\n\n 1) Disable RISCV BPF JIT builds when !MMU, from Björn Töpel.\n\n 2) nf_tables leaves dangling pointer after free, fix from Eric Dumazet.\n\n 3) Out of boundary write in __xsk_rcv_memcpy(), fix from Li RongQing.\n\n 4) Adjust icmp6 message source address selection when routes have a\n preferred source address set, from Tim Stallard.\n\n 5) Be sure to validate HSR protocol version when creating new links,\n from Taehee Yoo.\n\n 6) CAP_NET_ADMIN should be sufficient to manage l2tp tunnels even in\n non-initial namespaces, from Michael Weiß.\n\n 7) Missing release firmware call in mlx5, from Eran Ben Elisha.\n\n 8) Fix variable type in macsec_changelink(), caught by KASAN. Fix from\n Taehee Yoo.\n\n 9) Fix pause frame negotiation in marvell phy driver, from Clemens\n Gruber.\n\n10) Record RX queue early enough in tun packet paths such that XDP\n programs will see the correct RX queue index, from Gilberto Bertin.\n\n11) Fix double unlock in mptcp, from Florian Westphal.\n\n12) Fix offset overflow in ARM bpf JIT, from Luke Nelson.\n\n13) marvell10g needs to soft reset PHY when coming out of low power\n mode, from Russell King.\n\n14) Fix MTU setting regression in stmmac for some chip types, from\n Florian Fainelli.\n\n* git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (101 commits)\n amd-xgbe: Use __napi_schedule() in BH context\n mISDN: make dmril and dmrim static\n net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes\n net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode\n tipc: fix incorrect increasing of link window\n Documentation: Fix tcp_challenge_ack_limit default value\n net: tulip: make early_486_chipsets static\n dt-bindings: net: ethernet-phy: add desciption for ethernet-phy-id1234.d400\n ipv6: remove redundant assignment to variable err\n net/rds: Use ERR_PTR for rds_message_alloc_sgs()\n net: mscc: ocelot: fix untagged packet drops when enslaving to vlan aware bridge\n selftests/bpf: Check for correct program attach/detach in xdp_attach test\n libbpf: Fix type of old_fd in bpf_xdp_set_link_opts\n libbpf: Always specify expected_attach_type on program load if supported\n xsk: Add missing check on user supplied headroom size\n mac80211: fix channel switch trigger from unknown mesh peer\n mac80211: fix race in ieee80211_register_hw()\n net: marvell10g: soft-reset the PHY when coming out of low power\n net: marvell10g: report firmware version\n net/cxgb4: Check the return from t4_query_params properly\n ...\n" }, { "commit": "d518691cbd3be3dae218e05cca3f3fc9b2f1aa77", "tree": "97e88b1b17c159abe09af0c41323ea8c9285332e", "parents": [ "05eab4f328bb127de37c1d619013c340cc5aaf39" ], "author": { "name": "Sebastian Andrzej Siewior", "email": "bigeasy@linutronix.de", "time": "Thu Apr 16 17:57:40 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Apr 16 13:59:53 2020 -0700" }, "message": "amd-xgbe: Use __napi_schedule() in BH context\n\nThe driver uses __napi_schedule_irqoff() which is fine as long as it is\ninvoked with disabled interrupts by everybody. Since the commit\nmentioned below the driver may invoke xgbe_isr_task() in tasklet/softirq\ncontext. This may lead to list corruption if another driver uses\n__napi_schedule_irqoff() in IRQ context.\n\nUse __napi_schedule() which safe to use from IRQ and softirq context.\n\nFixes: 85b85c853401d (\"amd-xgbe: Re-issue interrupt if interrupt status not cleared\")\nSigned-off-by: Sebastian Andrzej Siewior \u003cbigeasy@linutronix.de\u003e\nAcked-by: Tom Lendacky \u003cthomas.lendacky@amd.com\u003e\nCc: Tom Lendacky \u003cthomas.lendacky@amd.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "05eab4f328bb127de37c1d619013c340cc5aaf39", "tree": "e0e922748553700b6dad1dbdc11c6176bf4344f1", "parents": [ "806fd188ce2a4f8b587e83e73c478e6484fbfa55" ], "author": { "name": "Jason Yan", "email": "yanaijie@huawei.com", "time": "Wed Apr 15 16:42:26 2020 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Apr 16 13:52:31 2020 -0700" }, "message": "mISDN: make dmril and dmrim static\n\nFix the following sparse warning:\n\ndrivers/isdn/hardware/mISDN/mISDNisar.c:746:12: warning: symbol \u0027dmril\u0027\nwas not declared. Should it be static?\ndrivers/isdn/hardware/mISDN/mISDNisar.c:749:12: warning: symbol \u0027dmrim\u0027\nwas not declared. Should it be static?\n\nReported-by: Hulk Robot \u003chulkci@huawei.com\u003e\nSigned-off-by: Jason Yan \u003cyanaijie@huawei.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "806fd188ce2a4f8b587e83e73c478e6484fbfa55", "tree": "d6f06e94fc68cba6d78cb373a901cc5f144e185d", "parents": [ "e045124e93995fe01e42ed530003ddba5d55db4f" ], "author": { "name": "Florian Fainelli", "email": "f.fainelli@gmail.com", "time": "Tue Apr 14 15:39:52 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Apr 16 13:47:53 2020 -0700" }, "message": "net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes\n\nAfter commit bfcb813203e619a8960a819bf533ad2a108d8105 (\"net: dsa:\nconfigure the MTU for switch ports\") my Lamobo R1 platform which uses\nan allwinner,sun7i-a20-gmac compatible Ethernet MAC started to fail\nby rejecting a MTU of 1536. The reason for that is that the DMA\ncapabilities are not readable on this version of the IP, and there\nis also no \u0027tx-fifo-depth\u0027 property being provided in Device Tree. The\nproperty is documented as optional, and is not provided.\n\nChen-Yu indicated that the FIFO sizes are 4KB for TX and 16KB for RX, so\nprovide these values through platform data as an immediate fix until\nvarious Device Tree sources get updated accordingly.\n\nFixes: eaf4fac47807 (\"net: stmmac: Do not accept invalid MTU values\")\nSuggested-by: Chen-Yu Tsai \u003cwens@csie.org\u003e\nSigned-off-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nAcked-by: Chen-Yu Tsai \u003cwens@csie.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "e045124e93995fe01e42ed530003ddba5d55db4f", "tree": "0433f83ca08ddd44d3e21f6a3b718246ba5ee5a4", "parents": [ "edadedf1c5b4e4404192a0a4c3c0c05e3b7672ab" ], "author": { "name": "DENG Qingfang", "email": "dqfext@gmail.com", "time": "Tue Apr 14 14:34:08 2020 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Apr 16 13:32:05 2020 -0700" }, "message": "net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode\n\nIn VLAN-unaware mode, the Egress Tag (EG_TAG) field in Port VLAN\nControl register must be set to Consistent to let tagged frames pass\nthrough as is, otherwise their tags will be stripped.\n\nFixes: 83163f7dca56 (\"net: dsa: mediatek: add VLAN support for MT7530\")\nSigned-off-by: DENG Qingfang \u003cdqfext@gmail.com\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nTested-by: René van Dorst \u003copensource@vdorst.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "9786cab674574239b04df638f825ee0e7d76a48c", "tree": "db7eab6edc35fde4ac7e0dbc3d7a0fe076449a32", "parents": [ "3fa84bf926f32edf798cfad0317e14df41ac0509", "af15f14c8cfcee515f4e9078889045ad63efefe3" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:45:47 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:45:47 2020 -0700" }, "message": "Merge tag \u0027selinux-pr-20200416\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux\n\nPull SELinux fix from Paul Moore:\n \"One small SELinux fix to ensure we cleanup properly on an error\n condition\"\n\n* tag \u0027selinux-pr-20200416\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux:\n selinux: free str on error in str_read()\n" }, { "commit": "3fa84bf926f32edf798cfad0317e14df41ac0509", "tree": "91f673bf77fd1c278e7536f3e87da5964aa4bf98", "parents": [ "4ede125902386c6fa946852da81709fcf490ae4a", "2a575f138d003fff0f4930b5cfae4a1c46343b8f" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:29:34 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:29:34 2020 -0700" }, "message": "Merge tag \u0027ceph-for-5.7-rc2\u0027 of git://github.com/ceph/ceph-client\n\nPull ceph fixes from Ilya Dryomov:\n\n - a set of patches for a deadlock on \"rbd map\" error path\n\n - a fix for invalid pointer dereference and uninitialized variable use\n on asynchronous create and unlink error paths.\n\n* tag \u0027ceph-for-5.7-rc2\u0027 of git://github.com/ceph/ceph-client:\n ceph: fix potential bad pointer deref in async dirops cb\u0027s\n rbd: don\u0027t mess with a page vector in rbd_notify_op_lock()\n rbd: don\u0027t test rbd_dev-\u003eopts in rbd_dev_image_release()\n rbd: call rbd_dev_unprobe() after unwatching and flushing notifies\n rbd: avoid a deadlock on header_rwsem when flushing notifies\n" }, { "commit": "4ede125902386c6fa946852da81709fcf490ae4a", "tree": "2f6048de2bc6cbec4c585dc4cde3efc0bed498fa", "parents": [ "86d32f9a7c54ad74f4514d7fef7c847883207291", "0bbe7f719985efd9adb3454679ecef0984cb6800" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:14:22 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:14:22 2020 -0700" }, "message": "Merge tag \u0027trace-v5.7-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace\n\nPull tracing fix from Steven Rostedt:\n \"This fixes a small race between allocating a snapshot buffer and\n setting the snapshot trigger.\n\n On a slow machine, the trigger can occur before the snapshot is\n allocated causing a warning to be displayed in the ring buffer, and no\n snapshot triggering. Reversing the allocation and the enabling of the\n trigger fixes the problem\"\n\n* tag \u0027trace-v5.7-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:\n tracing: Fix the race between registering \u0027snapshot\u0027 event trigger and triggering \u0027snapshot\u0027 operation\n" }, { "commit": "86d32f9a7c54ad74f4514d7fef7c847883207291", "tree": "15612f1d9e4e9c6f738085322656f648fbf795d5", "parents": [ "00086336a8d96a04aa960f912287692a258f6cf5" ], "author": { "name": "Vasily Averin", "email": "vvs@virtuozzo.com", "time": "Tue Apr 14 21:33:16 2020 +0100" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Apr 16 10:10:50 2020 -0700" }, "message": "keys: Fix proc_keys_next to increase position index\n\nIf seq_file .next function does not change position index,\nread after some lseek can generate unexpected output:\n\n $ dd if\u003d/proc/keys bs\u003d1 # full usual output\n 0f6bfdf5 I--Q--- 2 perm 3f010000 1000 1000 user 4af2f79ab8848d0a: 740\n 1fb91b32 I--Q--- 3 perm 1f3f0000 1000 65534 keyring _uid.1000: 2\n 27589480 I--Q--- 1 perm 0b0b0000 0 0 user invocation_id: 16\n 2f33ab67 I--Q--- 152 perm 3f030000 0 0 keyring _ses: 2\n 33f1d8fa I--Q--- 4 perm 3f030000 1000 1000 keyring _ses: 1\n 3d427fda I--Q--- 2 perm 3f010000 1000 1000 user 69ec44aec7678e5a: 740\n 3ead4096 I--Q--- 1 perm 1f3f0000 1000 65534 keyring _uid_ses.1000: 1\n 521+0 records in\n 521+0 records out\n 521 bytes copied, 0,00123769 s, 421 kB/s\n\nBut a read after lseek in middle of last line results in the partial\nlast line and then a repeat of the final line:\n\n $ dd if\u003d/proc/keys bs\u003d500 skip\u003d1\n dd: /proc/keys: cannot skip to specified offset\n g _uid_ses.1000: 1\n 3ead4096 I--Q--- 1 perm 1f3f0000 1000 65534 keyring _uid_ses.1000: 1\n 0+1 records in\n 0+1 records out\n 97 bytes copied, 0,000135035 s, 718 kB/s\n\nand a read after lseek beyond end of file results in the last line being\nshown:\n\n $ dd if\u003d/proc/keys bs\u003d1000 skip\u003d1 # read after lseek beyond end of file\n dd: /proc/keys: cannot skip to specified offset\n 3ead4096 I--Q--- 1 perm 1f3f0000 1000 65534 keyring _uid_ses.1000: 1\n 0+1 records in\n 0+1 records out\n 76 bytes copied, 0,000119981 s, 633 kB/s\n\nSee https://bugzilla.kernel.org/show_bug.cgi?id\u003d206283\n\nFixes: 1f4aace60b0e (\"fs/seq_file.c: simplify seq_file iteration code ...\")\nSigned-off-by: Vasily Averin \u003cvvs@virtuozzo.com\u003e\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\nReviewed-by: Jarkko Sakkinen \u003cjarkko.sakkinen@linux.intel.com\u003e\nCc: stable@vger.kernel.org\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "00086336a8d96a04aa960f912287692a258f6cf5", "tree": "2a806bfd31af51c96e8ede4b7a092e92da73401e", "parents": [ "8632e9b5645bbc2331d21d892b0d6961c1a08429", "a088b858f16af85e3db359b6c6aaa92dd3bc0921" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Apr 15 17:37:48 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Apr 15 17:37:48 2020 -0700" }, "message": "Merge tag \u0027efi-urgent-2020-04-15\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull EFI fixes from Ingo Molnar:\n \"Misc EFI fixes, including the boot failure regression caused by the\n BSS section not being cleared by the loaders\"\n\n* tag \u0027efi-urgent-2020-04-15\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n efi/x86: Revert struct layout change to fix kexec boot regression\n efi/x86: Don\u0027t remap text\u003c-\u003erodata gap read-only for mixed mode\n efi/x86: Fix the deletion of variables in mixed mode\n efi/libstub/file: Merge file name buffers to reduce stack usage\n Documentation/x86, efi/x86: Clarify EFI handover protocol and its requirements\n efi/arm: Deal with ADR going out of range in efi_enter_kernel()\n efi/x86: Always relocate the kernel for EFI handover entry\n efi/x86: Move efi stub globals from .bss to .data\n efi/libstub/x86: Remove redundant assignment to pointer hdr\n efi/cper: Use scnprintf() for avoiding potential buffer overflow\n" }, { "commit": "edadedf1c5b4e4404192a0a4c3c0c05e3b7672ab", "tree": "ea5f92b24be5dd68293dd3252ac9969d7b378764", "parents": [ "5309960e49f5e2363d2814488878a29e944e1be9" ], "author": { "name": "Tuong Lien", "email": "tuong.t.lien@dektech.com.au", "time": "Wed Apr 15 18:34:49 2020 +0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 16:23:33 2020 -0700" }, "message": "tipc: fix incorrect increasing of link window\n\nIn commit 16ad3f4022bb (\"tipc: introduce variable window congestion\ncontrol\"), we allow link window to change with the congestion avoidance\nalgorithm. However, there is a bug that during the slow-start if packet\nretransmission occurs, the link will enter the fast-recovery phase, set\nits window to the \u0027ssthresh\u0027 which is never less than 300, so the link\nwindow suddenly increases to that limit instead of decreasing.\n\nConsequently, two issues have been observed:\n\n- For broadcast-link: it can leave a gap between the link queues that a\nnew packet will be inserted and sent before the previous ones, i.e. not\nin-order.\n\n- For unicast: the algorithm does not work as expected, the link window\njumps to the slow-start threshold whereas packet retransmission occurs.\n\nThis commit fixes the issues by avoiding such the link window increase,\nbut still decreasing if the \u0027ssthresh\u0027 is lowered.\n\nFixes: 16ad3f4022bb (\"tipc: introduce variable window congestion control\")\nAcked-by: Jon Maloy \u003cjmaloy@redhat.com\u003e\nSigned-off-by: Tuong Lien \u003ctuong.t.lien@dektech.com.au\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "5309960e49f5e2363d2814488878a29e944e1be9", "tree": "d12648230149f6b3f119f73015717400f0f770a0", "parents": [ "ae5a44bb970ad8d0f7382cf3fc9738787e3cf19f" ], "author": { "name": "Cambda Zhu", "email": "cambda@linux.alibaba.com", "time": "Wed Apr 15 17:54:04 2020 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 16:22:59 2020 -0700" }, "message": "Documentation: Fix tcp_challenge_ack_limit default value\n\nThe default value of tcp_challenge_ack_limit has been changed from\n100 to 1000 and this patch fixes its documentation.\n\nSigned-off-by: Cambda Zhu \u003ccambda@linux.alibaba.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "ae5a44bb970ad8d0f7382cf3fc9738787e3cf19f", "tree": "8f13834eb217858c61875bb45a5c81d05a4db335", "parents": [ "c8322754642052b3580db8bc3c33fd671a41cdd6" ], "author": { "name": "Jason Yan", "email": "yanaijie@huawei.com", "time": "Wed Apr 15 16:42:48 2020 +0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 16:22:14 2020 -0700" }, "message": "net: tulip: make early_486_chipsets static\n\nFix the following sparse warning:\n\ndrivers/net/ethernet/dec/tulip/tulip_core.c:1280:28: warning: symbol\n\u0027early_486_chipsets\u0027 was not declared. Should it be static?\n\nReported-by: Hulk Robot \u003chulkci@huawei.com\u003e\nSigned-off-by: Jason Yan \u003cyanaijie@huawei.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "c8322754642052b3580db8bc3c33fd671a41cdd6", "tree": "f8765a42faf300a600ea869ecad0a37b1e3c5403", "parents": [ "672e24772aeb45293c86f6176520d98b19cd48a1" ], "author": { "name": "Johan Jonker", "email": "jbx6244@gmail.com", "time": "Wed Apr 15 22:01:49 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 16:21:12 2020 -0700" }, "message": "dt-bindings: net: ethernet-phy: add desciption for ethernet-phy-id1234.d400\n\nThe description below is already in use in\n\u0027rk3228-evb.dts\u0027, \u0027rk3229-xms6.dts\u0027 and \u0027rk3328.dtsi\u0027\nbut somehow never added to a document, so add\n\"ethernet-phy-id1234.d400\", \"ethernet-phy-ieee802.3-c22\"\nfor ethernet-phy nodes on Rockchip platforms to\n\u0027ethernet-phy.yaml\u0027.\n\nSigned-off-by: Johan Jonker \u003cjbx6244@gmail.com\u003e\nAcked-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "672e24772aeb45293c86f6176520d98b19cd48a1", "tree": "921c144f72266307c0e57a8f91752cb7a48e6dd0", "parents": [ "7dba92037baf3fa00b4880a31fd532542264994c" ], "author": { "name": "Colin Ian King", "email": "colin.king@canonical.com", "time": "Thu Apr 16 00:16:30 2020 +0100" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 16:20:22 2020 -0700" }, "message": "ipv6: remove redundant assignment to variable err\n\nThe variable err is being initialized with a value that is never read\nand it is being updated later with a new value. The initialization is\nredundant and can be removed.\n\nAddresses-Coverity: (\"Unused value\")\nSigned-off-by: Colin Ian King \u003ccolin.king@canonical.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "af15f14c8cfcee515f4e9078889045ad63efefe3", "tree": "1b200b5d57bc5479434ac08daa0b15027d23f06a", "parents": [ "c753924b628551564b6eea3c9896e4a95aa25ed9" ], "author": { "name": "Ondrej Mosnacek", "email": "omosnace@redhat.com", "time": "Tue Apr 14 16:23:51 2020 +0200" }, "committer": { "name": "Paul Moore", "email": "paul@paul-moore.com", "time": "Wed Apr 15 17:23:16 2020 -0400" }, "message": "selinux: free str on error in str_read()\n\nIn [see \"Fixes:\"] I missed the fact that str_read() may give back an\nallocated pointer even if it returns an error, causing a potential\nmemory leak in filename_trans_read_one(). Fix this by making the\nfunction free the allocated string whenever it returns a non-zero value,\nwhich also makes its behavior more obvious and prevents repeating the\nsame mistake in the future.\n\nReported-by: coverity-bot \u003ckeescook+coverity-bot@chromium.org\u003e\nAddresses-Coverity-ID: 1461665 (\"Resource leaks\")\nFixes: c3a276111ea2 (\"selinux: optimize storage of filename transitions\")\nSigned-off-by: Ondrej Mosnacek \u003comosnace@redhat.com\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\nSigned-off-by: Paul Moore \u003cpaul@paul-moore.com\u003e\n" }, { "commit": "7dba92037baf3fa00b4880a31fd532542264994c", "tree": "bb8dda947f92717171d9ad0c1ff7960c369384ad", "parents": [ "87b0f983f66f23762921129fd35966eddc3f2dae" ], "author": { "name": "Jason Gunthorpe", "email": "jgg@mellanox.com", "time": "Tue Apr 14 20:02:07 2020 -0300" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 12:33:29 2020 -0700" }, "message": "net/rds: Use ERR_PTR for rds_message_alloc_sgs()\n\nReturning the error code via a \u0027int *ret\u0027 when the function returns a\npointer is very un-kernely and causes gcc 10\u0027s static analysis to choke:\n\nnet/rds/message.c: In function ‘rds_message_map_pages’:\nnet/rds/message.c:358:10: warning: ‘ret’ may be used uninitialized in this function [-Wmaybe-uninitialized]\n 358 | return ERR_PTR(ret);\n\nUse a typical ERR_PTR return instead.\n\nSigned-off-by: Jason Gunthorpe \u003cjgg@mellanox.com\u003e\nAcked-by: Santosh Shilimkar \u003csantosh.shilimkar@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "87b0f983f66f23762921129fd35966eddc3f2dae", "tree": "9aed796c61f00c603293813d64942403bb0bbdc4", "parents": [ "78b877113f6ed39c96f2e78b8e1fbb13c225377a" ], "author": { "name": "Vladimir Oltean", "email": "vladimir.oltean@nxp.com", "time": "Tue Apr 14 22:36:15 2020 +0300" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 12:27:35 2020 -0700" }, "message": "net: mscc: ocelot: fix untagged packet drops when enslaving to vlan aware bridge\n\nTo rehash a previous explanation given in commit 1c44ce560b4d (\"net:\nmscc: ocelot: fix vlan_filtering when enslaving to bridge before link is\nup\"), the switch driver operates the in a mode where a single VLAN can\nbe transmitted as untagged on a particular egress port. That is the\n\"native VLAN on trunk port\" use case.\n\nThe configuration for this native VLAN is driven in 2 ways:\n - Set the egress port rewriter to strip the VLAN tag for the native\n VID (as it is egress-untagged, after all).\n - Configure the ingress port to drop untagged and priority-tagged\n traffic, if there is no native VLAN. The intention of this setting is\n that a trunk port with no native VLAN should not accept untagged\n traffic.\n\nSince both of the above configurations for the native VLAN should only\nbe done if VLAN awareness is requested, they are actually done from the\nocelot_port_vlan_filtering function, after the basic procedure of\ntoggling the VLAN awareness flag of the port.\n\nBut there\u0027s a problem with that simplistic approach: we are trying to\njuggle with 2 independent variables from a single function:\n - Native VLAN of the port - its value is held in port-\u003evid.\n - VLAN awareness state of the port - currently there are some issues\n here, more on that later*.\nThe actual problem can be seen when enslaving the switch ports to a VLAN\nfiltering bridge:\n 0. The driver configures a pvid of zero for each port, when in\n standalone mode. While the bridge configures a default_pvid of 1 for\n each port that gets added as a slave to it.\n 1. The bridge calls ocelot_port_vlan_filtering with vlan_aware\u003dtrue.\n The VLAN-filtering-dependent portion of the native VLAN\n configuration is done, considering that the native VLAN is 0.\n 2. The bridge calls ocelot_vlan_add with vid\u003d1, pvid\u003dtrue,\n untagged\u003dtrue. The native VLAN changes to 1 (change which gets\n propagated to hardware).\n 3. ??? - nobody calls ocelot_port_vlan_filtering again, to reapply the\n VLAN-filtering-dependent portion of the native VLAN configuration,\n for the new native VLAN of 1. One can notice that after toggling \"ip\n link set dev br0 type bridge vlan_filtering 0 \u0026\u0026 ip link set dev br0\n type bridge vlan_filtering 1\", the new native VLAN finally makes it\n through and untagged traffic finally starts flowing again. But\n obviously that shouldn\u0027t be needed.\n\nSo it is clear that 2 independent variables need to both re-trigger the\nnative VLAN configuration. So we introduce the second variable as\nocelot_port-\u003evlan_aware.\n\n*Actually both the DSA Felix driver and the Ocelot driver already had\neach its own variable:\n - Ocelot: ocelot_port_private-\u003evlan_aware\n - Felix: dsa_port-\u003evlan_filtering\nbut the common Ocelot library needs to work with a single, common,\nvariable, so there is some refactoring done to move the vlan_aware\nproperty from the private structure into the common ocelot_port\nstructure.\n\nFixes: 97bb69e1e36e (\"net: mscc: ocelot: break apart ocelot_vlan_port_apply\")\nSigned-off-by: Vladimir Oltean \u003cvladimir.oltean@nxp.com\u003e\nReviewed-by: Horatiu Vultur \u003choratiu.vultur@microchip.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "78b877113f6ed39c96f2e78b8e1fbb13c225377a", "tree": "e36e369a51d188e1d2cdc11540e3ec182e7afed4", "parents": [ "6058ee09ec5208254f99c7bd9f7bae556563ba3b", "c6c111523d9e697bfb463870759825be5d6caff6" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 11:35:42 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 11:35:42 2020 -0700" }, "message": "Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf\n\nDaniel Borkmann says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\npull-request: bpf 2020-04-15\n\nThe following pull-request contains BPF updates for your *net* tree.\n\nWe\u0027ve added 10 non-merge commits during the last 3 day(s) which contain\na total of 11 files changed, 238 insertions(+), 95 deletions(-).\n\nThe main changes are:\n\n1) Fix offset overflow for BPF_MEM BPF_DW insn mapping on arm32 JIT,\n from Luke Nelson and Xi Wang.\n\n2) Prevent mprotect() to make frozen \u0026 mmap()\u0027ed BPF map writeable\n again, from Andrii Nakryiko and Jann Horn.\n\n3) Fix type of old_fd in bpf_xdp_set_link_opts to int in libbpf and add\n selftests, from Toke Høiland-Jørgensen.\n\n4) Fix AF_XDP to check that headroom cannot be larger than the available\n space in the chunk, from Magnus Karlsson.\n\n5) Fix reset of XDP prog when expected_fd is set, from David Ahern.\n\n6) Fix a segfault in bpftool\u0027s struct_ops command when BTF is not\n available, from Daniel T. Lee.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "6058ee09ec5208254f99c7bd9f7bae556563ba3b", "tree": "b99cf1f50082523b087afc02f8e8c219867057b8", "parents": [ "91fac45cd0061854633036695cf37a11befa8062", "93e2d04a1888668183f3fb48666e90b9b31d29e6" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 11:27:23 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Wed Apr 15 11:27:23 2020 -0700" }, "message": "Merge tag \u0027mac80211-for-net-2020-04-15\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211\n\nJohannes Berg says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nA couple of fixes:\n * FTM responder policy netlink validation fix\n (but the only user validates again later)\n * kernel-doc fixes\n * a fix for a race in mac80211 radio registration vs. userspace\n * a mesh channel switch fix\n * a fix for a syzbot reported kasprintf() issue\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "c6c111523d9e697bfb463870759825be5d6caff6", "tree": "fb949e0ba4bb00676e818ac3d3a70efa62781a18", "parents": [ "49b452c382da2c2d1ccee1265cbb92da905c82f7" ], "author": { "name": "Toke Høiland-Jørgensen", "email": "toke@redhat.com", "time": "Tue Apr 14 16:50:25 2020 +0200" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Wed Apr 15 13:26:08 2020 +0200" }, "message": "selftests/bpf: Check for correct program attach/detach in xdp_attach test\n\nDavid Ahern noticed that there was a bug in the EXPECTED_FD code so\nprograms did not get detached properly when that parameter was supplied.\nThis case was not included in the xdp_attach tests; so let\u0027s add it to be\nsure that such a bug does not sneak back in down.\n\nFixes: 87854a0b57b3 (\"selftests/bpf: Add tests for attaching XDP programs\")\nReported-by: David Ahern \u003cdsahern@gmail.com\u003e\nSigned-off-by: Toke Høiland-Jørgensen \u003ctoke@redhat.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nAcked-by: Song Liu \u003csongliubraving@fb.com\u003e\nLink: https://lore.kernel.org/bpf/20200414145025.182163-2-toke@redhat.com\n" }, { "commit": "49b452c382da2c2d1ccee1265cbb92da905c82f7", "tree": "940a104c0547f3aa76fb064ec6f8f44eec5b0914", "parents": [ "25498a1969bf3687c29c29bbac92821d7a0f8b4a" ], "author": { "name": "Toke Høiland-Jørgensen", "email": "toke@redhat.com", "time": "Tue Apr 14 16:50:24 2020 +0200" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Wed Apr 15 13:26:08 2020 +0200" }, "message": "libbpf: Fix type of old_fd in bpf_xdp_set_link_opts\n\nThe \u0027old_fd\u0027 parameter used for atomic replacement of XDP programs is\nsupposed to be an FD, but was left as a u32 from an earlier iteration of\nthe patch that added it. It was converted to an int when read, so things\nworked correctly even with negative values, but better change the\ndefinition to correctly reflect the intention.\n\nFixes: bd5ca3ef93cd (\"libbpf: Add function to set link XDP fd while specifying old program\")\nReported-by: David Ahern \u003cdsahern@gmail.com\u003e\nSigned-off-by: Toke Høiland-Jørgensen \u003ctoke@redhat.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nAcked-by: David Ahern \u003cdsahern@gmail.com\u003e\nAcked-by: Song Liu \u003csongliubraving@fb.com\u003e\nLink: https://lore.kernel.org/bpf/20200414145025.182163-1-toke@redhat.com\n" }, { "commit": "25498a1969bf3687c29c29bbac92821d7a0f8b4a", "tree": "cc579427faea0bdaa8d7b4087eb048c863ac7906", "parents": [ "99e3a236dd43d06c65af0a2ef9cb44306aef6e02" ], "author": { "name": "Andrii Nakryiko", "email": "andriin@fb.com", "time": "Tue Apr 14 11:26:45 2020 -0700" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Wed Apr 15 13:22:43 2020 +0200" }, "message": "libbpf: Always specify expected_attach_type on program load if supported\n\nFor some types of BPF programs that utilize expected_attach_type, libbpf won\u0027t\nset load_attr.expected_attach_type, even if expected_attach_type is known from\nsection definition. This was done to preserve backwards compatibility with old\nkernels that didn\u0027t recognize expected_attach_type attribute yet (which was\nadded in 5e43f899b03a (\"bpf: Check attach type at prog load time\"). But this\nis problematic for some BPF programs that utilize newer features that require\nkernel to know specific expected_attach_type (e.g., extended set of return\ncodes for cgroup_skb/egress programs).\n\nThis patch makes libbpf specify expected_attach_type by default, but also\ndetect support for this field in kernel and not set it during program load.\nThis allows to have a good metadata for bpf_program\n(e.g., bpf_program__get_extected_attach_type()), but still work with old\nkernels (for cases where it can work at all).\n\nAdditionally, due to expected_attach_type being always set for recognized\nprogram types, bpf_program__attach_cgroup doesn\u0027t have to do extra checks to\ndetermine correct attach type, so remove that additional logic.\n\nAlso adjust section_names selftest to account for this change.\n\nMore detailed discussion can be found in [0].\n\n [0] https://lore.kernel.org/bpf/20200412003604.GA15986@rdna-mbp.dhcp.thefacebook.com/\n\nFixes: 5cf1e9145630 (\"bpf: cgroup inet skb programs can return 0 to 3\")\nFixes: 5e43f899b03a (\"bpf: Check attach type at prog load time\")\nReported-by: Andrey Ignatov \u003crdna@fb.com\u003e\nSigned-off-by: Andrii Nakryiko \u003candriin@fb.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nAcked-by: Song Liu \u003csongliubraving@fb.com\u003e\nAcked-by: Andrey Ignatov \u003crdna@fb.com\u003e\nLink: https://lore.kernel.org/bpf/20200414182645.1368174-1-andriin@fb.com\n" }, { "commit": "99e3a236dd43d06c65af0a2ef9cb44306aef6e02", "tree": "14527dbe4aed7324672dfc119739886f523697d0", "parents": [ "89f33dcadb349eb926a92633e2c5f61466afc596" ], "author": { "name": "Magnus Karlsson", "email": "magnus.karlsson@intel.com", "time": "Tue Apr 14 09:35:15 2020 +0200" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Wed Apr 15 13:07:18 2020 +0200" }, "message": "xsk: Add missing check on user supplied headroom size\n\nAdd a check that the headroom cannot be larger than the available\nspace in the chunk. In the current code, a malicious user can set the\nheadroom to a value larger than the chunk size minus the fixed XDP\nheadroom. That way packets with a length larger than the supported\nsize in the umem could get accepted and result in an out-of-bounds\nwrite.\n\nFixes: c0c77d8fb787 (\"xsk: add user memory registration support sockopt\")\nReported-by: Bui Quang Minh \u003cminhquangbui99@gmail.com\u003e\nSigned-off-by: Magnus Karlsson \u003cmagnus.karlsson@intel.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nLink: https://bugzilla.kernel.org/show_bug.cgi?id\u003d207225\nLink: https://lore.kernel.org/bpf/1586849715-23490-1-git-send-email-magnus.karlsson@intel.com\n" }, { "commit": "93e2d04a1888668183f3fb48666e90b9b31d29e6", "tree": "9d742c8b081a3ffef0f6239204b381aaabe833ec", "parents": [ "52e04b4ce5d03775b6a78f3ed1097480faacc9fd" ], "author": { "name": "Tamizh chelvam", "email": "tamizhr@codeaurora.org", "time": "Sat Mar 28 19:23:24 2020 +0530" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Wed Apr 15 09:54:26 2020 +0200" }, "message": "mac80211: fix channel switch trigger from unknown mesh peer\n\nPreviously mesh channel switch happens if beacon contains\nCSA IE without checking the mesh peer info. Due to that\nchannel switch happens even if the beacon is not from\nits own mesh peer. Fixing that by checking if the CSA\noriginated from the same mesh network before proceeding\nfor channel switch.\n\nSigned-off-by: Tamizh chelvam \u003ctamizhr@codeaurora.org\u003e\nLink: https://lore.kernel.org/r/1585403604-29274-1-git-send-email-tamizhr@codeaurora.org\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "52e04b4ce5d03775b6a78f3ed1097480faacc9fd", "tree": "52ed2229408e9a93884f3b6ade206abba0ef1428", "parents": [ "a710d21451ff2917b9004b65ba2f0db6380671d5" ], "author": { "name": "Sumit Garg", "email": "sumit.garg@linaro.org", "time": "Tue Apr 07 15:40:55 2020 +0530" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Wed Apr 15 09:31:58 2020 +0200" }, "message": "mac80211: fix race in ieee80211_register_hw()\n\nA race condition leading to a kernel crash is observed during invocation\nof ieee80211_register_hw() on a dragonboard410c device having wcn36xx\ndriver built as a loadable module along with a wifi manager in user-space\nwaiting for a wifi device (wlanX) to be active.\n\nSequence diagram for a particular kernel crash scenario:\n\n user-space ieee80211_register_hw() ieee80211_tasklet_handler()\n ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n | | |\n |\u003c---phy0----wiphy_register() |\n |-----iwd if_add----\u003e| |\n | |\u003c---IRQ----(RX packet)\n | Kernel crash |\n | due to unallocated |\n | workqueue. |\n | | |\n | alloc_ordered_workqueue() |\n | | |\n | Misc wiphy init. |\n | | |\n | ieee80211_if_add() |\n | | |\n\nAs evident from above sequence diagram, this race condition isn\u0027t specific\nto a particular wifi driver but rather the initialization sequence in\nieee80211_register_hw() needs to be fixed. So re-order the initialization\nsequence and the updated sequence diagram would look like:\n\n user-space ieee80211_register_hw() ieee80211_tasklet_handler()\n ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n | | |\n | alloc_ordered_workqueue() |\n | | |\n | Misc wiphy init. |\n | | |\n |\u003c---phy0----wiphy_register() |\n |-----iwd if_add----\u003e| |\n | |\u003c---IRQ----(RX packet)\n | | |\n | ieee80211_if_add() |\n | | |\n\nCc: stable@vger.kernel.org\nSigned-off-by: Sumit Garg \u003csumit.garg@linaro.org\u003e\nLink: https://lore.kernel.org/r/1586254255-28713-1-git-send-email-sumit.garg@linaro.org\n[Johannes: fix rtnl imbalances]\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "0bbe7f719985efd9adb3454679ecef0984cb6800", "tree": "88dbd9419d122a5ef82320fece3781ec607052ea", "parents": [ "8f3d9f354286745c751374f5f1fcafee6b3f3136" ], "author": { "name": "Xiao Yang", "email": "yangx.jy@cn.fujitsu.com", "time": "Tue Apr 14 09:51:45 2020 +0800" }, "committer": { "name": "Steven Rostedt (VMware)", "email": "rostedt@goodmis.org", "time": "Tue Apr 14 22:02:10 2020 -0400" }, "message": "tracing: Fix the race between registering \u0027snapshot\u0027 event trigger and triggering \u0027snapshot\u0027 operation\n\nTraced event can trigger \u0027snapshot\u0027 operation(i.e. calls snapshot_trigger()\nor snapshot_count_trigger()) when register_snapshot_trigger() has completed\nregistration but doesn\u0027t allocate buffer for \u0027snapshot\u0027 event trigger. In\nthe rare case, \u0027snapshot\u0027 operation always detects the lack of allocated\nbuffer so make register_snapshot_trigger() allocate buffer first.\n\ntrigger-snapshot.tc in kselftest reproduces the issue on slow vm:\n-----------------------------------------------------------\ncat trace\n...\nftracetest-3028 [002] .... 236.784290: sched_process_fork: comm\u003dftracetest pid\u003d3028 child_comm\u003dftracetest child_pid\u003d3036\n \u003c...\u003e-2875 [003] .... 240.460335: tracing_snapshot_instance_cond: *** SNAPSHOT NOT ALLOCATED ***\n \u003c...\u003e-2875 [003] .... 240.460338: tracing_snapshot_instance_cond: *** stopping trace here! ***\n-----------------------------------------------------------\n\nLink: http://lkml.kernel.org/r/20200414015145.66236-1-yangx.jy@cn.fujitsu.com\n\nCc: stable@vger.kernel.org\nFixes: 93e31ffbf417a (\"tracing: Add \u0027snapshot\u0027 event trigger command\")\nSigned-off-by: Xiao Yang \u003cyangx.jy@cn.fujitsu.com\u003e\nSigned-off-by: Steven Rostedt (VMware) \u003crostedt@goodmis.org\u003e\n" }, { "commit": "91fac45cd0061854633036695cf37a11befa8062", "tree": "395d2def7dbc1aed505bc7e644409261602c8056", "parents": [ "c799fca8baf18d1bbbbad6c3b736eefbde8bdb90", "8f48c2ac85eda8d8a01c83c6d73f891c43ef182d" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:48:09 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:48:09 2020 -0700" }, "message": "Merge branch \u0027Fix-88x3310-leaving-power-save-mode\u0027\n\nRussell King says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nFix 88x3310 leaving power save mode\n\nThis series fixes a problem with the 88x3310 PHY on Macchiatobin\ncoming out of powersave mode noticed by Matteo Croce. It seems\nthat certain PHY firmwares do not properly exit powersave mode,\nresulting in a fibre link not coming up.\n\nThe solution appears to be to soft-reset the PHY after clearing\nthe powersave bit.\n\nWe add support for reporting the PHY firmware version to the kernel\nlog, and use it to trigger this new behaviour if we have v0.3.x.x\nor more recent firmware on the PHY. This, however, is a guess as\nthe firmware revision documentation does not mention this issue,\nand we know that v0.2.1.0 works without this fix but v0.3.3.0 and\nlater does not.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "8f48c2ac85eda8d8a01c83c6d73f891c43ef182d", "tree": "395d2def7dbc1aed505bc7e644409261602c8056", "parents": [ "dd649b4ff0127559950965d739cc63efae50ecd9" ], "author": { "name": "Russell King", "email": "rmk+kernel@armlinux.org.uk", "time": "Tue Apr 14 20:49:08 2020 +0100" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:48:09 2020 -0700" }, "message": "net: marvell10g: soft-reset the PHY when coming out of low power\n\nSoft-reset the PHY when coming out of low power mode, which seems to\nbe necessary with firmware versions 0.3.3.0 and 0.3.10.0.\n\nThis depends on (\"net: marvell10g: report firmware version\")\n\nFixes: c9cc1c815d36 (\"net: phy: marvell10g: place in powersave mode at probe\")\nReported-by: Matteo Croce \u003cmcroce@redhat.com\u003e\nTested-by: Matteo Croce \u003cmcroce@redhat.com\u003e\nReviewed-by: Andrew Lunn \u003candrew@lunn.ch\u003e\nSigned-off-by: Russell King \u003crmk+kernel@armlinux.org.uk\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "dd649b4ff0127559950965d739cc63efae50ecd9", "tree": "d08253cc56e3406890362b30c6126c9b230ecafc", "parents": [ "c799fca8baf18d1bbbbad6c3b736eefbde8bdb90" ], "author": { "name": "Russell King", "email": "rmk+kernel@armlinux.org.uk", "time": "Tue Apr 14 20:49:03 2020 +0100" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:48:09 2020 -0700" }, "message": "net: marvell10g: report firmware version\n\nReport the firmware version when probing the PHY to allow issues\nattributable to firmware to be diagnosed.\n\nTested-by: Matteo Croce \u003cmcroce@redhat.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@armlinux.org.uk\u003e\nReviewed-by: Andrew Lunn \u003candrew@lunn.ch\u003e\nReviewed-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "c799fca8baf18d1bbbbad6c3b736eefbde8bdb90", "tree": "74ece70e1be1be042bb1c82c0f3b25bd7fbf17d8", "parents": [ "a7a0d6269652846671312b29992143f56e2866b8" ], "author": { "name": "Jason Gunthorpe", "email": "jgg@mellanox.com", "time": "Tue Apr 14 12:27:08 2020 -0300" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:44:54 2020 -0700" }, "message": "net/cxgb4: Check the return from t4_query_params properly\n\nPositive return values are also failures that don\u0027t set val,\nalthough this probably can\u0027t happen. Fixes gcc 10 warning:\n\ndrivers/net/ethernet/chelsio/cxgb4/t4_hw.c: In function ‘t4_phy_fw_ver’:\ndrivers/net/ethernet/chelsio/cxgb4/t4_hw.c:3747:14: warning: ‘val’ may be used uninitialized in this function [-Wmaybe-uninitialized]\n 3747 | *phy_fw_ver \u003d val;\n\nFixes: 01b6961410b7 (\"cxgb4: Add PHY firmware support for T420-BT cards\")\nSigned-off-by: Jason Gunthorpe \u003cjgg@mellanox.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "a7a0d6269652846671312b29992143f56e2866b8", "tree": "18b87435613ac99cd695e8ca0f05f7bb9c4d6f7c", "parents": [ "047c7308ea09e69875302bacbba711b5a154b609" ], "author": { "name": "Atsushi Nemoto", "email": "atsushi.nemoto@sord.co.jp", "time": "Tue Apr 14 10:12:34 2020 +0900" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:39:07 2020 -0700" }, "message": "net: stmmac: socfpga: Allow all RGMII modes\n\nAllow all the RGMII modes to be used. (Not only \"rgmii\", \"rgmii-id\"\nbut \"rgmii-txid\", \"rgmii-rxid\")\n\nSigned-off-by: Atsushi Nemoto \u003catsushi.nemoto@sord.co.jp\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "047c7308ea09e69875302bacbba711b5a154b609", "tree": "6f64bee195b93659e90e5cf2b4e6f8f45473a54c", "parents": [ "bec8141a17b1af160aa9ff652a74f69ef31f48c7", "3be98b2d5fbca3da7c4df0477eed95bfb5b83d64" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:33:26 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:33:26 2020 -0700" }, "message": "Merge branch \u0027mv88e6xxx-fixed-link-fixes\u0027\n\nAndrew Lunn says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nmv88e6xxx fixed link fixes\n\nRecent changes for how the MAC is configured broke fixed links, as\nused by CPU/DSA ports, and for SFPs when phylink cannot be used. The\nfirst fix is unchanged from v1. The second fix takes a different\nsolution than v1. If a CPU or DSA port is known to have a PHYLINK\ninstance, configure the port down before instantiating the PHYLINK, so\nit is in the down state as expected by PHYLINK.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "3be98b2d5fbca3da7c4df0477eed95bfb5b83d64", "tree": "6f64bee195b93659e90e5cf2b4e6f8f45473a54c", "parents": [ "34b5e6a33c1a8e466c3a73fd437f66fb16cb83ea" ], "author": { "name": "Andrew Lunn", "email": "andrew@lunn.ch", "time": "Tue Apr 14 02:34:39 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:33:26 2020 -0700" }, "message": "net: dsa: Down cpu/dsa ports phylink will control\n\nDSA and CPU ports can be configured in two ways. By default, the\ndriver should configure such ports to there maximum bandwidth. For\nmost use cases, this is sufficient. When this default is insufficient,\na phylink instance can be bound to such ports, and phylink will\nconfigure the port, e.g. based on fixed-link properties. phylink\nassumes the port is initially down. Given that the driver should have\nalready configured it to its maximum speed, ask the driver to down\nthe port before instantiating the phylink instance.\n\nFixes: 30c4a5b0aad8 (\"net: mv88e6xxx: use resolved link config in mac_link_up()\")\nSigned-off-by: Andrew Lunn \u003candrew@lunn.ch\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "34b5e6a33c1a8e466c3a73fd437f66fb16cb83ea", "tree": "5b35c8ebf492e31bc7c663e2a110718a1f76b5a0", "parents": [ "bec8141a17b1af160aa9ff652a74f69ef31f48c7" ], "author": { "name": "Andrew Lunn", "email": "andrew@lunn.ch", "time": "Tue Apr 14 02:34:38 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:33:25 2020 -0700" }, "message": "net: dsa: mv88e6xxx: Configure MAC when using fixed link\n\nThe 88e6185 is reporting it has detected a PHY, when a port is\nconnected to an SFP. As a result, the fixed-phy configuration is not\nbeing applied. That then breaks packet transfer, since the port is\nreported as being down.\n\nAdd additional conditions to check the interface mode, and if it is\nfixed always configure the port on link up/down, independent of the\nPPU status.\n\nFixes: 30c4a5b0aad8 (\"net: mv88e6xxx: use resolved link config in mac_link_up()\")\nSigned-off-by: Andrew Lunn \u003candrew@lunn.ch\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "bec8141a17b1af160aa9ff652a74f69ef31f48c7", "tree": "c167f783dabb068512bf3bb3bcc4d020740f850c", "parents": [ "0e631eee17dcea576ab922fa70e4fdbd596ee452", "2c0df9f9eddbc87fa2ef8da86264995404d816b9" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:30:14 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:30:14 2020 -0700" }, "message": "Merge branch \u0027ionic-address-automated-build-complaints\u0027\n\nShannon Nelson says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nionic: address automated build complaints\n\nKernel build checks found a couple of things to improve.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "2c0df9f9eddbc87fa2ef8da86264995404d816b9", "tree": "c167f783dabb068512bf3bb3bcc4d020740f850c", "parents": [ "555cd19d0c6a23b3faef949bccca4822cccc2eb7" ], "author": { "name": "Shannon Nelson", "email": "snelson@pensando.io", "time": "Mon Apr 13 10:33:11 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:30:14 2020 -0700" }, "message": "ionic: fix unused assignment\n\nRemove an unused initialized value.\n\nFixes: 7e4d47596b68 (\"ionic: replay filters after fw upgrade\")\nReported-by: kbuild test robot \u003clkp@intel.com\u003e\nSigned-off-by: Shannon Nelson \u003csnelson@pensando.io\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "555cd19d0c6a23b3faef949bccca4822cccc2eb7", "tree": "a8f1dae7bfd164e90efd57e323a0bd3f9ed61ee0", "parents": [ "0e631eee17dcea576ab922fa70e4fdbd596ee452" ], "author": { "name": "Shannon Nelson", "email": "snelson@pensando.io", "time": "Mon Apr 13 10:33:10 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:30:14 2020 -0700" }, "message": "ionic: add dynamic_debug header\n\nAdd the appropriate header for using dynamic_hex_dump(), which\nseems to be incidentally included in some configurations but\nnot all.\n\nFixes: 7e4d47596b68 (\"ionic: replay filters after fw upgrade\")\nReported-by: Randy Dunlap \u003crdunlap@infradead.org\u003e\nSigned-off-by: Shannon Nelson \u003csnelson@pensando.io\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "0e631eee17dcea576ab922fa70e4fdbd596ee452", "tree": "95eaeadb8b51a9087a5ef567ecc262ebe06edf52", "parents": [ "68dac3eb50be32957ae6e1e6da9281a3b7c6658b" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 13:57:14 2020 +0100" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:26:47 2020 -0700" }, "message": "rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket\n\nFix the DATA packet transmission to disable nofrag for UDPv4 on an AF_INET6\nsocket as well as UDPv6 when trying to transmit fragmentably.\n\nWithout this, packets filled to the normal size used by the kernel AFS\nclient of 1412 bytes be rejected by udp_sendmsg() with EMSGSIZE\nimmediately. The -\u003esk_error_report() notification hook is called, but\nrxrpc doesn\u0027t generate a trace for it.\n\nThis is a temporary fix; a more permanent solution needs to involve\nchanging the size of the packets being filled in accordance with the MTU,\nwhich isn\u0027t currently done in AF_RXRPC. The reason for not doing so was\nthat, barring the last packet in an rx jumbo packet, jumbos can only be\nassembled out of 1412-byte packets - and the plan was to construct jumbos\non the fly at transmission time.\n\nAlso, there\u0027s no point turning on IPV6_MTU_DISCOVER, since IPv6 has to\nengage in this anyway since fragmentation is only done by the sender. We\ncan then condense the switch-statement in rxrpc_send_data_packet().\n\nFixes: 75b54cb57ca3 (\"rxrpc: Add IPv6 support\")\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "68dac3eb50be32957ae6e1e6da9281a3b7c6658b", "tree": "444a7163a09ffcd8d4fef13e3d4d8af66cde92a4", "parents": [ "82f35276c64ff720de11fba31fd6369b45647a2e" ], "author": { "name": "Atsushi Nemoto", "email": "atsushi.nemoto@sord.co.jp", "time": "Fri Apr 10 12:16:16 2020 +0900" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 16:25:30 2020 -0700" }, "message": "net: phy: micrel: use genphy_read_status for KSZ9131\n\nKSZ9131 will not work with some switches due to workaround for KSZ9031\nintroduced in commit d2fd719bcb0e83cb39cfee22ee800f98a56eceb3\n(\"net/phy: micrel: Add workaround for bad autoneg\").\nUse genphy_read_status instead of dedicated ksz9031_read_status.\n\nFixes: bff5b4b37372 (\"net: phy: micrel: add Microchip KSZ9131 initial driver\")\nSigned-off-by: Atsushi Nemoto \u003catsushi.nemoto@sord.co.jp\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "82f35276c64ff720de11fba31fd6369b45647a2e", "tree": "d2c1df215c46e954c4a401c9f3b52e36762ecef1", "parents": [ "664d035c4707ac8643c2846d1a1d4cdf9ce89b90", "7dc7c41607d192ff660ba4ea82d517745c1d7523" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 13:07:19 2020 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Tue Apr 14 13:07:19 2020 -0700" }, "message": "Merge tag \u0027wireless-drivers-2020-04-14\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers\n\nKalle Valo says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nwireless-drivers fixes for v5.7\n\nFirst set of fixes for v5.6. Fixes for a crash and for two compiler\nwarnings.\n\nbrcmfmac\n\n* fix a crash related to monitor interface\n\nath11k\n\n* fix compiler warnings without CONFIG_THERMAL\n\nrtw88\n\n* fix compiler warnings related to suspend and resume functions\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "89f33dcadb349eb926a92633e2c5f61466afc596", "tree": "f72000dd6eece4b474b47754752c5ccd038b9637", "parents": [ "dfa74909cb6b846cbdabfc2c3c7de1d507fca075" ], "author": { "name": "Zou Wei", "email": "zou_wei@huawei.com", "time": "Mon Apr 13 19:57:56 2020 +0800" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Tue Apr 14 21:40:06 2020 +0200" }, "message": "bpf: remove unneeded conversion to bool in __mark_reg_unknown\n\nThis issue was detected by using the Coccinelle software:\n\n kernel/bpf/verifier.c:1259:16-21: WARNING: conversion to bool not needed here\n\nThe conversion to bool is unneeded, remove it.\n\nReported-by: Hulk Robot \u003chulkci@huawei.com\u003e\nSigned-off-by: Zou Wei \u003czou_wei@huawei.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nAcked-by: Song Liu \u003csongliubraving@fb.com\u003e\nLink: https://lore.kernel.org/bpf/1586779076-101346-1-git-send-email-zou_wei@huawei.com\n" }, { "commit": "dfa74909cb6b846cbdabfc2c3c7de1d507fca075", "tree": "abcec0eda77f457704330ae51338d22e98d656c9", "parents": [ "96b2eb6e77959b4b52f80e7a61d03db77606aac6" ], "author": { "name": "David Ahern", "email": "dsahern@gmail.com", "time": "Sun Apr 12 07:32:04 2020 -0600" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Tue Apr 14 21:38:02 2020 +0200" }, "message": "xdp: Reset prog in dev_change_xdp_fd when fd is negative\n\nThe commit mentioned in the Fixes tag reuses the local prog variable\nwhen looking up an expected_fd. The variable is not reset when fd \u003c 0\ncausing a detach with the expected_fd set to actually call\ndev_xdp_install for the existing program. The end result is that the\ndetach does not happen.\n\nFixes: 92234c8f15c8 (\"xdp: Support specifying expected existing program when attaching XDP\")\nSigned-off-by: David Ahern \u003cdsahern@gmail.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nReviewed-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\nReviewed-by: Toke Høiland-Jørgensen \u003ctoke@redhat.com\u003e\nLink: https://lore.kernel.org/bpf/20200412133204.43847-1-dsahern@kernel.org\n" }, { "commit": "96b2eb6e77959b4b52f80e7a61d03db77606aac6", "tree": "4b2925662cb05bc2667f432372bcbc02956b0439", "parents": [ "642c1654702731ab42a3be771bebbd6ef938f0dc" ], "author": { "name": "Daniel T. Lee", "email": "danieltimlee@gmail.com", "time": "Fri Apr 10 11:06:12 2020 +0900" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Tue Apr 14 21:33:53 2020 +0200" }, "message": "tools, bpftool: Fix struct_ops command invalid pointer free\n\nIn commit 65c93628599d (\"bpftool: Add struct_ops support\") a new\ntype of command named struct_ops has been added. This command requires\na kernel with CONFIG_DEBUG_INFO_BTF\u003dy set and for retrieving BTF info\nin bpftool, the helper get_btf_vmlinux() is used.\n\nWhen running this command on kernel without BTF debug info, this will\nlead to \u0027btf_vmlinux\u0027 variable being an invalid(error) pointer. And by\nthis, btf_free() causes a segfault when executing \u0027bpftool struct_ops\u0027.\n\nThis commit adds pointer validation with IS_ERR not to free invalid\npointer, and this will fix the segfault issue.\n\nFixes: 65c93628599d (\"bpftool: Add struct_ops support\")\nSigned-off-by: Daniel T. Lee \u003cdanieltimlee@gmail.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nAcked-by: Martin KaFai Lau \u003ckafai@fb.com\u003e\nLink: https://lore.kernel.org/bpf/20200410020612.2930667-1-danieltimlee@gmail.com\n" }, { "commit": "642c1654702731ab42a3be771bebbd6ef938f0dc", "tree": "766a7490a2cdb507523f1369f73ec902fb699e85", "parents": [ "1f6cb19be2e231fe092f40decb71f066eba090d7" ], "author": { "name": "Andrii Nakryiko", "email": "andriin@fb.com", "time": "Fri Apr 10 13:26:13 2020 -0700" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Tue Apr 14 21:28:57 2020 +0200" }, "message": "selftests/bpf: Validate frozen map contents stays frozen\n\nTest that frozen and mmap()\u0027ed BPF map can\u0027t be mprotect()\u0027ed as writable or\nexecutable memory. Also validate that \"downgrading\" from writable to read-only\ndoesn\u0027t screw up internal writable count accounting for the purposes of map\nfreezing.\n\nSigned-off-by: Andrii Nakryiko \u003candriin@fb.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nLink: https://lore.kernel.org/bpf/20200410202613.3679837-2-andriin@fb.com\n" }, { "commit": "1f6cb19be2e231fe092f40decb71f066eba090d7", "tree": "f403308df2df8c60baedaa5eed2444e617e320f0", "parents": [ "4178417cc5359c329790a4a8f4a6604612338cca" ], "author": { "name": "Andrii Nakryiko", "email": "andriin@fb.com", "time": "Fri Apr 10 13:26:12 2020 -0700" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Tue Apr 14 21:28:57 2020 +0200" }, "message": "bpf: Prevent re-mmap()\u0027ing BPF map as writable for initially r/o mapping\n\nVM_MAYWRITE flag during initial memory mapping determines if already mmap()\u0027ed\npages can be later remapped as writable ones through mprotect() call. To\nprevent user application to rewrite contents of memory-mapped as read-only and\nsubsequently frozen BPF map, remove VM_MAYWRITE flag completely on initially\nread-only mapping.\n\nAlternatively, we could treat any memory-mapping on unfrozen map as writable\nand bump writecnt instead. But there is little legitimate reason to map\nBPF map as read-only and then re-mmap() it as writable through mprotect(),\ninstead of just mmap()\u0027ing it as read/write from the very beginning.\n\nAlso, at the suggestion of Jann Horn, drop unnecessary refcounting in mmap\noperations. We can just rely on VMA holding reference to BPF map\u0027s file\nproperly.\n\nFixes: fc9702273e2e (\"bpf: Add mmap() support for BPF_MAP_TYPE_ARRAY\")\nReported-by: Jann Horn \u003cjannh@google.com\u003e\nSigned-off-by: Andrii Nakryiko \u003candriin@fb.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nReviewed-by: Jann Horn \u003cjannh@google.com\u003e\nLink: https://lore.kernel.org/bpf/20200410202613.3679837-1-andriin@fb.com\n" }, { "commit": "4178417cc5359c329790a4a8f4a6604612338cca", "tree": "4816744db5c1f822f9a5b55822213b890617f660", "parents": [ "e154659ba39a1c2be576aaa0a5bda8088d707950" ], "author": { "name": "Luke Nelson", "email": "lukenels@cs.washington.edu", "time": "Thu Apr 09 15:17:52 2020 -0700" }, "committer": { "name": "Daniel Borkmann", "email": "daniel@iogearbox.net", "time": "Tue Apr 14 21:27:54 2020 +0200" }, "message": "arm, bpf: Fix offset overflow for BPF_MEM BPF_DW\n\nThis patch fixes an incorrect check in how immediate memory offsets are\ncomputed for BPF_DW on arm.\n\nFor BPF_LDX/ST/STX + BPF_DW, the 32-bit arm JIT breaks down an 8-byte\naccess into two separate 4-byte accesses using off+0 and off+4. If off\nfits in imm12, the JIT emits a ldr/str instruction with the immediate\nand avoids the use of a temporary register. While the current check off\n\u003c\u003d 0xfff ensures that the first immediate off+0 doesn\u0027t overflow imm12,\nit\u0027s not sufficient for the second immediate off+4, which may cause the\nsecond access of BPF_DW to read/write the wrong address.\n\nThis patch fixes the problem by changing the check to\noff \u003c\u003d 0xfff - 4 for BPF_DW, ensuring off+4 will never overflow.\n\nA side effect of simplifying the check is that it now allows using\nnegative immediate offsets in ldr/str. This means that small negative\noffsets can also avoid the use of a temporary register.\n\nThis patch introduces no new failures in test_verifier or test_bpf.c.\n\nFixes: c5eae692571d6 (\"ARM: net: bpf: improve 64-bit store implementation\")\nFixes: ec19e02b343db (\"ARM: net: bpf: fix LDX instructions\")\nCo-developed-by: Xi Wang \u003cxi.wang@gmail.com\u003e\nSigned-off-by: Xi Wang \u003cxi.wang@gmail.com\u003e\nSigned-off-by: Luke Nelson \u003cluke.r.nels@gmail.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nLink: https://lore.kernel.org/bpf/20200409221752.28448-1-luke.r.nels@gmail.com\n" }, { "commit": "8632e9b5645bbc2331d21d892b0d6961c1a08429", "tree": "df3fbdae9311a15b7c36da9db915e6b0a5f53ddc", "parents": [ "6cc9306b8fc03019e81e4f10c93ff0528cba5217", "f3a99e761efa616028b255b4de58e9b5b87c5545" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Apr 14 11:58:04 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Apr 14 11:58:04 2020 -0700" }, "message": "Merge tag \u0027hyperv-fixes-signed\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux\n\nPull hyperv fixes from Wei Liu:\n\n - a series from Tianyu Lan to fix crash reporting on Hyper-V\n\n - three miscellaneous cleanup patches\n\n* tag \u0027hyperv-fixes-signed\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux:\n x86/Hyper-V: Report crash data in die() when panic_on_oops is set\n x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not set\n x86/Hyper-V: Report crash register data or kmsg before running crash kernel\n x86/Hyper-V: Trigger crash enlightenment only once during system crash.\n x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump\n x86/Hyper-V: Unload vmbus channel in hv panic callback\n x86: hyperv: report value of misc_features\n hv_debugfs: Make hv_debug_root static\n hv: hyperv_vmbus.h: Replace zero-length array with flexible-array member\n" }, { "commit": "6cc9306b8fc03019e81e4f10c93ff0528cba5217", "tree": "a725667615bb43c91a73b9f18256c64b4b03ef72", "parents": [ "f4cd66682b2728734b2fc44f5f1e83a5c740b5cf", "34c51814b2b87cb2e5a98c92fe957db2ee8e27f4" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Apr 14 11:51:30 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Apr 14 11:51:30 2020 -0700" }, "message": "Merge tag \u0027for-5.7-rc1-tag\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux\n\nPull btrfs fixes from David Sterba:\n \"We have a few regressions and one fix for stable:\n\n - revert fsync optimization\n\n - fix lost i_size update\n\n - fix a space accounting leak\n\n - build fix, add back definition of a deprecated ioctl flag\n\n - fix search condition for old roots in relocation\"\n\n* tag \u0027for-5.7-rc1-tag\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:\n btrfs: re-instantiate the removed BTRFS_SUBVOL_CREATE_ASYNC definition\n btrfs: fix reclaim counter leak of space_info objects\n btrfs: make full fsyncs always operate on the entire file again\n btrfs: fix lost i_size update after cloning inline extent\n btrfs: check commit root generation in should_ignore_root\n" }, { "commit": "f4cd66682b2728734b2fc44f5f1e83a5c740b5cf", "tree": "f415c4f19d692546eae424427bdcbe2283e52b1a", "parents": [ "ac4075bca10b29bfa0fed99d0a11826ef9ee5e69", "40fc81027f892284ce31f8b6de1e497f5b47e71f" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Apr 14 11:47:30 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Apr 14 11:47:30 2020 -0700" }, "message": "Merge tag \u0027afs-fixes-20200413\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs\n\nPull AFS fixes from David Howells:\n\n - Fix the decoding of fetched file status records so that the xdr\n pointer is advanced under all circumstances.\n\n - Fix the decoding of a fetched file status record that indicates an\n inline abort (ie. an error) so that it sets the flag saying the\n decoder stored the abort code.\n\n - Fix the decoding of the result of the rename operation so that it\n doesn\u0027t skip the decoding of the second fetched file status (ie. that\n of the dest dir) in the case that the source and dest dirs were the\n same as this causes the xdr pointer not to be advanced, leading to\n incorrect decoding of subsequent parts of the reply.\n\n - Fix the dump of a bad YFSFetchStatus record to dump the full length.\n\n - Fix a race between local editing of directory contents and accessing\n the dir for reading or d_revalidate by using the same lock in both.\n\n - Fix afs_d_revalidate() to not accidentally reverse the version on a\n dentry when it\u0027s meant to be bringing it forward.\n\n* tag \u0027afs-fixes-20200413\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs:\n afs: Fix afs_d_validate() to set the right directory version\n afs: Fix race between post-modification dir edit and readdir/d_revalidate\n afs: Fix length of dump of bad YFSFetchStatus record\n afs: Fix rename operation status delivery\n afs: Fix decoding of inline abort codes from version 1 status records\n afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus()\n" }, { "commit": "7dc7c41607d192ff660ba4ea82d517745c1d7523", "tree": "2add58ca447565e8b3abbbf4af5c23d44641867a", "parents": [ "c9be1a642a7b9ec021e3f32e084dc781b3e5216d" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Wed Apr 08 20:53:51 2020 +0200" }, "committer": { "name": "Kalle Valo", "email": "kvalo@codeaurora.org", "time": "Tue Apr 14 15:45:36 2020 +0300" }, "message": "rtw88: avoid unused function warnings\n\nThe rtw88 driver defines emtpy functions with multiple indirections\nbut gets one of these wrong:\n\ndrivers/net/wireless/realtek/rtw88/pci.c:1347:12: error: \u0027rtw_pci_resume\u0027 defined but not used [-Werror\u003dunused-function]\n 1347 | static int rtw_pci_resume(struct device *dev)\n | ^~~~~~~~~~~~~~\ndrivers/net/wireless/realtek/rtw88/pci.c:1342:12: error: \u0027rtw_pci_suspend\u0027 defined but not used [-Werror\u003dunused-function]\n 1342 | static int rtw_pci_suspend(struct device *dev)\n\nBetter simplify it to rely on the conditional reference in\nSIMPLE_DEV_PM_OPS(), and mark the functions as __maybe_unused to avoid\nwarning about it.\n\nI\u0027m not sure if these are needed at all given that the functions\ndon\u0027t do anything, but they were only recently added.\n\nFixes: 44bc17f7f5b3 (\"rtw88: support wowlan feature for 8822c\")\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nSigned-off-by: Kalle Valo \u003ckvalo@codeaurora.org\u003e\nLink: https://lore.kernel.org/r/20200408185413.218643-1-arnd@arndb.de\n" }, { "commit": "a710d21451ff2917b9004b65ba2f0db6380671d5", "tree": "be499b342601b44ba262b51dca1c01e0292e2dd6", "parents": [ "7ea862048317aa76d0f22334202779a25530980c" ], "author": { "name": "Lothar Rubusch", "email": "l.rubusch@gmail.com", "time": "Wed Apr 08 23:10:13 2020 +0000" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Tue Apr 14 12:40:02 2020 +0200" }, "message": "cfg80211: fix kernel-doc notation\n\nUpdate missing kernel-doc annotations and fix of related warnings\nat \u0027make htmldocs\u0027.\n\nSigned-off-by: Lothar Rubusch \u003cl.rubusch@gmail.com\u003e\nLink: https://lore.kernel.org/r/20200408231013.28370-1-l.rubusch@gmail.com\n[fix indentation, attribute references]\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "7ea862048317aa76d0f22334202779a25530980c", "tree": "777d9da213eb7bb24cf86464afca0908fba178fd", "parents": [ "0e012b4e4b5ec8e064be3502382579dd0bb43269" ], "author": { "name": "Tuomas Tynkkynen", "email": "tuomas.tynkkynen@iki.fi", "time": "Fri Apr 10 15:32:57 2020 +0300" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Tue Apr 14 12:31:46 2020 +0200" }, "message": "mac80211_hwsim: Use kstrndup() in place of kasprintf()\n\nsyzbot reports a warning:\n\nprecision 33020 too large\nWARNING: CPU: 0 PID: 9618 at lib/vsprintf.c:2471 set_precision+0x150/0x180 lib/vsprintf.c:2471\n vsnprintf+0xa7b/0x19a0 lib/vsprintf.c:2547\n kvasprintf+0xb2/0x170 lib/kasprintf.c:22\n kasprintf+0xbb/0xf0 lib/kasprintf.c:59\n hwsim_del_radio_nl+0x63a/0x7e0 drivers/net/wireless/mac80211_hwsim.c:3625\n genl_family_rcv_msg_doit net/netlink/genetlink.c:672 [inline]\n ...\n entry_SYSCALL_64_after_hwframe+0x49/0xbe\n\nThus it seems that kasprintf() with \"%.*s\" format can not be used for\nduplicating a string with arbitrary length. Replace it with kstrndup().\n\nNote that later this string is limited to NL80211_WIPHY_NAME_MAXLEN \u003d\u003d 64,\nbut the code is simpler this way.\n\nReported-by: syzbot+6693adf1698864d21734@syzkaller.appspotmail.com\nReported-by: syzbot+a4aee3f42d7584d76761@syzkaller.appspotmail.com\nCc: stable@kernel.org\nSigned-off-by: Tuomas Tynkkynen \u003ctuomas.tynkkynen@iki.fi\u003e\nLink: https://lore.kernel.org/r/20200410123257.14559-1-tuomas.tynkkynen@iki.fi\n[johannes: add note about length limit]\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "0e012b4e4b5ec8e064be3502382579dd0bb43269", "tree": "b5263d6e9cea3dfa4d29193631c05b5ca776a698", "parents": [ "e154659ba39a1c2be576aaa0a5bda8088d707950" ], "author": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Sun Apr 12 00:40:30 2020 +0200" }, "committer": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Tue Apr 14 12:28:48 2020 +0200" }, "message": "nl80211: fix NL80211_ATTR_FTM_RESPONDER policy\n\nThe nested policy here should be established using the\nNLA_POLICY_NESTED() macro so the length is properly\nfilled in.\n\nCc: stable@vger.kernel.org\nFixes: 81e54d08d9d8 (\"cfg80211: support FTM responder configuration/statistics\")\nLink: https://lore.kernel.org/r/20200412004029.9d0722bb56c8.Ie690bfcc4a1a61ff8d8ca7e475d59fcaa52fb2da@changeid\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n" }, { "commit": "a088b858f16af85e3db359b6c6aaa92dd3bc0921", "tree": "64895ec738952c9e196d845a74c3272d433ba551", "parents": [ "f6103162008dfd37567f240b50e5e1ea7cf2e00c" ], "author": { "name": "Ard Biesheuvel", "email": "ardb@kernel.org", "time": "Fri Apr 10 09:43:20 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:17 2020 +0200" }, "message": "efi/x86: Revert struct layout change to fix kexec boot regression\n\nCommit\n\n 0a67361dcdaa29 (\"efi/x86: Remove runtime table address from kexec EFI setup data\")\n\nremoved the code that retrieves the non-remapped UEFI runtime services\npointer from the data structure provided by kexec, as it was never really\nneeded on the kexec boot path: mapping the runtime services table at its\nnon-remapped address is only needed when calling SetVirtualAddressMap(),\nwhich never happens during a kexec boot in the first place.\n\nHowever, dropping the \u0027runtime\u0027 member from struct efi_setup_data was a\nmistake. That struct is shared ABI between the kernel and the kexec tooling\nfor x86, and so we cannot simply change its layout. So let\u0027s put back the\nremoved field, but call it \u0027unused\u0027 to reflect the fact that we never look\nat its contents. While at it, add a comment to remind our future selves\nthat the layout is external ABI.\n\nFixes: 0a67361dcdaa29 (\"efi/x86: Remove runtime table address from kexec EFI setup data\")\nReported-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nTested-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nReviewed-by: Dave Young \u003cdyoung@redhat.com\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\n" }, { "commit": "f6103162008dfd37567f240b50e5e1ea7cf2e00c", "tree": "cb775d148ef090561cf9b889fa51e27a2ed07257", "parents": [ "a4b81ccfd4caba017d2b84720b6de4edd16911a0" ], "author": { "name": "Ard Biesheuvel", "email": "ardb@kernel.org", "time": "Thu Apr 09 15:04:34 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:17 2020 +0200" }, "message": "efi/x86: Don\u0027t remap text\u003c-\u003erodata gap read-only for mixed mode\n\nCommit\n\n d9e3d2c4f10320 (\"efi/x86: Don\u0027t map the entire kernel text RW for mixed mode\")\n\nupdated the code that creates the 1:1 memory mapping to use read-only\nattributes for the 1:1 alias of the kernel\u0027s text and rodata sections, to\nprotect it from inadvertent modification. However, it failed to take into\naccount that the unused gap between text and rodata is given to the page\nallocator for general use.\n\nIf the vmap\u0027ed stack happens to be allocated from this region, any by-ref\noutput arguments passed to EFI runtime services that are allocated on the\nstack (such as the \u0027datasize\u0027 argument taken by GetVariable() when invoked\nfrom efivar_entry_size()) will be referenced via a read-only mapping,\nresulting in a page fault if the EFI code tries to write to it:\n\n BUG: unable to handle page fault for address: 00000000386aae88\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0003) - permissions violation\n PGD fd61063 P4D fd61063 PUD fd62063 PMD 386000e1\n Oops: 0003 [#1] SMP PTI\n CPU: 2 PID: 255 Comm: systemd-sysv-ge Not tainted 5.6.0-rc4-default+ #22\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n RIP: 0008:0x3eaeed95\n Code: ... \u003c89\u003e 03 be 05 00 00 80 a1 74 63 b1 3e 83 c0 48 e8 44 d2 ff ff eb 05\n RSP: 0018:000000000fd73fa0 EFLAGS: 00010002\n RAX: 0000000000000001 RBX: 00000000386aae88 RCX: 000000003e9f1120\n RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000001\n RBP: 000000000fd73fd8 R08: 00000000386aae88 R09: 0000000000000000\n R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000\n R13: ffffc0f040220000 R14: 0000000000000000 R15: 0000000000000000\n FS: 00007f21160ac940(0000) GS:ffff9cf23d500000(0000) knlGS:0000000000000000\n CS: 0008 DS: 0018 ES: 0018 CR0: 0000000080050033\n CR2: 00000000386aae88 CR3: 000000000fd6c004 CR4: 00000000003606e0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n Call Trace:\n Modules linked in:\n CR2: 00000000386aae88\n ---[ end trace a8bfbd202e712834 ]---\n\nLet\u0027s fix this by remapping text and rodata individually, and leave the\ngaps mapped read-write.\n\nFixes: d9e3d2c4f10320 (\"efi/x86: Don\u0027t map the entire kernel text RW for mixed mode\")\nReported-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nTested-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200409130434.6736-10-ardb@kernel.org\n" }, { "commit": "a4b81ccfd4caba017d2b84720b6de4edd16911a0", "tree": "7e77613301b80d8ae9e9893bed0c31f31a7eb176", "parents": [ "464fb126d98a047953040cc9c754801dbda54e5d" ], "author": { "name": "Gary Lin", "email": "glin@suse.com", "time": "Thu Apr 09 15:04:33 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:16 2020 +0200" }, "message": "efi/x86: Fix the deletion of variables in mixed mode\n\nefi_thunk_set_variable() treated the NULL \"data\" pointer as an invalid\nparameter, and this broke the deletion of variables in mixed mode.\nThis commit fixes the check of data so that the userspace program can\ndelete a variable in mixed mode.\n\nFixes: 8319e9d5ad98ffcc (\"efi/x86: Handle by-ref arguments covering multiple pages in mixed mode\")\nSigned-off-by: Gary Lin \u003cglin@suse.com\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200408081606.1504-1-glin@suse.com\nLink: https://lore.kernel.org/r/20200409130434.6736-9-ardb@kernel.org\n" }, { "commit": "464fb126d98a047953040cc9c754801dbda54e5d", "tree": "5973b7c7a6f0220c075df1d7fe235355d6c6177f", "parents": [ "8b84769a7a1505b279b337dae83d16390e83f5c1" ], "author": { "name": "Ard Biesheuvel", "email": "ardb@kernel.org", "time": "Thu Apr 09 15:04:32 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:15 2020 +0200" }, "message": "efi/libstub/file: Merge file name buffers to reduce stack usage\n\nArnd reports that commit\n\n 9302c1bb8e47 (\"efi/libstub: Rewrite file I/O routine\")\n\nreworks the file I/O routines in a way that triggers the following\nwarning:\n\n drivers/firmware/efi/libstub/file.c:240:1: warning: the frame size\n of 1200 bytes is larger than 1024 bytes [-Wframe-larger-than\u003d]\n\nWe can work around this issue dropping an instance of efi_char16_t[256]\nfrom the stack frame, and reusing the \u0027filename\u0027 field of the file info\nstruct that we use to obtain file information from EFI (which contains\nthe file name even though we already know it since we used it to open\nthe file in the first place)\n\nReported-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200409130434.6736-8-ardb@kernel.org\n" }, { "commit": "8b84769a7a1505b279b337dae83d16390e83f5c1", "tree": "1b0370bb59a3510436af239d920c77104daec8b2", "parents": [ "a94691680bace7e1404e4f235badb74e30467e86" ], "author": { "name": "Ard Biesheuvel", "email": "ardb@kernel.org", "time": "Thu Apr 09 15:04:31 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:15 2020 +0200" }, "message": "Documentation/x86, efi/x86: Clarify EFI handover protocol and its requirements\n\nThe EFI handover protocol was introduced on x86 to permit the boot\nloader to pass a populated boot_params structure as an additional\nfunction argument to the entry point. This allows the bootloader to\npass the base and size of a initrd image, which is more flexible\nthan relying on the EFI stub\u0027s file I/O routines, which can only\naccess the file system from which the kernel image itself was loaded\nfrom firmware.\n\nThis approach requires a fair amount of internal knowledge regarding\nthe layout of the boot_params structure on the part of the boot loader,\nas well as knowledge regarding the allowed placement of the initrd in\nmemory, and so it has been deprecated in favour of a new initrd loading\nmethod that is based on existing UEFI protocols and best practices.\n\nSo update the x86 boot protocol documentation to clarify that the EFI\nhandover protocol has been deprecated, and while at it, add a note that\ninvoking the EFI handover protocol still requires the PE/COFF image to\nbe loaded properly (as opposed to simply being copied into memory).\nAlso, drop the code32_start header field from the list of values that\nneed to be provided, as this is no longer required.\n\nReviewed-by: Borislav Petkov \u003cbp@suse.de\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200409130434.6736-7-ardb@kernel.org\n" }, { "commit": "a94691680bace7e1404e4f235badb74e30467e86", "tree": "349cc33f1ac553ff4ecbd49fce8f719c6ee91c2a", "parents": [ "21cb9b414301c76f77f70d990a784ad6360e5a20" ], "author": { "name": "Ard Biesheuvel", "email": "ardb@kernel.org", "time": "Thu Apr 09 15:04:30 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:14 2020 +0200" }, "message": "efi/arm: Deal with ADR going out of range in efi_enter_kernel()\n\nCommit\n\n 0698fac4ac2a (\"efi/arm: Clean EFI stub exit code from cache instead of avoiding it\")\n\nintroduced a PC-relative reference to \u0027call_cache_fn\u0027 into\nefi_enter_kernel(), which lives way at the end of head.S. In some cases,\nthe ARM version of the ADR instruction does not have sufficient range,\nresulting in a build error:\n\n arch/arm/boot/compressed/head.S:1453: Error: invalid constant (fffffffffffffbe4) after fixup\n\nARM defines an alternative with a wider range, called ADRL, but this does\nnot exist for Thumb-2. At the same time, the ADR instruction in Thumb-2\nhas a wider range, and so it does not suffer from the same issue.\n\nSo let\u0027s switch to ADRL for ARM builds, and keep the ADR for Thumb-2 builds.\n\nReported-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nTested-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200409130434.6736-6-ardb@kernel.org\n" }, { "commit": "21cb9b414301c76f77f70d990a784ad6360e5a20", "tree": "11bb5e67b5cef831600784ae65b614b6582c0dc4", "parents": [ "105cb9544b161819b7be23a8a8419353a3218807" ], "author": { "name": "Arvind Sankar", "email": "nivedita@alum.mit.edu", "time": "Thu Apr 09 15:04:29 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:13 2020 +0200" }, "message": "efi/x86: Always relocate the kernel for EFI handover entry\n\nCommit\n\n d5cdf4cfeac9 (\"efi/x86: Don\u0027t relocate the kernel unless necessary\")\n\ntries to avoid relocating the kernel in the EFI stub as far as possible.\n\nHowever, when systemd-boot is used to boot a unified kernel image [1],\nthe image is constructed by embedding the bzImage as a .linux section in\na PE executable that contains a small stub loader from systemd that will\ncall the EFI stub handover entry, together with additional sections and\npotentially an initrd. When this image is constructed, by for example\ndracut, the initrd is placed after the bzImage without ensuring that at\nleast init_size bytes are available for the bzImage. If the kernel is\nnot relocated by the EFI stub, this could result in the compressed\nkernel\u0027s startup code in head_{32,64}.S overwriting the initrd.\n\nTo prevent this, unconditionally relocate the kernel if the EFI stub was\nentered via the handover entry point.\n\n[1] https://systemd.io/BOOT_LOADER_SPECIFICATION/#type-2-efi-unified-kernel-images\n\nFixes: d5cdf4cfeac9 (\"efi/x86: Don\u0027t relocate the kernel unless necessary\")\nReported-by: Sergey Shatunov \u003cme@prok.pw\u003e\nSigned-off-by: Arvind Sankar \u003cnivedita@alum.mit.edu\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200406180614.429454-2-nivedita@alum.mit.edu\nLink: https://lore.kernel.org/r/20200409130434.6736-5-ardb@kernel.org\n" }, { "commit": "105cb9544b161819b7be23a8a8419353a3218807", "tree": "78e62783d3b38d8c5df68c43f70b5f9e3c3e9a36", "parents": [ "05a08796281feefcbe5cfdd67b48f5073d309aa8" ], "author": { "name": "Arvind Sankar", "email": "nivedita@alum.mit.edu", "time": "Thu Apr 09 15:04:28 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:13 2020 +0200" }, "message": "efi/x86: Move efi stub globals from .bss to .data\n\nCommit\n\n 3ee372ccce4d (\"x86/boot/compressed/64: Remove .bss/.pgtable from bzImage\")\n\nremoved the .bss section from the bzImage.\n\nHowever, while a PE loader is required to zero-initialize the .bss\nsection before calling the PE entry point, the EFI handover protocol\ndoes not currently document any requirement that .bss be initialized by\nthe bootloader prior to calling the handover entry.\n\nWhen systemd-boot is used to boot a unified kernel image [1], the image\nis constructed by embedding the bzImage as a .linux section in a PE\nexecutable that contains a small stub loader from systemd together with\nadditional sections and potentially an initrd. As the .bss section\nwithin the bzImage is no longer explicitly present as part of the file,\nit is not initialized before calling the EFI handover entry.\nFurthermore, as the size of the embedded .linux section is only the size\nof the bzImage file itself, the .bss section\u0027s memory may not even have\nbeen allocated.\n\nIn particular, this can result in efi_disable_pci_dma being true even\nwhen it was not specified via the command line or configuration option,\nwhich in turn causes crashes while booting on some systems.\n\nTo avoid issues, place all EFI stub global variables into the .data\nsection instead of .bss. As of this writing, only boolean flags for a\nfew command line arguments and the sys_table pointer were in .bss and\nwill now move into the .data section.\n\n[1] https://systemd.io/BOOT_LOADER_SPECIFICATION/#type-2-efi-unified-kernel-images\n\nFixes: 3ee372ccce4d (\"x86/boot/compressed/64: Remove .bss/.pgtable from bzImage\")\nReported-by: Sergey Shatunov \u003cme@prok.pw\u003e\nSigned-off-by: Arvind Sankar \u003cnivedita@alum.mit.edu\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200406180614.429454-1-nivedita@alum.mit.edu\nLink: https://lore.kernel.org/r/20200409130434.6736-4-ardb@kernel.org\n" }, { "commit": "05a08796281feefcbe5cfdd67b48f5073d309aa8", "tree": "c7a2376c9cc8e9e3dda95dfb6f0187a87a694679", "parents": [ "b450b30b97010e5c68ab522c6f6c54ef76bd0683" ], "author": { "name": "Colin Ian King", "email": "colin.king@canonical.com", "time": "Thu Apr 09 15:04:27 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:12 2020 +0200" }, "message": "efi/libstub/x86: Remove redundant assignment to pointer hdr\n\nThe pointer hdr is being assigned a value that is never read and\nit is being updated later with a new value. The assignment is\nredundant and can be removed.\n\nAddresses-Coverity: (\"Unused value\")\nSigned-off-by: Colin Ian King \u003ccolin.king@canonical.com\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200402102537.503103-1-colin.king@canonical.com\nLink: https://lore.kernel.org/r/20200409130434.6736-3-ardb@kernel.org\n" }, { "commit": "b450b30b97010e5c68ab522c6f6c54ef76bd0683", "tree": "f8d6491f8bf1f1e867d50537b6606064419e2f33", "parents": [ "8f3d9f354286745c751374f5f1fcafee6b3f3136" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Thu Apr 09 15:04:26 2020 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Tue Apr 14 08:32:11 2020 +0200" }, "message": "efi/cper: Use scnprintf() for avoiding potential buffer overflow\n\nSince snprintf() returns the would-be-output size instead of the\nactual output size, the succeeding calls may go beyond the given\nbuffer limit. Fix it by replacing with scnprintf().\n\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nLink: https://lore.kernel.org/r/20200311072145.5001-1-tiwai@suse.de\nLink: https://lore.kernel.org/r/20200409130434.6736-2-ardb@kernel.org\n" }, { "commit": "fbf4bcc9a8373122881909331f2f9566a128126e", "tree": "8ab1e8a6c18cc76d2e520dc6095cbead15847f81", "parents": [ "8f3d9f354286745c751374f5f1fcafee6b3f3136" ], "author": { "name": "Trond Myklebust", "email": "trond.myklebust@hammerspace.com", "time": "Mon Apr 13 15:55:21 2020 -0400" }, "committer": { "name": "Trond Myklebust", "email": "trond.myklebust@hammerspace.com", "time": "Mon Apr 13 15:55:21 2020 -0400" }, "message": "NFS: Fix an ABBA spinlock issue in pnfs_update_layout()\n\nWe need to drop the inode spinlock while calling nfs4_select_rw_stateid(),\nsince nfs4_copy_delegation_stateid() could take the delegation lock.\nNote that it is safe to do this, since all other calls to\npnfs_update_layout() for that inode will find themselves blocked by\nthe lock we hold on NFS_LAYOUT_FIRST_LAYOUTGET.\n\nFixes: fc51b1cf391d (\"NFS: Beware when dereferencing the delegation cred\")\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@hammerspace.com\u003e\n" }, { "commit": "ac4075bca10b29bfa0fed99d0a11826ef9ee5e69", "tree": "6537b597379b22038d16837a6ec230f26ddce30b", "parents": [ "8f3d9f354286745c751374f5f1fcafee6b3f3136" ], "author": { "name": "Geert Uytterhoeven", "email": "geert@linux-m68k.org", "time": "Mon Apr 13 11:35:52 2020 +0200" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Apr 13 11:08:52 2020 -0700" }, "message": "m68k: Drop redundant generic-y +\u003d hardirq.h\n\nThe cleanup in commit 630f289b7114c0e6 (\"asm-generic: make more\nkernel-space headers mandatory\") did not take into account the recently\nadded line for hardirq.h in commit acc45648b9aefa90 (\"m68k: Switch to\nasm-generic/hardirq.h\"), leading to the following message during the\nbuild:\n\n scripts/Makefile.asm-generic:25: redundant generic-y found in arch/m68k/include/asm/Kbuild: hardirq.h\n\nFix this by dropping the now redundant line.\n\nFixes: 630f289b7114c0e6 (\"asm-generic: make more kernel-space headers mandatory\")\nSigned-off-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nReviewed-by: Masahiro Yamada \u003cmasahiroy@kernel.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "2a575f138d003fff0f4930b5cfae4a1c46343b8f", "tree": "81df5b30d09f3b0360216ef0842dc0e26c7c77f7", "parents": [ "8ae0299a4b72f2f9ad2b755da91c6a2beabaee62" ], "author": { "name": "Jeff Layton", "email": "jlayton@kernel.org", "time": "Wed Apr 08 08:41:38 2020 -0400" }, "committer": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Apr 13 19:33:47 2020 +0200" }, "message": "ceph: fix potential bad pointer deref in async dirops cb\u0027s\n\nThe new async dirops callback routines can pass ERR_PTR values to\nceph_mdsc_free_path, which could cause an oops. Make ceph_mdsc_free_path\nignore ERR_PTR values. Also, ensure that the pr_warn messages look sane\neven if ceph_mdsc_build_path fails.\n\nReported-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nSigned-off-by: Jeff Layton \u003cjlayton@kernel.org\u003e\nReviewed-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\nSigned-off-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\n" }, { "commit": "538b8471fee89eaf18f6bfbbc0576473f952b83e", "tree": "cb83452adef29f5d88a2cd1242ba536a48feeb54", "parents": [ "5b69c23799ecfc279897e77f43625cc876d92765" ], "author": { "name": "Christophe JAILLET", "email": "christophe.jaillet@wanadoo.fr", "time": "Sat Apr 11 16:58:44 2020 +0200" }, "committer": { "name": "Enric Balletbo i Serra", "email": "enric.balletbo@collabora.com", "time": "Mon Apr 13 16:31:33 2020 +0200" }, "message": "platform/chrome: cros_ec_sensorhub: Add missing \u0027\\n\u0027 in log messages\n\nMessage logged by \u0027dev_xxx()\u0027 or \u0027pr_xxx()\u0027 should end with a \u0027\\n\u0027.\n\nFixes: 145d59baff59 (\"platform/chrome: cros_ec_sensorhub: Add FIFO support\")\nSigned-off-by: Christophe JAILLET \u003cchristophe.jaillet@wanadoo.fr\u003e\nSigned-off-by: Enric Balletbo i Serra \u003cenric.balletbo@collabora.com\u003e\n" }, { "commit": "40fc81027f892284ce31f8b6de1e497f5b47e71f", "tree": "68d3a89099d8fda3866485281ab11163c8c05c7c", "parents": [ "2105c2820d366b76f38e6ad61c75771881ecc532" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Sat Apr 11 08:50:45 2020 +0100" }, "committer": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 15:09:01 2020 +0100" }, "message": "afs: Fix afs_d_validate() to set the right directory version\n\nIf a dentry\u0027s version is somewhere between invalid_before and the current\ndirectory version, we should be setting it forward to the current version,\nnot backwards to the invalid_before version. Note that we\u0027re only doing\nthis at all because dentry::d_fsdata isn\u0027t large enough on a 32-bit system.\n\nFix this by using a separate variable for invalid_before so that we don\u0027t\naccidentally clobber the current dir version.\n\nFixes: a4ff7401fbfa (\"afs: Keep track of invalid-before version for dentry coherency\")\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\n" }, { "commit": "2105c2820d366b76f38e6ad61c75771881ecc532", "tree": "844875c0e41ad206541baa3b44bc77ba89d78ba2", "parents": [ "3efe55b09a92a59ed8214db801683cf13c9742c4" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Fri Apr 10 15:23:27 2020 +0100" }, "committer": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 15:09:01 2020 +0100" }, "message": "afs: Fix race between post-modification dir edit and readdir/d_revalidate\n\nAFS directories are retained locally as a structured file, with lookup\nbeing effected by a local search of the file contents. When a modification\n(such as mkdir) happens, the dir file content is modified locally rather\nthan redownloading the directory.\n\nThe directory contents are accessed in a number of ways, with a number of\ndifferent locks schemes:\n\n (1) Download of contents - dvnode-\u003evalidate_lock/write in afs_read_dir().\n\n (2) Lookup and readdir - dvnode-\u003evalidate_lock/read in afs_dir_iterate(),\n downgrading from (1) if necessary.\n\n (3) d_revalidate of child dentry - dvnode-\u003evalidate_lock/read in\n afs_do_lookup_one() downgrading from (1) if necessary.\n\n (4) Edit of dir after modification - page locks on individual dir pages.\n\nUnfortunately, because (4) uses different locking scheme to (1) - (3),\nnothing protects against the page being scanned whilst the edit is\nunderway. Even download is not safe as it doesn\u0027t lock the pages - relying\ninstead on the validate_lock to serialise as a whole (the theory being that\ndirectory contents are treated as a block and always downloaded as a\nblock).\n\nFix this by write-locking dvnode-\u003evalidate_lock around the edits. Care\nmust be taken in the rename case as there may be two different dirs - but\nthey need not be locked at the same time. In any case, once the lock is\ntaken, the directory version must be rechecked, and the edit skipped if a\nlater version has been downloaded by revalidation (there can\u0027t have been\nany local changes because the VFS holds the inode lock, but there can have\nbeen remote changes).\n\nFixes: 63a4681ff39c (\"afs: Locally edit directory data for mkdir/create/unlink/...\")\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\n" }, { "commit": "3efe55b09a92a59ed8214db801683cf13c9742c4", "tree": "1ff089168882dda80632c4ed24f51e332fa1f56d", "parents": [ "b98f0ec91c42d87a70da42726b852ac8d78a3257" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Wed Apr 01 23:32:12 2020 +0100" }, "committer": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 15:09:01 2020 +0100" }, "message": "afs: Fix length of dump of bad YFSFetchStatus record\n\nFix the length of the dump of a bad YFSFetchStatus record. The function\nwas copied from the AFS version, but the YFS variant contains bigger fields\nand extra information, so expand the dump to match.\n\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\n" }, { "commit": "b98f0ec91c42d87a70da42726b852ac8d78a3257", "tree": "26fa47281faa787c90c31f350724c7585008fa7a", "parents": [ "3e0d9892c0e7fa426ca6bf921cb4b543ca265714" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Wed Apr 08 20:56:20 2020 +0100" }, "committer": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 15:09:01 2020 +0100" }, "message": "afs: Fix rename operation status delivery\n\nThe afs_deliver_fs_rename() and yfs_deliver_fs_rename() functions both only\ndecode the second file status returned unless the parent directories are\ndifferent - unfortunately, this means that the xdr pointer isn\u0027t advanced\nand the volsync record will be read incorrectly in such an instance.\n\nFix this by always decoding the second status into the second\nstatus/callback block which wasn\u0027t being used if the dirs were the same.\n\nThe afs_update_dentry_version() calls that update the directory data\nversion numbers on the dentries can then unconditionally use the second\nstatus record as this will always reflect the state of the destination dir\n(the two records will be identical if the destination dir is the same as\nthe source dir)\n\nFixes: 260a980317da (\"[AFS]: Add \"directory write\" support.\")\nFixes: 30062bd13e36 (\"afs: Implement YFS support in the fs client\")\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\n" }, { "commit": "3e0d9892c0e7fa426ca6bf921cb4b543ca265714", "tree": "79f6f8d3ff45bff5f5af3ec2a3a4529bf2fb008d", "parents": [ "c72057b56f7e24865840a6961d801a7f21d30a5f" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Wed Apr 08 17:32:10 2020 +0100" }, "committer": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 15:09:01 2020 +0100" }, "message": "afs: Fix decoding of inline abort codes from version 1 status records\n\nIf we\u0027re decoding an AFSFetchStatus record and we see that the version is 1\nand the abort code is set and we\u0027re expecting inline errors, then we store\nthe abort code and ignore the remaining status record (which is correct),\nbut we don\u0027t set the flag to say we got a valid abort code.\n\nThis can affect operation of YFS.RemoveFile2 when removing a file and the\noperation of {,Y}FS.InlineBulkStatus when prospectively constructing or\nupdating of a set of inodes during a lookup.\n\nFix this to indicate the reception of a valid abort code.\n\nFixes: a38a75581e6e (\"afs: Fix unlink to handle YFS.RemoveFile2 better\")\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\n" }, { "commit": "c72057b56f7e24865840a6961d801a7f21d30a5f", "tree": "de16f261dc5b0129ebc2aa22e0563f228764dd6e", "parents": [ "8f3d9f354286745c751374f5f1fcafee6b3f3136" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Wed Apr 08 16:13:20 2020 +0100" }, "committer": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Mon Apr 13 15:09:01 2020 +0100" }, "message": "afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus()\n\nIf we receive a status record that has VNOVNODE set in the abort field,\nxdr_decode_AFSFetchStatus() and xdr_decode_YFSFetchStatus() don\u0027t advance\nthe XDR pointer, thereby corrupting anything subsequent decodes from the\nsame block of data.\n\nThis has the potential to affect AFS.InlineBulkStatus and\nYFS.InlineBulkStatus operation, but probably doesn\u0027t since the status\nrecords are extracted as individual blocks of data and the buffer pointer\nis reset between blocks.\n\nIt does affect YFS.RemoveFile2 operation, corrupting the volsync record -\nthough that is not currently used.\n\nOther operations abort the entire operation rather than returning an error\ninline, in which case there is no decoding to be done.\n\nFix this by unconditionally advancing the xdr pointer.\n\nFixes: 684b0f68cf1c (\"afs: Fix AFSFetchStatus decoder to provide OpenAFS compatibility\")\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\n" }, { "commit": "8ae0299a4b72f2f9ad2b755da91c6a2beabaee62", "tree": "e9242b430584644366ea03d13582a794f750268b", "parents": [ "b8776051529230f76e464d5ffc5d1cf8465576bf" ], "author": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Tue Mar 17 15:18:48 2020 +0100" }, "committer": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Apr 13 08:55:49 2020 +0200" }, "message": "rbd: don\u0027t mess with a page vector in rbd_notify_op_lock()\n\nrbd_notify_op_lock() isn\u0027t interested in a notify reply. Instead of\naccepting that page vector just to free it, have watch-notify code take\ncare of it.\n\nSigned-off-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\nReviewed-by: Jason Dillaman \u003cdillaman@redhat.com\u003e\n" }, { "commit": "b8776051529230f76e464d5ffc5d1cf8465576bf", "tree": "e11ac47ff54f5db33102937957b74627a1b9a449", "parents": [ "952c48b0ed18919bff7528501e9a3fff8a24f8cd" ], "author": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Mar 16 17:16:28 2020 +0100" }, "committer": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Apr 13 08:55:49 2020 +0200" }, "message": "rbd: don\u0027t test rbd_dev-\u003eopts in rbd_dev_image_release()\n\nrbd_dev-\u003eopts is used to distinguish between the image that is being\nmapped and a parent. However, because we no longer establish watch for\nread-only mappings, this test is imprecise and results in unnecessary\nrbd_unregister_watch() calls.\n\nMake it consistent with need_watch in rbd_dev_image_probe().\n\nFixes: b9ef2b8858a0 (\"rbd: don\u0027t establish watch for read-only mappings\")\nSigned-off-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\nReviewed-by: Jason Dillaman \u003cdillaman@redhat.com\u003e\n" }, { "commit": "952c48b0ed18919bff7528501e9a3fff8a24f8cd", "tree": "cb1c4416ad298503d23abd3298da76bfbf3c5634", "parents": [ "0e4e1de5b63fa423b13593337a27fd2d2b0bcf77" ], "author": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Mar 16 15:52:54 2020 +0100" }, "committer": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Apr 13 08:55:49 2020 +0200" }, "message": "rbd: call rbd_dev_unprobe() after unwatching and flushing notifies\n\nrbd_dev_unprobe() is supposed to undo most of rbd_dev_image_probe(),\nincluding rbd_dev_header_info(), which means that rbd_dev_header_info()\nisn\u0027t supposed to be called after rbd_dev_unprobe().\n\nHowever, rbd_dev_image_release() calls rbd_dev_unprobe() before\nrbd_unregister_watch(). This is racy because a header update notify\ncan sneak in:\n\n \"rbd unmap\" thread ceph-watch-notify worker\n\n rbd_dev_image_release()\n rbd_dev_unprobe()\n free and zero out header\n rbd_watch_cb()\n rbd_dev_refresh()\n rbd_dev_header_info()\n read in header\n\nThe same goes for \"rbd map\" because rbd_dev_image_probe() calls\nrbd_dev_unprobe() on errors. In both cases this results in a memory\nleak.\n\nFixes: fd22aef8b47c (\"rbd: move rbd_unregister_watch() call into rbd_dev_image_release()\")\nSigned-off-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\nReviewed-by: Jason Dillaman \u003cdillaman@redhat.com\u003e\n" }, { "commit": "0e4e1de5b63fa423b13593337a27fd2d2b0bcf77", "tree": "8abbb9cb2d0db92749231abb3214c5b2699dd11c", "parents": [ "8f3d9f354286745c751374f5f1fcafee6b3f3136" ], "author": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Fri Mar 13 11:20:51 2020 +0100" }, "committer": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Apr 13 08:55:49 2020 +0200" }, "message": "rbd: avoid a deadlock on header_rwsem when flushing notifies\n\nrbd_unregister_watch() flushes notifies and therefore cannot be called\nunder header_rwsem because a header update notify takes header_rwsem to\nsynchronize with \"rbd map\". If mapping an image fails after the watch\nis established and a header update notify sneaks in, we deadlock when\nerroring out from rbd_dev_image_probe().\n\nMove watch registration and unregistration out of the critical section.\nThe only reason they were put there was to make header_rwsem management\nslightly more obvious.\n\nFixes: 811c66887746 (\"rbd: fix rbd map vs notify races\")\nSigned-off-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\nReviewed-by: Jason Dillaman \u003cdillaman@redhat.com\u003e\n" }, { "commit": "5b69c23799ecfc279897e77f43625cc876d92765", "tree": "fa4837bbb27dfb912aa1f0bfeb1849b5dc4a9564", "parents": [ "a46387712da12b61bf1ce1a3f63b60a17b098960" ], "author": { "name": "Dan Carpenter", "email": "dan.carpenter@oracle.com", "time": "Tue Apr 07 12:29:35 2020 +0300" }, "committer": { "name": "Enric Balletbo i Serra", "email": "enric.balletbo@collabora.com", "time": "Mon Apr 13 08:09:27 2020 +0200" }, "message": "platform/chrome: cros_ec_sensorhub: Off by one in cros_sensorhub_send_sample()\n\nThe sensorhub-\u003epush_data[] array has sensorhub-\u003esensor_num elements.\nIt\u0027s allocated in cros_ec_sensorhub_ring_add(). So the \u003e should be \u003e\u003d\nto prevent a read one element beyond the end of the array.\n\nFixes: 145d59baff59 (\"platform/chrome: cros_ec_sensorhub: Add FIFO support\")\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nReviewed-by: Guenter Roeck \u003cgroeck@chromium.org\u003e\nSigned-off-by: Enric Balletbo i Serra \u003cenric.balletbo@collabora.com\u003e\n" }, { "commit": "664d035c4707ac8643c2846d1a1d4cdf9ce89b90", "tree": "7b2e9b4a2ee2e5607696c109c0772d620202b68f", "parents": [ "e154659ba39a1c2be576aaa0a5bda8088d707950" ], "author": { "name": "Christophe JAILLET", "email": "christophe.jaillet@wanadoo.fr", "time": "Sun Apr 12 23:20:34 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Apr 12 21:20:27 2020 -0700" }, "message": "net: mvneta: Fix a typo\n\ns/mvmeta/mvneta/\n\nSigned-off-by: Christophe JAILLET \u003cchristophe.jaillet@wanadoo.fr\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "e154659ba39a1c2be576aaa0a5bda8088d707950", "tree": "35d3133115483b71105b54d15b5012fbe9ecfe5c", "parents": [ "3fe260e00cd0bf0be853c48fcc1e19853df615bb" ], "author": { "name": "Florian Westphal", "email": "fw@strlen.de", "time": "Sat Apr 11 21:05:01 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Apr 12 21:04:08 2020 -0700" }, "message": "mptcp: fix double-unlock in mptcp_poll\n\nmptcp_connect/28740 is trying to release lock (sk_lock-AF_INET) at:\n[\u003cffffffff82c15869\u003e] mptcp_poll+0xb9/0x550\nbut there are no more locks to release!\nCall Trace:\n lock_release+0x50f/0x750\n release_sock+0x171/0x1b0\n mptcp_poll+0xb9/0x550\n sock_poll+0x157/0x470\n ? get_net_ns+0xb0/0xb0\n do_sys_poll+0x63c/0xdd0\n\nProblem is that __mptcp_tcp_fallback() releases the mptcp socket lock,\nbut after recent change it doesn\u0027t do this in all of its return paths.\n\nTo fix this, remove the unlock from __mptcp_tcp_fallback() and\nalways do the unlock in the caller.\n\nAlso add a small comment as to why we have this\n__mptcp_needs_tcp_fallback().\n\nFixes: 0b4f33def7bbde (\"mptcp: fix tcp fallback crash\")\nReported-by: syzbot+e56606435b7bfeea8cf5@syzkaller.appspotmail.com\nSigned-off-by: Florian Westphal \u003cfw@strlen.de\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "3fe260e00cd0bf0be853c48fcc1e19853df615bb", "tree": "0560451c14b2fb13eb0206ed898a0b0be65f3c04", "parents": [ "e6aaeafd56e33345f1d242cde33dd92614734be8" ], "author": { "name": "Gilberto Bertin", "email": "me@jibi.io", "time": "Fri Apr 10 18:20:59 2020 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Apr 12 20:58:24 2020 -0700" }, "message": "net: tun: record RX queue in skb before do_xdp_generic()\n\nThis allows netif_receive_generic_xdp() to correctly determine the RX\nqueue from which the skb is coming, so that the context passed to the\nXDP program will contain the correct RX queue index.\n\nSigned-off-by: Gilberto Bertin \u003cme@jibi.io\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "8f3d9f354286745c751374f5f1fcafee6b3f3136", "tree": "a76e23b60ecceed68b5fa4904f677fe20e304b6e", "parents": [ "3b50142d8528e1efc1c07f69c540f926c58ab3ad" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Apr 12 12:35:55 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Apr 12 12:35:55 2020 -0700" }, "message": "Linux 5.7-rc1\n" }, { "commit": "e6aaeafd56e33345f1d242cde33dd92614734be8", "tree": "b51c5d532b66b95bd937f26fffa6d2bdefab21c8", "parents": [ "2ba538989479b3ff34f66728ecfbaf3c5daf0797" ], "author": { "name": "Christophe JAILLET", "email": "christophe.jaillet@wanadoo.fr", "time": "Sat Apr 11 09:52:11 2020 +0200" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Sun Apr 12 11:44:39 2020 -0700" }, "message": "net: ethernet: ti: Add missing \u0027\\n\u0027 in log messages\n\nMessage logged by \u0027dev_xxx()\u0027 or \u0027pr_xxx()\u0027 should end with a \u0027\\n\u0027.\n\nFixes: 93a76530316a (\"net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver\")\nSigned-off-by: Christophe JAILLET \u003cchristophe.jaillet@wanadoo.fr\u003e\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "2ba538989479b3ff34f66728ecfbaf3c5daf0797", "tree": "fe5faedea6a31fe00cb11eb801de6691ded4443b", "parents": [ "465aa30420bc730ad8f0fe235bc80d169e4b5831" ], "author": { "name": "Christophe JAILLET", "email": "christophe.jaillet@wanadoo.fr", "time": "Sat Apr 11 09:30:04 2020 +0200" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Sun Apr 12 11:44:18 2020 -0700" }, "message": "soc: qcom: ipa: Add a missing \u0027\\n\u0027 in a log message\n\nMessage logged by \u0027dev_xxx()\u0027 or \u0027pr_xxx()\u0027 should end with a \u0027\\n\u0027.\n\nFixes: a646d6ec9098 (\"soc: qcom: ipa: modem and microcontroller\")\nSigned-off-by: Christophe JAILLET \u003cchristophe.jaillet@wanadoo.fr\u003e\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "465aa30420bc730ad8f0fe235bc80d169e4b5831", "tree": "6e7328c5ae56355dca2ca0acbcb3125a485ccf6b", "parents": [ "3b72f84f8fb65e83e85e9be58eabcf95a40b8f46" ], "author": { "name": "Colin Ian King", "email": "colin.king@canonical.com", "time": "Fri Apr 10 20:11:50 2020 +0100" }, "committer": { "name": "Jakub Kicinski", "email": "kuba@kernel.org", "time": "Sun Apr 12 11:44:02 2020 -0700" }, "message": "net: neterion: remove redundant assignment to variable tmp64\n\nThe variable tmp64 is being initialized with a value that is never read\nand it is being updated later with a new value. The initialization is\nredundant and can be removed.\n\nAddresses-Coverity: (\"Unused value\")\nSigned-off-by: Colin Ian King \u003ccolin.king@canonical.com\u003e\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n" }, { "commit": "3b50142d8528e1efc1c07f69c540f926c58ab3ad", "tree": "e2b4ce2e75bd32e915ee5a045e493307bc2e81d6", "parents": [ "4400b7d68f6ea4b8392ddc8b3d0242a114e8a639" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Apr 12 11:04:58 2020 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Apr 12 11:04:58 2020 -0700" }, "message": "MAINTAINERS: sort field names for all entries\n\nThis sorts the actual field names too, potentially causing even more\nchaos and confusion at merge time if you have edited the MAINTAINERS\nfile. But the end result is a more consistent layout, and hopefully\nit\u0027s a one-time pain minimized by doing this just before the -rc1\nrelease.\n\nThis was entirely scripted:\n\n ./scripts/parse-maintainers.pl --input\u003dMAINTAINERS --output\u003dMAINTAINERS --order\n\nRequested-by: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" } ], "next": "4400b7d68f6ea4b8392ddc8b3d0242a114e8a639" }