diff options
| author | Sasha Levin <sashal@kernel.org> | 2024-04-28 07:06:22 -0400 |
|---|---|---|
| committer | Sasha Levin <sashal@kernel.org> | 2024-04-28 07:06:22 -0400 |
| commit | 6db10cbf47f05a0e38f5f991befd3637e8d2e7b9 (patch) | |
| tree | 0d730e7c9a3772318e2c52ba52d66d1d081e39ed | |
| parent | ce69ccabeae9f6b765f5750d84f857e6ce2d0bd6 (diff) | |
| download | stable-queue-6db10cbf47f05a0e38f5f991befd3637e8d2e7b9.tar.gz | |
Fixes for 6.6
Signed-off-by: Sasha Levin <sashal@kernel.org>
96 files changed, 7937 insertions, 0 deletions
diff --git a/queue-6.6/af_unix-suppress-false-positive-lockdep-splat-for-sp.patch b/queue-6.6/af_unix-suppress-false-positive-lockdep-splat-for-sp.patch new file mode 100644 index 0000000000..6bc9c642fc --- /dev/null +++ b/queue-6.6/af_unix-suppress-false-positive-lockdep-splat-for-sp.patch @@ -0,0 +1,171 @@ +From ba68dc7681701a68c7ab016bbebdd84e8b6d99a5 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 10:04:43 -0700 +Subject: af_unix: Suppress false-positive lockdep splat for spin_lock() in + __unix_gc(). + +From: Kuniyuki Iwashima <kuniyu@amazon.com> + +[ Upstream commit 1971d13ffa84a551d29a81fdf5b5ec5be166ac83 ] + +syzbot reported a lockdep splat regarding unix_gc_lock and +unix_state_lock(). + +One is called from recvmsg() for a connected socket, and another +is called from GC for TCP_LISTEN socket. + +So, the splat is false-positive. + +Let's add a dedicated lock class for the latter to suppress the splat. + +Note that this change is not necessary for net-next.git as the issue +is only applied to the old GC impl. + +[0]: +WARNING: possible circular locking dependency detected +6.9.0-rc5-syzkaller-00007-g4d2008430ce8 #0 Not tainted + ----------------------------------------------------- +kworker/u8:1/11 is trying to acquire lock: +ffff88807cea4e70 (&u->lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline] +ffff88807cea4e70 (&u->lock){+.+.}-{2:2}, at: __unix_gc+0x40e/0xf70 net/unix/garbage.c:302 + +but task is already holding lock: +ffffffff8f6ab638 (unix_gc_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline] +ffffffff8f6ab638 (unix_gc_lock){+.+.}-{2:2}, at: __unix_gc+0x117/0xf70 net/unix/garbage.c:261 + +which lock already depends on the new lock. + +the existing dependency chain (in reverse order) is: + + -> #1 (unix_gc_lock){+.+.}-{2:2}: + lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 + __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] + _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154 + spin_lock include/linux/spinlock.h:351 [inline] + unix_notinflight+0x13d/0x390 net/unix/garbage.c:140 + unix_detach_fds net/unix/af_unix.c:1819 [inline] + unix_destruct_scm+0x221/0x350 net/unix/af_unix.c:1876 + skb_release_head_state+0x100/0x250 net/core/skbuff.c:1188 + skb_release_all net/core/skbuff.c:1200 [inline] + __kfree_skb net/core/skbuff.c:1216 [inline] + kfree_skb_reason+0x16d/0x3b0 net/core/skbuff.c:1252 + kfree_skb include/linux/skbuff.h:1262 [inline] + manage_oob net/unix/af_unix.c:2672 [inline] + unix_stream_read_generic+0x1125/0x2700 net/unix/af_unix.c:2749 + unix_stream_splice_read+0x239/0x320 net/unix/af_unix.c:2981 + do_splice_read fs/splice.c:985 [inline] + splice_file_to_pipe+0x299/0x500 fs/splice.c:1295 + do_splice+0xf2d/0x1880 fs/splice.c:1379 + __do_splice fs/splice.c:1436 [inline] + __do_sys_splice fs/splice.c:1652 [inline] + __se_sys_splice+0x331/0x4a0 fs/splice.c:1634 + do_syscall_x64 arch/x86/entry/common.c:52 [inline] + do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 + entry_SYSCALL_64_after_hwframe+0x77/0x7f + + -> #0 (&u->lock){+.+.}-{2:2}: + check_prev_add kernel/locking/lockdep.c:3134 [inline] + check_prevs_add kernel/locking/lockdep.c:3253 [inline] + validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869 + __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137 + lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 + __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] + _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154 + spin_lock include/linux/spinlock.h:351 [inline] + __unix_gc+0x40e/0xf70 net/unix/garbage.c:302 + process_one_work kernel/workqueue.c:3254 [inline] + process_scheduled_works+0xa10/0x17c0 kernel/workqueue.c:3335 + worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 + kthread+0x2f0/0x390 kernel/kthread.c:388 + ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 + ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 + +other info that might help us debug this: + + Possible unsafe locking scenario: + + CPU0 CPU1 + ---- ---- + lock(unix_gc_lock); + lock(&u->lock); + lock(unix_gc_lock); + lock(&u->lock); + + *** DEADLOCK *** + +3 locks held by kworker/u8:1/11: + #0: ffff888015089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3229 [inline] + #0: ffff888015089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x8e0/0x17c0 kernel/workqueue.c:3335 + #1: ffffc90000107d00 (unix_gc_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3230 [inline] + #1: ffffc90000107d00 (unix_gc_work){+.+.}-{0:0}, at: process_scheduled_works+0x91b/0x17c0 kernel/workqueue.c:3335 + #2: ffffffff8f6ab638 (unix_gc_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline] + #2: ffffffff8f6ab638 (unix_gc_lock){+.+.}-{2:2}, at: __unix_gc+0x117/0xf70 net/unix/garbage.c:261 + +stack backtrace: +CPU: 0 PID: 11 Comm: kworker/u8:1 Not tainted 6.9.0-rc5-syzkaller-00007-g4d2008430ce8 #0 +Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 +Workqueue: events_unbound __unix_gc +Call Trace: + <TASK> + __dump_stack lib/dump_stack.c:88 [inline] + dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 + check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2187 + check_prev_add kernel/locking/lockdep.c:3134 [inline] + check_prevs_add kernel/locking/lockdep.c:3253 [inline] + validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869 + __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137 + lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 + __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] + _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154 + spin_lock include/linux/spinlock.h:351 [inline] + __unix_gc+0x40e/0xf70 net/unix/garbage.c:302 + process_one_work kernel/workqueue.c:3254 [inline] + process_scheduled_works+0xa10/0x17c0 kernel/workqueue.c:3335 + worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 + kthread+0x2f0/0x390 kernel/kthread.c:388 + ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 + ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 + </TASK> + +Fixes: 47d8ac011fe1 ("af_unix: Fix garbage collector racing against connect()") +Reported-and-tested-by: syzbot+fa379358c28cc87cc307@syzkaller.appspotmail.com +Closes: https://syzkaller.appspot.com/bug?extid=fa379358c28cc87cc307 +Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com> +Link: https://lore.kernel.org/r/20240424170443.9832-1-kuniyu@amazon.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + include/net/af_unix.h | 3 +++ + net/unix/garbage.c | 2 +- + 2 files changed, 4 insertions(+), 1 deletion(-) + +diff --git a/include/net/af_unix.h b/include/net/af_unix.h +index d1b07ddbe677e..77bf30203d3cf 100644 +--- a/include/net/af_unix.h ++++ b/include/net/af_unix.h +@@ -77,6 +77,9 @@ enum unix_socket_lock_class { + U_LOCK_NORMAL, + U_LOCK_SECOND, /* for double locking, see unix_state_double_lock(). */ + U_LOCK_DIAG, /* used while dumping icons, see sk_diag_dump_icons(). */ ++ U_LOCK_GC_LISTENER, /* used for listening socket while determining gc ++ * candidates to close a small race window. ++ */ + }; + + static inline void unix_state_lock_nested(struct sock *sk, +diff --git a/net/unix/garbage.c b/net/unix/garbage.c +index 8734c0c1fc197..2a758531e1027 100644 +--- a/net/unix/garbage.c ++++ b/net/unix/garbage.c +@@ -260,7 +260,7 @@ void unix_gc(void) + __set_bit(UNIX_GC_MAYBE_CYCLE, &u->gc_flags); + + if (sk->sk_state == TCP_LISTEN) { +- unix_state_lock(sk); ++ unix_state_lock_nested(sk, U_LOCK_GC_LISTENER); + unix_state_unlock(sk); + } + } +-- +2.43.0 + diff --git a/queue-6.6/arc-plat-hsdk-remove-misplaced-interrupt-cells-prope.patch b/queue-6.6/arc-plat-hsdk-remove-misplaced-interrupt-cells-prope.patch new file mode 100644 index 0000000000..88e09335ac --- /dev/null +++ b/queue-6.6/arc-plat-hsdk-remove-misplaced-interrupt-cells-prope.patch @@ -0,0 +1,44 @@ +From 419fd9cf117a7640be3e6b18f0e761655ad9df5f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 29 Mar 2024 10:36:50 +0000 +Subject: ARC: [plat-hsdk]: Remove misplaced interrupt-cells property + +From: Alexey Brodkin <Alexey.Brodkin@synopsys.com> + +[ Upstream commit 61231eb8113ce47991f35024f9c20810b37996bf ] + +"gmac" node stands for just an ordinary Ethernet controller, +which is by no means a provider of interrupts, i.e. it doesn't serve +as an interrupt controller, thus "#interrupt-cells" property doesn't +belong to it and so we remove it. + +Fixes: +------------>8------------ + DTC arch/arc/boot/dts/hsdk.dtb +arch/arc/boot/dts/hsdk.dts:207.23-235.5: Warning (interrupt_provider): /soc/ethernet@8000: '#interrupt-cells' found, but node is not an interrupt provider +arch/arc/boot/dts/hsdk.dtb: Warning (interrupt_map): Failed prerequisite 'interrupt_provider' +------------>8------------ + +Reported-by: Vineet Gupta <vgupta@kernel.org> +Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> +Signed-off-by: Vineet Gupta <vgupta@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arc/boot/dts/hsdk.dts | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/arch/arc/boot/dts/hsdk.dts b/arch/arc/boot/dts/hsdk.dts +index 6691f42550778..41b980df862b1 100644 +--- a/arch/arc/boot/dts/hsdk.dts ++++ b/arch/arc/boot/dts/hsdk.dts +@@ -205,7 +205,6 @@ + }; + + gmac: ethernet@8000 { +- #interrupt-cells = <1>; + compatible = "snps,dwmac"; + reg = <0x8000 0x2000>; + interrupts = <10>; +-- +2.43.0 + diff --git a/queue-6.6/arm-dts-imx6ull-tarragon-fix-usb-over-current-polari.patch b/queue-6.6/arm-dts-imx6ull-tarragon-fix-usb-over-current-polari.patch new file mode 100644 index 0000000000..239e244be8 --- /dev/null +++ b/queue-6.6/arm-dts-imx6ull-tarragon-fix-usb-over-current-polari.patch @@ -0,0 +1,36 @@ +From a1d7adcbd72b825c943d43b969572aa23ddf11ad Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 16 Apr 2024 21:06:58 +0200 +Subject: ARM: dts: imx6ull-tarragon: fix USB over-current polarity + +From: Michael Heimpold <michael.heimpold@chargebyte.com> + +[ Upstream commit d7f3040a565214a30e2f07dc9b91566d316e2d36 ] + +Our Tarragon platform uses a active-low signal to inform +the i.MX6ULL about the over-current detection. + +Fixes: 5e4f393ccbf0 ("ARM: dts: imx6ull: Add chargebyte Tarragon support") +Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com> +Signed-off-by: Stefan Wahren <wahrenst@gmx.net> +Signed-off-by: Shawn Guo <shawnguo@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm/boot/dts/nxp/imx/imx6ull-tarragon-common.dtsi | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/arm/boot/dts/nxp/imx/imx6ull-tarragon-common.dtsi b/arch/arm/boot/dts/nxp/imx/imx6ull-tarragon-common.dtsi +index 3fdece5bd31f9..5248a058230c8 100644 +--- a/arch/arm/boot/dts/nxp/imx/imx6ull-tarragon-common.dtsi ++++ b/arch/arm/boot/dts/nxp/imx/imx6ull-tarragon-common.dtsi +@@ -805,6 +805,7 @@ + &pinctrl_usb_pwr>; + dr_mode = "host"; + power-active-high; ++ over-current-active-low; + disable-over-current; + status = "okay"; + }; +-- +2.43.0 + diff --git a/queue-6.6/arm-dts-microchip-at91-sama7g5ek-replace-regulator-s.patch b/queue-6.6/arm-dts-microchip-at91-sama7g5ek-replace-regulator-s.patch new file mode 100644 index 0000000000..12090e5eb5 --- /dev/null +++ b/queue-6.6/arm-dts-microchip-at91-sama7g5ek-replace-regulator-s.patch @@ -0,0 +1,71 @@ +From 7619c2167beae3b59a90a9184318cf770bc002a8 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 4 Apr 2024 15:38:23 +0300 +Subject: ARM: dts: microchip: at91-sama7g5ek: Replace + regulator-suspend-voltage with the valid property + +From: Andrei Simion <andrei.simion@microchip.com> + +[ Upstream commit e027b71762e84ee9d4ba9ad5401b956b9e83ed2a ] + +By checking the pmic node with microchip,mcp16502.yaml# +'regulator-suspend-voltage' does not match any of the +regexes 'pinctrl-[0-9]+' from schema microchip,mcp16502.yaml# +which inherits regulator.yaml#. So replace regulator-suspend-voltage +with regulator-suspend-microvolt to avoid the inconsitency. + +Fixes: 85b1304b9daa ("ARM: dts: at91: sama7g5ek: set regulator voltages for standby state") +Signed-off-by: Andrei Simion <andrei.simion@microchip.com> +Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com> +Link: https://lore.kernel.org/r/20240404123824.19182-2-andrei.simion@microchip.com +[claudiu.beznea: added a dot before starting the last sentence in commit + description] +Signed-off-by: Claudiu Beznea <claudiu.beznea@tuxon.dev> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm/boot/dts/microchip/at91-sama7g5ek.dts | 8 ++++---- + 1 file changed, 4 insertions(+), 4 deletions(-) + +diff --git a/arch/arm/boot/dts/microchip/at91-sama7g5ek.dts b/arch/arm/boot/dts/microchip/at91-sama7g5ek.dts +index 217e9b96c61e5..20b2497657ae4 100644 +--- a/arch/arm/boot/dts/microchip/at91-sama7g5ek.dts ++++ b/arch/arm/boot/dts/microchip/at91-sama7g5ek.dts +@@ -293,7 +293,7 @@ + + regulator-state-standby { + regulator-on-in-suspend; +- regulator-suspend-voltage = <1150000>; ++ regulator-suspend-microvolt = <1150000>; + regulator-mode = <4>; + }; + +@@ -314,7 +314,7 @@ + + regulator-state-standby { + regulator-on-in-suspend; +- regulator-suspend-voltage = <1050000>; ++ regulator-suspend-microvolt = <1050000>; + regulator-mode = <4>; + }; + +@@ -331,7 +331,7 @@ + regulator-always-on; + + regulator-state-standby { +- regulator-suspend-voltage = <1800000>; ++ regulator-suspend-microvolt = <1800000>; + regulator-on-in-suspend; + }; + +@@ -346,7 +346,7 @@ + regulator-max-microvolt = <3700000>; + + regulator-state-standby { +- regulator-suspend-voltage = <1800000>; ++ regulator-suspend-microvolt = <1800000>; + regulator-on-in-suspend; + }; + +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-cherry-add-platform-thermal-confi.patch b/queue-6.6/arm64-dts-mediatek-cherry-add-platform-thermal-confi.patch new file mode 100644 index 0000000000..4f466e2ff7 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-cherry-add-platform-thermal-confi.patch @@ -0,0 +1,158 @@ +From c9dbaf460590f6198b3ba62d475eb4adc18a75cb Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 24 Apr 2023 13:25:20 +0200 +Subject: arm64: dts: mediatek: cherry: Add platform thermal configuration + +From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> + +[ Upstream commit 729f30eac8bce6783f889cf8390ea869d03407e6 ] + +This platform has three auxiliary NTC thermistors, connected to the +SoC's ADC pins. Enable the auxadc in order to be able to read the +ADC values, add a generic-adc-thermal LUT for each and finally assign +them to the SoC's thermal zones. + +Tested-by: Chen-Yu Tsai <wenst@chromium.org> +Reviewed-by: Chen-Yu Tsai <wenst@chromium.org> +Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com> +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20230424112523.1436926-2-angelogioacchino.delregno@collabora.com +Stable-dep-of: 17b33dd9e4a3 ("arm64: dts: mediatek: cherry: Describe CPU supplies") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../boot/dts/mediatek/mt8195-cherry.dtsi | 105 ++++++++++++++++++ + 1 file changed, 105 insertions(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi +index 3f508e5c18434..d721ddb230747 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi +@@ -114,6 +114,77 @@ + regulator-boot-on; + }; + ++ /* Murata NCP03WF104F05RL */ ++ tboard_thermistor1: thermal-sensor-t1 { ++ compatible = "generic-adc-thermal"; ++ #thermal-sensor-cells = <0>; ++ io-channels = <&auxadc 0>; ++ io-channel-names = "sensor-channel"; ++ temperature-lookup-table = < (-10000) 1553 ++ (-5000) 1485 ++ 0 1406 ++ 5000 1317 ++ 10000 1219 ++ 15000 1115 ++ 20000 1007 ++ 25000 900 ++ 30000 796 ++ 35000 697 ++ 40000 605 ++ 45000 523 ++ 50000 449 ++ 55000 384 ++ 60000 327 ++ 65000 279 ++ 70000 237 ++ 75000 202 ++ 80000 172 ++ 85000 147 ++ 90000 125 ++ 95000 107 ++ 100000 92 ++ 105000 79 ++ 110000 68 ++ 115000 59 ++ 120000 51 ++ 125000 44>; ++ }; ++ ++ tboard_thermistor2: thermal-sensor-t2 { ++ compatible = "generic-adc-thermal"; ++ #thermal-sensor-cells = <0>; ++ io-channels = <&auxadc 1>; ++ io-channel-names = "sensor-channel"; ++ temperature-lookup-table = < (-10000) 1553 ++ (-5000) 1485 ++ 0 1406 ++ 5000 1317 ++ 10000 1219 ++ 15000 1115 ++ 20000 1007 ++ 25000 900 ++ 30000 796 ++ 35000 697 ++ 40000 605 ++ 45000 523 ++ 50000 449 ++ 55000 384 ++ 60000 327 ++ 65000 279 ++ 70000 237 ++ 75000 202 ++ 80000 172 ++ 85000 147 ++ 90000 125 ++ 95000 107 ++ 100000 92 ++ 105000 79 ++ 110000 68 ++ 115000 59 ++ 120000 51 ++ 125000 44>; ++ }; ++ + usb_vbus: regulator-5v0-usb-vbus { + compatible = "regulator-fixed"; + regulator-name = "usb-vbus"; +@@ -176,6 +247,10 @@ + memory-region = <&afe_mem>; + }; + ++&auxadc { ++ status = "okay"; ++}; ++ + &dp_intf0 { + status = "okay"; + +@@ -1127,6 +1202,36 @@ + }; + }; + ++&thermal_zones { ++ soc-area-thermal { ++ polling-delay = <1000>; ++ polling-delay-passive = <250>; ++ thermal-sensors = <&tboard_thermistor1>; ++ ++ trips { ++ trip-crit { ++ temperature = <84000>; ++ hysteresis = <1000>; ++ type = "critical"; ++ }; ++ }; ++ }; ++ ++ pmic-area-thermal { ++ polling-delay = <1000>; ++ polling-delay-passive = <0>; ++ thermal-sensors = <&tboard_thermistor2>; ++ ++ trips { ++ trip-crit { ++ temperature = <84000>; ++ hysteresis = <1000>; ++ type = "critical"; ++ }; ++ }; ++ }; ++}; ++ + &u3phy0 { + status = "okay"; + }; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-cherry-describe-cpu-supplies.patch b/queue-6.6/arm64-dts-mediatek-cherry-describe-cpu-supplies.patch new file mode 100644 index 0000000000..ce075fa631 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-cherry-describe-cpu-supplies.patch @@ -0,0 +1,70 @@ +From 9cfcef8b27d3e9b9038ba2ef559d91065846c28d Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 10 Jan 2024 11:23:01 -0300 +Subject: arm64: dts: mediatek: cherry: Describe CPU supplies +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: NÃcolas F. R. A. Prado <nfraprado@collabora.com> + +[ Upstream commit 17b33dd9e4a38fbaca87c68e532b52f9d0492ba7 ] + +Describe in each CPU node the regulator supplying it. + +Fixes: 260c04d425eb ("arm64: dts: mediatek: cherry: Enable MT6315 regulators on SPMI bus") +Signed-off-by: NÃcolas F. R. A. Prado <nfraprado@collabora.com> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240110142305.755367-2-nfraprado@collabora.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../boot/dts/mediatek/mt8195-cherry.dtsi | 32 +++++++++++++++++++ + 1 file changed, 32 insertions(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi +index d721ddb230747..663c9f414b611 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi +@@ -251,6 +251,38 @@ + status = "okay"; + }; + ++&cpu0 { ++ cpu-supply = <&mt6359_vcore_buck_reg>; ++}; ++ ++&cpu1 { ++ cpu-supply = <&mt6359_vcore_buck_reg>; ++}; ++ ++&cpu2 { ++ cpu-supply = <&mt6359_vcore_buck_reg>; ++}; ++ ++&cpu3 { ++ cpu-supply = <&mt6359_vcore_buck_reg>; ++}; ++ ++&cpu4 { ++ cpu-supply = <&mt6315_6_vbuck1>; ++}; ++ ++&cpu5 { ++ cpu-supply = <&mt6315_6_vbuck1>; ++}; ++ ++&cpu6 { ++ cpu-supply = <&mt6315_6_vbuck1>; ++}; ++ ++&cpu7 { ++ cpu-supply = <&mt6315_6_vbuck1>; ++}; ++ + &dp_intf0 { + status = "okay"; + +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt2712-fix-validation-errors.patch b/queue-6.6/arm64-dts-mediatek-mt2712-fix-validation-errors.patch new file mode 100644 index 0000000000..4a89770907 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt2712-fix-validation-errors.patch @@ -0,0 +1,94 @@ +From 8c575c3701840b2f6cd28d86d8da43ef5c75e17c Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 1 Mar 2024 08:47:41 +0100 +Subject: arm64: dts: mediatek: mt2712: fix validation errors +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 3baac7291effb501c4d52df7019ebf52011e5772 ] + +1. Fixup infracfg clock controller binding + It also acts as reset controller so #reset-cells is required. +2. Use -pins suffix for pinctrl + +This fixes: +arch/arm64/boot/dts/mediatek/mt2712-evb.dtb: syscon@10001000: '#reset-cells' is a required property + from schema $id: http://devicetree.org/schemas/arm/mediatek/mediatek,infracfg.yaml# +arch/arm64/boot/dts/mediatek/mt2712-evb.dtb: pinctrl@1000b000: 'eth_default', 'eth_sleep', 'usb0_iddig', 'usb1_iddig' do not match any of the regexes: 'pinctrl-[0-9]+', 'pins$' + from schema $id: http://devicetree.org/schemas/pinctrl/mediatek,mt65xx-pinctrl.yaml# + +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240301074741.8362-1-zajec5@gmail.com +[Angelo: Added Fixes tags] +Fixes: 5d4839709c8e ("arm64: dts: mt2712: Add clock controller device nodes") +Fixes: 1724f4cc5133 ("arm64: dts: Add USB3 related nodes for MT2712") +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 8 ++++---- + arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 3 ++- + 2 files changed, 6 insertions(+), 5 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt2712-evb.dts b/arch/arm64/boot/dts/mediatek/mt2712-evb.dts +index fffdb7bbf889e..2d0ef6f23b3a9 100644 +--- a/arch/arm64/boot/dts/mediatek/mt2712-evb.dts ++++ b/arch/arm64/boot/dts/mediatek/mt2712-evb.dts +@@ -129,7 +129,7 @@ + }; + + &pio { +- eth_default: eth_default { ++ eth_default: eth-default-pins { + tx_pins { + pinmux = <MT2712_PIN_71_GBE_TXD3__FUNC_GBE_TXD3>, + <MT2712_PIN_72_GBE_TXD2__FUNC_GBE_TXD2>, +@@ -156,7 +156,7 @@ + }; + }; + +- eth_sleep: eth_sleep { ++ eth_sleep: eth-sleep-pins { + tx_pins { + pinmux = <MT2712_PIN_71_GBE_TXD3__FUNC_GPIO71>, + <MT2712_PIN_72_GBE_TXD2__FUNC_GPIO72>, +@@ -182,14 +182,14 @@ + }; + }; + +- usb0_id_pins_float: usb0_iddig { ++ usb0_id_pins_float: usb0-iddig-pins { + pins_iddig { + pinmux = <MT2712_PIN_12_IDDIG_P0__FUNC_IDDIG_A>; + bias-pull-up; + }; + }; + +- usb1_id_pins_float: usb1_iddig { ++ usb1_id_pins_float: usb1-iddig-pins { + pins_iddig { + pinmux = <MT2712_PIN_14_IDDIG_P1__FUNC_IDDIG_B>; + bias-pull-up; +diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi +index ed1a9d3194153..f767f921bdee1 100644 +--- a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi +@@ -249,10 +249,11 @@ + #clock-cells = <1>; + }; + +- infracfg: syscon@10001000 { ++ infracfg: clock-controller@10001000 { + compatible = "mediatek,mt2712-infracfg", "syscon"; + reg = <0 0x10001000 0 0x1000>; + #clock-cells = <1>; ++ #reset-cells = <1>; + }; + + pericfg: syscon@10003000 { +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7622-drop-reset-names-from-ther.patch b/queue-6.6/arm64-dts-mediatek-mt7622-drop-reset-names-from-ther.patch new file mode 100644 index 0000000000..78d448c484 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7622-drop-reset-names-from-ther.patch @@ -0,0 +1,44 @@ +From 4e0fdaaa6f8202a397a2f8cf51e70e68c7bcb8c7 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 17 Mar 2024 23:10:50 +0100 +Subject: arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit ecb5b0034f5bcc35003b4b965cf50c6e98316e79 ] + +Binding doesn't specify "reset-names" property and Linux driver also +doesn't use it. + +Fix following validation error: +arch/arm64/boot/dts/mediatek/mt7622-rfb1.dtb: thermal@1100b000: Unevaluated properties are not allowed ('reset-names' was unexpected) + from schema $id: http://devicetree.org/schemas/thermal/mediatek,thermal.yaml# + +Fixes: ae457b7679c4 ("arm64: dts: mt7622: add SoC and peripheral related device nodes") +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240317221050.18595-5-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7622.dtsi | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +index 8e46480b5364b..917fa39a74f8d 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +@@ -513,7 +513,6 @@ + <&pericfg CLK_PERI_AUXADC_PD>; + clock-names = "therm", "auxadc"; + resets = <&pericfg MT7622_PERI_THERM_SW_RST>; +- reset-names = "therm"; + mediatek,auxadc = <&auxadc>; + mediatek,apmixedsys = <&apmixedsys>; + nvmem-cells = <&thermal_calibration>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7622-fix-clock-controllers.patch b/queue-6.6/arm64-dts-mediatek-mt7622-fix-clock-controllers.patch new file mode 100644 index 0000000000..c83ab745cc --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7622-fix-clock-controllers.patch @@ -0,0 +1,96 @@ +From 1352076152f96551c89cfe2b36e8f8d36a29c352 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 17 Mar 2024 23:10:47 +0100 +Subject: arm64: dts: mediatek: mt7622: fix clock controllers +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 3ba5a61594347ab46e7c2cff6cd63ea0f1282efb ] + +1. Drop unneeded "syscon"s (bindings were updated recently) +2. Use "clock-controller" in nodenames +3. Add missing "#clock-cells" + +Fixes: d7167881e03e ("arm64: dts: mt7622: add clock controller device nodes") +Fixes: e9b65ecb7c30 ("arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet Dispatch") +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240317221050.18595-2-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7622.dtsi | 27 +++++++++++------------- + 1 file changed, 12 insertions(+), 15 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +index 3ee9266fa8e98..283fdf7d2d8b9 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +@@ -283,16 +283,14 @@ + }; + }; + +- apmixedsys: apmixedsys@10209000 { +- compatible = "mediatek,mt7622-apmixedsys", +- "syscon"; ++ apmixedsys: clock-controller@10209000 { ++ compatible = "mediatek,mt7622-apmixedsys"; + reg = <0 0x10209000 0 0x1000>; + #clock-cells = <1>; + }; + +- topckgen: topckgen@10210000 { +- compatible = "mediatek,mt7622-topckgen", +- "syscon"; ++ topckgen: clock-controller@10210000 { ++ compatible = "mediatek,mt7622-topckgen"; + reg = <0 0x10210000 0 0x1000>; + #clock-cells = <1>; + }; +@@ -734,9 +732,8 @@ + power-domains = <&scpsys MT7622_POWER_DOMAIN_WB>; + }; + +- ssusbsys: ssusbsys@1a000000 { +- compatible = "mediatek,mt7622-ssusbsys", +- "syscon"; ++ ssusbsys: clock-controller@1a000000 { ++ compatible = "mediatek,mt7622-ssusbsys"; + reg = <0 0x1a000000 0 0x1000>; + #clock-cells = <1>; + #reset-cells = <1>; +@@ -793,9 +790,8 @@ + }; + }; + +- pciesys: pciesys@1a100800 { +- compatible = "mediatek,mt7622-pciesys", +- "syscon"; ++ pciesys: clock-controller@1a100800 { ++ compatible = "mediatek,mt7622-pciesys"; + reg = <0 0x1a100800 0 0x1000>; + #clock-cells = <1>; + #reset-cells = <1>; +@@ -921,12 +917,13 @@ + }; + }; + +- hifsys: syscon@1af00000 { +- compatible = "mediatek,mt7622-hifsys", "syscon"; ++ hifsys: clock-controller@1af00000 { ++ compatible = "mediatek,mt7622-hifsys"; + reg = <0 0x1af00000 0 0x70>; ++ #clock-cells = <1>; + }; + +- ethsys: syscon@1b000000 { ++ ethsys: clock-controller@1b000000 { + compatible = "mediatek,mt7622-ethsys", + "syscon"; + reg = <0 0x1b000000 0 0x1000>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7622-fix-ethernet-controller-co.patch b/queue-6.6/arm64-dts-mediatek-mt7622-fix-ethernet-controller-co.patch new file mode 100644 index 0000000000..a49c8673f4 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7622-fix-ethernet-controller-co.patch @@ -0,0 +1,45 @@ +From d929e84b8f5aec01d31e61641c2d7f0ed6eb941e Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 17 Mar 2024 23:10:49 +0100 +Subject: arm64: dts: mediatek: mt7622: fix ethernet controller "compatible" +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 208add29ce5b7291f6c466e4dfd9cbf61c72888e ] + +Fix following validation error: +arch/arm64/boot/dts/mediatek/mt7622-rfb1.dtb: ethernet@1b100000: compatible: ['mediatek,mt7622-eth', 'mediatek,mt2701-eth', 'syscon'] is too long + from schema $id: http://devicetree.org/schemas/net/mediatek,net.yaml# +(and other complains about wrong clocks). + +Fixes: 5f599b3a0bb8 ("arm64: dts: mt7622: add ethernet device nodes") +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240317221050.18595-4-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7622.dtsi | 4 +--- + 1 file changed, 1 insertion(+), 3 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +index 4c8a71c8184b7..8e46480b5364b 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +@@ -963,9 +963,7 @@ + }; + + eth: ethernet@1b100000 { +- compatible = "mediatek,mt7622-eth", +- "mediatek,mt2701-eth", +- "syscon"; ++ compatible = "mediatek,mt7622-eth"; + reg = <0 0x1b100000 0 0x20000>; + interrupts = <GIC_SPI 223 IRQ_TYPE_LEVEL_LOW>, + <GIC_SPI 224 IRQ_TYPE_LEVEL_LOW>, +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7622-fix-ir-nodename.patch b/queue-6.6/arm64-dts-mediatek-mt7622-fix-ir-nodename.patch new file mode 100644 index 0000000000..d4524e9c6c --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7622-fix-ir-nodename.patch @@ -0,0 +1,42 @@ +From 80514a70d5e9a8181483078f91f0f75946674d16 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 17 Mar 2024 23:10:48 +0100 +Subject: arm64: dts: mediatek: mt7622: fix IR nodename +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 800dc93c3941e372c94278bf4059e6e82f60bd66 ] + +Fix following validation error: +arch/arm64/boot/dts/mediatek/mt7622-rfb1.dtb: cir@10009000: $nodename:0: 'cir@10009000' does not match '^ir(-receiver)?(@[a-f0-9]+)?$' + from schema $id: http://devicetree.org/schemas/media/mediatek,mt7622-cir.yaml# + +Fixes: ae457b7679c4 ("arm64: dts: mt7622: add SoC and peripheral related device nodes") +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240317221050.18595-3-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7622.dtsi | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +index 283fdf7d2d8b9..4c8a71c8184b7 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi +@@ -252,7 +252,7 @@ + clock-names = "hif_sel"; + }; + +- cir: cir@10009000 { ++ cir: ir-receiver@10009000 { + compatible = "mediatek,mt7622-cir"; + reg = <0 0x10009000 0 0x1000>; + interrupts = <GIC_SPI 175 IRQ_TYPE_LEVEL_LOW>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7986-drop-invalid-properties-fr.patch b/queue-6.6/arm64-dts-mediatek-mt7986-drop-invalid-properties-fr.patch new file mode 100644 index 0000000000..8c19380d29 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7986-drop-invalid-properties-fr.patch @@ -0,0 +1,47 @@ +From d3ed2377ae53a1b9c4234f04ce2598ad49430176 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 13 Feb 2024 06:37:37 +0100 +Subject: arm64: dts: mediatek: mt7986: drop invalid properties from ethsys +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 3b449bfd2ff6c5d3ceecfcb18528ff8e1b4ac2fd ] + +Mediatek ethsys controller / syscon binding doesn't allow any subnodes +so "#address-cells" and "#size-cells" are redundant (actually: +disallowed). + +This fixes: +arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: syscon@15000000: '#address-cells', '#size-cells' do not match any of the regexes: 'pinctrl-[0-9]+' + from schema $id: http://devicetree.org/schemas/clock/mediatek,ethsys.yaml# + +Fixes: 1f9986b258c2 ("arm64: dts: mediatek: add clock support for mt7986a") +Cc: Sam Shih <sam.shih@mediatek.com> +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240213053739.14387-1-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7986a.dtsi | 2 -- + 1 file changed, 2 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +index eba5e27a1bbea..850b664dfa13d 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +@@ -501,8 +501,6 @@ + compatible = "mediatek,mt7986-ethsys", + "syscon"; + reg = <0 0x15000000 0 0x1000>; +- #address-cells = <1>; +- #size-cells = <1>; + #clock-cells = <1>; + #reset-cells = <1>; + }; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7986-drop-invalid-thermal-block.patch b/queue-6.6/arm64-dts-mediatek-mt7986-drop-invalid-thermal-block.patch new file mode 100644 index 0000000000..e2a2c206e6 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7986-drop-invalid-thermal-block.patch @@ -0,0 +1,55 @@ +From 73fc55080c8c29c4f7e0d98a03945426c55737a0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 13 Feb 2024 06:37:39 +0100 +Subject: arm64: dts: mediatek: mt7986: drop invalid thermal block clock +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 970f8b01bd7719a22e577ba6c78e27f9ccf22783 ] + +Thermal block uses only two clocks. Its binding doesn't document or +allow "adc_32k". Also Linux driver doesn't support it. + +It has been additionally verified by Angelo by his detailed research on +MT7981 / MT7986 clocks (thanks!). + +This fixes: +arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: thermal@1100c800: clocks: [[4, 27], [4, 44], [4, 45]] is too long + from schema $id: http://devicetree.org/schemas/thermal/mediatek,thermal.yaml# +arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: thermal@1100c800: clock-names: ['therm', 'auxadc', 'adc_32k'] is too long + from schema $id: http://devicetree.org/schemas/thermal/mediatek,thermal.yaml# + +Fixes: 0a9615d58d04 ("arm64: dts: mt7986: add thermal and efuse") +Cc: Daniel Golle <daniel@makrotopia.org> +Link: https://lore.kernel.org/linux-devicetree/17d143aa-576e-4d67-a0ea-b79f3518b81c@collabora.com/ +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240213053739.14387-3-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7986a.dtsi | 5 ++--- + 1 file changed, 2 insertions(+), 3 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +index f3a2a89fada41..559990dcd1d17 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +@@ -332,9 +332,8 @@ + reg = <0 0x1100c800 0 0x800>; + interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&infracfg CLK_INFRA_THERM_CK>, +- <&infracfg CLK_INFRA_ADC_26M_CK>, +- <&infracfg CLK_INFRA_ADC_FRC_CK>; +- clock-names = "therm", "auxadc", "adc_32k"; ++ <&infracfg CLK_INFRA_ADC_26M_CK>; ++ clock-names = "therm", "auxadc"; + nvmem-cells = <&thermal_calibration>; + nvmem-cell-names = "calibration-data"; + #thermal-sensor-cells = <1>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7986-drop-reset-cells-from-ethe.patch b/queue-6.6/arm64-dts-mediatek-mt7986-drop-reset-cells-from-ethe.patch new file mode 100644 index 0000000000..8c0335a1a3 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7986-drop-reset-cells-from-ethe.patch @@ -0,0 +1,46 @@ +From 924203021fc0b05543528cf5c50313c64215ca8f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 13 Feb 2024 06:37:38 +0100 +Subject: arm64: dts: mediatek: mt7986: drop "#reset-cells" from Ethernet + controller +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 9bd88afc94c3570289a0f1c696578b3e1f4e3169 ] + +Ethernet block doesn't include or act as a reset controller. +Documentation also doesn't document "#reset-cells" for it. + +This fixes: +arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: ethernet@15100000: Unevaluated properties are not allowed ('#reset-cells' was unexpected) + from schema $id: http://devicetree.org/schemas/net/mediatek,net.yaml# + +Fixes: 082ff36bd5c0 ("arm64: dts: mediatek: mt7986: introduce ethernet nodes") +Cc: Lorenzo Bianconi <lorenzo@kernel.org> +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240213053739.14387-2-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7986a.dtsi | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +index 850b664dfa13d..5c2fe2f43a142 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +@@ -577,7 +577,6 @@ + <&topckgen CLK_TOP_SGM_325M_SEL>; + assigned-clock-parents = <&apmixedsys CLK_APMIXED_NET2PLL>, + <&apmixedsys CLK_APMIXED_SGMPLL>; +- #reset-cells = <1>; + #address-cells = <1>; + #size-cells = <0>; + mediatek,ethsys = <ðsys>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7986-prefix-bpi-r3-cooling-maps.patch b/queue-6.6/arm64-dts-mediatek-mt7986-prefix-bpi-r3-cooling-maps.patch new file mode 100644 index 0000000000..04d6a6b16e --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7986-prefix-bpi-r3-cooling-maps.patch @@ -0,0 +1,57 @@ +From 8547858c502a4607f5bbdc817062919ca49c400a Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 13 Feb 2024 07:14:59 +0100 +Subject: arm64: dts: mediatek: mt7986: prefix BPI-R3 cooling maps with "map-" +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit f8c65a5e4560781f2ea175d8f26cd75ac98e8d78 ] + +This fixes: +arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtb: thermal-zones: cpu-thermal:cooling-maps: 'cpu-active-high', 'cpu-active-low', 'cpu-active-med' do not match any of the regexes: '^map[-a-zA-Z0-9]*$', 'pinctrl-[0-9]+' + from schema $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml# + +Fixes: c26f779a2295 ("arm64: dts: mt7986: add pwm-fan and cooling-maps to BPI-R3 dts") +Cc: Daniel Golle <daniel@makrotopia.org> +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240213061459.17917-1-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts b/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts +index e1ec2cccf4444..aba6686eb34a3 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts ++++ b/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts +@@ -146,19 +146,19 @@ + + &cpu_thermal { + cooling-maps { +- cpu-active-high { ++ map-cpu-active-high { + /* active: set fan to cooling level 2 */ + cooling-device = <&fan 2 2>; + trip = <&cpu_trip_active_high>; + }; + +- cpu-active-med { ++ map-cpu-active-med { + /* active: set fan to cooling level 1 */ + cooling-device = <&fan 1 1>; + trip = <&cpu_trip_active_med>; + }; + +- cpu-active-low { ++ map-cpu-active-low { + /* active: set fan to cooling level 0 */ + cooling-device = <&fan 0 0>; + trip = <&cpu_trip_active_low>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7986-reorder-nodes.patch b/queue-6.6/arm64-dts-mediatek-mt7986-reorder-nodes.patch new file mode 100644 index 0000000000..cf27d2f4fa --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7986-reorder-nodes.patch @@ -0,0 +1,216 @@ +From 6062a26bf05c67d6abd5d148c149e281706b02ab Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 12 Feb 2024 13:16:20 +0100 +Subject: arm64: dts: mediatek: mt7986: reorder nodes +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 3f79e8f3364499750d7442767b101b7bc5864ddf ] + +Use order described as preferred in DTS Coding Style: +1. Sort bus nodes by unit address +2. Use alpha-numerical order for the rest + +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Link: https://lore.kernel.org/r/20240212121620.15035-2-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Stable-dep-of: 970f8b01bd77 ("arm64: dts: mediatek: mt7986: drop invalid thermal block clock") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7986a.dtsi | 116 +++++++++++----------- + 1 file changed, 58 insertions(+), 58 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +index 5c2fe2f43a142..f3a2a89fada41 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +@@ -16,13 +16,6 @@ + #address-cells = <2>; + #size-cells = <2>; + +- clk40m: oscillator-40m { +- compatible = "fixed-clock"; +- clock-frequency = <40000000>; +- #clock-cells = <0>; +- clock-output-names = "clkxtal"; +- }; +- + cpus { + #address-cells = <1>; + #size-cells = <0>; +@@ -59,6 +52,13 @@ + }; + }; + ++ clk40m: oscillator-40m { ++ compatible = "fixed-clock"; ++ clock-frequency = <40000000>; ++ #clock-cells = <0>; ++ clock-output-names = "clkxtal"; ++ }; ++ + psci { + compatible = "arm,psci-0.2"; + method = "smc"; +@@ -121,15 +121,6 @@ + + }; + +- timer { +- compatible = "arm,armv8-timer"; +- interrupt-parent = <&gic>; +- interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, +- <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, +- <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, +- <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; +- }; +- + soc { + compatible = "simple-bus"; + ranges; +@@ -203,6 +194,19 @@ + #interrupt-cells = <2>; + }; + ++ pwm: pwm@10048000 { ++ compatible = "mediatek,mt7986-pwm"; ++ reg = <0 0x10048000 0 0x1000>; ++ #pwm-cells = <2>; ++ interrupts = <GIC_SPI 137 IRQ_TYPE_LEVEL_HIGH>; ++ clocks = <&topckgen CLK_TOP_PWM_SEL>, ++ <&infracfg CLK_INFRA_PWM_STA>, ++ <&infracfg CLK_INFRA_PWM1_CK>, ++ <&infracfg CLK_INFRA_PWM2_CK>; ++ clock-names = "top", "main", "pwm1", "pwm2"; ++ status = "disabled"; ++ }; ++ + sgmiisys0: syscon@10060000 { + compatible = "mediatek,mt7986-sgmiisys_0", + "syscon"; +@@ -240,19 +244,6 @@ + status = "disabled"; + }; + +- pwm: pwm@10048000 { +- compatible = "mediatek,mt7986-pwm"; +- reg = <0 0x10048000 0 0x1000>; +- #pwm-cells = <2>; +- interrupts = <GIC_SPI 137 IRQ_TYPE_LEVEL_HIGH>; +- clocks = <&topckgen CLK_TOP_PWM_SEL>, +- <&infracfg CLK_INFRA_PWM_STA>, +- <&infracfg CLK_INFRA_PWM1_CK>, +- <&infracfg CLK_INFRA_PWM2_CK>; +- clock-names = "top", "main", "pwm1", "pwm2"; +- status = "disabled"; +- }; +- + uart0: serial@11002000 { + compatible = "mediatek,mt7986-uart", + "mediatek,mt6577-uart"; +@@ -336,6 +327,21 @@ + status = "disabled"; + }; + ++ thermal: thermal@1100c800 { ++ compatible = "mediatek,mt7986-thermal"; ++ reg = <0 0x1100c800 0 0x800>; ++ interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>; ++ clocks = <&infracfg CLK_INFRA_THERM_CK>, ++ <&infracfg CLK_INFRA_ADC_26M_CK>, ++ <&infracfg CLK_INFRA_ADC_FRC_CK>; ++ clock-names = "therm", "auxadc", "adc_32k"; ++ nvmem-cells = <&thermal_calibration>; ++ nvmem-cell-names = "calibration-data"; ++ #thermal-sensor-cells = <1>; ++ mediatek,auxadc = <&auxadc>; ++ mediatek,apmixedsys = <&apmixedsys>; ++ }; ++ + auxadc: adc@1100d000 { + compatible = "mediatek,mt7986-auxadc"; + reg = <0 0x1100d000 0 0x1000>; +@@ -387,21 +393,6 @@ + status = "disabled"; + }; + +- thermal: thermal@1100c800 { +- compatible = "mediatek,mt7986-thermal"; +- reg = <0 0x1100c800 0 0x800>; +- interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>; +- clocks = <&infracfg CLK_INFRA_THERM_CK>, +- <&infracfg CLK_INFRA_ADC_26M_CK>, +- <&infracfg CLK_INFRA_ADC_FRC_CK>; +- clock-names = "therm", "auxadc", "adc_32k"; +- nvmem-cells = <&thermal_calibration>; +- nvmem-cell-names = "calibration-data"; +- #thermal-sensor-cells = <1>; +- mediatek,auxadc = <&auxadc>; +- mediatek,apmixedsys = <&apmixedsys>; +- }; +- + pcie: pcie@11280000 { + compatible = "mediatek,mt7986-pcie", + "mediatek,mt8192-pcie"; +@@ -531,20 +522,6 @@ + mediatek,wo-ccif = <&wo_ccif1>; + }; + +- wo_ccif0: syscon@151a5000 { +- compatible = "mediatek,mt7986-wo-ccif", "syscon"; +- reg = <0 0x151a5000 0 0x1000>; +- interrupt-parent = <&gic>; +- interrupts = <GIC_SPI 211 IRQ_TYPE_LEVEL_HIGH>; +- }; +- +- wo_ccif1: syscon@151ad000 { +- compatible = "mediatek,mt7986-wo-ccif", "syscon"; +- reg = <0 0x151ad000 0 0x1000>; +- interrupt-parent = <&gic>; +- interrupts = <GIC_SPI 212 IRQ_TYPE_LEVEL_HIGH>; +- }; +- + eth: ethernet@15100000 { + compatible = "mediatek,mt7986-eth"; + reg = <0 0x15100000 0 0x80000>; +@@ -586,6 +563,20 @@ + status = "disabled"; + }; + ++ wo_ccif0: syscon@151a5000 { ++ compatible = "mediatek,mt7986-wo-ccif", "syscon"; ++ reg = <0 0x151a5000 0 0x1000>; ++ interrupt-parent = <&gic>; ++ interrupts = <GIC_SPI 211 IRQ_TYPE_LEVEL_HIGH>; ++ }; ++ ++ wo_ccif1: syscon@151ad000 { ++ compatible = "mediatek,mt7986-wo-ccif", "syscon"; ++ reg = <0 0x151ad000 0 0x1000>; ++ interrupt-parent = <&gic>; ++ interrupts = <GIC_SPI 212 IRQ_TYPE_LEVEL_HIGH>; ++ }; ++ + wifi: wifi@18000000 { + compatible = "mediatek,mt7986-wmac"; + reg = <0 0x18000000 0 0x1000000>, +@@ -643,4 +634,13 @@ + }; + }; + }; ++ ++ timer { ++ compatible = "arm,armv8-timer"; ++ interrupt-parent = <&gic>; ++ interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, ++ <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, ++ <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, ++ <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; ++ }; + }; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt7986-reorder-properties.patch b/queue-6.6/arm64-dts-mediatek-mt7986-reorder-properties.patch new file mode 100644 index 0000000000..f2c316350c --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt7986-reorder-properties.patch @@ -0,0 +1,249 @@ +From 0e56d07c9e5567ab1bf0687cc56f50c9f54963a7 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 12 Feb 2024 13:16:19 +0100 +Subject: arm64: dts: mediatek: mt7986: reorder properties +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> + +[ Upstream commit 7eb133c99fbebc6adb1cbd22c926d42d2bbca648 ] + +Use order described as preferred in DTS Coding Style. Mostly just move +"compatible", "reg" and "ranges" properties. In two nodes also move +vendor-prefixed props down. + +Signed-off-by: RafaÅ‚ MiÅ‚ecki <rafal@milecki.pl> +Link: https://lore.kernel.org/r/20240212121620.15035-1-zajec5@gmail.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Stable-dep-of: 3b449bfd2ff6 ("arm64: dts: mediatek: mt7986: drop invalid properties from ethsys") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt7986a.dtsi | 67 ++++++++++++----------- + 1 file changed, 34 insertions(+), 33 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +index d974739eae1c9..eba5e27a1bbea 100644 +--- a/arch/arm64/boot/dts/mediatek/mt7986a.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt7986a.dtsi +@@ -27,34 +27,34 @@ + #address-cells = <1>; + #size-cells = <0>; + cpu0: cpu@0 { +- device_type = "cpu"; + compatible = "arm,cortex-a53"; +- enable-method = "psci"; + reg = <0x0>; ++ device_type = "cpu"; ++ enable-method = "psci"; + #cooling-cells = <2>; + }; + + cpu1: cpu@1 { +- device_type = "cpu"; + compatible = "arm,cortex-a53"; +- enable-method = "psci"; + reg = <0x1>; ++ device_type = "cpu"; ++ enable-method = "psci"; + #cooling-cells = <2>; + }; + + cpu2: cpu@2 { +- device_type = "cpu"; + compatible = "arm,cortex-a53"; +- enable-method = "psci"; + reg = <0x2>; ++ device_type = "cpu"; ++ enable-method = "psci"; + #cooling-cells = <2>; + }; + + cpu3: cpu@3 { +- device_type = "cpu"; +- enable-method = "psci"; + compatible = "arm,cortex-a53"; + reg = <0x3>; ++ device_type = "cpu"; ++ enable-method = "psci"; + #cooling-cells = <2>; + }; + }; +@@ -131,22 +131,22 @@ + }; + + soc { +- #address-cells = <2>; +- #size-cells = <2>; + compatible = "simple-bus"; + ranges; ++ #address-cells = <2>; ++ #size-cells = <2>; + + gic: interrupt-controller@c000000 { + compatible = "arm,gic-v3"; +- #interrupt-cells = <3>; +- interrupt-parent = <&gic>; +- interrupt-controller; + reg = <0 0x0c000000 0 0x10000>, /* GICD */ + <0 0x0c080000 0 0x80000>, /* GICR */ + <0 0x0c400000 0 0x2000>, /* GICC */ + <0 0x0c410000 0 0x1000>, /* GICH */ + <0 0x0c420000 0 0x2000>; /* GICV */ ++ interrupt-parent = <&gic>; + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>; ++ interrupt-controller; ++ #interrupt-cells = <3>; + }; + + infracfg: infracfg@10001000 { +@@ -310,9 +310,9 @@ + + spi0: spi@1100a000 { + compatible = "mediatek,mt7986-spi-ipm", "mediatek,spi-ipm"; ++ reg = <0 0x1100a000 0 0x100>; + #address-cells = <1>; + #size-cells = <0>; +- reg = <0 0x1100a000 0 0x100>; + interrupts = <GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&topckgen CLK_TOP_MPLL_D2>, + <&topckgen CLK_TOP_SPI_SEL>, +@@ -324,9 +324,9 @@ + + spi1: spi@1100b000 { + compatible = "mediatek,mt7986-spi-ipm", "mediatek,spi-ipm"; ++ reg = <0 0x1100b000 0 0x100>; + #address-cells = <1>; + #size-cells = <0>; +- reg = <0 0x1100b000 0 0x100>; + interrupts = <GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&topckgen CLK_TOP_MPLL_D2>, + <&topckgen CLK_TOP_SPIM_MST_SEL>, +@@ -388,7 +388,6 @@ + }; + + thermal: thermal@1100c800 { +- #thermal-sensor-cells = <1>; + compatible = "mediatek,mt7986-thermal"; + reg = <0 0x1100c800 0 0x800>; + interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>; +@@ -396,30 +395,30 @@ + <&infracfg CLK_INFRA_ADC_26M_CK>, + <&infracfg CLK_INFRA_ADC_FRC_CK>; + clock-names = "therm", "auxadc", "adc_32k"; +- mediatek,auxadc = <&auxadc>; +- mediatek,apmixedsys = <&apmixedsys>; + nvmem-cells = <&thermal_calibration>; + nvmem-cell-names = "calibration-data"; ++ #thermal-sensor-cells = <1>; ++ mediatek,auxadc = <&auxadc>; ++ mediatek,apmixedsys = <&apmixedsys>; + }; + + pcie: pcie@11280000 { + compatible = "mediatek,mt7986-pcie", + "mediatek,mt8192-pcie"; ++ reg = <0x00 0x11280000 0x00 0x4000>; ++ reg-names = "pcie-mac"; ++ ranges = <0x82000000 0x00 0x20000000 0x00 ++ 0x20000000 0x00 0x10000000>; + device_type = "pci"; + #address-cells = <3>; + #size-cells = <2>; +- reg = <0x00 0x11280000 0x00 0x4000>; +- reg-names = "pcie-mac"; + interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>; + bus-range = <0x00 0xff>; +- ranges = <0x82000000 0x00 0x20000000 0x00 +- 0x20000000 0x00 0x10000000>; + clocks = <&infracfg CLK_INFRA_IPCIE_PIPE_CK>, + <&infracfg CLK_INFRA_IPCIE_CK>, + <&infracfg CLK_INFRA_IPCIER_CK>, + <&infracfg CLK_INFRA_IPCIEB_CK>; + clock-names = "pl_250m", "tl_26m", "peri_26m", "top_133m"; +- status = "disabled"; + + phys = <&pcie_port PHY_TYPE_PCIE>; + phy-names = "pcie-phy"; +@@ -430,6 +429,8 @@ + <0 0 0 2 &pcie_intc 1>, + <0 0 0 3 &pcie_intc 2>, + <0 0 0 4 &pcie_intc 3>; ++ status = "disabled"; ++ + pcie_intc: interrupt-controller { + #address-cells = <0>; + #interrupt-cells = <1>; +@@ -440,9 +441,9 @@ + pcie_phy: t-phy { + compatible = "mediatek,mt7986-tphy", + "mediatek,generic-tphy-v2"; ++ ranges; + #address-cells = <2>; + #size-cells = <2>; +- ranges; + status = "disabled"; + + pcie_port: pcie-phy@11c00000 { +@@ -467,9 +468,9 @@ + usb_phy: t-phy@11e10000 { + compatible = "mediatek,mt7986-tphy", + "mediatek,generic-tphy-v2"; ++ ranges = <0 0 0x11e10000 0x1700>; + #address-cells = <1>; + #size-cells = <1>; +- ranges = <0 0 0x11e10000 0x1700>; + status = "disabled"; + + u2port0: usb-phy@0 { +@@ -497,11 +498,11 @@ + }; + + ethsys: syscon@15000000 { +- #address-cells = <1>; +- #size-cells = <1>; + compatible = "mediatek,mt7986-ethsys", + "syscon"; + reg = <0 0x15000000 0 0x1000>; ++ #address-cells = <1>; ++ #size-cells = <1>; + #clock-cells = <1>; + #reset-cells = <1>; + }; +@@ -578,26 +579,26 @@ + <&topckgen CLK_TOP_SGM_325M_SEL>; + assigned-clock-parents = <&apmixedsys CLK_APMIXED_NET2PLL>, + <&apmixedsys CLK_APMIXED_SGMPLL>; ++ #reset-cells = <1>; ++ #address-cells = <1>; ++ #size-cells = <0>; + mediatek,ethsys = <ðsys>; + mediatek,sgmiisys = <&sgmiisys0>, <&sgmiisys1>; + mediatek,wed-pcie = <&wed_pcie>; + mediatek,wed = <&wed0>, <&wed1>; +- #reset-cells = <1>; +- #address-cells = <1>; +- #size-cells = <0>; + status = "disabled"; + }; + + wifi: wifi@18000000 { + compatible = "mediatek,mt7986-wmac"; ++ reg = <0 0x18000000 0 0x1000000>, ++ <0 0x10003000 0 0x1000>, ++ <0 0x11d10000 0 0x1000>; + resets = <&watchdog MT7986_TOPRGU_CONSYS_SW_RST>; + reset-names = "consys"; + clocks = <&topckgen CLK_TOP_CONN_MCUSYS_SEL>, + <&topckgen CLK_TOP_AP2CNN_HOST_SEL>; + clock-names = "mcu", "ap2conn"; +- reg = <0 0x18000000 0 0x1000000>, +- <0 0x10003000 0 0x1000>, +- <0 0x11d10000 0 0x1000>; + interrupts = <GIC_SPI 213 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 214 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 215 IRQ_TYPE_LEVEL_HIGH>, +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8183-add-power-domains-properit.patch b/queue-6.6/arm64-dts-mediatek-mt8183-add-power-domains-properit.patch new file mode 100644 index 0000000000..7b43ec9070 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8183-add-power-domains-properit.patch @@ -0,0 +1,39 @@ +From e6de38f764ff375a5d8a14b66b621146aade6970 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 23 Feb 2024 17:11:21 +0800 +Subject: arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg + +From: Ikjoon Jang <ikjn@chromium.org> + +[ Upstream commit 1781f2c461804c0123f59afc7350e520a88edffb ] + +mfgcfg clock is under MFG_ASYNC power domain. + +Fixes: e526c9bc11f8 ("arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile") +Fixes: 37fb78b9aeb7 ("arm64: dts: mediatek: Add mt8183 power domains controller") +Signed-off-by: Weiyi Lu <weiyi.lu@mediatek.com> +Signed-off-by: Ikjoon Jang <ikjn@chromium.org> +Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> +Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> +Link: https://lore.kernel.org/r/20240223091122.2430037-1-wenst@chromium.org +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8183.dtsi | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi +index df6e9990cd5fa..8721a5ffca30a 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi +@@ -1628,6 +1628,7 @@ + compatible = "mediatek,mt8183-mfgcfg", "syscon"; + reg = <0 0x13000000 0 0x1000>; + #clock-cells = <1>; ++ power-domains = <&spm MT8183_POWER_DOMAIN_MFG_ASYNC>; + }; + + gpu: gpu@13040000 { +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8183-kukui-use-default-min-volt.patch b/queue-6.6/arm64-dts-mediatek-mt8183-kukui-use-default-min-volt.patch new file mode 100644 index 0000000000..785d3df7b6 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8183-kukui-use-default-min-volt.patch @@ -0,0 +1,40 @@ +From c841fb581582f19209722f9f3c0bb59e1bffbcf5 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 15 Mar 2024 19:16:04 +0800 +Subject: arm64: dts: mediatek: mt8183-kukui: Use default min voltage for + MT6358 + +From: Pin-yen Lin <treapking@chromium.org> + +[ Upstream commit 296118a8dc297de47d9b3a364b9743f8446bd612 ] + +The requested voltage could be lower than the minimum voltage on the +GPU OPP table when the MTK Smart Voltage Scaling (SVS) driver is +enabled, so removing the definition in mt8183-kukui to use the default +minimum voltage (500000 uV) defined in mt6358.dtsi. + +Fixes: 31c6732da9d5 ("arm64: dts: mediatek: mt8183-kukui: Override vgpu/vsram_gpu constraints") +Signed-off-by: Pin-yen Lin <treapking@chromium.org> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240315111621.2263159-4-treapking@chromium.org +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi b/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi +index 70becf10cacb8..d846342c1d3b2 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi +@@ -405,7 +405,6 @@ + }; + + &mt6358_vgpu_reg { +- regulator-min-microvolt = <625000>; + regulator-max-microvolt = <900000>; + + regulator-coupled-with = <&mt6358_vsram_gpu_reg>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8192-add-missing-gce-client-reg.patch b/queue-6.6/arm64-dts-mediatek-mt8192-add-missing-gce-client-reg.patch new file mode 100644 index 0000000000..532b162f22 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8192-add-missing-gce-client-reg.patch @@ -0,0 +1,43 @@ +From 4ae0b223c18b1bef4b4a22c933d7189a96da2362 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 29 Feb 2024 14:44:28 -0500 +Subject: arm64: dts: mediatek: mt8192: Add missing gce-client-reg to mutex +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: NÃcolas F. R. A. Prado <nfraprado@collabora.com> + +[ Upstream commit 00bcc8810d9dd69d3899a4189e2f3964f263a600 ] + +Add the missing mediatek,gce-client-reg property to the mutex node to +allow it to use the GCE. This prevents the "can't parse gce-client-reg +property" error from being printed and should result in better +performance. + +Fixes: b4b75bac952b ("arm64: dts: mt8192: Add display nodes") +Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: NÃcolas F. R. A. Prado <nfraprado@collabora.com> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240229-gce-client-reg-add-missing-mt8192-95-v1-1-b12c233a8a33@collabora.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8192.dtsi | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8192.dtsi b/arch/arm64/boot/dts/mediatek/mt8192.dtsi +index f1fc14e53f8c7..b1443adc55aab 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8192.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8192.dtsi +@@ -1412,6 +1412,7 @@ + reg = <0 0x14001000 0 0x1000>; + interrupts = <GIC_SPI 252 IRQ_TYPE_LEVEL_HIGH 0>; + clocks = <&mmsys CLK_MM_DISP_MUTEX0>; ++ mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX 0x1000 0x1000>; + mediatek,gce-events = <CMDQ_EVENT_DISP_STREAM_DONE_ENG_EVENT_0>, + <CMDQ_EVENT_DISP_STREAM_DONE_ENG_EVENT_1>; + power-domains = <&spm MT8192_POWER_DOMAIN_DISP>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8192-asurada-update-min-voltage.patch b/queue-6.6/arm64-dts-mediatek-mt8192-asurada-update-min-voltage.patch new file mode 100644 index 0000000000..fcd5ac9e38 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8192-asurada-update-min-voltage.patch @@ -0,0 +1,62 @@ +From f5d25013e0daae0e0fbe2241734bd03588951b6c Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 15 Mar 2024 19:16:02 +0800 +Subject: arm64: dts: mediatek: mt8192-asurada: Update min voltage constraint + for MT6315 + +From: Pin-yen Lin <treapking@chromium.org> + +[ Upstream commit 374a7c6400e314458178255a63c37d6347845092 ] + +Update the minimum voltage from 300000 uV to 400000 uV so it matches +the MT6315 datasheet. + +Also update the minimum voltage for Vgpu regulator from 606250 uV to +400000 uV because the requested voltage could be lower than the minimum +voltage on the GPU OPP table when the MTK Smart Voltage Scaling (SVS) +driver is enabled. + +Fixes: 3183cb62b033 ("arm64: dts: mediatek: asurada: Add SPMI regulators") +Signed-off-by: Pin-yen Lin <treapking@chromium.org> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240315111621.2263159-2-treapking@chromium.org +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi +index 4bd1494b354c0..dc39ebd1bbfc8 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi +@@ -1392,7 +1392,7 @@ + mt6315_6_vbuck1: vbuck1 { + regulator-compatible = "vbuck1"; + regulator-name = "Vbcpu"; +- regulator-min-microvolt = <300000>; ++ regulator-min-microvolt = <400000>; + regulator-max-microvolt = <1193750>; + regulator-enable-ramp-delay = <256>; + regulator-allowed-modes = <0 1 2>; +@@ -1402,7 +1402,7 @@ + mt6315_6_vbuck3: vbuck3 { + regulator-compatible = "vbuck3"; + regulator-name = "Vlcpu"; +- regulator-min-microvolt = <300000>; ++ regulator-min-microvolt = <400000>; + regulator-max-microvolt = <1193750>; + regulator-enable-ramp-delay = <256>; + regulator-allowed-modes = <0 1 2>; +@@ -1419,7 +1419,7 @@ + mt6315_7_vbuck1: vbuck1 { + regulator-compatible = "vbuck1"; + regulator-name = "Vgpu"; +- regulator-min-microvolt = <606250>; ++ regulator-min-microvolt = <400000>; + regulator-max-microvolt = <800000>; + regulator-enable-ramp-delay = <256>; + regulator-allowed-modes = <0 1 2>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch b/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch new file mode 100644 index 0000000000..a2ffccbd82 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch @@ -0,0 +1,59 @@ +From 4765c97d873bcd6903bc56517cbe836c49a1e15b Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 29 Feb 2024 14:44:29 -0500 +Subject: arm64: dts: mediatek: mt8195: Add missing gce-client-reg to + vpp/vdosys +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: NÃcolas F. R. A. Prado <nfraprado@collabora.com> + +[ Upstream commit 96b0c1528ef41fe754f5d1378b1db6c098a2e33f ] + +Add the missing mediatek,gce-client-reg property to the vppsys and +vdosys nodes to allow them to use the GCE. This prevents the "can't +parse gce-client-reg property" error from being printed and should +result in better performance. + +Fixes: 6aa5b46d1755 ("arm64: dts: mt8195: Add vdosys and vppsys clock nodes") +Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: NÃcolas F. R. A. Prado <nfraprado@collabora.com> +Link: https://lore.kernel.org/r/20240229-gce-client-reg-add-missing-mt8192-95-v1-2-b12c233a8a33@collabora.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8195.dtsi | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi +index 6708c4d21abf9..8fe8917daed1d 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi +@@ -1963,6 +1963,7 @@ + compatible = "mediatek,mt8195-vppsys0", "syscon"; + reg = <0 0x14000000 0 0x1000>; + #clock-cells = <1>; ++ mediatek,gce-client-reg = <&gce1 SUBSYS_1400XXXX 0 0x1000>; + }; + + mutex@1400f000 { +@@ -2077,6 +2078,7 @@ + compatible = "mediatek,mt8195-vppsys1", "syscon"; + reg = <0 0x14f00000 0 0x1000>; + #clock-cells = <1>; ++ mediatek,gce-client-reg = <&gce1 SUBSYS_14f0XXXX 0 0x1000>; + }; + + mutex@14f01000 { +@@ -2623,6 +2625,7 @@ + reg = <0 0x1c01a000 0 0x1000>; + mboxes = <&gce0 0 CMDQ_THR_PRIO_4>; + #clock-cells = <1>; ++ mediatek,gce-client-reg = <&gce0 SUBSYS_1c01XXXX 0xa000 0x1000>; + }; + + +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-15253 b/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-15253 new file mode 100644 index 0000000000..3d7597d5bc --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-15253 @@ -0,0 +1,42 @@ +From cbb023a69eefaef446b0f383b73dbfcea97d5482 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 29 Feb 2024 14:44:30 -0500 +Subject: arm64: dts: mediatek: mt8195: Add missing gce-client-reg to mutex +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: NÃcolas F. R. A. Prado <nfraprado@collabora.com> + +[ Upstream commit 3b129949184a1251e6a42db714f6d68b75fabedd ] + +Add the missing mediatek,gce-client-reg property to the mutex node to +allow it to use the GCE. This prevents the "can't parse gce-client-reg +property" error from being printed and should result in better +performance. + +Fixes: b852ee68fd72 ("arm64: dts: mt8195: Add display node for vdosys0") +Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: NÃcolas F. R. A. Prado <nfraprado@collabora.com> +Link: https://lore.kernel.org/r/20240229-gce-client-reg-add-missing-mt8192-95-v1-3-b12c233a8a33@collabora.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8195.dtsi | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi +index 8fe8917daed1d..884e56f4a93bb 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi +@@ -2779,6 +2779,7 @@ + interrupts = <GIC_SPI 658 IRQ_TYPE_LEVEL_HIGH 0>; + power-domains = <&spm MT8195_POWER_DOMAIN_VDOSYS0>; + clocks = <&vdosys0 CLK_VDO0_DISP_MUTEX0>; ++ mediatek,gce-client-reg = <&gce0 SUBSYS_1c01XXXX 0x6000 0x1000>; + mediatek,gce-events = <CMDQ_EVENT_VDO0_DISP_STREAM_DONE_0>; + }; + +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-7739 b/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-7739 new file mode 100644 index 0000000000..a82d249678 --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-7739 @@ -0,0 +1,42 @@ +From 10c27b7861beddc26bd8aa1944a431a8e92b32a6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 29 Feb 2024 14:44:31 -0500 +Subject: arm64: dts: mediatek: mt8195: Add missing gce-client-reg to mutex1 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: NÃcolas F. R. A. Prado <nfraprado@collabora.com> + +[ Upstream commit 58f126296c3c52d02bf3fad1f68c331d718c4a9b ] + +Add the missing mediatek,gce-client-reg property to the mutex1 node to +allow it to use the GCE. This prevents the "can't parse gce-client-reg +property" error from being printed and should result in better +performance. + +Fixes: 92d2c23dc269 ("arm64: dts: mt8195: add display node for vdosys1") +Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: NÃcolas F. R. A. Prado <nfraprado@collabora.com> +Link: https://lore.kernel.org/r/20240229-gce-client-reg-add-missing-mt8192-95-v1-4-b12c233a8a33@collabora.com +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8195.dtsi | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi +index 884e56f4a93bb..2bb9d9aa65fed 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi +@@ -2850,6 +2850,7 @@ + power-domains = <&spm MT8195_POWER_DOMAIN_VDOSYS1>; + clocks = <&vdosys1 CLK_VDO1_DISP_MUTEX>; + clock-names = "vdo1_mutex"; ++ mediatek,gce-client-reg = <&gce0 SUBSYS_1c10XXXX 0x1000 0x1000>; + mediatek,gce-events = <CMDQ_EVENT_VDO1_STREAM_DONE_ENG_0>; + }; + +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-mediatek-mt8195-cherry-update-min-voltage-.patch b/queue-6.6/arm64-dts-mediatek-mt8195-cherry-update-min-voltage-.patch new file mode 100644 index 0000000000..fa4c1b6a5e --- /dev/null +++ b/queue-6.6/arm64-dts-mediatek-mt8195-cherry-update-min-voltage-.patch @@ -0,0 +1,53 @@ +From b0fedbb63fa8b7923ac47e9ac3a5affa3434d0a4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 15 Mar 2024 19:16:03 +0800 +Subject: arm64: dts: mediatek: mt8195-cherry: Update min voltage constraint + for MT6315 + +From: Pin-yen Lin <treapking@chromium.org> + +[ Upstream commit e9a6b8b5c61350535c7eb5ea9b2dde0d5745bd1b ] + +Update the minimum voltage from 300000 uV to 400000 uV so it matches +the MT6315 datasheet. + +Also update the minimum voltage for Vgpu regulator from 625000 uV to +400000 uV because the requested voltage could be lower than the minimum +voltage on the GPU OPP table when the MTK Smart Voltage Scaling (SVS) +driver is enabled. + +Fixes: 260c04d425eb ("arm64: dts: mediatek: cherry: Enable MT6315 regulators on SPMI bus") +Signed-off-by: Pin-yen Lin <treapking@chromium.org> +Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Link: https://lore.kernel.org/r/20240315111621.2263159-3-treapking@chromium.org +Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi +index 663c9f414b611..b78f408110bf7 100644 +--- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi ++++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi +@@ -1205,7 +1205,7 @@ + mt6315_6_vbuck1: vbuck1 { + regulator-compatible = "vbuck1"; + regulator-name = "Vbcpu"; +- regulator-min-microvolt = <300000>; ++ regulator-min-microvolt = <400000>; + regulator-max-microvolt = <1193750>; + regulator-enable-ramp-delay = <256>; + regulator-ramp-delay = <6250>; +@@ -1223,7 +1223,7 @@ + mt6315_7_vbuck1: vbuck1 { + regulator-compatible = "vbuck1"; + regulator-name = "Vgpu"; +- regulator-min-microvolt = <625000>; ++ regulator-min-microvolt = <400000>; + regulator-max-microvolt = <1193750>; + regulator-enable-ramp-delay = <256>; + regulator-ramp-delay = <6250>; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-qcom-sc8180x-fix-ss_phy_irq-for-secondary-.patch b/queue-6.6/arm64-dts-qcom-sc8180x-fix-ss_phy_irq-for-secondary-.patch new file mode 100644 index 0000000000..ffa8b574e4 --- /dev/null +++ b/queue-6.6/arm64-dts-qcom-sc8180x-fix-ss_phy_irq-for-secondary-.patch @@ -0,0 +1,73 @@ +From 84b090f6f217b2c22d523fa49920a433f767f8f2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 28 Mar 2024 03:21:57 +0100 +Subject: arm64: dts: qcom: sc8180x: Fix ss_phy_irq for secondary USB + controller + +From: Maximilian Luz <luzmaximilian@gmail.com> + +[ Upstream commit ecda8309098402f878c96184f29a1b7ec682d772 ] + +The ACPI DSDT of the Surface Pro X (SQ2) specifies the interrupts for +the secondary UBS controller as + + Name (_CRS, ResourceTemplate () + { + Interrupt (ResourceConsumer, Level, ActiveHigh, Shared, ,, ) + { + 0x000000AA, + } + Interrupt (ResourceConsumer, Level, ActiveHigh, SharedAndWake, ,, ) + { + 0x000000A7, // hs_phy_irq: &intc GIC_SPI 136 + } + Interrupt (ResourceConsumer, Level, ActiveHigh, SharedAndWake, ,, ) + { + 0x00000228, // ss_phy_irq: &pdc 40 + } + Interrupt (ResourceConsumer, Edge, ActiveHigh, SharedAndWake, ,, ) + { + 0x0000020A, // dm_hs_phy_irq: &pdc 10 + } + Interrupt (ResourceConsumer, Edge, ActiveHigh, SharedAndWake, ,, ) + { + 0x0000020B, // dp_hs_phy_irq: &pdc 11 + } + }) + +Generally, the interrupts above 0x200 map to the PDC interrupts (as used +in the devicetree) as ACPI_NUMBER - 0x200. Note that this lines up with +dm_hs_phy_irq and dp_hs_phy_irq (as well as the interrupts for the +primary USB controller). + +Based on the snippet above, ss_phy_irq should therefore be PDC 40 (= +0x28) and not PDC 7. The latter is according to ACPI instead used as +ss_phy_irq for port 0 of the multiport USB controller). Fix this by +setting ss_phy_irq to '&pdc 40'. + +Fixes: b080f53a8f44 ("arm64: dts: qcom: sc8180x: Add remoteprocs, wifi and usb nodes") +Signed-off-by: Maximilian Luz <luzmaximilian@gmail.com> +Reviewed-by: Bjorn Andersson <andersson@kernel.org> +Link: https://lore.kernel.org/r/20240328022224.336938-1-luzmaximilian@gmail.com +Signed-off-by: Bjorn Andersson <andersson@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/qcom/sc8180x.dtsi | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/qcom/sc8180x.dtsi b/arch/arm64/boot/dts/qcom/sc8180x.dtsi +index 6eb4c5eb6bb8c..fbb9bf09078a0 100644 +--- a/arch/arm64/boot/dts/qcom/sc8180x.dtsi ++++ b/arch/arm64/boot/dts/qcom/sc8180x.dtsi +@@ -2644,7 +2644,7 @@ + resets = <&gcc GCC_USB30_SEC_BCR>; + power-domains = <&gcc USB30_SEC_GDSC>; + interrupts-extended = <&intc GIC_SPI 136 IRQ_TYPE_LEVEL_HIGH>, +- <&pdc 7 IRQ_TYPE_LEVEL_HIGH>, ++ <&pdc 40 IRQ_TYPE_LEVEL_HIGH>, + <&pdc 10 IRQ_TYPE_EDGE_BOTH>, + <&pdc 11 IRQ_TYPE_EDGE_BOTH>; + interrupt-names = "hs_phy_irq", "ss_phy_irq", +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-rockchip-enable-internal-pull-up-on-pcie_w.patch b/queue-6.6/arm64-dts-rockchip-enable-internal-pull-up-on-pcie_w.patch new file mode 100644 index 0000000000..401ec69f7d --- /dev/null +++ b/queue-6.6/arm64-dts-rockchip-enable-internal-pull-up-on-pcie_w.patch @@ -0,0 +1,44 @@ +From 1bcfd1c59d5de9bf8919397885463aeb2b5be4a2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 8 Mar 2024 16:46:08 +0100 +Subject: arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for + RK3399 Puma + +From: Quentin Schulz <quentin.schulz@theobroma-systems.com> + +[ Upstream commit 945a7c8570916650a415757d15d83e0fa856a686 ] + +The PCIE_WAKE# has a diode used as a level-shifter, and is used as an +input pin. While the SoC default is to enable the pull-up, the core +rk3399 pinconf for this pin opted for pull-none. So as to not disturb +the behaviour of other boards which may rely on pull-none instead of +pull-up, set the needed pull-up only for RK3399 Puma. + +Fixes: 60fd9f72ce8a ("arm64: dts: rockchip: add Haikou baseboard with RK3399-Q7 SoM") +Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> +Link: https://lore.kernel.org/r/20240308-puma-diode-pu-v2-2-309f83da110a@theobroma-systems.com +Signed-off-by: Heiko Stuebner <heiko@sntech.de> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +index 2979e6f4f96ce..39ec38ac716ed 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi ++++ b/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +@@ -401,6 +401,11 @@ + gpio1830-supply = <&vcc_1v8>; + }; + ++&pcie_clkreqn_cpm { ++ rockchip,pins = ++ <2 RK_PD2 RK_FUNC_GPIO &pcfg_pull_up>; ++}; ++ + &pinctrl { + i2c8 { + i2c8_xfer_a: i2c8-xfer { +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-rockchip-enable-internal-pull-up-on-q7_usb.patch b/queue-6.6/arm64-dts-rockchip-enable-internal-pull-up-on-q7_usb.patch new file mode 100644 index 0000000000..cc9fb6c538 --- /dev/null +++ b/queue-6.6/arm64-dts-rockchip-enable-internal-pull-up-on-q7_usb.patch @@ -0,0 +1,40 @@ +From 7a0da8d93267128ce1cf053db814eaf26b38490f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 8 Mar 2024 16:46:07 +0100 +Subject: arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 + Puma + +From: Quentin Schulz <quentin.schulz@theobroma-systems.com> + +[ Upstream commit e6b1168f37e3f86d9966276c5a3fff9eb0df3e5f ] + +The Q7_USB_ID has a diode used as a level-shifter, and is used as an +input pin. The SoC default for this pin is a pull-up, which is correct +but the pinconf in the introducing commit missed that, so let's fix this +oversight. + +Fixes: ed2c66a95c0c ("arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode") +Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> +Link: https://lore.kernel.org/r/20240308-puma-diode-pu-v2-1-309f83da110a@theobroma-systems.com +Signed-off-by: Heiko Stuebner <heiko@sntech.de> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +index 20e3f41efe97f..9b9d70bf7f0ca 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi ++++ b/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +@@ -443,7 +443,7 @@ + usb3 { + usb3_id: usb3-id { + rockchip,pins = +- <1 RK_PC2 RK_FUNC_GPIO &pcfg_pull_none>; ++ <1 RK_PC2 RK_FUNC_GPIO &pcfg_pull_up>; + }; + }; + }; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-rockchip-fix-alphabetical-ordering-rk3399-.patch b/queue-6.6/arm64-dts-rockchip-fix-alphabetical-ordering-rk3399-.patch new file mode 100644 index 0000000000..1c8c17fb71 --- /dev/null +++ b/queue-6.6/arm64-dts-rockchip-fix-alphabetical-ordering-rk3399-.patch @@ -0,0 +1,62 @@ +From f7b16b292c0912e81f39cf6c60e34031114f7589 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 8 Mar 2024 09:52:43 +0100 +Subject: arm64: dts: rockchip: fix alphabetical ordering RK3399 puma + +From: Iskander Amara <iskander.amara@theobroma-systems.com> + +[ Upstream commit f0abb4b2c7acf3c3e4130dc3f54cd90cf2ae62bc ] + +Nodes overridden by their reference should be ordered alphabetically to +make it easier to read the DTS. pinctrl node is defined in the wrong +location so let's reorder it. + +Signed-off-by: Iskander Amara <iskander.amara@theobroma-systems.com> +Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com> +Link: https://lore.kernel.org/r/20240308085243.69903-2-iskander.amara@theobroma-systems.com +Signed-off-by: Heiko Stuebner <heiko@sntech.de> +Stable-dep-of: 945a7c857091 ("arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 Puma") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 18 +++++++++--------- + 1 file changed, 9 insertions(+), 9 deletions(-) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +index 9b9d70bf7f0ca..2979e6f4f96ce 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi ++++ b/arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +@@ -401,15 +401,6 @@ + gpio1830-supply = <&vcc_1v8>; + }; + +-&pmu_io_domains { +- status = "okay"; +- pmu1830-supply = <&vcc_1v8>; +-}; +- +-&pwm2 { +- status = "okay"; +-}; +- + &pinctrl { + i2c8 { + i2c8_xfer_a: i2c8-xfer { +@@ -448,6 +439,15 @@ + }; + }; + ++&pmu_io_domains { ++ status = "okay"; ++ pmu1830-supply = <&vcc_1v8>; ++}; ++ ++&pwm2 { ++ status = "okay"; ++}; ++ + &sdhci { + /* + * Signal integrity isn't great at 200MHz but 100MHz has proven stable +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-rockchip-regulator-for-sd-needs-to-be-alwa.patch b/queue-6.6/arm64-dts-rockchip-regulator-for-sd-needs-to-be-alwa.patch new file mode 100644 index 0000000000..62aee78a52 --- /dev/null +++ b/queue-6.6/arm64-dts-rockchip-regulator-for-sd-needs-to-be-alwa.patch @@ -0,0 +1,43 @@ +From 888b0a0695506afc0cc2fe6330b69a6dcbd7ba60 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 5 Mar 2024 15:32:18 +0100 +Subject: arm64: dts: rockchip: regulator for sd needs to be always on for + BPI-R2Pro + +From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com> + +[ Upstream commit 433d54818f64a2fe0562f8c04c7a81f562368515 ] + +With default dts configuration for BPI-R2Pro, the regulator for sd card is +powered off when reboot is commanded, and the only solution to detect the +sd card again, and therefore, allow rebooting from there, is to do a +hardware reset. + +Configure the regulator for sd to be always on for BPI-R2Pro in order to +avoid this issue. + +Fixes: f901aaadaa2a ("arm64: dts: rockchip: Add Bananapi R2 Pro") +Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com> +Link: https://lore.kernel.org/r/20240305143222.189413-1-jtornosm@redhat.com +Signed-off-by: Heiko Stuebner <heiko@sntech.de> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts +index 87c45d8be420f..dc5892d25c100 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts ++++ b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts +@@ -416,6 +416,8 @@ + + vccio_sd: LDO_REG5 { + regulator-name = "vccio_sd"; ++ regulator-always-on; ++ regulator-boot-on; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <3300000>; + +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-rockchip-remove-unsupported-node-from-the-.patch b/queue-6.6/arm64-dts-rockchip-remove-unsupported-node-from-the-.patch new file mode 100644 index 0000000000..0d0183f52c --- /dev/null +++ b/queue-6.6/arm64-dts-rockchip-remove-unsupported-node-from-the-.patch @@ -0,0 +1,54 @@ +From 3836bc9641955057881a29059ad65b65c37814b3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 1 Apr 2024 00:20:56 +0200 +Subject: arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro + dts + +From: Dragan Simic <dsimic@manjaro.org> + +[ Upstream commit 43853e843aa6c3d47ff2b0cce898318839483d05 ] + +Remove a redundant node from the Pine64 Pinebook Pro dts, which is intended +to provide a value for the delay in PCI Express enumeration, but that isn't +supported without additional out-of-tree kernel patches. + +There were already efforts to upstream those kernel patches, because they +reportedly make some PCI Express cards (such as LSI SAS HBAs) usable in +Pine64 RockPro64 (which is also based on the RK3399); otherwise, those PCI +Express cards fail to enumerate. However, providing the required background +and explanations proved to be a tough nut to crack, which is the reason why +those patches remain outside of the kernel mainline for now. + +If those out-of-tree patches eventually become upstreamed, the resulting +device-tree changes will almost surely belong to the RK3399 SoC dtsi. Also, +the above-mentioned unusable-without-out-of-tree-patches PCI Express devices +are in all fairness not usable in a Pinebook Pro without some extensive +hardware modifications, which is another reason to delete this redundant +node. When it comes to the Pinebook Pro, only M.2 NVMe SSDs can be installed +out of the box (using an additional passive adapter PCB sold separately by +Pine64), which reportedly works fine with no additional patches. + +Fixes: 5a65505a6988 ("arm64: dts: rockchip: Add initial support for Pinebook Pro") +Signed-off-by: Dragan Simic <dsimic@manjaro.org> +Link: https://lore.kernel.org/r/0f82c3f97cb798d012270d13b34d8d15305ef293.1711923520.git.dsimic@manjaro.org +Signed-off-by: Heiko Stuebner <heiko@sntech.de> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts +index 054c6a4d1a45f..294eb2de263de 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts ++++ b/arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts +@@ -779,7 +779,6 @@ + }; + + &pcie0 { +- bus-scan-delay-ms = <1000>; + ep-gpios = <&gpio2 RK_PD4 GPIO_ACTIVE_HIGH>; + num-lanes = <4>; + pinctrl-names = "default"; +-- +2.43.0 + diff --git a/queue-6.6/arm64-dts-rockchip-set-phy-address-of-mt7531-switch-.patch b/queue-6.6/arm64-dts-rockchip-set-phy-address-of-mt7531-switch-.patch new file mode 100644 index 0000000000..f128111ddb --- /dev/null +++ b/queue-6.6/arm64-dts-rockchip-set-phy-address-of-mt7531-switch-.patch @@ -0,0 +1,49 @@ +From 61e8e027738f4f9c502afe23604946ae519b3c54 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 14 Mar 2024 15:24:35 +0300 +Subject: arm64: dts: rockchip: set PHY address of MT7531 switch to 0x1f +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Arınç ÃœNAL <arinc.unal@arinc9.com> + +[ Upstream commit a2ac2a1b02590a22a236c43c455f421cdede45f5 ] + +The MT7531 switch listens on PHY address 0x1f on an MDIO bus. I've got two +findings that support this. There's no bootstrapping option to change the +PHY address of the switch. The Linux driver hardcodes 0x1f as the PHY +address of the switch. So the reg property on the device tree is currently +ignored by the Linux driver. + +Therefore, describe the correct PHY address on Banana Pi BPI-R2 Pro that +has this switch. + +Signed-off-by: Arınç ÃœNAL <arinc.unal@arinc9.com> +Fixes: c1804463e5c6 ("arm64: dts: rockchip: Add mt7531 dsa node to BPI-R2-Pro board") +Link: https://lore.kernel.org/r/20240314-for-rockchip-mt7531-phy-address-v1-1-743b5873358f@arinc9.com +Signed-off-by: Heiko Stuebner <heiko@sntech.de> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts +index f9127ddfbb7df..87c45d8be420f 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts ++++ b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts +@@ -525,9 +525,9 @@ + #address-cells = <1>; + #size-cells = <0>; + +- switch@0 { ++ switch@1f { + compatible = "mediatek,mt7531"; +- reg = <0>; ++ reg = <0x1f>; + + ports { + #address-cells = <1>; +-- +2.43.0 + diff --git a/queue-6.6/ax25-fix-netdev-refcount-issue.patch b/queue-6.6/ax25-fix-netdev-refcount-issue.patch new file mode 100644 index 0000000000..ff0171e4ea --- /dev/null +++ b/queue-6.6/ax25-fix-netdev-refcount-issue.patch @@ -0,0 +1,95 @@ +From 358edd2bdf6cf04ff44dd91acf108e67d3e53731 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 19 Apr 2024 10:04:56 +0800 +Subject: ax25: Fix netdev refcount issue + +From: Duoming Zhou <duoming@zju.edu.cn> + +[ Upstream commit 467324bcfe1a31ec65d0cf4aa59421d6b7a7d52b ] + +The dev_tracker is added to ax25_cb in ax25_bind(). When the +ax25 device is detaching, the dev_tracker of ax25_cb should be +deallocated in ax25_kill_by_device() instead of the dev_tracker +of ax25_dev. The log reported by ref_tracker is shown below: + +[ 80.884935] ref_tracker: reference already released. +[ 80.885150] ref_tracker: allocated in: +[ 80.885349] ax25_dev_device_up+0x105/0x540 +[ 80.885730] ax25_device_event+0xa4/0x420 +[ 80.885730] notifier_call_chain+0xc9/0x1e0 +[ 80.885730] __dev_notify_flags+0x138/0x280 +[ 80.885730] dev_change_flags+0xd7/0x180 +[ 80.885730] dev_ifsioc+0x6a9/0xa30 +[ 80.885730] dev_ioctl+0x4d8/0xd90 +[ 80.885730] sock_do_ioctl+0x1c2/0x2d0 +[ 80.885730] sock_ioctl+0x38b/0x4f0 +[ 80.885730] __se_sys_ioctl+0xad/0xf0 +[ 80.885730] do_syscall_64+0xc4/0x1b0 +[ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f +[ 80.885730] ref_tracker: freed in: +[ 80.885730] ax25_device_event+0x272/0x420 +[ 80.885730] notifier_call_chain+0xc9/0x1e0 +[ 80.885730] dev_close_many+0x272/0x370 +[ 80.885730] unregister_netdevice_many_notify+0x3b5/0x1180 +[ 80.885730] unregister_netdev+0xcf/0x120 +[ 80.885730] sixpack_close+0x11f/0x1b0 +[ 80.885730] tty_ldisc_kill+0xcb/0x190 +[ 80.885730] tty_ldisc_hangup+0x338/0x3d0 +[ 80.885730] __tty_hangup+0x504/0x740 +[ 80.885730] tty_release+0x46e/0xd80 +[ 80.885730] __fput+0x37f/0x770 +[ 80.885730] __x64_sys_close+0x7b/0xb0 +[ 80.885730] do_syscall_64+0xc4/0x1b0 +[ 80.885730] entry_SYSCALL_64_after_hwframe+0x67/0x6f +[ 80.893739] ------------[ cut here ]------------ +[ 80.894030] WARNING: CPU: 2 PID: 140 at lib/ref_tracker.c:255 ref_tracker_free+0x47b/0x6b0 +[ 80.894297] Modules linked in: +[ 80.894929] CPU: 2 PID: 140 Comm: ax25_conn_rel_6 Not tainted 6.9.0-rc4-g8cd26fd90c1a #11 +[ 80.895190] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qem4 +[ 80.895514] RIP: 0010:ref_tracker_free+0x47b/0x6b0 +[ 80.895808] Code: 83 c5 18 4c 89 eb 48 c1 eb 03 8a 04 13 84 c0 0f 85 df 01 00 00 41 83 7d 00 00 75 4b 4c 89 ff 9 +[ 80.896171] RSP: 0018:ffff888009edf8c0 EFLAGS: 00000286 +[ 80.896339] RAX: 1ffff1100141ac00 RBX: 1ffff1100149463b RCX: dffffc0000000000 +[ 80.896502] RDX: 0000000000000001 RSI: 0000000000000246 RDI: ffff88800a0d6518 +[ 80.896925] RBP: ffff888009edf9b0 R08: ffff88806d3288d3 R09: 1ffff1100da6511a +[ 80.897212] R10: dffffc0000000000 R11: ffffed100da6511b R12: ffff88800a4a31d4 +[ 80.897859] R13: ffff88800a4a31d8 R14: dffffc0000000000 R15: ffff88800a0d6518 +[ 80.898279] FS: 00007fd88b7fe700(0000) GS:ffff88806d300000(0000) knlGS:0000000000000000 +[ 80.899436] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 80.900181] CR2: 00007fd88c001d48 CR3: 000000000993e000 CR4: 00000000000006f0 +... +[ 80.935774] ref_tracker: sp%d@000000000bb9df3d has 1/1 users at +[ 80.935774] ax25_bind+0x424/0x4e0 +[ 80.935774] __sys_bind+0x1d9/0x270 +[ 80.935774] __x64_sys_bind+0x75/0x80 +[ 80.935774] do_syscall_64+0xc4/0x1b0 +[ 80.935774] entry_SYSCALL_64_after_hwframe+0x67/0x6f + +Change ax25_dev->dev_tracker to the dev_tracker of ax25_cb +in order to mitigate the bug. + +Fixes: feef318c855a ("ax25: fix UAF bugs of net_device caused by rebinding operation") +Signed-off-by: Duoming Zhou <duoming@zju.edu.cn> +Link: https://lore.kernel.org/r/20240419020456.29826-1-duoming@zju.edu.cn +Signed-off-by: Paolo Abeni <pabeni@redhat.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/ax25/af_ax25.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/net/ax25/af_ax25.c b/net/ax25/af_ax25.c +index 5db805d5f74d7..9d11d26e46c0e 100644 +--- a/net/ax25/af_ax25.c ++++ b/net/ax25/af_ax25.c +@@ -103,7 +103,7 @@ static void ax25_kill_by_device(struct net_device *dev) + s->ax25_dev = NULL; + if (sk->sk_socket) { + netdev_put(ax25_dev->dev, +- &ax25_dev->dev_tracker); ++ &s->dev_tracker); + ax25_dev_put(ax25_dev); + } + ax25_cb_del(s); +-- +2.43.0 + diff --git a/queue-6.6/bluetooth-btusb-fix-triggering-coredump-implementati.patch b/queue-6.6/bluetooth-btusb-fix-triggering-coredump-implementati.patch new file mode 100644 index 0000000000..b1a0978904 --- /dev/null +++ b/queue-6.6/bluetooth-btusb-fix-triggering-coredump-implementati.patch @@ -0,0 +1,47 @@ +From e248d677b5d9902807f7d977d12c582660779980 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 25 Mar 2024 16:11:49 +0800 +Subject: Bluetooth: btusb: Fix triggering coredump implementation for QCA + +From: Zijun Hu <quic_zijuhu@quicinc.com> + +[ Upstream commit b23d98d46d2858dcc0fd016caff165cbdc24e70a ] + +btusb_coredump_qca() uses __hci_cmd_sync() to send a vendor-specific +command to trigger firmware coredump, but the command does not +have any event as its sync response, so it is not suitable to use +__hci_cmd_sync(), fixed by using __hci_cmd_send(). + +Fixes: 20981ce2d5a5 ("Bluetooth: btusb: Add WCN6855 devcoredump support") +Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com> +Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/bluetooth/btusb.c | 9 ++++----- + 1 file changed, 4 insertions(+), 5 deletions(-) + +diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c +index 1976593bc804e..02f38417aae3d 100644 +--- a/drivers/bluetooth/btusb.c ++++ b/drivers/bluetooth/btusb.c +@@ -3457,13 +3457,12 @@ static void btusb_dump_hdr_qca(struct hci_dev *hdev, struct sk_buff *skb) + + static void btusb_coredump_qca(struct hci_dev *hdev) + { ++ int err; + static const u8 param[] = { 0x26 }; +- struct sk_buff *skb; + +- skb = __hci_cmd_sync(hdev, 0xfc0c, 1, param, HCI_CMD_TIMEOUT); +- if (IS_ERR(skb)) +- bt_dev_err(hdev, "%s: triggle crash failed (%ld)", __func__, PTR_ERR(skb)); +- kfree_skb(skb); ++ err = __hci_cmd_send(hdev, 0xfc0c, 1, param); ++ if (err < 0) ++ bt_dev_err(hdev, "%s: triggle crash failed (%d)", __func__, err); + } + + /* +-- +2.43.0 + diff --git a/queue-6.6/bluetooth-btusb-mediatek-fix-double-free-of-skb-in-c.patch b/queue-6.6/bluetooth-btusb-mediatek-fix-double-free-of-skb-in-c.patch new file mode 100644 index 0000000000..851ad7fe12 --- /dev/null +++ b/queue-6.6/bluetooth-btusb-mediatek-fix-double-free-of-skb-in-c.patch @@ -0,0 +1,50 @@ +From 78943d11d3123eb68e283271e693d6eda45c757d Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 17 Apr 2024 16:27:38 -0700 +Subject: Bluetooth: btusb: mediatek: Fix double free of skb in coredump + +From: Sean Wang <sean.wang@mediatek.com> + +[ Upstream commit 18bdb386a1a30e7a3d7732a98e45e69cf6b5710d ] + +hci_devcd_append() would free the skb on error so the caller don't +have to free it again otherwise it would cause the double free of skb. + +Fixes: 0b7015132878 ("Bluetooth: btusb: mediatek: add MediaTek devcoredump support") +Reported-by : Dan Carpenter <dan.carpenter@linaro.org> +Signed-off-by: Sean Wang <sean.wang@mediatek.com> +Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/bluetooth/btmtk.c | 7 +++---- + 1 file changed, 3 insertions(+), 4 deletions(-) + +diff --git a/drivers/bluetooth/btmtk.c b/drivers/bluetooth/btmtk.c +index ac8ebccd35075..812fd2a8f853e 100644 +--- a/drivers/bluetooth/btmtk.c ++++ b/drivers/bluetooth/btmtk.c +@@ -380,8 +380,10 @@ int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb) + switch (data->cd_info.state) { + case HCI_DEVCOREDUMP_IDLE: + err = hci_devcd_init(hdev, MTK_COREDUMP_SIZE); +- if (err < 0) ++ if (err < 0) { ++ kfree_skb(skb); + break; ++ } + data->cd_info.cnt = 0; + + /* It is supposed coredump can be done within 5 seconds */ +@@ -407,9 +409,6 @@ int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb) + break; + } + +- if (err < 0) +- kfree_skb(skb); +- + return err; + } + EXPORT_SYMBOL_GPL(btmtk_process_coredump); +-- +2.43.0 + diff --git a/queue-6.6/bluetooth-hci_event-fix-sending-hci_op_read_enc_key_.patch b/queue-6.6/bluetooth-hci_event-fix-sending-hci_op_read_enc_key_.patch new file mode 100644 index 0000000000..31642b8a72 --- /dev/null +++ b/queue-6.6/bluetooth-hci_event-fix-sending-hci_op_read_enc_key_.patch @@ -0,0 +1,61 @@ +From a12d739ed077eb37bed92a798a3e0bcdf2644357 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 15 Apr 2024 13:41:01 -0400 +Subject: Bluetooth: hci_event: Fix sending HCI_OP_READ_ENC_KEY_SIZE + +From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> + +[ Upstream commit a9a830a676a9a93c5020f5c61236166931fa4266 ] + +The code shall always check if HCI_QUIRK_BROKEN_READ_ENC_KEY_SIZE has +been set before attempting to use HCI_OP_READ_ENC_KEY_SIZE. + +Fixes: c569242cd492 ("Bluetooth: hci_event: set the conn encrypted before conn establishes") +Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + include/net/bluetooth/hci_core.h | 4 ++++ + net/bluetooth/hci_event.c | 5 ++--- + 2 files changed, 6 insertions(+), 3 deletions(-) + +diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h +index 103b290d6efb0..e6f659ce534e6 100644 +--- a/include/net/bluetooth/hci_core.h ++++ b/include/net/bluetooth/hci_core.h +@@ -1865,6 +1865,10 @@ void hci_conn_del_sysfs(struct hci_conn *conn); + #define privacy_mode_capable(dev) (use_ll_privacy(dev) && \ + (hdev->commands[39] & 0x04)) + ++#define read_key_size_capable(dev) \ ++ ((dev)->commands[20] & 0x10 && \ ++ !test_bit(HCI_QUIRK_BROKEN_READ_ENC_KEY_SIZE, &hdev->quirks)) ++ + /* Use enhanced synchronous connection if command is supported and its quirk + * has not been set. + */ +diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c +index 80e71ce32f09f..1b4abf8e90f6b 100644 +--- a/net/bluetooth/hci_event.c ++++ b/net/bluetooth/hci_event.c +@@ -3229,7 +3229,7 @@ static void hci_conn_complete_evt(struct hci_dev *hdev, void *data, + if (key) { + set_bit(HCI_CONN_ENCRYPT, &conn->flags); + +- if (!(hdev->commands[20] & 0x10)) { ++ if (!read_key_size_capable(hdev)) { + conn->enc_key_size = HCI_LINK_KEY_SIZE; + } else { + cp.handle = cpu_to_le16(conn->handle); +@@ -3679,8 +3679,7 @@ static void hci_encrypt_change_evt(struct hci_dev *hdev, void *data, + * controller really supports it. If it doesn't, assume + * the default size (16). + */ +- if (!(hdev->commands[20] & 0x10) || +- test_bit(HCI_QUIRK_BROKEN_READ_ENC_KEY_SIZE, &hdev->quirks)) { ++ if (!read_key_size_capable(hdev)) { + conn->enc_key_size = HCI_LINK_KEY_SIZE; + goto notify; + } +-- +2.43.0 + diff --git a/queue-6.6/bluetooth-hci_sync-using-hci_cmd_sync_submit-when-re.patch b/queue-6.6/bluetooth-hci_sync-using-hci_cmd_sync_submit-when-re.patch new file mode 100644 index 0000000000..2e557c886b --- /dev/null +++ b/queue-6.6/bluetooth-hci_sync-using-hci_cmd_sync_submit-when-re.patch @@ -0,0 +1,58 @@ +From 37a36b0bffd21205acc946cc78c801961511de08 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 21:59:03 +0800 +Subject: Bluetooth: hci_sync: Using hci_cmd_sync_submit when removing Adv + Monitor + +From: Chun-Yi Lee <jlee@suse.com> + +[ Upstream commit 88cd6e6b2d327faa13e4505b07f1e380e51b21ff ] + +Since the d883a4669a1de be introduced in v6.4, bluetooth daemon +got the following failed message of MGMT_OP_REMOVE_ADV_MONITOR +command when controller is power-off: + +bluetoothd[20976]: +src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv +Monitors: Failed> + +Normally this situation is happened when the bluetoothd deamon +be started manually after system booting. Which means that +bluetoothd received MGMT_EV_INDEX_ADDED event after kernel +runs hci_power_off(). + +Base on doc/mgmt-api.txt, the MGMT_OP_REMOVE_ADV_MONITOR command +can be used when the controller is not powered. This patch changes +the code in remove_adv_monitor() to use hci_cmd_sync_submit() +instead of hci_cmd_sync_queue(). + +Fixes: d883a4669a1de ("Bluetooth: hci_sync: Only allow hci_cmd_sync_queue if running") +Cc: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Cc: Manish Mandlik <mmandlik@google.com> +Cc: Archie Pusaka <apusaka@chromium.org> +Cc: Miao-chen Chou <mcchou@chromium.org> +Signed-off-by: Chun-Yi Lee <jlee@suse.com> +Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/bluetooth/mgmt.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c +index 6d41bc0e7896a..ac693e64f1f9f 100644 +--- a/net/bluetooth/mgmt.c ++++ b/net/bluetooth/mgmt.c +@@ -5477,8 +5477,8 @@ static int remove_adv_monitor(struct sock *sk, struct hci_dev *hdev, + goto unlock; + } + +- err = hci_cmd_sync_queue(hdev, mgmt_remove_adv_monitor_sync, cmd, +- mgmt_remove_adv_monitor_complete); ++ err = hci_cmd_sync_submit(hdev, mgmt_remove_adv_monitor_sync, cmd, ++ mgmt_remove_adv_monitor_complete); + + if (err) { + mgmt_pending_remove(cmd); +-- +2.43.0 + diff --git a/queue-6.6/bluetooth-mgmt-fix-failing-to-mgmt_op_add_uuid-mgmt_.patch b/queue-6.6/bluetooth-mgmt-fix-failing-to-mgmt_op_add_uuid-mgmt_.patch new file mode 100644 index 0000000000..9786562be5 --- /dev/null +++ b/queue-6.6/bluetooth-mgmt-fix-failing-to-mgmt_op_add_uuid-mgmt_.patch @@ -0,0 +1,70 @@ +From 333613dd72c5d9710fa5792beb6b6b323a52f451 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 16 Apr 2024 15:34:45 -0400 +Subject: Bluetooth: MGMT: Fix failing to MGMT_OP_ADD_UUID/MGMT_OP_REMOVE_UUID + +From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> + +[ Upstream commit 6eb5fcc416f127f220b9177a5c9ae751cac1cda8 ] + +These commands don't require the adapter to be up and running so don't +use hci_cmd_sync_queue which would check that flag, instead use +hci_cmd_sync_submit which would ensure mgmt_class_complete is set +properly regardless if any command was actually run or not. + +Link: https://github.com/bluez/bluez/issues/809 +Fixes: d883a4669a1d ("Bluetooth: hci_sync: Only allow hci_cmd_sync_queue if running") +Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/bluetooth/mgmt.c | 20 +++++++++++++++----- + 1 file changed, 15 insertions(+), 5 deletions(-) + +diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c +index 92fd3786bbdff..6d41bc0e7896a 100644 +--- a/net/bluetooth/mgmt.c ++++ b/net/bluetooth/mgmt.c +@@ -2616,7 +2616,11 @@ static int add_uuid(struct sock *sk, struct hci_dev *hdev, void *data, u16 len) + goto failed; + } + +- err = hci_cmd_sync_queue(hdev, add_uuid_sync, cmd, mgmt_class_complete); ++ /* MGMT_OP_ADD_UUID don't require adapter the UP/Running so use ++ * hci_cmd_sync_submit instead of hci_cmd_sync_queue. ++ */ ++ err = hci_cmd_sync_submit(hdev, add_uuid_sync, cmd, ++ mgmt_class_complete); + if (err < 0) { + mgmt_pending_free(cmd); + goto failed; +@@ -2710,8 +2714,11 @@ static int remove_uuid(struct sock *sk, struct hci_dev *hdev, void *data, + goto unlock; + } + +- err = hci_cmd_sync_queue(hdev, remove_uuid_sync, cmd, +- mgmt_class_complete); ++ /* MGMT_OP_REMOVE_UUID don't require adapter the UP/Running so use ++ * hci_cmd_sync_submit instead of hci_cmd_sync_queue. ++ */ ++ err = hci_cmd_sync_submit(hdev, remove_uuid_sync, cmd, ++ mgmt_class_complete); + if (err < 0) + mgmt_pending_free(cmd); + +@@ -2777,8 +2784,11 @@ static int set_dev_class(struct sock *sk, struct hci_dev *hdev, void *data, + goto unlock; + } + +- err = hci_cmd_sync_queue(hdev, set_class_sync, cmd, +- mgmt_class_complete); ++ /* MGMT_OP_SET_DEV_CLASS don't require adapter the UP/Running so use ++ * hci_cmd_sync_submit instead of hci_cmd_sync_queue. ++ */ ++ err = hci_cmd_sync_submit(hdev, set_class_sync, cmd, ++ mgmt_class_complete); + if (err < 0) + mgmt_pending_free(cmd); + +-- +2.43.0 + diff --git a/queue-6.6/bluetooth-qca-set-power_ctrl_enabled-on-null-returne.patch b/queue-6.6/bluetooth-qca-set-power_ctrl_enabled-on-null-returne.patch new file mode 100644 index 0000000000..4ad0e18b8a --- /dev/null +++ b/queue-6.6/bluetooth-qca-set-power_ctrl_enabled-on-null-returne.patch @@ -0,0 +1,84 @@ +From 59b192dae4ccd8bb8ff9d11eaca36e0315762fce Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 14:29:32 +0200 +Subject: Bluetooth: qca: set power_ctrl_enabled on NULL returned by + gpiod_get_optional() + +From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org> + +[ Upstream commit 3d05fc82237aa97162d0d7dc300b55bb34e91d02 ] + +Any return value from gpiod_get_optional() other than a pointer to a +GPIO descriptor or a NULL-pointer is an error and the driver should +abort probing. That being said: commit 56d074d26c58 ("Bluetooth: hci_qca: +don't use IS_ERR_OR_NULL() with gpiod_get_optional()") no longer sets +power_ctrl_enabled on NULL-pointer returned by +devm_gpiod_get_optional(). Restore this behavior but bail-out on errors. +While at it: also bail-out on error returned when trying to get the +"swctrl" GPIO. + +Reported-by: Wren Turkal <wt@penguintechs.org> +Reported-by: Zijun Hu <quic_zijuhu@quicinc.com> +Closes: https://lore.kernel.org/linux-bluetooth/1713449192-25926-2-git-send-email-quic_zijuhu@quicinc.com/ +Fixes: 56d074d26c58 ("Bluetooth: hci_qca: don't use IS_ERR_OR_NULL() with gpiod_get_optional()") +Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> +Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org> +Tested-by: Wren Turkal" <wt@penguintechs.org> +Reported-by: Wren Turkal <wt@penguintechs.org> +Reported-by: Zijun Hu <quic_zijuhu@quicinc.com> +Reviewed-by: Krzysztof Kozlowski<krzysztof.kozlowski@linaro.org> +Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> +Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/bluetooth/hci_qca.c | 18 +++++++++++++----- + 1 file changed, 13 insertions(+), 5 deletions(-) + +diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c +index 8861b8017fbdf..b491dd9acf315 100644 +--- a/drivers/bluetooth/hci_qca.c ++++ b/drivers/bluetooth/hci_qca.c +@@ -2298,16 +2298,21 @@ static int qca_serdev_probe(struct serdev_device *serdev) + (data->soc_type == QCA_WCN6750 || + data->soc_type == QCA_WCN6855)) { + dev_err(&serdev->dev, "failed to acquire BT_EN gpio\n"); +- power_ctrl_enabled = false; ++ return PTR_ERR(qcadev->bt_en); + } + ++ if (!qcadev->bt_en) ++ power_ctrl_enabled = false; ++ + qcadev->sw_ctrl = devm_gpiod_get_optional(&serdev->dev, "swctrl", + GPIOD_IN); + if (IS_ERR(qcadev->sw_ctrl) && + (data->soc_type == QCA_WCN6750 || + data->soc_type == QCA_WCN6855 || +- data->soc_type == QCA_WCN7850)) +- dev_warn(&serdev->dev, "failed to acquire SW_CTRL gpio\n"); ++ data->soc_type == QCA_WCN7850)) { ++ dev_err(&serdev->dev, "failed to acquire SW_CTRL gpio\n"); ++ return PTR_ERR(qcadev->sw_ctrl); ++ } + + qcadev->susclk = devm_clk_get_optional(&serdev->dev, NULL); + if (IS_ERR(qcadev->susclk)) { +@@ -2326,10 +2331,13 @@ static int qca_serdev_probe(struct serdev_device *serdev) + qcadev->bt_en = devm_gpiod_get_optional(&serdev->dev, "enable", + GPIOD_OUT_LOW); + if (IS_ERR(qcadev->bt_en)) { +- dev_warn(&serdev->dev, "failed to acquire enable gpio\n"); +- power_ctrl_enabled = false; ++ dev_err(&serdev->dev, "failed to acquire enable gpio\n"); ++ return PTR_ERR(qcadev->bt_en); + } + ++ if (!qcadev->bt_en) ++ power_ctrl_enabled = false; ++ + qcadev->susclk = devm_clk_get_optional(&serdev->dev, NULL); + if (IS_ERR(qcadev->susclk)) { + dev_warn(&serdev->dev, "failed to acquire clk\n"); +-- +2.43.0 + diff --git a/queue-6.6/bnxt_en-fix-the-pci-aer-routines.patch b/queue-6.6/bnxt_en-fix-the-pci-aer-routines.patch new file mode 100644 index 0000000000..d6ab548735 --- /dev/null +++ b/queue-6.6/bnxt_en-fix-the-pci-aer-routines.patch @@ -0,0 +1,79 @@ +From c0e2b91353c0bf93682629064ad71f1bec57f43a Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 19 Apr 2024 11:34:48 -0700 +Subject: bnxt_en: Fix the PCI-AER routines + +From: Vikas Gupta <vikas.gupta@broadcom.com> + +[ Upstream commit a1acdc226baec331512f815d6ac9dd6f8435cc7f ] + +We do not support two simultaneous recoveries so check for reset +flag, BNXT_STATE_IN_FW_RESET, and do not proceed with AER further. +When the pci channel state is pci_channel_io_frozen, the PCIe link +can not be trusted so we disable the traffic immediately and stop +BAR access by calling bnxt_fw_fatal_close(). BAR access after +AER fatal error can cause an NMI. + +Fixes: f75d9a0aa967 ("bnxt_en: Re-write PCI BARs after PCI fatal error.") +Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com> +Signed-off-by: Michael Chan <michael.chan@broadcom.com> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/broadcom/bnxt/bnxt.c | 19 ++++++++++++++++--- + 1 file changed, 16 insertions(+), 3 deletions(-) + +diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c +index 1cf4aae8702b4..d40b91719b79b 100644 +--- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c ++++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c +@@ -13972,6 +13972,7 @@ static pci_ers_result_t bnxt_io_error_detected(struct pci_dev *pdev, + { + struct net_device *netdev = pci_get_drvdata(pdev); + struct bnxt *bp = netdev_priv(netdev); ++ bool abort = false; + + netdev_info(netdev, "PCI I/O error detected\n"); + +@@ -13980,16 +13981,27 @@ static pci_ers_result_t bnxt_io_error_detected(struct pci_dev *pdev, + + bnxt_ulp_stop(bp); + +- if (state == pci_channel_io_perm_failure) { ++ if (test_and_set_bit(BNXT_STATE_IN_FW_RESET, &bp->state)) { ++ netdev_err(bp->dev, "Firmware reset already in progress\n"); ++ abort = true; ++ } ++ ++ if (abort || state == pci_channel_io_perm_failure) { + rtnl_unlock(); + return PCI_ERS_RESULT_DISCONNECT; + } + +- if (state == pci_channel_io_frozen) ++ /* Link is not reliable anymore if state is pci_channel_io_frozen ++ * so we disable bus master to prevent any potential bad DMAs before ++ * freeing kernel memory. ++ */ ++ if (state == pci_channel_io_frozen) { + set_bit(BNXT_STATE_PCI_CHANNEL_IO_FROZEN, &bp->state); ++ bnxt_fw_fatal_close(bp); ++ } + + if (netif_running(netdev)) +- bnxt_close(netdev); ++ __bnxt_close_nic(bp, true, true); + + if (pci_is_enabled(pdev)) + pci_disable_device(pdev); +@@ -14075,6 +14087,7 @@ static pci_ers_result_t bnxt_io_slot_reset(struct pci_dev *pdev) + } + + reset_exit: ++ clear_bit(BNXT_STATE_IN_FW_RESET, &bp->state); + bnxt_clear_reservations(bp, true); + rtnl_unlock(); + +-- +2.43.0 + diff --git a/queue-6.6/bnxt_en-refactor-reset-close-code.patch b/queue-6.6/bnxt_en-refactor-reset-close-code.patch new file mode 100644 index 0000000000..ddd77c9785 --- /dev/null +++ b/queue-6.6/bnxt_en-refactor-reset-close-code.patch @@ -0,0 +1,60 @@ +From 1eabf6d47caa474ccb94cd8e70bbc31ce5513fb0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 19 Apr 2024 11:34:47 -0700 +Subject: bnxt_en: refactor reset close code + +From: Vikas Gupta <vikas.gupta@broadcom.com> + +[ Upstream commit 7474b1c82be3780692d537d331f9aa7fc1e5a368 ] + +Introduce bnxt_fw_fatal_close() API which can be used +to stop data path and disable device when firmware +is in fatal state. + +Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com> +Signed-off-by: Michael Chan <michael.chan@broadcom.com> +Signed-off-by: David S. Miller <davem@davemloft.net> +Stable-dep-of: a1acdc226bae ("bnxt_en: Fix the PCI-AER routines") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/broadcom/bnxt/bnxt.c | 17 +++++++++++------ + 1 file changed, 11 insertions(+), 6 deletions(-) + +diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c +index 38e3b2225ff1c..1cf4aae8702b4 100644 +--- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c ++++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c +@@ -11807,6 +11807,16 @@ static void bnxt_rx_ring_reset(struct bnxt *bp) + bnxt_rtnl_unlock_sp(bp); + } + ++static void bnxt_fw_fatal_close(struct bnxt *bp) ++{ ++ bnxt_tx_disable(bp); ++ bnxt_disable_napi(bp); ++ bnxt_disable_int_sync(bp); ++ bnxt_free_irq(bp); ++ bnxt_clear_int_mode(bp); ++ pci_disable_device(bp->pdev); ++} ++ + static void bnxt_fw_reset_close(struct bnxt *bp) + { + bnxt_ulp_stop(bp); +@@ -11820,12 +11830,7 @@ static void bnxt_fw_reset_close(struct bnxt *bp) + pci_read_config_word(bp->pdev, PCI_SUBSYSTEM_ID, &val); + if (val == 0xffff) + bp->fw_reset_min_dsecs = 0; +- bnxt_tx_disable(bp); +- bnxt_disable_napi(bp); +- bnxt_disable_int_sync(bp); +- bnxt_free_irq(bp); +- bnxt_clear_int_mode(bp); +- pci_disable_device(bp->pdev); ++ bnxt_fw_fatal_close(bp); + } + __bnxt_close_nic(bp, true, false); + bnxt_vf_reps_free(bp); +-- +2.43.0 + diff --git a/queue-6.6/bridge-br_netlink.c-no-need-to-return-void-function.patch b/queue-6.6/bridge-br_netlink.c-no-need-to-return-void-function.patch new file mode 100644 index 0000000000..8240c1601b --- /dev/null +++ b/queue-6.6/bridge-br_netlink.c-no-need-to-return-void-function.patch @@ -0,0 +1,36 @@ +From 191d20a9fc4341489ec58384c33ff5b7b6bc467f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 19 Apr 2024 16:02:00 +0800 +Subject: bridge/br_netlink.c: no need to return void function + +From: Hangbin Liu <liuhangbin@gmail.com> + +[ Upstream commit 4fd1edcdf13c0d234543ecf502092be65c5177db ] + +br_info_notify is a void function. There is no need to return. + +Fixes: b6d0425b816e ("bridge: cfm: Netlink Notifications.") +Signed-off-by: Hangbin Liu <liuhangbin@gmail.com> +Acked-by: Nikolay Aleksandrov <razor@blackwall.org> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/bridge/br_netlink.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/net/bridge/br_netlink.c b/net/bridge/br_netlink.c +index 10f0d33d8ccf2..65e9ed3851425 100644 +--- a/net/bridge/br_netlink.c ++++ b/net/bridge/br_netlink.c +@@ -666,7 +666,7 @@ void br_ifinfo_notify(int event, const struct net_bridge *br, + { + u32 filter = RTEXT_FILTER_BRVLAN_COMPRESSED; + +- return br_info_notify(event, br, port, filter); ++ br_info_notify(event, br, port, filter); + } + + /* +-- +2.43.0 + diff --git a/queue-6.6/cifs-fix-reacquisition-of-volume-cookie-on-still-liv.patch b/queue-6.6/cifs-fix-reacquisition-of-volume-cookie-on-still-liv.patch new file mode 100644 index 0000000000..52a62742fd --- /dev/null +++ b/queue-6.6/cifs-fix-reacquisition-of-volume-cookie-on-still-liv.patch @@ -0,0 +1,119 @@ +From 0463487c002d53d83d346bb7ca8f90a93e358c6a Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 4 Apr 2024 16:05:19 +0100 +Subject: cifs: Fix reacquisition of volume cookie on still-live connection + +From: David Howells <dhowells@redhat.com> + +[ Upstream commit dad80c6bff770d25f67ec25fe011730e4a463008 ] + +During mount, cifs_mount_get_tcon() gets a tcon resource connection record +and then attaches an fscache volume cookie to it. However, it does this +irrespective of whether or not the tcon returned from cifs_get_tcon() is a +new record or one that's already in use. This leads to a warning about a +volume cookie collision and a leaked volume cookie because tcon->fscache +gets reset. + +Fix this be adding a mutex and a "we've already tried this" flag and only +doing it once for the lifetime of the tcon. + +[!] Note: Looking at cifs_mount_get_tcon(), a more general solution may +actually be required. Reacquiring the volume cookie isn't the only thing +that function does: it also partially reinitialises the tcon record without +any locking - which may cause live filesystem ops already using the tcon +through a previous mount to malfunction. + +This can be reproduced simply by something like: + + mount //example.com/test /xfstest.test -o user=shares,pass=xxx,fsc + mount //example.com/test /mnt -o user=shares,pass=xxx,fsc + +Fixes: 70431bfd825d ("cifs: Support fscache indexing rewrite") +Signed-off-by: David Howells <dhowells@redhat.com> +Acked-by: Paulo Alcantara (Red Hat) <pc@manguebit.com> +cc: Shyam Prasad N <sprasad@microsoft.com> +cc: linux-cifs@vger.kernel.org +cc: linux-fsdevel@vger.kernel.org +Signed-off-by: Steve French <stfrench@microsoft.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + fs/smb/client/cifsglob.h | 2 ++ + fs/smb/client/fscache.c | 13 +++++++++++++ + fs/smb/client/misc.c | 3 +++ + 3 files changed, 18 insertions(+) + +diff --git a/fs/smb/client/cifsglob.h b/fs/smb/client/cifsglob.h +index 68fd61a564089..12a48e1d80c3f 100644 +--- a/fs/smb/client/cifsglob.h ++++ b/fs/smb/client/cifsglob.h +@@ -1247,7 +1247,9 @@ struct cifs_tcon { + __u32 max_cached_dirs; + #ifdef CONFIG_CIFS_FSCACHE + u64 resource_id; /* server resource id */ ++ bool fscache_acquired; /* T if we've tried acquiring a cookie */ + struct fscache_volume *fscache; /* cookie for share */ ++ struct mutex fscache_lock; /* Prevent regetting a cookie */ + #endif + struct list_head pending_opens; /* list of incomplete opens */ + struct cached_fids *cfids; +diff --git a/fs/smb/client/fscache.c b/fs/smb/client/fscache.c +index a4ee801b29394..ecabc4b400535 100644 +--- a/fs/smb/client/fscache.c ++++ b/fs/smb/client/fscache.c +@@ -43,12 +43,23 @@ int cifs_fscache_get_super_cookie(struct cifs_tcon *tcon) + char *key; + int ret = -ENOMEM; + ++ if (tcon->fscache_acquired) ++ return 0; ++ ++ mutex_lock(&tcon->fscache_lock); ++ if (tcon->fscache_acquired) { ++ mutex_unlock(&tcon->fscache_lock); ++ return 0; ++ } ++ tcon->fscache_acquired = true; ++ + tcon->fscache = NULL; + switch (sa->sa_family) { + case AF_INET: + case AF_INET6: + break; + default: ++ mutex_unlock(&tcon->fscache_lock); + cifs_dbg(VFS, "Unknown network family '%d'\n", sa->sa_family); + return -EINVAL; + } +@@ -57,6 +68,7 @@ int cifs_fscache_get_super_cookie(struct cifs_tcon *tcon) + + sharename = extract_sharename(tcon->tree_name); + if (IS_ERR(sharename)) { ++ mutex_unlock(&tcon->fscache_lock); + cifs_dbg(FYI, "%s: couldn't extract sharename\n", __func__); + return PTR_ERR(sharename); + } +@@ -90,6 +102,7 @@ int cifs_fscache_get_super_cookie(struct cifs_tcon *tcon) + kfree(key); + out: + kfree(sharename); ++ mutex_unlock(&tcon->fscache_lock); + return ret; + } + +diff --git a/fs/smb/client/misc.c b/fs/smb/client/misc.c +index 74627d647818a..0d13db80e67c9 100644 +--- a/fs/smb/client/misc.c ++++ b/fs/smb/client/misc.c +@@ -141,6 +141,9 @@ tcon_info_alloc(bool dir_leases_enabled) + atomic_set(&ret_buf->num_local_opens, 0); + atomic_set(&ret_buf->num_remote_opens, 0); + ret_buf->stats_from_time = ktime_get_real_seconds(); ++#ifdef CONFIG_CIFS_FSCACHE ++ mutex_init(&ret_buf->fscache_lock); ++#endif + + return ret_buf; + } +-- +2.43.0 + diff --git a/queue-6.6/cifs-reinstate-original-behavior-again-for-forceuid-.patch b/queue-6.6/cifs-reinstate-original-behavior-again-for-forceuid-.patch new file mode 100644 index 0000000000..852c0312ac --- /dev/null +++ b/queue-6.6/cifs-reinstate-original-behavior-again-for-forceuid-.patch @@ -0,0 +1,82 @@ +From acbc68f78b733d1a2b8a7b8745570d1796b4c7ae Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 15 Apr 2024 16:47:49 +0900 +Subject: cifs: reinstate original behavior again for forceuid/forcegid + +From: Takayuki Nagata <tnagata@redhat.com> + +[ Upstream commit 77d8aa79ecfb209308e0644c02f655122b31def7 ] + +forceuid/forcegid should be enabled by default when uid=/gid= options are +specified, but commit 24e0a1eff9e2 ("cifs: switch to new mount api") +changed the behavior. Due to the change, a mounted share does not show +intentional uid/gid for files and directories even though uid=/gid= +options are specified since forceuid/forcegid are not enabled. + +This patch reinstates original behavior that overrides uid/gid with +specified uid/gid by the options. + +Fixes: 24e0a1eff9e2 ("cifs: switch to new mount api") +Signed-off-by: Takayuki Nagata <tnagata@redhat.com> +Acked-by: Paulo Alcantara (Red Hat) <pc@manguebit.com> +Acked-by: Ronnie Sahlberg <lsahlber@redhat.com> +Acked-by: Tom Talpey <tom@talpey.com> +Signed-off-by: Steve French <stfrench@microsoft.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + fs/smb/client/fs_context.c | 12 ++++++++++++ + fs/smb/client/fs_context.h | 2 ++ + 2 files changed, 14 insertions(+) + +diff --git a/fs/smb/client/fs_context.c b/fs/smb/client/fs_context.c +index 58567ae617b9f..103421791bb5d 100644 +--- a/fs/smb/client/fs_context.c ++++ b/fs/smb/client/fs_context.c +@@ -714,6 +714,16 @@ static int smb3_fs_context_validate(struct fs_context *fc) + /* set the port that we got earlier */ + cifs_set_port((struct sockaddr *)&ctx->dstaddr, ctx->port); + ++ if (ctx->uid_specified && !ctx->forceuid_specified) { ++ ctx->override_uid = 1; ++ pr_notice("enabling forceuid mount option implicitly because uid= option is specified\n"); ++ } ++ ++ if (ctx->gid_specified && !ctx->forcegid_specified) { ++ ctx->override_gid = 1; ++ pr_notice("enabling forcegid mount option implicitly because gid= option is specified\n"); ++ } ++ + if (ctx->override_uid && !ctx->uid_specified) { + ctx->override_uid = 0; + pr_notice("ignoring forceuid mount option specified with no uid= option\n"); +@@ -983,12 +993,14 @@ static int smb3_fs_context_parse_param(struct fs_context *fc, + ctx->override_uid = 0; + else + ctx->override_uid = 1; ++ ctx->forceuid_specified = true; + break; + case Opt_forcegid: + if (result.negated) + ctx->override_gid = 0; + else + ctx->override_gid = 1; ++ ctx->forcegid_specified = true; + break; + case Opt_perm: + if (result.negated) +diff --git a/fs/smb/client/fs_context.h b/fs/smb/client/fs_context.h +index 8cfc25b609b6b..4e409238fe8f7 100644 +--- a/fs/smb/client/fs_context.h ++++ b/fs/smb/client/fs_context.h +@@ -155,6 +155,8 @@ enum cifs_param { + }; + + struct smb3_fs_context { ++ bool forceuid_specified; ++ bool forcegid_specified; + bool uid_specified; + bool cruid_specified; + bool gid_specified; +-- +2.43.0 + diff --git a/queue-6.6/cxl-core-fix-potential-payload-size-confusion-in-cxl.patch b/queue-6.6/cxl-core-fix-potential-payload-size-confusion-in-cxl.patch new file mode 100644 index 0000000000..7a6aa69109 --- /dev/null +++ b/queue-6.6/cxl-core-fix-potential-payload-size-confusion-in-cxl.patch @@ -0,0 +1,120 @@ +From ce6ef0697a395521a5298d413f5f5c47d4fcfc5f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 5 Apr 2024 15:00:16 -0700 +Subject: cxl/core: Fix potential payload size confusion in + cxl_mem_get_poison() + +From: Dan Williams <dan.j.williams@intel.com> + +[ Upstream commit 4b759dd5765503bd466defac7d93aca14c23a15d ] + +A recent change to cxl_mem_get_records_log() [1] highlighted a subtle +nuance of looping calls to cxl_internal_send_cmd(), i.e. that +cxl_internal_send_cmd() modifies the 'size_out' member of the @mbox_cmd +argument. That mechanism is useful for communicating underflow, but it +is unwanted when reusing @mbox_cmd for a subsequent submission. It turns +out that cxl_xfer_log() avoids this scenario by always redefining +@mbox_cmd each iteration. + +Update cxl_mem_get_records_log() and cxl_mem_get_poison() to follow the +same style as cxl_xfer_log(), i.e. re-define @mbox_cmd each iteration. +The cxl_mem_get_records_log() change is just a style fixup, but the +cxl_mem_get_poison() change is a potential fix, per Alison [2]: + + Poison list retrieval can hit this case if the MORE flag is set and + a follow on read of the list delivers more records than the previous + read. ie. device gives one record, sets the _MORE flag, then gives 5. + +Not an urgent fix since this behavior has not been seen in the wild, +but worth tracking as a fix. + +Cc: Kwangjin Ko <kwangjin.ko@sk.com> +Cc: Alison Schofield <alison.schofield@intel.com> +Fixes: ed83f7ca398b ("cxl/mbox: Add GET_POISON_LIST mailbox command") +Link: http://lore.kernel.org/r/20240402081404.1106-2-kwangjin.ko@sk.com [1] +Link: http://lore.kernel.org/r/ZhAhAL/GOaWFrauw@aschofie-mobl2 [2] +Signed-off-by: Dan Williams <dan.j.williams@intel.com> +Reviewed-by: Ira Weiny <ira.weiny@intel.com> +Reviewed-by: Alison Schofield <alison.schofield@intel.com> +Link: https://lore.kernel.org/r/171235441633.2716581.12330082428680958635.stgit@dwillia2-xfh.jf.intel.com +Signed-off-by: Dave Jiang <dave.jiang@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/cxl/core/mbox.c | 38 +++++++++++++++++--------------------- + 1 file changed, 17 insertions(+), 21 deletions(-) + +diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c +index 4b4c15e943380..fecaa18f4dd20 100644 +--- a/drivers/cxl/core/mbox.c ++++ b/drivers/cxl/core/mbox.c +@@ -959,25 +959,22 @@ static void cxl_mem_get_records_log(struct cxl_memdev_state *mds, + struct cxl_memdev *cxlmd = mds->cxlds.cxlmd; + struct device *dev = mds->cxlds.dev; + struct cxl_get_event_payload *payload; +- struct cxl_mbox_cmd mbox_cmd; + u8 log_type = type; + u16 nr_rec; + + mutex_lock(&mds->event.log_lock); + payload = mds->event.buf; + +- mbox_cmd = (struct cxl_mbox_cmd) { +- .opcode = CXL_MBOX_OP_GET_EVENT_RECORD, +- .payload_in = &log_type, +- .size_in = sizeof(log_type), +- .payload_out = payload, +- .min_out = struct_size(payload, records, 0), +- }; +- + do { + int rc, i; +- +- mbox_cmd.size_out = mds->payload_size; ++ struct cxl_mbox_cmd mbox_cmd = (struct cxl_mbox_cmd) { ++ .opcode = CXL_MBOX_OP_GET_EVENT_RECORD, ++ .payload_in = &log_type, ++ .size_in = sizeof(log_type), ++ .payload_out = payload, ++ .size_out = mds->payload_size, ++ .min_out = struct_size(payload, records, 0), ++ }; + + rc = cxl_internal_send_cmd(mds, &mbox_cmd); + if (rc) { +@@ -1311,7 +1308,6 @@ int cxl_mem_get_poison(struct cxl_memdev *cxlmd, u64 offset, u64 len, + struct cxl_memdev_state *mds = to_cxl_memdev_state(cxlmd->cxlds); + struct cxl_mbox_poison_out *po; + struct cxl_mbox_poison_in pi; +- struct cxl_mbox_cmd mbox_cmd; + int nr_records = 0; + int rc; + +@@ -1323,16 +1319,16 @@ int cxl_mem_get_poison(struct cxl_memdev *cxlmd, u64 offset, u64 len, + pi.offset = cpu_to_le64(offset); + pi.length = cpu_to_le64(len / CXL_POISON_LEN_MULT); + +- mbox_cmd = (struct cxl_mbox_cmd) { +- .opcode = CXL_MBOX_OP_GET_POISON, +- .size_in = sizeof(pi), +- .payload_in = &pi, +- .size_out = mds->payload_size, +- .payload_out = po, +- .min_out = struct_size(po, record, 0), +- }; +- + do { ++ struct cxl_mbox_cmd mbox_cmd = (struct cxl_mbox_cmd){ ++ .opcode = CXL_MBOX_OP_GET_POISON, ++ .size_in = sizeof(pi), ++ .payload_in = &pi, ++ .size_out = mds->payload_size, ++ .payload_out = po, ++ .min_out = struct_size(po, record, 0), ++ }; ++ + rc = cxl_internal_send_cmd(mds, &mbox_cmd); + if (rc) + break; +-- +2.43.0 + diff --git a/queue-6.6/drm-gma500-remove-lid-code.patch b/queue-6.6/drm-gma500-remove-lid-code.patch new file mode 100644 index 0000000000..320c7722be --- /dev/null +++ b/queue-6.6/drm-gma500-remove-lid-code.patch @@ -0,0 +1,193 @@ +From f612d10b23b7ab0242ab2c9980437d900eb9da36 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 15 Apr 2024 13:27:31 +0200 +Subject: drm/gma500: Remove lid code + +From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com> + +[ Upstream commit 6aff4c26ed677b1f464f721fbd3e7767f24a684d ] + +Due to a change in the order of initialization, the lid timer got +started before proper setup was made. This resulted in a crash during +boot. + +The lid switch is handled by gma500 through a timer that periodically +polls the opregion for changes. These types of ACPI events shouldn't be +handled by the graphics driver so let's get rid of the lid code. This +fixes the crash during boot. + +Reported-by: Enrico Bartky <enrico.bartky@gmail.com> +Fixes: 8f1aaccb04b7 ("drm/gma500: Implement client-based fbdev emulation") +Tested-by: Enrico Bartky <enrico.bartky@gmail.com> +Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com> +Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de> +Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> +Link: https://patchwork.freedesktop.org/patch/msgid/20240415112731.31841-1-patrik.r.jakobsson@gmail.com +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/gpu/drm/gma500/Makefile | 1 - + drivers/gpu/drm/gma500/psb_device.c | 5 +- + drivers/gpu/drm/gma500/psb_drv.h | 9 ---- + drivers/gpu/drm/gma500/psb_lid.c | 80 ----------------------------- + 4 files changed, 1 insertion(+), 94 deletions(-) + delete mode 100644 drivers/gpu/drm/gma500/psb_lid.c + +diff --git a/drivers/gpu/drm/gma500/Makefile b/drivers/gpu/drm/gma500/Makefile +index 4f302cd5e1a6c..58fed80c7392a 100644 +--- a/drivers/gpu/drm/gma500/Makefile ++++ b/drivers/gpu/drm/gma500/Makefile +@@ -34,7 +34,6 @@ gma500_gfx-y += \ + psb_intel_lvds.o \ + psb_intel_modes.o \ + psb_intel_sdvo.o \ +- psb_lid.o \ + psb_irq.o + + gma500_gfx-$(CONFIG_ACPI) += opregion.o +diff --git a/drivers/gpu/drm/gma500/psb_device.c b/drivers/gpu/drm/gma500/psb_device.c +index dcfcd7b89d4a1..6dece8f0e380f 100644 +--- a/drivers/gpu/drm/gma500/psb_device.c ++++ b/drivers/gpu/drm/gma500/psb_device.c +@@ -73,8 +73,7 @@ static int psb_backlight_setup(struct drm_device *dev) + } + + psb_intel_lvds_set_brightness(dev, PSB_MAX_BRIGHTNESS); +- /* This must occur after the backlight is properly initialised */ +- psb_lid_timer_init(dev_priv); ++ + return 0; + } + +@@ -259,8 +258,6 @@ static int psb_chip_setup(struct drm_device *dev) + + static void psb_chip_teardown(struct drm_device *dev) + { +- struct drm_psb_private *dev_priv = to_drm_psb_private(dev); +- psb_lid_timer_takedown(dev_priv); + gma_intel_teardown_gmbus(dev); + } + +diff --git a/drivers/gpu/drm/gma500/psb_drv.h b/drivers/gpu/drm/gma500/psb_drv.h +index 70d9adafa2333..bb1cd45c085cd 100644 +--- a/drivers/gpu/drm/gma500/psb_drv.h ++++ b/drivers/gpu/drm/gma500/psb_drv.h +@@ -170,7 +170,6 @@ + + #define PSB_NUM_VBLANKS 2 + #define PSB_WATCHDOG_DELAY (HZ * 2) +-#define PSB_LID_DELAY (HZ / 10) + + #define PSB_MAX_BRIGHTNESS 100 + +@@ -499,11 +498,7 @@ struct drm_psb_private { + /* Hotplug handling */ + struct work_struct hotplug_work; + +- /* LID-Switch */ +- spinlock_t lid_lock; +- struct timer_list lid_timer; + struct psb_intel_opregion opregion; +- u32 lid_last_state; + + /* Watchdog */ + uint32_t apm_reg; +@@ -599,10 +594,6 @@ struct psb_ops { + int i2c_bus; /* I2C bus identifier for Moorestown */ + }; + +-/* psb_lid.c */ +-extern void psb_lid_timer_init(struct drm_psb_private *dev_priv); +-extern void psb_lid_timer_takedown(struct drm_psb_private *dev_priv); +- + /* modesetting */ + extern void psb_modeset_init(struct drm_device *dev); + extern void psb_modeset_cleanup(struct drm_device *dev); +diff --git a/drivers/gpu/drm/gma500/psb_lid.c b/drivers/gpu/drm/gma500/psb_lid.c +deleted file mode 100644 +index 58a7fe3926360..0000000000000 +--- a/drivers/gpu/drm/gma500/psb_lid.c ++++ /dev/null +@@ -1,80 +0,0 @@ +-// SPDX-License-Identifier: GPL-2.0-only +-/************************************************************************** +- * Copyright (c) 2007, Intel Corporation. +- * +- * Authors: Thomas Hellstrom <thomas-at-tungstengraphics-dot-com> +- **************************************************************************/ +- +-#include <linux/spinlock.h> +- +-#include "psb_drv.h" +-#include "psb_intel_reg.h" +-#include "psb_reg.h" +- +-static void psb_lid_timer_func(struct timer_list *t) +-{ +- struct drm_psb_private *dev_priv = from_timer(dev_priv, t, lid_timer); +- struct drm_device *dev = (struct drm_device *)&dev_priv->dev; +- struct timer_list *lid_timer = &dev_priv->lid_timer; +- unsigned long irq_flags; +- u32 __iomem *lid_state = dev_priv->opregion.lid_state; +- u32 pp_status; +- +- if (readl(lid_state) == dev_priv->lid_last_state) +- goto lid_timer_schedule; +- +- if ((readl(lid_state)) & 0x01) { +- /*lid state is open*/ +- REG_WRITE(PP_CONTROL, REG_READ(PP_CONTROL) | POWER_TARGET_ON); +- do { +- pp_status = REG_READ(PP_STATUS); +- } while ((pp_status & PP_ON) == 0 && +- (pp_status & PP_SEQUENCE_MASK) != 0); +- +- if (REG_READ(PP_STATUS) & PP_ON) { +- /*FIXME: should be backlight level before*/ +- psb_intel_lvds_set_brightness(dev, 100); +- } else { +- DRM_DEBUG("LVDS panel never powered up"); +- return; +- } +- } else { +- psb_intel_lvds_set_brightness(dev, 0); +- +- REG_WRITE(PP_CONTROL, REG_READ(PP_CONTROL) & ~POWER_TARGET_ON); +- do { +- pp_status = REG_READ(PP_STATUS); +- } while ((pp_status & PP_ON) == 0); +- } +- dev_priv->lid_last_state = readl(lid_state); +- +-lid_timer_schedule: +- spin_lock_irqsave(&dev_priv->lid_lock, irq_flags); +- if (!timer_pending(lid_timer)) { +- lid_timer->expires = jiffies + PSB_LID_DELAY; +- add_timer(lid_timer); +- } +- spin_unlock_irqrestore(&dev_priv->lid_lock, irq_flags); +-} +- +-void psb_lid_timer_init(struct drm_psb_private *dev_priv) +-{ +- struct timer_list *lid_timer = &dev_priv->lid_timer; +- unsigned long irq_flags; +- +- spin_lock_init(&dev_priv->lid_lock); +- spin_lock_irqsave(&dev_priv->lid_lock, irq_flags); +- +- timer_setup(lid_timer, psb_lid_timer_func, 0); +- +- lid_timer->expires = jiffies + PSB_LID_DELAY; +- +- add_timer(lid_timer); +- spin_unlock_irqrestore(&dev_priv->lid_lock, irq_flags); +-} +- +-void psb_lid_timer_takedown(struct drm_psb_private *dev_priv) +-{ +- del_timer_sync(&dev_priv->lid_timer); +-} +- +-- +2.43.0 + diff --git a/queue-6.6/eth-bnxt-fix-counting-packets-discarded-due-to-oom-a.patch b/queue-6.6/eth-bnxt-fix-counting-packets-discarded-due-to-oom-a.patch new file mode 100644 index 0000000000..abe20d5eb1 --- /dev/null +++ b/queue-6.6/eth-bnxt-fix-counting-packets-discarded-due-to-oom-a.patch @@ -0,0 +1,150 @@ +From 41c80ca897ba17a08df35e5526a5187159f96cea Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 17:21:48 -0700 +Subject: eth: bnxt: fix counting packets discarded due to OOM and netpoll + +From: Jakub Kicinski <kuba@kernel.org> + +[ Upstream commit 730117730709992c9f6535dd7b47638ee561ec45 ] + +I added OOM and netpoll discard counters, naively assuming that +the cpr pointer is pointing to a common completion ring. +Turns out that is usually *a* completion ring but not *the* +completion ring which bnapi->cp_ring points to. bnapi->cp_ring +is where the stats are read from, so we end up reporting 0 +thru ethtool -S and qstat even though the drop events have happened. +Make 100% sure we're recording statistics in the correct structure. + +Fixes: 907fd4a294db ("bnxt: count discards due to memory allocation errors") +Reviewed-by: Michael Chan <michael.chan@broadcom.com> +Link: https://lore.kernel.org/r/20240424002148.3937059-1-kuba@kernel.org +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/broadcom/bnxt/bnxt.c | 44 ++++++++++------------- + 1 file changed, 18 insertions(+), 26 deletions(-) + +diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c +index d40b91719b79b..724624737d095 100644 +--- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c ++++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c +@@ -1659,7 +1659,7 @@ static inline struct sk_buff *bnxt_tpa_end(struct bnxt *bp, + skb = bnxt_copy_skb(bnapi, data_ptr, len, mapping); + if (!skb) { + bnxt_abort_tpa(cpr, idx, agg_bufs); +- cpr->sw_stats.rx.rx_oom_discards += 1; ++ cpr->bnapi->cp_ring.sw_stats.rx.rx_oom_discards += 1; + return NULL; + } + } else { +@@ -1669,7 +1669,7 @@ static inline struct sk_buff *bnxt_tpa_end(struct bnxt *bp, + new_data = __bnxt_alloc_rx_frag(bp, &new_mapping, GFP_ATOMIC); + if (!new_data) { + bnxt_abort_tpa(cpr, idx, agg_bufs); +- cpr->sw_stats.rx.rx_oom_discards += 1; ++ cpr->bnapi->cp_ring.sw_stats.rx.rx_oom_discards += 1; + return NULL; + } + +@@ -1685,7 +1685,7 @@ static inline struct sk_buff *bnxt_tpa_end(struct bnxt *bp, + if (!skb) { + skb_free_frag(data); + bnxt_abort_tpa(cpr, idx, agg_bufs); +- cpr->sw_stats.rx.rx_oom_discards += 1; ++ cpr->bnapi->cp_ring.sw_stats.rx.rx_oom_discards += 1; + return NULL; + } + skb_reserve(skb, bp->rx_offset); +@@ -1696,7 +1696,7 @@ static inline struct sk_buff *bnxt_tpa_end(struct bnxt *bp, + skb = bnxt_rx_agg_pages_skb(bp, cpr, skb, idx, agg_bufs, true); + if (!skb) { + /* Page reuse already handled by bnxt_rx_pages(). */ +- cpr->sw_stats.rx.rx_oom_discards += 1; ++ cpr->bnapi->cp_ring.sw_stats.rx.rx_oom_discards += 1; + return NULL; + } + } +@@ -1914,11 +1914,8 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, + u32 frag_len = bnxt_rx_agg_pages_xdp(bp, cpr, &xdp, + cp_cons, agg_bufs, + false); +- if (!frag_len) { +- cpr->sw_stats.rx.rx_oom_discards += 1; +- rc = -ENOMEM; +- goto next_rx; +- } ++ if (!frag_len) ++ goto oom_next_rx; + } + xdp_active = true; + } +@@ -1941,9 +1938,7 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, + else + bnxt_xdp_buff_frags_free(rxr, &xdp); + } +- cpr->sw_stats.rx.rx_oom_discards += 1; +- rc = -ENOMEM; +- goto next_rx; ++ goto oom_next_rx; + } + } else { + u32 payload; +@@ -1954,29 +1949,21 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, + payload = 0; + skb = bp->rx_skb_func(bp, rxr, cons, data, data_ptr, dma_addr, + payload | len); +- if (!skb) { +- cpr->sw_stats.rx.rx_oom_discards += 1; +- rc = -ENOMEM; +- goto next_rx; +- } ++ if (!skb) ++ goto oom_next_rx; + } + + if (agg_bufs) { + if (!xdp_active) { + skb = bnxt_rx_agg_pages_skb(bp, cpr, skb, cp_cons, agg_bufs, false); +- if (!skb) { +- cpr->sw_stats.rx.rx_oom_discards += 1; +- rc = -ENOMEM; +- goto next_rx; +- } ++ if (!skb) ++ goto oom_next_rx; + } else { + skb = bnxt_xdp_build_skb(bp, skb, agg_bufs, rxr->page_pool, &xdp, rxcmp1); + if (!skb) { + /* we should be able to free the old skb here */ + bnxt_xdp_buff_frags_free(rxr, &xdp); +- cpr->sw_stats.rx.rx_oom_discards += 1; +- rc = -ENOMEM; +- goto next_rx; ++ goto oom_next_rx; + } + } + } +@@ -2054,6 +2041,11 @@ static int bnxt_rx_pkt(struct bnxt *bp, struct bnxt_cp_ring_info *cpr, + *raw_cons = tmp_raw_cons; + + return rc; ++ ++oom_next_rx: ++ cpr->bnapi->cp_ring.sw_stats.rx.rx_oom_discards += 1; ++ rc = -ENOMEM; ++ goto next_rx; + } + + /* In netpoll mode, if we are using a combined completion ring, we need to +@@ -2099,7 +2091,7 @@ static int bnxt_force_rx_discard(struct bnxt *bp, + } + rc = bnxt_rx_pkt(bp, cpr, raw_cons, event); + if (rc && rc != -EBUSY) +- cpr->sw_stats.rx.rx_netpoll_discards += 1; ++ cpr->bnapi->cp_ring.sw_stats.rx.rx_netpoll_discards += 1; + return rc; + } + +-- +2.43.0 + diff --git a/queue-6.6/gpio-tangier-use-correct-type-for-the-irq-chip-data.patch b/queue-6.6/gpio-tangier-use-correct-type-for-the-irq-chip-data.patch new file mode 100644 index 0000000000..1e83589963 --- /dev/null +++ b/queue-6.6/gpio-tangier-use-correct-type-for-the-irq-chip-data.patch @@ -0,0 +1,57 @@ +From fd598f26bc789a27472591467ea12588db14ca49 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 20 Mar 2024 21:43:03 +0200 +Subject: gpio: tangier: Use correct type for the IRQ chip data + +From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> + +[ Upstream commit 7d045025a24b6336d444d359bd4312f351d017f9 ] + +IRQ chip data contains a pointer to the GPIO chip. Luckily we have +the pointers the same, but strictly speaking it's not guaranteed. +Even though, still better to fix this. + +Fixes: ccf6fd6dcc86 ("gpio: merrifield: Introduce GPIO driver to support Merrifield") +Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/gpio/gpio-tangier.c | 9 ++++++--- + 1 file changed, 6 insertions(+), 3 deletions(-) + +diff --git a/drivers/gpio/gpio-tangier.c b/drivers/gpio/gpio-tangier.c +index 7ce3eddaed257..1ce40b7673b11 100644 +--- a/drivers/gpio/gpio-tangier.c ++++ b/drivers/gpio/gpio-tangier.c +@@ -205,7 +205,8 @@ static int tng_gpio_set_config(struct gpio_chip *chip, unsigned int offset, + + static void tng_irq_ack(struct irq_data *d) + { +- struct tng_gpio *priv = irq_data_get_irq_chip_data(d); ++ struct gpio_chip *gc = irq_data_get_irq_chip_data(d); ++ struct tng_gpio *priv = gpiochip_get_data(gc); + irq_hw_number_t gpio = irqd_to_hwirq(d); + unsigned long flags; + void __iomem *gisr; +@@ -241,7 +242,8 @@ static void tng_irq_unmask_mask(struct tng_gpio *priv, u32 gpio, bool unmask) + + static void tng_irq_mask(struct irq_data *d) + { +- struct tng_gpio *priv = irq_data_get_irq_chip_data(d); ++ struct gpio_chip *gc = irq_data_get_irq_chip_data(d); ++ struct tng_gpio *priv = gpiochip_get_data(gc); + irq_hw_number_t gpio = irqd_to_hwirq(d); + + tng_irq_unmask_mask(priv, gpio, false); +@@ -250,7 +252,8 @@ static void tng_irq_mask(struct irq_data *d) + + static void tng_irq_unmask(struct irq_data *d) + { +- struct tng_gpio *priv = irq_data_get_irq_chip_data(d); ++ struct gpio_chip *gc = irq_data_get_irq_chip_data(d); ++ struct tng_gpio *priv = gpiochip_get_data(gc); + irq_hw_number_t gpio = irqd_to_hwirq(d); + + gpiochip_enable_irq(&priv->chip, gpio); +-- +2.43.0 + diff --git a/queue-6.6/gpio-tegra186-fix-tegra186_gpio_is_accessible-check.patch b/queue-6.6/gpio-tegra186-fix-tegra186_gpio_is_accessible-check.patch new file mode 100644 index 0000000000..7cd06b5e84 --- /dev/null +++ b/queue-6.6/gpio-tegra186-fix-tegra186_gpio_is_accessible-check.patch @@ -0,0 +1,81 @@ +From 57ee8a18a3272ea19863ae668fbe8d7d0dfb237e Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 15:25:14 +0530 +Subject: gpio: tegra186: Fix tegra186_gpio_is_accessible() check + +From: Prathamesh Shete <pshete@nvidia.com> + +[ Upstream commit d806f474a9a7993648a2c70642ee129316d8deff ] + +The controller has several register bits describing access control +information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it +means we have full read/write access to all the registers for given GPIO +pin. When SCR_SEC[R|W]EN is set, it means we need to further check the +accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all +the registers for given GPIO pin. + +This check was previously declaring that a GPIO pin was accessible +only if either of the following conditions were met: + + - SCR_SEC_REN + SCR_SEC_WEN both set + + or + + - SCR_SEC_REN + SCR_SEC_WEN both set and + SCR_SEC_G1R + SCR_SEC_G1W both set + +Update the check to properly handle cases where only one of +SCR_SEC_REN or SCR_SEC_WEN is set. + +Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.") +Signed-off-by: Prathamesh Shete <pshete@nvidia.com> +Acked-by: Thierry Reding <treding@nvidia.com> +Link: https://lore.kernel.org/r/20240424095514.24397-1-pshete@nvidia.com +Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/gpio/gpio-tegra186.c | 20 +++++++++++--------- + 1 file changed, 11 insertions(+), 9 deletions(-) + +diff --git a/drivers/gpio/gpio-tegra186.c b/drivers/gpio/gpio-tegra186.c +index d87dd06db40d0..9130c691a2dd3 100644 +--- a/drivers/gpio/gpio-tegra186.c ++++ b/drivers/gpio/gpio-tegra186.c +@@ -36,12 +36,6 @@ + #define TEGRA186_GPIO_SCR_SEC_REN BIT(27) + #define TEGRA186_GPIO_SCR_SEC_G1W BIT(9) + #define TEGRA186_GPIO_SCR_SEC_G1R BIT(1) +-#define TEGRA186_GPIO_FULL_ACCESS (TEGRA186_GPIO_SCR_SEC_WEN | \ +- TEGRA186_GPIO_SCR_SEC_REN | \ +- TEGRA186_GPIO_SCR_SEC_G1R | \ +- TEGRA186_GPIO_SCR_SEC_G1W) +-#define TEGRA186_GPIO_SCR_SEC_ENABLE (TEGRA186_GPIO_SCR_SEC_WEN | \ +- TEGRA186_GPIO_SCR_SEC_REN) + + /* control registers */ + #define TEGRA186_GPIO_ENABLE_CONFIG 0x00 +@@ -177,10 +171,18 @@ static inline bool tegra186_gpio_is_accessible(struct tegra_gpio *gpio, unsigned + + value = __raw_readl(secure + TEGRA186_GPIO_SCR); + +- if ((value & TEGRA186_GPIO_SCR_SEC_ENABLE) == 0) +- return true; ++ /* ++ * When SCR_SEC_[R|W]EN is unset, then we have full read/write access to all the ++ * registers for given GPIO pin. ++ * When SCR_SEC[R|W]EN is set, then there is need to further check the accompanying ++ * SCR_SEC_G1[R|W] bit to determine read/write access to all the registers for given ++ * GPIO pin. ++ */ + +- if ((value & TEGRA186_GPIO_FULL_ACCESS) == TEGRA186_GPIO_FULL_ACCESS) ++ if (((value & TEGRA186_GPIO_SCR_SEC_REN) == 0 || ++ ((value & TEGRA186_GPIO_SCR_SEC_REN) && (value & TEGRA186_GPIO_SCR_SEC_G1R))) && ++ ((value & TEGRA186_GPIO_SCR_SEC_WEN) == 0 || ++ ((value & TEGRA186_GPIO_SCR_SEC_WEN) && (value & TEGRA186_GPIO_SCR_SEC_G1W)))) + return true; + + return false; +-- +2.43.0 + diff --git a/queue-6.6/hid-intel-ish-hid-ipc-fix-dev_err-usage-with-uniniti.patch b/queue-6.6/hid-intel-ish-hid-ipc-fix-dev_err-usage-with-uniniti.patch new file mode 100644 index 0000000000..7b8a0434fd --- /dev/null +++ b/queue-6.6/hid-intel-ish-hid-ipc-fix-dev_err-usage-with-uniniti.patch @@ -0,0 +1,49 @@ +From 307fb3f1e3fc52a12693cf39f5d451a971aae032 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 6 Mar 2024 00:44:04 +0000 +Subject: HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized + dev->devc + +From: Zhang Lixu <lixu.zhang@intel.com> + +[ Upstream commit 92826905ae340b7f2b25759a06c8c60bfc476b9f ] + +The variable dev->devc in ish_dev_init was utilized by dev_err before it +was properly assigned. To rectify this, the assignment of dev->devc has +been moved to immediately follow memory allocation. + +Without this change "(NULL device *)" is printed for device information. + +Fixes: 8ae2f2b0a284 ("HID: intel-ish-hid: ipc: Fix potential use-after-free in work function") +Fixes: ae02e5d40d5f ("HID: intel-ish-hid: ipc layer") +Signed-off-by: Zhang Lixu <lixu.zhang@intel.com> +Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> +Signed-off-by: Jiri Kosina <jkosina@suse.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/hid/intel-ish-hid/ipc/ipc.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/hid/intel-ish-hid/ipc/ipc.c b/drivers/hid/intel-ish-hid/ipc/ipc.c +index a49c6affd7c4c..dd5fc60874ba1 100644 +--- a/drivers/hid/intel-ish-hid/ipc/ipc.c ++++ b/drivers/hid/intel-ish-hid/ipc/ipc.c +@@ -948,6 +948,7 @@ struct ishtp_device *ish_dev_init(struct pci_dev *pdev) + if (!dev) + return NULL; + ++ dev->devc = &pdev->dev; + ishtp_device_init(dev); + + init_waitqueue_head(&dev->wait_hw_ready); +@@ -983,7 +984,6 @@ struct ishtp_device *ish_dev_init(struct pci_dev *pdev) + } + + dev->ops = &ish_hw_ops; +- dev->devc = &pdev->dev; + dev->mtu = IPC_PAYLOAD_SIZE - sizeof(struct ishtp_msg_hdr); + return dev; + } +-- +2.43.0 + diff --git a/queue-6.6/hid-logitech-dj-allow-mice-to-use-all-types-of-repor.patch b/queue-6.6/hid-logitech-dj-allow-mice-to-use-all-types-of-repor.patch new file mode 100644 index 0000000000..39c467927e --- /dev/null +++ b/queue-6.6/hid-logitech-dj-allow-mice-to-use-all-types-of-repor.patch @@ -0,0 +1,39 @@ +From f95c2a75027c05aa70ad3835045eef023992928b Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 3 Apr 2024 19:54:24 +0300 +Subject: HID: logitech-dj: allow mice to use all types of reports + +From: Yaraslau Furman <yaro330@gmail.com> + +[ Upstream commit 21f28a7eb78dea6c59be6b0a5e0b47bf3d25fcbb ] + +You can bind whatever action you want to the mouse's reprogrammable +buttons using Windows application. Allow Linux to receive multimedia keycodes. + +Fixes: 3ed224e273ac ("HID: logitech-dj: Fix 064d:c52f receiver support") +Signed-off-by: Yaraslau Furman <yaro330@gmail.com> +Reviewed-by: Hans de Goede <hdegoede@redhat.com> +Signed-off-by: Jiri Kosina <jkosina@suse.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/hid/hid-logitech-dj.c | 4 +--- + 1 file changed, 1 insertion(+), 3 deletions(-) + +diff --git a/drivers/hid/hid-logitech-dj.c b/drivers/hid/hid-logitech-dj.c +index e6a8b6d8eab70..3c3c497b6b911 100644 +--- a/drivers/hid/hid-logitech-dj.c ++++ b/drivers/hid/hid-logitech-dj.c +@@ -965,9 +965,7 @@ static void logi_hidpp_dev_conn_notif_equad(struct hid_device *hdev, + } + break; + case REPORT_TYPE_MOUSE: +- workitem->reports_supported |= STD_MOUSE | HIDPP; +- if (djrcv_dev->type == recvr_type_mouse_only) +- workitem->reports_supported |= MULTIMEDIA; ++ workitem->reports_supported |= STD_MOUSE | HIDPP | MULTIMEDIA; + break; + } + } +-- +2.43.0 + diff --git a/queue-6.6/i40e-do-not-use-wq_mem_reclaim-flag-for-workqueue.patch b/queue-6.6/i40e-do-not-use-wq_mem_reclaim-flag-for-workqueue.patch new file mode 100644 index 0000000000..d5d31f582c --- /dev/null +++ b/queue-6.6/i40e-do-not-use-wq_mem_reclaim-flag-for-workqueue.patch @@ -0,0 +1,125 @@ +From 9c07014270e2b27e9e11c6ffdd3bfe1df6445374 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 11:27:17 -0700 +Subject: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue + +From: Sindhu Devale <sindhu.devale@intel.com> + +[ Upstream commit 2cc7d150550cc981aceedf008f5459193282425c ] + +Issue reported by customer during SRIOV testing, call trace: +When both i40e and the i40iw driver are loaded, a warning +in check_flush_dependency is being triggered. This seems +to be because of the i40e driver workqueue is allocated with +the WQ_MEM_RECLAIM flag, and the i40iw one is not. + +Similar error was encountered on ice too and it was fixed by +removing the flag. Do the same for i40e too. + +[Feb 9 09:08] ------------[ cut here ]------------ +[ +0.000004] workqueue: WQ_MEM_RECLAIM i40e:i40e_service_task [i40e] is +flushing !WQ_MEM_RECLAIM infiniband:0x0 +[ +0.000060] WARNING: CPU: 0 PID: 937 at kernel/workqueue.c:2966 +check_flush_dependency+0x10b/0x120 +[ +0.000007] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq +snd_timer snd_seq_device snd soundcore nls_utf8 cifs cifs_arc4 +nls_ucs2_utils rdma_cm iw_cm ib_cm cifs_md4 dns_resolver netfs qrtr +rfkill sunrpc vfat fat intel_rapl_msr intel_rapl_common irdma +intel_uncore_frequency intel_uncore_frequency_common ice ipmi_ssif +isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal +intel_powerclamp gnss coretemp ib_uverbs rapl intel_cstate ib_core +iTCO_wdt iTCO_vendor_support acpi_ipmi mei_me ipmi_si intel_uncore +ioatdma i2c_i801 joydev pcspkr mei ipmi_devintf lpc_ich +intel_pch_thermal i2c_smbus ipmi_msghandler acpi_power_meter acpi_pad +xfs libcrc32c ast sd_mod drm_shmem_helper t10_pi drm_kms_helper sg ixgbe +drm i40e ahci crct10dif_pclmul libahci crc32_pclmul igb crc32c_intel +libata ghash_clmulni_intel i2c_algo_bit mdio dca wmi dm_mirror +dm_region_hash dm_log dm_mod fuse +[ +0.000050] CPU: 0 PID: 937 Comm: kworker/0:3 Kdump: loaded Not +tainted 6.8.0-rc2-Feb-net_dev-Qiueue-00279-gbd43c5687e05 #1 +[ +0.000003] Hardware name: Intel Corporation S2600BPB/S2600BPB, BIOS +SE5C620.86B.02.01.0013.121520200651 12/15/2020 +[ +0.000001] Workqueue: i40e i40e_service_task [i40e] +[ +0.000024] RIP: 0010:check_flush_dependency+0x10b/0x120 +[ +0.000003] Code: ff 49 8b 54 24 18 48 8d 8b b0 00 00 00 49 89 e8 48 +81 c6 b0 00 00 00 48 c7 c7 b0 97 fa 9f c6 05 8a cc 1f 02 01 e8 35 b3 fd +ff <0f> 0b e9 10 ff ff ff 80 3d 78 cc 1f 02 00 75 94 e9 46 ff ff ff 90 +[ +0.000002] RSP: 0018:ffffbd294976bcf8 EFLAGS: 00010282 +[ +0.000002] RAX: 0000000000000000 RBX: ffff94d4c483c000 RCX: +0000000000000027 +[ +0.000001] RDX: ffff94d47f620bc8 RSI: 0000000000000001 RDI: +ffff94d47f620bc0 +[ +0.000001] RBP: 0000000000000000 R08: 0000000000000000 R09: +00000000ffff7fff +[ +0.000001] R10: ffffbd294976bb98 R11: ffffffffa0be65e8 R12: +ffff94c5451ea180 +[ +0.000001] R13: ffff94c5ab5e8000 R14: ffff94c5c20b6e05 R15: +ffff94c5f1330ab0 +[ +0.000001] FS: 0000000000000000(0000) GS:ffff94d47f600000(0000) +knlGS:0000000000000000 +[ +0.000002] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ +0.000001] CR2: 00007f9e6f1fca70 CR3: 0000000038e20004 CR4: +00000000007706f0 +[ +0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: +0000000000000000 +[ +0.000001] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: +0000000000000400 +[ +0.000001] PKRU: 55555554 +[ +0.000001] Call Trace: +[ +0.000001] <TASK> +[ +0.000002] ? __warn+0x80/0x130 +[ +0.000003] ? check_flush_dependency+0x10b/0x120 +[ +0.000002] ? report_bug+0x195/0x1a0 +[ +0.000005] ? handle_bug+0x3c/0x70 +[ +0.000003] ? exc_invalid_op+0x14/0x70 +[ +0.000002] ? asm_exc_invalid_op+0x16/0x20 +[ +0.000006] ? check_flush_dependency+0x10b/0x120 +[ +0.000002] ? check_flush_dependency+0x10b/0x120 +[ +0.000002] __flush_workqueue+0x126/0x3f0 +[ +0.000015] ib_cache_cleanup_one+0x1c/0xe0 [ib_core] +[ +0.000056] __ib_unregister_device+0x6a/0xb0 [ib_core] +[ +0.000023] ib_unregister_device_and_put+0x34/0x50 [ib_core] +[ +0.000020] i40iw_close+0x4b/0x90 [irdma] +[ +0.000022] i40e_notify_client_of_netdev_close+0x54/0xc0 [i40e] +[ +0.000035] i40e_service_task+0x126/0x190 [i40e] +[ +0.000024] process_one_work+0x174/0x340 +[ +0.000003] worker_thread+0x27e/0x390 +[ +0.000001] ? __pfx_worker_thread+0x10/0x10 +[ +0.000002] kthread+0xdf/0x110 +[ +0.000002] ? __pfx_kthread+0x10/0x10 +[ +0.000002] ret_from_fork+0x2d/0x50 +[ +0.000003] ? __pfx_kthread+0x10/0x10 +[ +0.000001] ret_from_fork_asm+0x1b/0x30 +[ +0.000004] </TASK> +[ +0.000001] ---[ end trace 0000000000000000 ]--- + +Fixes: 4d5957cbdecd ("i40e: remove WQ_UNBOUND and the task limit of our workqueue") +Signed-off-by: Sindhu Devale <sindhu.devale@intel.com> +Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> +Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com> +Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com> +Tested-by: Robert Ganzynkowicz <robert.ganzynkowicz@intel.com> +Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com> +Link: https://lore.kernel.org/r/20240423182723.740401-2-anthony.l.nguyen@intel.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/intel/i40e/i40e_main.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c +index a21fc92aa2725..54d3bd8ec5ea3 100644 +--- a/drivers/net/ethernet/intel/i40e/i40e_main.c ++++ b/drivers/net/ethernet/intel/i40e/i40e_main.c +@@ -16778,7 +16778,7 @@ static int __init i40e_init_module(void) + * since we need to be able to guarantee forward progress even under + * memory pressure. + */ +- i40e_wq = alloc_workqueue("%s", WQ_MEM_RECLAIM, 0, i40e_driver_name); ++ i40e_wq = alloc_workqueue("%s", 0, 0, i40e_driver_name); + if (!i40e_wq) { + pr_err("%s: Failed to create workqueue\n", i40e_driver_name); + return -ENOMEM; +-- +2.43.0 + diff --git a/queue-6.6/i40e-report-mfs-in-decimal-base-instead-of-hex.patch b/queue-6.6/i40e-report-mfs-in-decimal-base-instead-of-hex.patch new file mode 100644 index 0000000000..b4b6c3578c --- /dev/null +++ b/queue-6.6/i40e-report-mfs-in-decimal-base-instead-of-hex.patch @@ -0,0 +1,59 @@ +From c9fa55acc8b4d7d61fb1e0917b9cb75c50b4fb54 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 11:27:18 -0700 +Subject: i40e: Report MFS in decimal base instead of hex + +From: Erwan Velu <e.velu@criteo.com> + +[ Upstream commit ef3c313119ea448c22da10366faa26b5b4b1a18e ] + +If the MFS is set below the default (0x2600), a warning message is +reported like the following : + + MFS for port 1 has been set below the default: 600 + +This message is a bit confusing as the number shown here (600) is in +fact an hexa number: 0x600 = 1536 + +Without any explicit "0x" prefix, this message is read like the MFS is +set to 600 bytes. + +MFS, as per MTUs, are usually expressed in decimal base. + +This commit reports both current and default MFS values in decimal +so it's less confusing for end-users. + +A typical warning message looks like the following : + + MFS for port 1 (1536) has been set below the default (9728) + +Signed-off-by: Erwan Velu <e.velu@criteo.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Tested-by: Tony Brelinski <tony.brelinski@intel.com> +Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com> +Fixes: 3a2c6ced90e1 ("i40e: Add a check to see if MFS is set") +Link: https://lore.kernel.org/r/20240423182723.740401-3-anthony.l.nguyen@intel.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/intel/i40e/i40e_main.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c +index 54d3bd8ec5ea3..f8d1a994c2f65 100644 +--- a/drivers/net/ethernet/intel/i40e/i40e_main.c ++++ b/drivers/net/ethernet/intel/i40e/i40e_main.c +@@ -16237,8 +16237,8 @@ static int i40e_probe(struct pci_dev *pdev, const struct pci_device_id *ent) + val = (rd32(&pf->hw, I40E_PRTGL_SAH) & + I40E_PRTGL_SAH_MFS_MASK) >> I40E_PRTGL_SAH_MFS_SHIFT; + if (val < MAX_FRAME_SIZE_DEFAULT) +- dev_warn(&pdev->dev, "MFS for port %x has been set below the default: %x\n", +- pf->hw.port, val); ++ dev_warn(&pdev->dev, "MFS for port %x (%d) has been set below the default (%d)\n", ++ pf->hw.port, val, MAX_FRAME_SIZE_DEFAULT); + + /* Add a filter to drop all Flow control frames from any VSI from being + * transmitted. By doing so we stop a malicious VF from sending out +-- +2.43.0 + diff --git a/queue-6.6/iavf-fix-tc-config-comparison-with-existing-adapter-.patch b/queue-6.6/iavf-fix-tc-config-comparison-with-existing-adapter-.patch new file mode 100644 index 0000000000..80d031376c --- /dev/null +++ b/queue-6.6/iavf-fix-tc-config-comparison-with-existing-adapter-.patch @@ -0,0 +1,76 @@ +From 3bf7cdf76e3bf7486f824dc5ebf37be063d44767 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 11:27:19 -0700 +Subject: iavf: Fix TC config comparison with existing adapter TC config + +From: Sudheer Mogilappagari <sudheer.mogilappagari@intel.com> + +[ Upstream commit 54976cf58d6168b8d15cebb395069f23b2f34b31 ] + +Same number of TCs doesn't imply that underlying TC configs are +same. The config could be different due to difference in number +of queues in each TC. Add utility function to determine if TC +configs are same. + +Fixes: d5b33d024496 ("i40evf: add ndo_setup_tc callback to i40evf") +Signed-off-by: Sudheer Mogilappagari <sudheer.mogilappagari@intel.com> +Tested-by: Mineri Bhange <minerix.bhange@intel.com> (A Contingent Worker at Intel) +Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com> +Link: https://lore.kernel.org/r/20240423182723.740401-4-anthony.l.nguyen@intel.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/intel/iavf/iavf_main.c | 30 ++++++++++++++++++++- + 1 file changed, 29 insertions(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c +index 257865647c865..ce0b919995264 100644 +--- a/drivers/net/ethernet/intel/iavf/iavf_main.c ++++ b/drivers/net/ethernet/intel/iavf/iavf_main.c +@@ -3574,6 +3574,34 @@ static void iavf_del_all_cloud_filters(struct iavf_adapter *adapter) + spin_unlock_bh(&adapter->cloud_filter_list_lock); + } + ++/** ++ * iavf_is_tc_config_same - Compare the mqprio TC config with the ++ * TC config already configured on this adapter. ++ * @adapter: board private structure ++ * @mqprio_qopt: TC config received from kernel. ++ * ++ * This function compares the TC config received from the kernel ++ * with the config already configured on the adapter. ++ * ++ * Return: True if configuration is same, false otherwise. ++ **/ ++static bool iavf_is_tc_config_same(struct iavf_adapter *adapter, ++ struct tc_mqprio_qopt *mqprio_qopt) ++{ ++ struct virtchnl_channel_info *ch = &adapter->ch_config.ch_info[0]; ++ int i; ++ ++ if (adapter->num_tc != mqprio_qopt->num_tc) ++ return false; ++ ++ for (i = 0; i < adapter->num_tc; i++) { ++ if (ch[i].count != mqprio_qopt->count[i] || ++ ch[i].offset != mqprio_qopt->offset[i]) ++ return false; ++ } ++ return true; ++} ++ + /** + * __iavf_setup_tc - configure multiple traffic classes + * @netdev: network interface device structure +@@ -3631,7 +3659,7 @@ static int __iavf_setup_tc(struct net_device *netdev, void *type_data) + if (ret) + return ret; + /* Return if same TC config is requested */ +- if (adapter->num_tc == num_tc) ++ if (iavf_is_tc_config_same(adapter, &mqprio_qopt->qopt)) + return 0; + adapter->num_tc = num_tc; + +-- +2.43.0 + diff --git a/queue-6.6/ice-fix-lag-and-vf-lock-dependency-in-ice_reset_vf.patch b/queue-6.6/ice-fix-lag-and-vf-lock-dependency-in-ice_reset_vf.patch new file mode 100644 index 0000000000..ecf6148f39 --- /dev/null +++ b/queue-6.6/ice-fix-lag-and-vf-lock-dependency-in-ice_reset_vf.patch @@ -0,0 +1,184 @@ +From 94dc2a40cc26a9cbb57ee939c101e67938ea0f2e Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 11:27:20 -0700 +Subject: ice: fix LAG and VF lock dependency in ice_reset_vf() + +From: Jacob Keller <jacob.e.keller@intel.com> + +[ Upstream commit 96fdd1f6b4ed72a741fb0eb705c0e13049b8721f ] + +9f74a3dfcf83 ("ice: Fix VF Reset paths when interface in a failed over +aggregate"), the ice driver has acquired the LAG mutex in ice_reset_vf(). +The commit placed this lock acquisition just prior to the acquisition of +the VF configuration lock. + +If ice_reset_vf() acquires the configuration lock via the ICE_VF_RESET_LOCK +flag, this could deadlock with ice_vc_cfg_qs_msg() because it always +acquires the locks in the order of the VF configuration lock and then the +LAG mutex. + +Lockdep reports this violation almost immediately on creating and then +removing 2 VF: + +====================================================== +WARNING: possible circular locking dependency detected +6.8.0-rc6 #54 Tainted: G W O +------------------------------------------------------ +kworker/60:3/6771 is trying to acquire lock: +ff40d43e099380a0 (&vf->cfg_lock){+.+.}-{3:3}, at: ice_reset_vf+0x22f/0x4d0 [ice] + +but task is already holding lock: +ff40d43ea1961210 (&pf->lag_mutex){+.+.}-{3:3}, at: ice_reset_vf+0xb7/0x4d0 [ice] + +which lock already depends on the new lock. + +the existing dependency chain (in reverse order) is: + +-> #1 (&pf->lag_mutex){+.+.}-{3:3}: + __lock_acquire+0x4f8/0xb40 + lock_acquire+0xd4/0x2d0 + __mutex_lock+0x9b/0xbf0 + ice_vc_cfg_qs_msg+0x45/0x690 [ice] + ice_vc_process_vf_msg+0x4f5/0x870 [ice] + __ice_clean_ctrlq+0x2b5/0x600 [ice] + ice_service_task+0x2c9/0x480 [ice] + process_one_work+0x1e9/0x4d0 + worker_thread+0x1e1/0x3d0 + kthread+0x104/0x140 + ret_from_fork+0x31/0x50 + ret_from_fork_asm+0x1b/0x30 + +-> #0 (&vf->cfg_lock){+.+.}-{3:3}: + check_prev_add+0xe2/0xc50 + validate_chain+0x558/0x800 + __lock_acquire+0x4f8/0xb40 + lock_acquire+0xd4/0x2d0 + __mutex_lock+0x9b/0xbf0 + ice_reset_vf+0x22f/0x4d0 [ice] + ice_process_vflr_event+0x98/0xd0 [ice] + ice_service_task+0x1cc/0x480 [ice] + process_one_work+0x1e9/0x4d0 + worker_thread+0x1e1/0x3d0 + kthread+0x104/0x140 + ret_from_fork+0x31/0x50 + ret_from_fork_asm+0x1b/0x30 + +other info that might help us debug this: + Possible unsafe locking scenario: + CPU0 CPU1 + ---- ---- + lock(&pf->lag_mutex); + lock(&vf->cfg_lock); + lock(&pf->lag_mutex); + lock(&vf->cfg_lock); + + *** DEADLOCK *** +4 locks held by kworker/60:3/6771: + #0: ff40d43e05428b38 ((wq_completion)ice){+.+.}-{0:0}, at: process_one_work+0x176/0x4d0 + #1: ff50d06e05197e58 ((work_completion)(&pf->serv_task)){+.+.}-{0:0}, at: process_one_work+0x176/0x4d0 + #2: ff40d43ea1960e50 (&pf->vfs.table_lock){+.+.}-{3:3}, at: ice_process_vflr_event+0x48/0xd0 [ice] + #3: ff40d43ea1961210 (&pf->lag_mutex){+.+.}-{3:3}, at: ice_reset_vf+0xb7/0x4d0 [ice] + +stack backtrace: +CPU: 60 PID: 6771 Comm: kworker/60:3 Tainted: G W O 6.8.0-rc6 #54 +Hardware name: +Workqueue: ice ice_service_task [ice] +Call Trace: + <TASK> + dump_stack_lvl+0x4a/0x80 + check_noncircular+0x12d/0x150 + check_prev_add+0xe2/0xc50 + ? save_trace+0x59/0x230 + ? add_chain_cache+0x109/0x450 + validate_chain+0x558/0x800 + __lock_acquire+0x4f8/0xb40 + ? lockdep_hardirqs_on+0x7d/0x100 + lock_acquire+0xd4/0x2d0 + ? ice_reset_vf+0x22f/0x4d0 [ice] + ? lock_is_held_type+0xc7/0x120 + __mutex_lock+0x9b/0xbf0 + ? ice_reset_vf+0x22f/0x4d0 [ice] + ? ice_reset_vf+0x22f/0x4d0 [ice] + ? rcu_is_watching+0x11/0x50 + ? ice_reset_vf+0x22f/0x4d0 [ice] + ice_reset_vf+0x22f/0x4d0 [ice] + ? process_one_work+0x176/0x4d0 + ice_process_vflr_event+0x98/0xd0 [ice] + ice_service_task+0x1cc/0x480 [ice] + process_one_work+0x1e9/0x4d0 + worker_thread+0x1e1/0x3d0 + ? __pfx_worker_thread+0x10/0x10 + kthread+0x104/0x140 + ? __pfx_kthread+0x10/0x10 + ret_from_fork+0x31/0x50 + ? __pfx_kthread+0x10/0x10 + ret_from_fork_asm+0x1b/0x30 + </TASK> + +To avoid deadlock, we must acquire the LAG mutex only after acquiring the +VF configuration lock. Fix the ice_reset_vf() to acquire the LAG mutex only +after we either acquire or check that the VF configuration lock is held. + +Fixes: 9f74a3dfcf83 ("ice: Fix VF Reset paths when interface in a failed over aggregate") +Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> +Reviewed-by: Dave Ertman <david.m.ertman@intel.com> +Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com> +Tested-by: Przemek Kitszel <przemyslaw.kitszel@intel.com> +Tested-by: Rafal Romanowski <rafal.romanowski@intel.com> +Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com> +Link: https://lore.kernel.org/r/20240423182723.740401-5-anthony.l.nguyen@intel.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/intel/ice/ice_vf_lib.c | 16 ++++++++-------- + 1 file changed, 8 insertions(+), 8 deletions(-) + +diff --git a/drivers/net/ethernet/intel/ice/ice_vf_lib.c b/drivers/net/ethernet/intel/ice/ice_vf_lib.c +index d488c7156d093..03b9d7d748518 100644 +--- a/drivers/net/ethernet/intel/ice/ice_vf_lib.c ++++ b/drivers/net/ethernet/intel/ice/ice_vf_lib.c +@@ -847,6 +847,11 @@ int ice_reset_vf(struct ice_vf *vf, u32 flags) + return 0; + } + ++ if (flags & ICE_VF_RESET_LOCK) ++ mutex_lock(&vf->cfg_lock); ++ else ++ lockdep_assert_held(&vf->cfg_lock); ++ + lag = pf->lag; + mutex_lock(&pf->lag_mutex); + if (lag && lag->bonded && lag->primary) { +@@ -858,11 +863,6 @@ int ice_reset_vf(struct ice_vf *vf, u32 flags) + act_prt = ICE_LAG_INVALID_PORT; + } + +- if (flags & ICE_VF_RESET_LOCK) +- mutex_lock(&vf->cfg_lock); +- else +- lockdep_assert_held(&vf->cfg_lock); +- + if (ice_is_vf_disabled(vf)) { + vsi = ice_get_vf_vsi(vf); + if (!vsi) { +@@ -947,14 +947,14 @@ int ice_reset_vf(struct ice_vf *vf, u32 flags) + ice_mbx_clear_malvf(&vf->mbx_info); + + out_unlock: +- if (flags & ICE_VF_RESET_LOCK) +- mutex_unlock(&vf->cfg_lock); +- + if (lag && lag->bonded && lag->primary && + act_prt != ICE_LAG_INVALID_PORT) + ice_lag_move_vf_nodes_cfg(lag, pri_prt, act_prt); + mutex_unlock(&pf->lag_mutex); + ++ if (flags & ICE_VF_RESET_LOCK) ++ mutex_unlock(&vf->cfg_lock); ++ + return err; + } + +-- +2.43.0 + diff --git a/queue-6.6/icmp-prevent-possible-null-dereferences-from-icmp_bu.patch b/queue-6.6/icmp-prevent-possible-null-dereferences-from-icmp_bu.patch new file mode 100644 index 0000000000..672cb70211 --- /dev/null +++ b/queue-6.6/icmp-prevent-possible-null-dereferences-from-icmp_bu.patch @@ -0,0 +1,74 @@ +From 61a815e63670ad172fef07da2a19e8c09485798f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sat, 20 Apr 2024 07:01:16 +0000 +Subject: icmp: prevent possible NULL dereferences from icmp_build_probe() + +From: Eric Dumazet <edumazet@google.com> + +[ Upstream commit c58e88d49097bd12dfcfef4f075b43f5d5830941 ] + +First problem is a double call to __in_dev_get_rcu(), because +the second one could return NULL. + +if (__in_dev_get_rcu(dev) && __in_dev_get_rcu(dev)->ifa_list) + +Second problem is a read from dev->ip6_ptr with no NULL check: + +if (!list_empty(&rcu_dereference(dev->ip6_ptr)->addr_list)) + +Use the correct RCU API to fix these. + +v2: add missing include <net/addrconf.h> + +Fixes: d329ea5bd884 ("icmp: add response to RFC 8335 PROBE messages") +Signed-off-by: Eric Dumazet <edumazet@google.com> +Cc: Andreas Roeseler <andreas.a.roeseler@gmail.com> +Reviewed-by: David Ahern <dsahern@kernel.org> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/ipv4/icmp.c | 12 ++++++++++-- + 1 file changed, 10 insertions(+), 2 deletions(-) + +diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c +index b8607763d113a..3b221643206de 100644 +--- a/net/ipv4/icmp.c ++++ b/net/ipv4/icmp.c +@@ -92,6 +92,7 @@ + #include <net/inet_common.h> + #include <net/ip_fib.h> + #include <net/l3mdev.h> ++#include <net/addrconf.h> + + /* + * Build xmit assembly blocks +@@ -1032,6 +1033,8 @@ bool icmp_build_probe(struct sk_buff *skb, struct icmphdr *icmphdr) + struct icmp_ext_hdr *ext_hdr, _ext_hdr; + struct icmp_ext_echo_iio *iio, _iio; + struct net *net = dev_net(skb->dev); ++ struct inet6_dev *in6_dev; ++ struct in_device *in_dev; + struct net_device *dev; + char buff[IFNAMSIZ]; + u16 ident_len; +@@ -1115,10 +1118,15 @@ bool icmp_build_probe(struct sk_buff *skb, struct icmphdr *icmphdr) + /* Fill bits in reply message */ + if (dev->flags & IFF_UP) + status |= ICMP_EXT_ECHOREPLY_ACTIVE; +- if (__in_dev_get_rcu(dev) && __in_dev_get_rcu(dev)->ifa_list) ++ ++ in_dev = __in_dev_get_rcu(dev); ++ if (in_dev && rcu_access_pointer(in_dev->ifa_list)) + status |= ICMP_EXT_ECHOREPLY_IPV4; +- if (!list_empty(&rcu_dereference(dev->ip6_ptr)->addr_list)) ++ ++ in6_dev = __in6_dev_get(dev); ++ if (in6_dev && !list_empty(&in6_dev->addr_list)) + status |= ICMP_EXT_ECHOREPLY_IPV6; ++ + dev_put(dev); + icmphdr->un.echo.sequence |= htons(status); + return true; +-- +2.43.0 + diff --git a/queue-6.6/ipv4-check-for-null-idev-in-ip_route_use_hint.patch b/queue-6.6/ipv4-check-for-null-idev-in-ip_route_use_hint.patch new file mode 100644 index 0000000000..49c27b6169 --- /dev/null +++ b/queue-6.6/ipv4-check-for-null-idev-in-ip_route_use_hint.patch @@ -0,0 +1,83 @@ +From d9670b444c4a7c28b5a4b7f4d945b18d2af1fb3c Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 21 Apr 2024 18:43:26 +0000 +Subject: ipv4: check for NULL idev in ip_route_use_hint() + +From: Eric Dumazet <edumazet@google.com> + +[ Upstream commit 58a4c9b1e5a3e53c9148e80b90e1e43897ce77d1 ] + +syzbot was able to trigger a NULL deref in fib_validate_source() +in an old tree [1]. + +It appears the bug exists in latest trees. + +All calls to __in_dev_get_rcu() must be checked for a NULL result. + +[1] +general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN +KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] +CPU: 2 PID: 3257 Comm: syz-executor.3 Not tainted 5.10.0-syzkaller #0 +Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 + RIP: 0010:fib_validate_source+0xbf/0x15a0 net/ipv4/fib_frontend.c:425 +Code: 18 f2 f2 f2 f2 42 c7 44 20 23 f3 f3 f3 f3 48 89 44 24 78 42 c6 44 20 27 f3 e8 5d 88 48 fc 4c 89 e8 48 c1 e8 03 48 89 44 24 18 <42> 80 3c 20 00 74 08 4c 89 ef e8 d2 15 98 fc 48 89 5c 24 10 41 bf +RSP: 0018:ffffc900015fee40 EFLAGS: 00010246 +RAX: 0000000000000000 RBX: ffff88800f7a4000 RCX: ffff88800f4f90c0 +RDX: 0000000000000000 RSI: 0000000004001eac RDI: ffff8880160c64c0 +RBP: ffffc900015ff060 R08: 0000000000000000 R09: ffff88800f7a4000 +R10: 0000000000000002 R11: ffff88800f4f90c0 R12: dffffc0000000000 +R13: 0000000000000000 R14: 0000000000000000 R15: ffff88800f7a4000 +FS: 00007f938acfe6c0(0000) GS:ffff888058c00000(0000) knlGS:0000000000000000 +CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +CR2: 00007f938acddd58 CR3: 000000001248e000 CR4: 0000000000352ef0 +DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 +DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 +Call Trace: + ip_route_use_hint+0x410/0x9b0 net/ipv4/route.c:2231 + ip_rcv_finish_core+0x2c4/0x1a30 net/ipv4/ip_input.c:327 + ip_list_rcv_finish net/ipv4/ip_input.c:612 [inline] + ip_sublist_rcv+0x3ed/0xe50 net/ipv4/ip_input.c:638 + ip_list_rcv+0x422/0x470 net/ipv4/ip_input.c:673 + __netif_receive_skb_list_ptype net/core/dev.c:5572 [inline] + __netif_receive_skb_list_core+0x6b1/0x890 net/core/dev.c:5620 + __netif_receive_skb_list net/core/dev.c:5672 [inline] + netif_receive_skb_list_internal+0x9f9/0xdc0 net/core/dev.c:5764 + netif_receive_skb_list+0x55/0x3e0 net/core/dev.c:5816 + xdp_recv_frames net/bpf/test_run.c:257 [inline] + xdp_test_run_batch net/bpf/test_run.c:335 [inline] + bpf_test_run_xdp_live+0x1818/0x1d00 net/bpf/test_run.c:363 + bpf_prog_test_run_xdp+0x81f/0x1170 net/bpf/test_run.c:1376 + bpf_prog_test_run+0x349/0x3c0 kernel/bpf/syscall.c:3736 + __sys_bpf+0x45c/0x710 kernel/bpf/syscall.c:5115 + __do_sys_bpf kernel/bpf/syscall.c:5201 [inline] + __se_sys_bpf kernel/bpf/syscall.c:5199 [inline] + __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5199 + +Fixes: 02b24941619f ("ipv4: use dst hint for ipv4 list receive") +Reported-by: syzbot <syzkaller@googlegroups.com> +Signed-off-by: Eric Dumazet <edumazet@google.com> +Acked-by: Paolo Abeni <pabeni@redhat.com> +Link: https://lore.kernel.org/r/20240421184326.1704930-1-edumazet@google.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/ipv4/route.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/net/ipv4/route.c b/net/ipv4/route.c +index e1e30c09a1753..7c05cbcd39d33 100644 +--- a/net/ipv4/route.c ++++ b/net/ipv4/route.c +@@ -2166,6 +2166,9 @@ int ip_route_use_hint(struct sk_buff *skb, __be32 daddr, __be32 saddr, + int err = -EINVAL; + u32 tag = 0; + ++ if (!in_dev) ++ return -EINVAL; ++ + if (ipv4_is_multicast(saddr) || ipv4_is_lbcast(saddr)) + goto martian_source; + +-- +2.43.0 + diff --git a/queue-6.6/ipvs-fix-checksumming-on-gso-of-sctp-packets.patch b/queue-6.6/ipvs-fix-checksumming-on-gso-of-sctp-packets.patch new file mode 100644 index 0000000000..23061a5937 --- /dev/null +++ b/queue-6.6/ipvs-fix-checksumming-on-gso-of-sctp-packets.patch @@ -0,0 +1,53 @@ +From 1aa600d8dff471f1d12721cff0b1b664807dd026 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 21 Apr 2024 16:22:32 +0200 +Subject: ipvs: Fix checksumming on GSO of SCTP packets + +From: Ismael Luceno <iluceno@suse.de> + +[ Upstream commit e10d3ba4d434ed172914617ed8d74bd411421193 ] + +It was observed in the wild that pairs of consecutive packets would leave +the IPVS with the same wrong checksum, and the issue only went away when +disabling GSO. + +IPVS needs to avoid computing the SCTP checksum when using GSO. + +Fixes: 90017accff61 ("sctp: Add GSO support") +Co-developed-by: Firo Yang <firo.yang@suse.com> +Signed-off-by: Ismael Luceno <iluceno@suse.de> +Tested-by: Andreas Taschner <andreas.taschner@suse.com> +Acked-by: Julian Anastasov <ja@ssi.bg> +Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/netfilter/ipvs/ip_vs_proto_sctp.c | 6 ++++-- + 1 file changed, 4 insertions(+), 2 deletions(-) + +diff --git a/net/netfilter/ipvs/ip_vs_proto_sctp.c b/net/netfilter/ipvs/ip_vs_proto_sctp.c +index a0921adc31a9f..1e689c7141271 100644 +--- a/net/netfilter/ipvs/ip_vs_proto_sctp.c ++++ b/net/netfilter/ipvs/ip_vs_proto_sctp.c +@@ -126,7 +126,8 @@ sctp_snat_handler(struct sk_buff *skb, struct ip_vs_protocol *pp, + if (sctph->source != cp->vport || payload_csum || + skb->ip_summed == CHECKSUM_PARTIAL) { + sctph->source = cp->vport; +- sctp_nat_csum(skb, sctph, sctphoff); ++ if (!skb_is_gso(skb) || !skb_is_gso_sctp(skb)) ++ sctp_nat_csum(skb, sctph, sctphoff); + } else { + skb->ip_summed = CHECKSUM_UNNECESSARY; + } +@@ -174,7 +175,8 @@ sctp_dnat_handler(struct sk_buff *skb, struct ip_vs_protocol *pp, + (skb->ip_summed == CHECKSUM_PARTIAL && + !(skb_dst(skb)->dev->features & NETIF_F_SCTP_CRC))) { + sctph->dest = cp->dport; +- sctp_nat_csum(skb, sctph, sctphoff); ++ if (!skb_is_gso(skb) || !skb_is_gso_sctp(skb)) ++ sctp_nat_csum(skb, sctph, sctphoff); + } else if (skb->ip_summed != CHECKSUM_PARTIAL) { + skb->ip_summed = CHECKSUM_UNNECESSARY; + } +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-core-unregister-emad-trap-using-forward-action.patch b/queue-6.6/mlxsw-core-unregister-emad-trap-using-forward-action.patch new file mode 100644 index 0000000000..721963ed64 --- /dev/null +++ b/queue-6.6/mlxsw-core-unregister-emad-trap-using-forward-action.patch @@ -0,0 +1,57 @@ +From b724f0bc90688dbcb4c03622d3027c1bda08a13f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 15:46:06 +0200 +Subject: mlxsw: core: Unregister EMAD trap using FORWARD action + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 976c44af48141cd8595601c0af2a19a43c5b228b ] + +The device's manual (PRM - Programmer's Reference Manual) classifies the +trap that is used to deliver EMAD responses as an "event trap". Among +other things, it means that the only actions that can be associated with +the trap are TRAP and FORWARD (NOP). + +Currently, during driver de-initialization the driver unregisters the +trap by setting its action to DISCARD, which violates the above +guideline. Future firmware versions will prevent such misuses by +returning an error. This does not prevent the driver from working, but +an error will be printed to the kernel log during module removal / +devlink reload: + +mlxsw_spectrum 0000:03:00.0: Reg cmd access status failed (status=7(bad parameter)) +mlxsw_spectrum 0000:03:00.0: Reg cmd access failed (reg_id=7003(hpkt),type=write) + +Suppress the error message by aligning the driver to the manual and use +a FORWARD (NOP) action when unregistering the trap. + +Fixes: 4ec14b7634b2 ("mlxsw: Add interface to access registers and process events") +Cc: Jiri Pirko <jiri@resnulli.us> +Cc: Amit Cohen <amcohen@nvidia.com> +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Link: https://lore.kernel.org/r/753a89e14008fde08cb4a2c1e5f537b81d8eb2d6.1713446092.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/core.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/core.c b/drivers/net/ethernet/mellanox/mlxsw/core.c +index 1ccf3b73ed724..85507d01fd457 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/core.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/core.c +@@ -835,7 +835,7 @@ static void mlxsw_emad_rx_listener_func(struct sk_buff *skb, u16 local_port, + + static const struct mlxsw_listener mlxsw_emad_rx_listener = + MLXSW_RXL(mlxsw_emad_rx_listener_func, ETHEMAD, TRAP_TO_CPU, false, +- EMAD, DISCARD); ++ EMAD, FORWARD); + + static int mlxsw_emad_tlv_enable(struct mlxsw_core *mlxsw_core) + { +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-core_env-fix-driver-initialization-with-old-fi.patch b/queue-6.6/mlxsw-core_env-fix-driver-initialization-with-old-fi.patch new file mode 100644 index 0000000000..30729bd39a --- /dev/null +++ b/queue-6.6/mlxsw-core_env-fix-driver-initialization-with-old-fi.patch @@ -0,0 +1,86 @@ +From d3f7c5f47080ce30af4ab6e3e914aecaf11f6aab Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 15:46:07 +0200 +Subject: mlxsw: core_env: Fix driver initialization with old firmware + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 7e2050a8366315aeaf0316b3d362e67cf58f3ea8 ] + +The driver queries the Management Capabilities Mask (MCAM) register +during initialization to understand if it can read up to 128 bytes from +transceiver modules. + +However, not all firmware versions support this register, leading to the +driver failing to load. + +Fix by treating an error in the register query as an indication that the +feature is not supported. + +Fixes: 1f4aea1f72da ("mlxsw: core_env: Read transceiver module EEPROM in 128 bytes chunks") +Reported-by: Tim 'mithro' Ansell <me@mith.ro> +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/0afa8b2e8bac178f5f88211344429176dcc72281.1713446092.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../net/ethernet/mellanox/mlxsw/core_env.c | 20 ++++++------------- + 1 file changed, 6 insertions(+), 14 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/core_env.c b/drivers/net/ethernet/mellanox/mlxsw/core_env.c +index d637c0348fa15..b71bc23245fe2 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/core_env.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/core_env.c +@@ -1357,24 +1357,20 @@ static struct mlxsw_linecards_event_ops mlxsw_env_event_ops = { + .got_inactive = mlxsw_env_got_inactive, + }; + +-static int mlxsw_env_max_module_eeprom_len_query(struct mlxsw_env *mlxsw_env) ++static void mlxsw_env_max_module_eeprom_len_query(struct mlxsw_env *mlxsw_env) + { + char mcam_pl[MLXSW_REG_MCAM_LEN]; +- bool mcia_128b_supported; ++ bool mcia_128b_supported = false; + int err; + + mlxsw_reg_mcam_pack(mcam_pl, + MLXSW_REG_MCAM_FEATURE_GROUP_ENHANCED_FEATURES); + err = mlxsw_reg_query(mlxsw_env->core, MLXSW_REG(mcam), mcam_pl); +- if (err) +- return err; +- +- mlxsw_reg_mcam_unpack(mcam_pl, MLXSW_REG_MCAM_MCIA_128B, +- &mcia_128b_supported); ++ if (!err) ++ mlxsw_reg_mcam_unpack(mcam_pl, MLXSW_REG_MCAM_MCIA_128B, ++ &mcia_128b_supported); + + mlxsw_env->max_eeprom_len = mcia_128b_supported ? 128 : 48; +- +- return 0; + } + + int mlxsw_env_init(struct mlxsw_core *mlxsw_core, +@@ -1445,15 +1441,11 @@ int mlxsw_env_init(struct mlxsw_core *mlxsw_core, + if (err) + goto err_type_set; + +- err = mlxsw_env_max_module_eeprom_len_query(env); +- if (err) +- goto err_eeprom_len_query; +- ++ mlxsw_env_max_module_eeprom_len_query(env); + env->line_cards[0]->active = true; + + return 0; + +-err_eeprom_len_query: + err_type_set: + mlxsw_env_module_event_disable(env, 0); + err_mlxsw_env_module_event_enable: +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-incorrect-list-api-usage.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-incorrect-list-api-usage.patch new file mode 100644 index 0000000000..f842de6bd6 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-incorrect-list-api-usage.patch @@ -0,0 +1,84 @@ +From ab98bce8fd901e158dde8a97323730ce75ffd6d9 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:26:01 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit b377add0f0117409c418ddd6504bd682ebe0bf79 ] + +Both the function that migrates all the chunks within a region and the +function that migrates all the entries within a chunk call +list_first_entry() on the respective lists without checking that the +lists are not empty. This is incorrect usage of the API, which leads to +the following warning [1]. + +Fix by returning if the lists are empty as there is nothing to migrate +in this case. + +[1] +WARNING: CPU: 0 PID: 6437 at drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c:1266 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x1f1/0> +Modules linked in: +CPU: 0 PID: 6437 Comm: kworker/0:37 Not tainted 6.9.0-rc3-custom-00883-g94a65f079ef6 #39 +Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 +Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work +RIP: 0010:mlxsw_sp_acl_tcam_vchunk_migrate_all+0x1f1/0x2c0 +[...] +Call Trace: + <TASK> + mlxsw_sp_acl_tcam_vregion_rehash_work+0x6c/0x4a0 + process_one_work+0x151/0x370 + worker_thread+0x2cb/0x3e0 + kthread+0xd0/0x100 + ret_from_fork+0x34/0x50 + ret_from_fork_asm+0x1a/0x30 + </TASK> + +Fixes: 6f9579d4e302 ("mlxsw: spectrum_acl: Remember where to continue rehash migration") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/4628e9a22d1d84818e28310abbbc498e7bc31bc9.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 7 +++++++ + 1 file changed, 7 insertions(+) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index e8c6078866213..89a5ebc3463ff 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -1254,6 +1254,9 @@ mlxsw_sp_acl_tcam_vchunk_migrate_one(struct mlxsw_sp *mlxsw_sp, + return 0; + } + ++ if (list_empty(&vchunk->ventry_list)) ++ goto out; ++ + /* If the migration got interrupted, we have the ventry to start from + * stored in context. + */ +@@ -1305,6 +1308,7 @@ mlxsw_sp_acl_tcam_vchunk_migrate_one(struct mlxsw_sp *mlxsw_sp, + } + } + ++out: + mlxsw_sp_acl_tcam_vchunk_migrate_end(mlxsw_sp, vchunk, ctx); + return 0; + } +@@ -1318,6 +1322,9 @@ mlxsw_sp_acl_tcam_vchunk_migrate_all(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_acl_tcam_vchunk *vchunk; + int err; + ++ if (list_empty(&vregion->vchunk_list)) ++ return 0; ++ + /* If the migration got interrupted, we have the vchunk + * we are working on stored in context. + */ +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-memory-leak-during-rehas.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-memory-leak-during-rehas.patch new file mode 100644 index 0000000000..51ca1482d3 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-memory-leak-during-rehas.patch @@ -0,0 +1,91 @@ +From 0dfc16814a97eee00fa9bc259eea40ac10b65a7a Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:25:59 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix memory leak during rehash + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 8ca3f7a7b61393804c46f170743c3b839df13977 ] + +The rehash delayed work migrates filters from one region to another. +This is done by iterating over all chunks (all the filters with the same +priority) in the region and in each chunk iterating over all the +filters. + +If the migration fails, the code tries to migrate the filters back to +the old region. However, the rollback itself can also fail in which case +another migration will be erroneously performed. Besides the fact that +this ping pong is not a very good idea, it also creates a problem. + +Each virtual chunk references two chunks: The currently used one +('vchunk->chunk') and a backup ('vchunk->chunk2'). During migration the +first holds the chunk we want to migrate filters to and the second holds +the chunk we are migrating filters from. + +The code currently assumes - but does not verify - that the backup chunk +does not exist (NULL) if the currently used chunk does not reference the +target region. This assumption breaks when we are trying to rollback a +rollback, resulting in the backup chunk being overwritten and leaked +[1]. + +Fix by not rolling back a failed rollback and add a warning to avoid +future cases. + +[1] +WARNING: CPU: 5 PID: 1063 at lib/parman.c:291 parman_destroy+0x17/0x20 +Modules linked in: +CPU: 5 PID: 1063 Comm: kworker/5:11 Tainted: G W 6.9.0-rc2-custom-00784-gc6a05c468a0b #14 +Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 +Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work +RIP: 0010:parman_destroy+0x17/0x20 +[...] +Call Trace: + <TASK> + mlxsw_sp_acl_atcam_region_fini+0x19/0x60 + mlxsw_sp_acl_tcam_region_destroy+0x49/0xf0 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x1f1/0x470 + process_one_work+0x151/0x370 + worker_thread+0x2cb/0x3e0 + kthread+0xd0/0x100 + ret_from_fork+0x34/0x50 + ret_from_fork_asm+0x1a/0x30 + </TASK> + +Fixes: 843500518509 ("mlxsw: spectrum_acl: Do rollback as another call to mlxsw_sp_acl_tcam_vchunk_migrate_all()") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/d5edd4f4503934186ae5cfe268503b16345b4e0f.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 568ae7092fe0e..0902eb7651e14 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -1200,6 +1200,8 @@ mlxsw_sp_acl_tcam_vchunk_migrate_start(struct mlxsw_sp *mlxsw_sp, + { + struct mlxsw_sp_acl_tcam_chunk *new_chunk; + ++ WARN_ON(vchunk->chunk2); ++ + new_chunk = mlxsw_sp_acl_tcam_chunk_create(mlxsw_sp, vchunk, region); + if (IS_ERR(new_chunk)) + return PTR_ERR(new_chunk); +@@ -1334,6 +1336,8 @@ mlxsw_sp_acl_tcam_vregion_migrate(struct mlxsw_sp *mlxsw_sp, + err = mlxsw_sp_acl_tcam_vchunk_migrate_all(mlxsw_sp, vregion, + ctx, credits); + if (err) { ++ if (ctx->this_is_rollback) ++ return err; + /* In case migration was not successful, we need to swap + * so the original region pointer is assigned again + * to vregion->region. +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-memory-leak-when-canceli.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-memory-leak-when-canceli.patch new file mode 100644 index 0000000000..72abceed04 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-memory-leak-when-canceli.patch @@ -0,0 +1,82 @@ +From 7033e9b344d5da84d0364e3593ea0b486f924d27 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:26:02 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit fb4e2b70a7194b209fc7320bbf33b375f7114bd5 ] + +The rehash delayed work is rescheduled with a delay if the number of +credits at end of the work is not negative as supposedly it means that +the migration ended. Otherwise, it is rescheduled immediately. + +After "mlxsw: spectrum_acl_tcam: Fix possible use-after-free during +rehash" the above is no longer accurate as a non-negative number of +credits is no longer indicative of the migration being done. It can also +happen if the work encountered an error in which case the migration will +resume the next time the work is scheduled. + +The significance of the above is that it is possible for the work to be +pending and associated with hints that were allocated when the migration +started. This leads to the hints being leaked [1] when the work is +canceled while pending as part of ACL region dismantle. + +Fix by freeing the hints if hints are associated with a work that was +canceled while pending. + +Blame the original commit since the reliance on not having a pending +work associated with hints is fragile. + +[1] +unreferenced object 0xffff88810e7c3000 (size 256): + comm "kworker/0:16", pid 176, jiffies 4295460353 + hex dump (first 32 bytes): + 00 30 95 11 81 88 ff ff 61 00 00 00 00 00 00 80 .0......a....... + 00 00 61 00 40 00 00 00 00 00 00 00 04 00 00 00 ..a.@........... + backtrace (crc 2544ddb9): + [<00000000cf8cfab3>] kmalloc_trace+0x23f/0x2a0 + [<000000004d9a1ad9>] objagg_hints_get+0x42/0x390 + [<000000000b143cf3>] mlxsw_sp_acl_erp_rehash_hints_get+0xca/0x400 + [<0000000059bdb60a>] mlxsw_sp_acl_tcam_vregion_rehash_work+0x868/0x1160 + [<00000000e81fd734>] process_one_work+0x59c/0xf20 + [<00000000ceee9e81>] worker_thread+0x799/0x12c0 + [<00000000bda6fe39>] kthread+0x246/0x300 + [<0000000070056d23>] ret_from_fork+0x34/0x70 + [<00000000dea2b93e>] ret_from_fork_asm+0x1a/0x30 + +Fixes: c9c9af91f1d9 ("mlxsw: spectrum_acl: Allow to interrupt/continue rehash work") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/0cc12ebb07c4d4c41a1265ee2c28b392ff997a86.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 6 +++++- + 1 file changed, 5 insertions(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 89a5ebc3463ff..92a406f02eae7 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -836,10 +836,14 @@ mlxsw_sp_acl_tcam_vregion_destroy(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_acl_tcam *tcam = vregion->tcam; + + if (vgroup->vregion_rehash_enabled && ops->region_rehash_hints_get) { ++ struct mlxsw_sp_acl_tcam_rehash_ctx *ctx = &vregion->rehash.ctx; ++ + mutex_lock(&tcam->lock); + list_del(&vregion->tlist); + mutex_unlock(&tcam->lock); +- cancel_delayed_work_sync(&vregion->rehash.dw); ++ if (cancel_delayed_work_sync(&vregion->rehash.dw) && ++ ctx->hints_priv) ++ ops->region_rehash_hints_put(ctx->hints_priv); + } + mlxsw_sp_acl_tcam_vgroup_vregion_detach(mlxsw_sp, vregion); + if (vregion->region2) +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch new file mode 100644 index 0000000000..b653b54892 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch @@ -0,0 +1,107 @@ +From 6624c817d6c4fb94bf5ce5a59016d1a82116cbd6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:25:56 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity + update + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 79b5b4b18bc85b19d3a518483f9abbbe6d7b3ba4 ] + +The rule activity update delayed work periodically traverses the list of +configured rules and queries their activity from the device. + +As part of this task it accesses the entry pointed by 'ventry->entry', +but this entry can be changed concurrently by the rehash delayed work, +leading to a use-after-free [1]. + +Fix by closing the race and perform the activity query under the +'vregion->lock' mutex. + +[1] +BUG: KASAN: slab-use-after-free in mlxsw_sp_acl_tcam_flower_rule_activity_get+0x121/0x140 +Read of size 8 at addr ffff8881054ed808 by task kworker/0:18/181 + +CPU: 0 PID: 181 Comm: kworker/0:18 Not tainted 6.9.0-rc2-custom-00781-gd5ab772d32f7 #2 +Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 +Workqueue: mlxsw_core mlxsw_sp_acl_rule_activity_update_work +Call Trace: + <TASK> + dump_stack_lvl+0xc6/0x120 + print_report+0xce/0x670 + kasan_report+0xd7/0x110 + mlxsw_sp_acl_tcam_flower_rule_activity_get+0x121/0x140 + mlxsw_sp_acl_rule_activity_update_work+0x219/0x400 + process_one_work+0x8eb/0x19b0 + worker_thread+0x6c9/0xf70 + kthread+0x2c9/0x3b0 + ret_from_fork+0x4d/0x80 + ret_from_fork_asm+0x1a/0x30 + </TASK> + +Allocated by task 1039: + kasan_save_stack+0x33/0x60 + kasan_save_track+0x14/0x30 + __kasan_kmalloc+0x8f/0xa0 + __kmalloc+0x19c/0x360 + mlxsw_sp_acl_tcam_entry_create+0x7b/0x1f0 + mlxsw_sp_acl_tcam_vchunk_migrate_all+0x30d/0xb50 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 + process_one_work+0x8eb/0x19b0 + worker_thread+0x6c9/0xf70 + kthread+0x2c9/0x3b0 + ret_from_fork+0x4d/0x80 + ret_from_fork_asm+0x1a/0x30 + +Freed by task 1039: + kasan_save_stack+0x33/0x60 + kasan_save_track+0x14/0x30 + kasan_save_free_info+0x3b/0x60 + poison_slab_object+0x102/0x170 + __kasan_slab_free+0x14/0x30 + kfree+0xc1/0x290 + mlxsw_sp_acl_tcam_vchunk_migrate_all+0x3d7/0xb50 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 + process_one_work+0x8eb/0x19b0 + worker_thread+0x6c9/0xf70 + kthread+0x2c9/0x3b0 + ret_from_fork+0x4d/0x80 + ret_from_fork_asm+0x1a/0x30 + +Fixes: 2bffc5322fd8 ("mlxsw: spectrum_acl: Don't take mutex in mlxsw_sp_acl_tcam_vregion_rehash_work()") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/1fcce0a60b231ebeb2515d91022284ba7b4ffe7a.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 10 ++++++++-- + 1 file changed, 8 insertions(+), 2 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 9c0c728bb42dc..7e69225c057de 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -1159,8 +1159,14 @@ mlxsw_sp_acl_tcam_ventry_activity_get(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_acl_tcam_ventry *ventry, + bool *activity) + { +- return mlxsw_sp_acl_tcam_entry_activity_get(mlxsw_sp, +- ventry->entry, activity); ++ struct mlxsw_sp_acl_tcam_vregion *vregion = ventry->vchunk->vregion; ++ int err; ++ ++ mutex_lock(&vregion->lock); ++ err = mlxsw_sp_acl_tcam_entry_activity_get(mlxsw_sp, ventry->entry, ++ activity); ++ mutex_unlock(&vregion->lock); ++ return err; + } + + static int +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch-19343 b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch-19343 new file mode 100644 index 0000000000..6e61bec85e --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch-19343 @@ -0,0 +1,103 @@ +From 1fc076371acb296a095f374db4b2efb123a1eb11 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:25:57 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 54225988889931467a9b55fdbef534079b665519 ] + +The rehash delayed work migrates filters from one region to another +according to the number of available credits. + +The migrated from region is destroyed at the end of the work if the +number of credits is non-negative as the assumption is that this is +indicative of migration being complete. This assumption is incorrect as +a non-negative number of credits can also be the result of a failed +migration. + +The destruction of a region that still has filters referencing it can +result in a use-after-free [1]. + +Fix by not destroying the region if migration failed. + +[1] +BUG: KASAN: slab-use-after-free in mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 +Read of size 8 at addr ffff8881735319e8 by task kworker/0:31/3858 + +CPU: 0 PID: 3858 Comm: kworker/0:31 Tainted: G W 6.9.0-rc2-custom-00782-gf2275c2157d8 #5 +Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 +Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work +Call Trace: + <TASK> + dump_stack_lvl+0xc6/0x120 + print_report+0xce/0x670 + kasan_report+0xd7/0x110 + mlxsw_sp_acl_ctcam_region_entry_remove+0x21d/0x230 + mlxsw_sp_acl_ctcam_entry_del+0x2e/0x70 + mlxsw_sp_acl_atcam_entry_del+0x81/0x210 + mlxsw_sp_acl_tcam_vchunk_migrate_all+0x3cd/0xb50 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x157/0x1300 + process_one_work+0x8eb/0x19b0 + worker_thread+0x6c9/0xf70 + kthread+0x2c9/0x3b0 + ret_from_fork+0x4d/0x80 + ret_from_fork_asm+0x1a/0x30 + </TASK> + +Allocated by task 174: + kasan_save_stack+0x33/0x60 + kasan_save_track+0x14/0x30 + __kasan_kmalloc+0x8f/0xa0 + __kmalloc+0x19c/0x360 + mlxsw_sp_acl_tcam_region_create+0xdf/0x9c0 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x954/0x1300 + process_one_work+0x8eb/0x19b0 + worker_thread+0x6c9/0xf70 + kthread+0x2c9/0x3b0 + ret_from_fork+0x4d/0x80 + ret_from_fork_asm+0x1a/0x30 + +Freed by task 7: + kasan_save_stack+0x33/0x60 + kasan_save_track+0x14/0x30 + kasan_save_free_info+0x3b/0x60 + poison_slab_object+0x102/0x170 + __kasan_slab_free+0x14/0x30 + kfree+0xc1/0x290 + mlxsw_sp_acl_tcam_region_destroy+0x272/0x310 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x731/0x1300 + process_one_work+0x8eb/0x19b0 + worker_thread+0x6c9/0xf70 + kthread+0x2c9/0x3b0 + ret_from_fork+0x4d/0x80 + ret_from_fork_asm+0x1a/0x30 + +Fixes: c9c9af91f1d9 ("mlxsw: spectrum_acl: Allow to interrupt/continue rehash work") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/3e412b5659ec2310c5c615760dfe5eac18dd7ebd.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 7e69225c057de..1ff0b2c7c11de 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -1451,6 +1451,7 @@ mlxsw_sp_acl_tcam_vregion_rehash(struct mlxsw_sp *mlxsw_sp, + ctx, credits); + if (err) { + dev_err(mlxsw_sp->bus_info->dev, "Failed to migrate vregion\n"); ++ return; + } + + if (*credits >= 0) +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-race-during-rehash-delay.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-race-during-rehash-delay.patch new file mode 100644 index 0000000000..0a765df243 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-race-during-rehash-delay.patch @@ -0,0 +1,80 @@ +From 36c34a5c6264c1aca2c1d22089d03c3f7b3ba296 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:25:55 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix race during rehash delayed work + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit d90cfe20562407d9f080d24123078d666d730707 ] + +The purpose of the rehash delayed work is to reduce the number of masks +(eRPs) used by an ACL region as the eRP bank is a global and limited +resource. + +This is done in three steps: + +1. Creating a new set of masks and a new ACL region which will use the + new masks and to which the existing filters will be migrated to. The + new region is assigned to 'vregion->region' and the region from which + the filters are migrated from is assigned to 'vregion->region2'. + +2. Migrating all the filters from the old region to the new region. + +3. Destroying the old region and setting 'vregion->region2' to NULL. + +Only the second steps is performed under the 'vregion->lock' mutex +although its comments says that among other things it "Protects +consistency of region, region2 pointers". + +This is problematic as the first step can race with filter insertion +from user space that uses 'vregion->region', but under the mutex. + +Fix by holding the mutex across the entirety of the delayed work and not +only during the second step. + +Fixes: 2bffc5322fd8 ("mlxsw: spectrum_acl: Don't take mutex in mlxsw_sp_acl_tcam_vregion_rehash_work()") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/1ec1d54edf2bad0a369e6b4fa030aba64e1f124b.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index b6a4652a6475a..9c0c728bb42dc 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -718,7 +718,9 @@ static void mlxsw_sp_acl_tcam_vregion_rehash_work(struct work_struct *work) + rehash.dw.work); + int credits = MLXSW_SP_ACL_TCAM_VREGION_REHASH_CREDITS; + ++ mutex_lock(&vregion->lock); + mlxsw_sp_acl_tcam_vregion_rehash(vregion->mlxsw_sp, vregion, &credits); ++ mutex_unlock(&vregion->lock); + if (credits < 0) + /* Rehash gone out of credits so it was interrupted. + * Schedule the work as soon as possible to continue. +@@ -1323,7 +1325,6 @@ mlxsw_sp_acl_tcam_vregion_migrate(struct mlxsw_sp *mlxsw_sp, + int err, err2; + + trace_mlxsw_sp_acl_tcam_vregion_migrate(mlxsw_sp, vregion); +- mutex_lock(&vregion->lock); + err = mlxsw_sp_acl_tcam_vchunk_migrate_all(mlxsw_sp, vregion, + ctx, credits); + if (err) { +@@ -1343,7 +1344,6 @@ mlxsw_sp_acl_tcam_vregion_migrate(struct mlxsw_sp *mlxsw_sp, + /* Let the rollback to be continued later on. */ + } + } +- mutex_unlock(&vregion->lock); + trace_mlxsw_sp_acl_tcam_vregion_migrate_end(mlxsw_sp, vregion); + return err; + } +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-race-in-region-id-alloca.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-race-in-region-id-alloca.patch new file mode 100644 index 0000000000..6990b822d9 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-race-in-region-id-alloca.patch @@ -0,0 +1,182 @@ +From 34aa7a295e00aac3245bc1915d6fb4f2e59a7ea6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:25:54 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix race in region ID allocation + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 627f9c1bb882765a84aa78015abbacd783d429be ] + +Region identifiers can be allocated both when user space tries to insert +a new tc filter and when filters are migrated from one region to another +as part of the rehash delayed work. + +There is no lock protecting the bitmap from which these identifiers are +allocated from, which is racy and leads to bad parameter errors from the +device's firmware. + +Fix by converting the bitmap to IDA which handles its own locking. For +consistency, do the same for the group identifiers that are part of the +same structure. + +Fixes: 2bffc5322fd8 ("mlxsw: spectrum_acl: Don't take mutex in mlxsw_sp_acl_tcam_vregion_rehash_work()") +Reported-by: Amit Cohen <amcohen@nvidia.com> +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/ce494b7940cadfe84f3e18da7785b51ef5f776e3.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../mellanox/mlxsw/spectrum_acl_tcam.c | 61 ++++++++----------- + .../mellanox/mlxsw/spectrum_acl_tcam.h | 5 +- + 2 files changed, 30 insertions(+), 36 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index f20052776b3f2..b6a4652a6475a 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -10,6 +10,7 @@ + #include <linux/netdevice.h> + #include <linux/mutex.h> + #include <linux/refcount.h> ++#include <linux/idr.h> + #include <net/devlink.h> + #include <trace/events/mlxsw.h> + +@@ -58,41 +59,43 @@ int mlxsw_sp_acl_tcam_priority_get(struct mlxsw_sp *mlxsw_sp, + static int mlxsw_sp_acl_tcam_region_id_get(struct mlxsw_sp_acl_tcam *tcam, + u16 *p_id) + { +- u16 id; ++ int id; + +- id = find_first_zero_bit(tcam->used_regions, tcam->max_regions); +- if (id < tcam->max_regions) { +- __set_bit(id, tcam->used_regions); +- *p_id = id; +- return 0; +- } +- return -ENOBUFS; ++ id = ida_alloc_max(&tcam->used_regions, tcam->max_regions - 1, ++ GFP_KERNEL); ++ if (id < 0) ++ return id; ++ ++ *p_id = id; ++ ++ return 0; + } + + static void mlxsw_sp_acl_tcam_region_id_put(struct mlxsw_sp_acl_tcam *tcam, + u16 id) + { +- __clear_bit(id, tcam->used_regions); ++ ida_free(&tcam->used_regions, id); + } + + static int mlxsw_sp_acl_tcam_group_id_get(struct mlxsw_sp_acl_tcam *tcam, + u16 *p_id) + { +- u16 id; ++ int id; + +- id = find_first_zero_bit(tcam->used_groups, tcam->max_groups); +- if (id < tcam->max_groups) { +- __set_bit(id, tcam->used_groups); +- *p_id = id; +- return 0; +- } +- return -ENOBUFS; ++ id = ida_alloc_max(&tcam->used_groups, tcam->max_groups - 1, ++ GFP_KERNEL); ++ if (id < 0) ++ return id; ++ ++ *p_id = id; ++ ++ return 0; + } + + static void mlxsw_sp_acl_tcam_group_id_put(struct mlxsw_sp_acl_tcam *tcam, + u16 id) + { +- __clear_bit(id, tcam->used_groups); ++ ida_free(&tcam->used_groups, id); + } + + struct mlxsw_sp_acl_tcam_pattern { +@@ -1549,19 +1552,11 @@ int mlxsw_sp_acl_tcam_init(struct mlxsw_sp *mlxsw_sp, + if (max_tcam_regions < max_regions) + max_regions = max_tcam_regions; + +- tcam->used_regions = bitmap_zalloc(max_regions, GFP_KERNEL); +- if (!tcam->used_regions) { +- err = -ENOMEM; +- goto err_alloc_used_regions; +- } ++ ida_init(&tcam->used_regions); + tcam->max_regions = max_regions; + + max_groups = MLXSW_CORE_RES_GET(mlxsw_sp->core, ACL_MAX_GROUPS); +- tcam->used_groups = bitmap_zalloc(max_groups, GFP_KERNEL); +- if (!tcam->used_groups) { +- err = -ENOMEM; +- goto err_alloc_used_groups; +- } ++ ida_init(&tcam->used_groups); + tcam->max_groups = max_groups; + tcam->max_group_size = MLXSW_CORE_RES_GET(mlxsw_sp->core, + ACL_MAX_GROUP_SIZE); +@@ -1575,10 +1570,8 @@ int mlxsw_sp_acl_tcam_init(struct mlxsw_sp *mlxsw_sp, + return 0; + + err_tcam_init: +- bitmap_free(tcam->used_groups); +-err_alloc_used_groups: +- bitmap_free(tcam->used_regions); +-err_alloc_used_regions: ++ ida_destroy(&tcam->used_groups); ++ ida_destroy(&tcam->used_regions); + mlxsw_sp_acl_tcam_rehash_params_unregister(mlxsw_sp); + err_rehash_params_register: + mutex_destroy(&tcam->lock); +@@ -1591,8 +1584,8 @@ void mlxsw_sp_acl_tcam_fini(struct mlxsw_sp *mlxsw_sp, + const struct mlxsw_sp_acl_tcam_ops *ops = mlxsw_sp->acl_tcam_ops; + + ops->fini(mlxsw_sp, tcam->priv); +- bitmap_free(tcam->used_groups); +- bitmap_free(tcam->used_regions); ++ ida_destroy(&tcam->used_groups); ++ ida_destroy(&tcam->used_regions); + mlxsw_sp_acl_tcam_rehash_params_unregister(mlxsw_sp); + mutex_destroy(&tcam->lock); + } +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.h b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.h +index 462bf448497d3..79a1d86065125 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.h ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.h +@@ -6,15 +6,16 @@ + + #include <linux/list.h> + #include <linux/parman.h> ++#include <linux/idr.h> + + #include "reg.h" + #include "spectrum.h" + #include "core_acl_flex_keys.h" + + struct mlxsw_sp_acl_tcam { +- unsigned long *used_regions; /* bit array */ ++ struct ida used_regions; + unsigned int max_regions; +- unsigned long *used_groups; /* bit array */ ++ struct ida used_groups; + unsigned int max_groups; + unsigned int max_group_size; + struct mutex lock; /* guards vregion list */ +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-fix-warning-during-rehash.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-warning-during-rehash.patch new file mode 100644 index 0000000000..4f450ffb5e --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-fix-warning-during-rehash.patch @@ -0,0 +1,133 @@ +From 3d07d4dd2b893e022fe78c411476b90e222c68e4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:26:00 +0200 +Subject: mlxsw: spectrum_acl_tcam: Fix warning during rehash + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 743edc8547a92b6192aa1f1b6bb78233fa21dc9b ] + +As previously explained, the rehash delayed work migrates filters from +one region to another. This is done by iterating over all chunks (all +the filters with the same priority) in the region and in each chunk +iterating over all the filters. + +When the work runs out of credits it stores the current chunk and entry +as markers in the per-work context so that it would know where to resume +the migration from the next time the work is scheduled. + +Upon error, the chunk marker is reset to NULL, but without resetting the +entry markers despite being relative to it. This can result in migration +being resumed from an entry that does not belong to the chunk being +migrated. In turn, this will eventually lead to a chunk being iterated +over as if it is an entry. Because of how the two structures happen to +be defined, this does not lead to KASAN splats, but to warnings such as +[1]. + +Fix by creating a helper that resets all the markers and call it from +all the places the currently only reset the chunk marker. For good +measures also call it when starting a completely new rehash. Add a +warning to avoid future cases. + +[1] +WARNING: CPU: 7 PID: 1076 at drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_keys.c:407 mlxsw_afk_encode+0x242/0x2f0 +Modules linked in: +CPU: 7 PID: 1076 Comm: kworker/7:24 Tainted: G W 6.9.0-rc3-custom-00880-g29e61d91b77b #29 +Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 +Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work +RIP: 0010:mlxsw_afk_encode+0x242/0x2f0 +[...] +Call Trace: + <TASK> + mlxsw_sp_acl_atcam_entry_add+0xd9/0x3c0 + mlxsw_sp_acl_tcam_entry_create+0x5e/0xa0 + mlxsw_sp_acl_tcam_vchunk_migrate_all+0x109/0x290 + mlxsw_sp_acl_tcam_vregion_rehash_work+0x6c/0x470 + process_one_work+0x151/0x370 + worker_thread+0x2cb/0x3e0 + kthread+0xd0/0x100 + ret_from_fork+0x34/0x50 + </TASK> + +Fixes: 6f9579d4e302 ("mlxsw: spectrum_acl: Remember where to continue rehash migration") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/cc17eed86b41dd829d39b07906fec074a9ce580e.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../mellanox/mlxsw/spectrum_acl_tcam.c | 20 ++++++++++++++++--- + 1 file changed, 17 insertions(+), 3 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 0902eb7651e14..e8c6078866213 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -730,6 +730,17 @@ static void mlxsw_sp_acl_tcam_vregion_rehash_work(struct work_struct *work) + mlxsw_sp_acl_tcam_vregion_rehash_work_schedule(vregion); + } + ++static void ++mlxsw_sp_acl_tcam_rehash_ctx_vchunk_reset(struct mlxsw_sp_acl_tcam_rehash_ctx *ctx) ++{ ++ /* The entry markers are relative to the current chunk and therefore ++ * needs to be reset together with the chunk marker. ++ */ ++ ctx->current_vchunk = NULL; ++ ctx->start_ventry = NULL; ++ ctx->stop_ventry = NULL; ++} ++ + static void + mlxsw_sp_acl_tcam_rehash_ctx_vchunk_changed(struct mlxsw_sp_acl_tcam_vchunk *vchunk) + { +@@ -752,7 +763,7 @@ mlxsw_sp_acl_tcam_rehash_ctx_vregion_changed(struct mlxsw_sp_acl_tcam_vregion *v + * the current chunk pointer to make sure all chunks + * are properly migrated. + */ +- vregion->rehash.ctx.current_vchunk = NULL; ++ mlxsw_sp_acl_tcam_rehash_ctx_vchunk_reset(&vregion->rehash.ctx); + } + + static struct mlxsw_sp_acl_tcam_vregion * +@@ -1220,7 +1231,7 @@ mlxsw_sp_acl_tcam_vchunk_migrate_end(struct mlxsw_sp *mlxsw_sp, + { + mlxsw_sp_acl_tcam_chunk_destroy(mlxsw_sp, vchunk->chunk2); + vchunk->chunk2 = NULL; +- ctx->current_vchunk = NULL; ++ mlxsw_sp_acl_tcam_rehash_ctx_vchunk_reset(ctx); + } + + static int +@@ -1252,6 +1263,8 @@ mlxsw_sp_acl_tcam_vchunk_migrate_one(struct mlxsw_sp *mlxsw_sp, + ventry = list_first_entry(&vchunk->ventry_list, + typeof(*ventry), list); + ++ WARN_ON(ventry->vchunk != vchunk); ++ + list_for_each_entry_from(ventry, &vchunk->ventry_list, list) { + /* During rollback, once we reach the ventry that failed + * to migrate, we are done. +@@ -1343,7 +1356,7 @@ mlxsw_sp_acl_tcam_vregion_migrate(struct mlxsw_sp *mlxsw_sp, + * to vregion->region. + */ + swap(vregion->region, vregion->region2); +- ctx->current_vchunk = NULL; ++ mlxsw_sp_acl_tcam_rehash_ctx_vchunk_reset(ctx); + ctx->this_is_rollback = true; + err2 = mlxsw_sp_acl_tcam_vchunk_migrate_all(mlxsw_sp, vregion, + ctx, credits); +@@ -1402,6 +1415,7 @@ mlxsw_sp_acl_tcam_vregion_rehash_start(struct mlxsw_sp *mlxsw_sp, + + ctx->hints_priv = hints_priv; + ctx->this_is_rollback = false; ++ mlxsw_sp_acl_tcam_rehash_ctx_vchunk_reset(ctx); + + return 0; + +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-spectrum_acl_tcam-rate-limit-error-message.patch b/queue-6.6/mlxsw-spectrum_acl_tcam-rate-limit-error-message.patch new file mode 100644 index 0000000000..1065fab5f5 --- /dev/null +++ b/queue-6.6/mlxsw-spectrum_acl_tcam-rate-limit-error-message.patch @@ -0,0 +1,45 @@ +From cd11111b0fdb37c07ab488adca5b9733e27a166d Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 17:25:58 +0200 +Subject: mlxsw: spectrum_acl_tcam: Rate limit error message + +From: Ido Schimmel <idosch@nvidia.com> + +[ Upstream commit 5bcf925587e9b5d36420d572a0b4d131c90fb306 ] + +In the rare cases when the device resources are exhausted it is likely +that the rehash delayed work will fail. An error message will be printed +whenever this happens which can be overwhelming considering the fact +that the work is per-region and that there can be hundreds of regions. + +Fix by rate limiting the error message. + +Fixes: e5e7962ee5c2 ("mlxsw: spectrum_acl: Implement region migration according to hints") +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Tested-by: Alexander Zubkov <green@qrator.net> +Reviewed-by: Petr Machata <petrm@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/c510763b2ebd25e7990d80183feff91cde593145.1713797103.git.petrm@nvidia.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 1ff0b2c7c11de..568ae7092fe0e 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -1450,7 +1450,7 @@ mlxsw_sp_acl_tcam_vregion_rehash(struct mlxsw_sp *mlxsw_sp, + err = mlxsw_sp_acl_tcam_vregion_migrate(mlxsw_sp, vregion, + ctx, credits); + if (err) { +- dev_err(mlxsw_sp->bus_info->dev, "Failed to migrate vregion\n"); ++ dev_err_ratelimited(mlxsw_sp->bus_info->dev, "Failed to migrate vregion\n"); + return; + } + +-- +2.43.0 + diff --git a/queue-6.6/mlxsw-use-refcount_t-for-reference-counting.patch b/queue-6.6/mlxsw-use-refcount_t-for-reference-counting.patch new file mode 100644 index 0000000000..12434f6063 --- /dev/null +++ b/queue-6.6/mlxsw-use-refcount_t-for-reference-counting.patch @@ -0,0 +1,396 @@ +From 7b56fd2d8fe568a05f7655a3265d7553df68c491 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 26 Jan 2024 19:58:31 +0100 +Subject: mlxsw: Use refcount_t for reference counting + +From: Amit Cohen <amcohen@nvidia.com> + +[ Upstream commit 1267f7223bec186dc26ef4e6075496c6217355de ] + +mlxsw driver uses 'unsigned int' for reference counters in several +structures. Instead, use refcount_t type which allows us to catch overflow +and underflow issues. Change the type of the counters and use the +appropriate API. + +Signed-off-by: Amit Cohen <amcohen@nvidia.com> +Reviewed-by: Ido Schimmel <idosch@nvidia.com> +Signed-off-by: Ido Schimmel <idosch@nvidia.com> +Signed-off-by: Petr Machata <petrm@nvidia.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Signed-off-by: Paolo Abeni <pabeni@redhat.com> +Stable-dep-of: 627f9c1bb882 ("mlxsw: spectrum_acl_tcam: Fix race in region ID allocation") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../mellanox/mlxsw/core_acl_flex_actions.c | 16 ++++++++-------- + .../mellanox/mlxsw/core_acl_flex_keys.c | 9 +++++---- + .../net/ethernet/mellanox/mlxsw/spectrum_acl.c | 11 ++++++----- + .../ethernet/mellanox/mlxsw/spectrum_acl_tcam.c | 17 +++++++++-------- + .../ethernet/mellanox/mlxsw/spectrum_router.c | 15 ++++++++------- + .../mellanox/mlxsw/spectrum_switchdev.c | 8 ++++---- + 6 files changed, 40 insertions(+), 36 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_actions.c b/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_actions.c +index faa63ea9b83e1..1915fa41c6224 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_actions.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_actions.c +@@ -95,7 +95,7 @@ struct mlxsw_afa_set { + */ + has_trap:1, + has_police:1; +- unsigned int ref_count; ++ refcount_t ref_count; + struct mlxsw_afa_set *next; /* Pointer to the next set. */ + struct mlxsw_afa_set *prev; /* Pointer to the previous set, + * note that set may have multiple +@@ -120,7 +120,7 @@ struct mlxsw_afa_fwd_entry { + struct rhash_head ht_node; + struct mlxsw_afa_fwd_entry_ht_key ht_key; + u32 kvdl_index; +- unsigned int ref_count; ++ refcount_t ref_count; + }; + + static const struct rhashtable_params mlxsw_afa_fwd_entry_ht_params = { +@@ -282,7 +282,7 @@ static struct mlxsw_afa_set *mlxsw_afa_set_create(bool is_first) + /* Need to initialize the set to pass by default */ + mlxsw_afa_set_goto_set(set, MLXSW_AFA_SET_GOTO_BINDING_CMD_TERM, 0); + set->ht_key.is_first = is_first; +- set->ref_count = 1; ++ refcount_set(&set->ref_count, 1); + return set; + } + +@@ -330,7 +330,7 @@ static void mlxsw_afa_set_unshare(struct mlxsw_afa *mlxsw_afa, + static void mlxsw_afa_set_put(struct mlxsw_afa *mlxsw_afa, + struct mlxsw_afa_set *set) + { +- if (--set->ref_count) ++ if (!refcount_dec_and_test(&set->ref_count)) + return; + if (set->shared) + mlxsw_afa_set_unshare(mlxsw_afa, set); +@@ -350,7 +350,7 @@ static struct mlxsw_afa_set *mlxsw_afa_set_get(struct mlxsw_afa *mlxsw_afa, + set = rhashtable_lookup_fast(&mlxsw_afa->set_ht, &orig_set->ht_key, + mlxsw_afa_set_ht_params); + if (set) { +- set->ref_count++; ++ refcount_inc(&set->ref_count); + mlxsw_afa_set_put(mlxsw_afa, orig_set); + } else { + set = orig_set; +@@ -564,7 +564,7 @@ mlxsw_afa_fwd_entry_create(struct mlxsw_afa *mlxsw_afa, u16 local_port) + if (!fwd_entry) + return ERR_PTR(-ENOMEM); + fwd_entry->ht_key.local_port = local_port; +- fwd_entry->ref_count = 1; ++ refcount_set(&fwd_entry->ref_count, 1); + + err = rhashtable_insert_fast(&mlxsw_afa->fwd_entry_ht, + &fwd_entry->ht_node, +@@ -607,7 +607,7 @@ mlxsw_afa_fwd_entry_get(struct mlxsw_afa *mlxsw_afa, u16 local_port) + fwd_entry = rhashtable_lookup_fast(&mlxsw_afa->fwd_entry_ht, &ht_key, + mlxsw_afa_fwd_entry_ht_params); + if (fwd_entry) { +- fwd_entry->ref_count++; ++ refcount_inc(&fwd_entry->ref_count); + return fwd_entry; + } + return mlxsw_afa_fwd_entry_create(mlxsw_afa, local_port); +@@ -616,7 +616,7 @@ mlxsw_afa_fwd_entry_get(struct mlxsw_afa *mlxsw_afa, u16 local_port) + static void mlxsw_afa_fwd_entry_put(struct mlxsw_afa *mlxsw_afa, + struct mlxsw_afa_fwd_entry *fwd_entry) + { +- if (--fwd_entry->ref_count) ++ if (!refcount_dec_and_test(&fwd_entry->ref_count)) + return; + mlxsw_afa_fwd_entry_destroy(mlxsw_afa, fwd_entry); + } +diff --git a/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_keys.c b/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_keys.c +index 70f9b5e85a26f..bf140e7416e19 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_keys.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_keys.c +@@ -5,6 +5,7 @@ + #include <linux/slab.h> + #include <linux/list.h> + #include <linux/errno.h> ++#include <linux/refcount.h> + + #include "item.h" + #include "core_acl_flex_keys.h" +@@ -105,7 +106,7 @@ EXPORT_SYMBOL(mlxsw_afk_destroy); + + struct mlxsw_afk_key_info { + struct list_head list; +- unsigned int ref_count; ++ refcount_t ref_count; + unsigned int blocks_count; + int element_to_block[MLXSW_AFK_ELEMENT_MAX]; /* index is element, value + * is index inside "blocks" +@@ -282,7 +283,7 @@ mlxsw_afk_key_info_create(struct mlxsw_afk *mlxsw_afk, + if (err) + goto err_picker; + list_add(&key_info->list, &mlxsw_afk->key_info_list); +- key_info->ref_count = 1; ++ refcount_set(&key_info->ref_count, 1); + return key_info; + + err_picker: +@@ -304,7 +305,7 @@ mlxsw_afk_key_info_get(struct mlxsw_afk *mlxsw_afk, + + key_info = mlxsw_afk_key_info_find(mlxsw_afk, elusage); + if (key_info) { +- key_info->ref_count++; ++ refcount_inc(&key_info->ref_count); + return key_info; + } + return mlxsw_afk_key_info_create(mlxsw_afk, elusage); +@@ -313,7 +314,7 @@ EXPORT_SYMBOL(mlxsw_afk_key_info_get); + + void mlxsw_afk_key_info_put(struct mlxsw_afk_key_info *key_info) + { +- if (--key_info->ref_count) ++ if (!refcount_dec_and_test(&key_info->ref_count)) + return; + mlxsw_afk_key_info_destroy(key_info); + } +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c +index 7c59c8a135840..b01b000bc71c1 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl.c +@@ -9,6 +9,7 @@ + #include <linux/rhashtable.h> + #include <linux/netdevice.h> + #include <linux/mutex.h> ++#include <linux/refcount.h> + #include <net/net_namespace.h> + #include <net/tc_act/tc_vlan.h> + +@@ -55,7 +56,7 @@ struct mlxsw_sp_acl_ruleset { + struct rhash_head ht_node; /* Member of acl HT */ + struct mlxsw_sp_acl_ruleset_ht_key ht_key; + struct rhashtable rule_ht; +- unsigned int ref_count; ++ refcount_t ref_count; + unsigned int min_prio; + unsigned int max_prio; + unsigned long priv[]; +@@ -99,7 +100,7 @@ static bool + mlxsw_sp_acl_ruleset_is_singular(const struct mlxsw_sp_acl_ruleset *ruleset) + { + /* We hold a reference on ruleset ourselves */ +- return ruleset->ref_count == 2; ++ return refcount_read(&ruleset->ref_count) == 2; + } + + int mlxsw_sp_acl_ruleset_bind(struct mlxsw_sp *mlxsw_sp, +@@ -176,7 +177,7 @@ mlxsw_sp_acl_ruleset_create(struct mlxsw_sp *mlxsw_sp, + ruleset = kzalloc(alloc_size, GFP_KERNEL); + if (!ruleset) + return ERR_PTR(-ENOMEM); +- ruleset->ref_count = 1; ++ refcount_set(&ruleset->ref_count, 1); + ruleset->ht_key.block = block; + ruleset->ht_key.chain_index = chain_index; + ruleset->ht_key.ops = ops; +@@ -222,13 +223,13 @@ static void mlxsw_sp_acl_ruleset_destroy(struct mlxsw_sp *mlxsw_sp, + + static void mlxsw_sp_acl_ruleset_ref_inc(struct mlxsw_sp_acl_ruleset *ruleset) + { +- ruleset->ref_count++; ++ refcount_inc(&ruleset->ref_count); + } + + static void mlxsw_sp_acl_ruleset_ref_dec(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_acl_ruleset *ruleset) + { +- if (--ruleset->ref_count) ++ if (!refcount_dec_and_test(&ruleset->ref_count)) + return; + mlxsw_sp_acl_ruleset_destroy(mlxsw_sp, ruleset); + } +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +index 50ea1eff02b2f..f20052776b3f2 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c +@@ -9,6 +9,7 @@ + #include <linux/rhashtable.h> + #include <linux/netdevice.h> + #include <linux/mutex.h> ++#include <linux/refcount.h> + #include <net/devlink.h> + #include <trace/events/mlxsw.h> + +@@ -155,7 +156,7 @@ struct mlxsw_sp_acl_tcam_vregion { + struct mlxsw_sp_acl_tcam_rehash_ctx ctx; + } rehash; + struct mlxsw_sp *mlxsw_sp; +- unsigned int ref_count; ++ refcount_t ref_count; + }; + + struct mlxsw_sp_acl_tcam_vchunk; +@@ -176,7 +177,7 @@ struct mlxsw_sp_acl_tcam_vchunk { + unsigned int priority; /* Priority within the vregion and group */ + struct mlxsw_sp_acl_tcam_vgroup *vgroup; + struct mlxsw_sp_acl_tcam_vregion *vregion; +- unsigned int ref_count; ++ refcount_t ref_count; + }; + + struct mlxsw_sp_acl_tcam_entry { +@@ -769,7 +770,7 @@ mlxsw_sp_acl_tcam_vregion_create(struct mlxsw_sp *mlxsw_sp, + vregion->tcam = tcam; + vregion->mlxsw_sp = mlxsw_sp; + vregion->vgroup = vgroup; +- vregion->ref_count = 1; ++ refcount_set(&vregion->ref_count, 1); + + vregion->key_info = mlxsw_afk_key_info_get(afk, elusage); + if (IS_ERR(vregion->key_info)) { +@@ -856,7 +857,7 @@ mlxsw_sp_acl_tcam_vregion_get(struct mlxsw_sp *mlxsw_sp, + */ + return ERR_PTR(-EOPNOTSUPP); + } +- vregion->ref_count++; ++ refcount_inc(&vregion->ref_count); + return vregion; + } + +@@ -871,7 +872,7 @@ static void + mlxsw_sp_acl_tcam_vregion_put(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_acl_tcam_vregion *vregion) + { +- if (--vregion->ref_count) ++ if (!refcount_dec_and_test(&vregion->ref_count)) + return; + mlxsw_sp_acl_tcam_vregion_destroy(mlxsw_sp, vregion); + } +@@ -924,7 +925,7 @@ mlxsw_sp_acl_tcam_vchunk_create(struct mlxsw_sp *mlxsw_sp, + INIT_LIST_HEAD(&vchunk->ventry_list); + vchunk->priority = priority; + vchunk->vgroup = vgroup; +- vchunk->ref_count = 1; ++ refcount_set(&vchunk->ref_count, 1); + + vregion = mlxsw_sp_acl_tcam_vregion_get(mlxsw_sp, vgroup, + priority, elusage); +@@ -1008,7 +1009,7 @@ mlxsw_sp_acl_tcam_vchunk_get(struct mlxsw_sp *mlxsw_sp, + if (WARN_ON(!mlxsw_afk_key_info_subset(vchunk->vregion->key_info, + elusage))) + return ERR_PTR(-EINVAL); +- vchunk->ref_count++; ++ refcount_inc(&vchunk->ref_count); + return vchunk; + } + return mlxsw_sp_acl_tcam_vchunk_create(mlxsw_sp, vgroup, +@@ -1019,7 +1020,7 @@ static void + mlxsw_sp_acl_tcam_vchunk_put(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_acl_tcam_vchunk *vchunk) + { +- if (--vchunk->ref_count) ++ if (!refcount_dec_and_test(&vchunk->ref_count)) + return; + mlxsw_sp_acl_tcam_vchunk_destroy(mlxsw_sp, vchunk); + } +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c +index ae2fb9efbc509..d15aa6b25a888 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c +@@ -501,7 +501,7 @@ struct mlxsw_sp_rt6 { + + struct mlxsw_sp_lpm_tree { + u8 id; /* tree ID */ +- unsigned int ref_count; ++ refcount_t ref_count; + enum mlxsw_sp_l3proto proto; + unsigned long prefix_ref_count[MLXSW_SP_PREFIX_COUNT]; + struct mlxsw_sp_prefix_usage prefix_usage; +@@ -578,7 +578,7 @@ mlxsw_sp_lpm_tree_find_unused(struct mlxsw_sp *mlxsw_sp) + + for (i = 0; i < mlxsw_sp->router->lpm.tree_count; i++) { + lpm_tree = &mlxsw_sp->router->lpm.trees[i]; +- if (lpm_tree->ref_count == 0) ++ if (refcount_read(&lpm_tree->ref_count) == 0) + return lpm_tree; + } + return NULL; +@@ -654,7 +654,7 @@ mlxsw_sp_lpm_tree_create(struct mlxsw_sp *mlxsw_sp, + sizeof(lpm_tree->prefix_usage)); + memset(&lpm_tree->prefix_ref_count, 0, + sizeof(lpm_tree->prefix_ref_count)); +- lpm_tree->ref_count = 1; ++ refcount_set(&lpm_tree->ref_count, 1); + return lpm_tree; + + err_left_struct_set: +@@ -678,7 +678,7 @@ mlxsw_sp_lpm_tree_get(struct mlxsw_sp *mlxsw_sp, + + for (i = 0; i < mlxsw_sp->router->lpm.tree_count; i++) { + lpm_tree = &mlxsw_sp->router->lpm.trees[i]; +- if (lpm_tree->ref_count != 0 && ++ if (refcount_read(&lpm_tree->ref_count) && + lpm_tree->proto == proto && + mlxsw_sp_prefix_usage_eq(&lpm_tree->prefix_usage, + prefix_usage)) { +@@ -691,14 +691,15 @@ mlxsw_sp_lpm_tree_get(struct mlxsw_sp *mlxsw_sp, + + static void mlxsw_sp_lpm_tree_hold(struct mlxsw_sp_lpm_tree *lpm_tree) + { +- lpm_tree->ref_count++; ++ refcount_inc(&lpm_tree->ref_count); + } + + static void mlxsw_sp_lpm_tree_put(struct mlxsw_sp *mlxsw_sp, + struct mlxsw_sp_lpm_tree *lpm_tree) + { +- if (--lpm_tree->ref_count == 0) +- mlxsw_sp_lpm_tree_destroy(mlxsw_sp, lpm_tree); ++ if (!refcount_dec_and_test(&lpm_tree->ref_count)) ++ return; ++ mlxsw_sp_lpm_tree_destroy(mlxsw_sp, lpm_tree); + } + + #define MLXSW_SP_LPM_TREE_MIN 1 /* tree 0 is reserved */ +diff --git a/drivers/net/ethernet/mellanox/mlxsw/spectrum_switchdev.c b/drivers/net/ethernet/mellanox/mlxsw/spectrum_switchdev.c +index 6c749c148148d..6397ff0dc951c 100644 +--- a/drivers/net/ethernet/mellanox/mlxsw/spectrum_switchdev.c ++++ b/drivers/net/ethernet/mellanox/mlxsw/spectrum_switchdev.c +@@ -61,7 +61,7 @@ struct mlxsw_sp_bridge_port { + struct mlxsw_sp_bridge_device *bridge_device; + struct list_head list; + struct list_head vlans_list; +- unsigned int ref_count; ++ refcount_t ref_count; + u8 stp_state; + unsigned long flags; + bool mrouter; +@@ -495,7 +495,7 @@ mlxsw_sp_bridge_port_create(struct mlxsw_sp_bridge_device *bridge_device, + BR_MCAST_FLOOD; + INIT_LIST_HEAD(&bridge_port->vlans_list); + list_add(&bridge_port->list, &bridge_device->ports_list); +- bridge_port->ref_count = 1; ++ refcount_set(&bridge_port->ref_count, 1); + + err = switchdev_bridge_port_offload(brport_dev, mlxsw_sp_port->dev, + NULL, NULL, NULL, false, extack); +@@ -531,7 +531,7 @@ mlxsw_sp_bridge_port_get(struct mlxsw_sp_bridge *bridge, + + bridge_port = mlxsw_sp_bridge_port_find(bridge, brport_dev); + if (bridge_port) { +- bridge_port->ref_count++; ++ refcount_inc(&bridge_port->ref_count); + return bridge_port; + } + +@@ -558,7 +558,7 @@ static void mlxsw_sp_bridge_port_put(struct mlxsw_sp_bridge *bridge, + { + struct mlxsw_sp_bridge_device *bridge_device; + +- if (--bridge_port->ref_count != 0) ++ if (!refcount_dec_and_test(&bridge_port->ref_count)) + return; + bridge_device = bridge_port->bridge_device; + mlxsw_sp_bridge_port_destroy(bridge_port); +-- +2.43.0 + diff --git a/queue-6.6/net-bcmasp-fix-memory-leak-when-bringing-down-interf.patch b/queue-6.6/net-bcmasp-fix-memory-leak-when-bringing-down-interf.patch new file mode 100644 index 0000000000..7e0d0630fe --- /dev/null +++ b/queue-6.6/net-bcmasp-fix-memory-leak-when-bringing-down-interf.patch @@ -0,0 +1,83 @@ +From 11d52c780b49a536c9841d8b17cede1b1904396e Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 11:05:41 -0700 +Subject: net: bcmasp: fix memory leak when bringing down interface + +From: Justin Chen <justin.chen@broadcom.com> + +[ Upstream commit 9f898fc2c31fbf0ac5ecd289f528a716464cb005 ] + +When bringing down the TX rings we flush the rings but forget to +reclaimed the flushed packets. This leads to a memory leak since we +do not free the dma mapped buffers. This also leads to tx control +block corruption when bringing down the interface for power +management. + +Fixes: 490cb412007d ("net: bcmasp: Add support for ASP2.0 Ethernet controller") +Signed-off-by: Justin Chen <justin.chen@broadcom.com> +Acked-by: Florian Fainelli <florian.fainelli@broadcom.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/20240418180541.2271719-1-justin.chen@broadcom.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + .../net/ethernet/broadcom/asp2/bcmasp_intf.c | 21 ++++++++++++------- + 1 file changed, 14 insertions(+), 7 deletions(-) + +diff --git a/drivers/net/ethernet/broadcom/asp2/bcmasp_intf.c b/drivers/net/ethernet/broadcom/asp2/bcmasp_intf.c +index b3d04f49f77e9..6bf149d645941 100644 +--- a/drivers/net/ethernet/broadcom/asp2/bcmasp_intf.c ++++ b/drivers/net/ethernet/broadcom/asp2/bcmasp_intf.c +@@ -435,10 +435,8 @@ static void umac_init(struct bcmasp_intf *intf) + umac_wl(intf, 0x800, UMC_RX_MAX_PKT_SZ); + } + +-static int bcmasp_tx_poll(struct napi_struct *napi, int budget) ++static int bcmasp_tx_reclaim(struct bcmasp_intf *intf) + { +- struct bcmasp_intf *intf = +- container_of(napi, struct bcmasp_intf, tx_napi); + struct bcmasp_intf_stats64 *stats = &intf->stats64; + struct device *kdev = &intf->parent->pdev->dev; + unsigned long read, released = 0; +@@ -481,10 +479,16 @@ static int bcmasp_tx_poll(struct napi_struct *napi, int budget) + DESC_RING_COUNT); + } + +- /* Ensure all descriptors have been written to DRAM for the hardware +- * to see updated contents. +- */ +- wmb(); ++ return released; ++} ++ ++static int bcmasp_tx_poll(struct napi_struct *napi, int budget) ++{ ++ struct bcmasp_intf *intf = ++ container_of(napi, struct bcmasp_intf, tx_napi); ++ int released = 0; ++ ++ released = bcmasp_tx_reclaim(intf); + + napi_complete(&intf->tx_napi); + +@@ -794,6 +798,7 @@ static int bcmasp_init_tx(struct bcmasp_intf *intf) + + intf->tx_spb_index = 0; + intf->tx_spb_clean_index = 0; ++ memset(intf->tx_cbs, 0, sizeof(struct bcmasp_tx_cb) * DESC_RING_COUNT); + + netif_napi_add_tx(intf->ndev, &intf->tx_napi, bcmasp_tx_poll); + +@@ -904,6 +909,8 @@ static void bcmasp_netif_deinit(struct net_device *dev) + } while (timeout-- > 0); + tx_spb_dma_wl(intf, 0x0, TX_SPB_DMA_FIFO_CTRL); + ++ bcmasp_tx_reclaim(intf); ++ + umac_enable_set(intf, UMC_CMD_TX_EN, 0); + + phy_stop(dev->phydev); +-- +2.43.0 + diff --git a/queue-6.6/net-dsa-mv88e6xx-fix-supported_interfaces-setup-in-m.patch b/queue-6.6/net-dsa-mv88e6xx-fix-supported_interfaces-setup-in-m.patch new file mode 100644 index 0000000000..388988df0a --- /dev/null +++ b/queue-6.6/net-dsa-mv88e6xx-fix-supported_interfaces-setup-in-m.patch @@ -0,0 +1,138 @@ +From d307cd7dd616208117015403905053a518fb8df1 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 17 Apr 2024 12:37:37 +0200 +Subject: net: dsa: mv88e6xx: fix supported_interfaces setup in + mv88e6250_phylink_get_caps() + +From: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> + +[ Upstream commit a4e3899065ffa87d49dc20e8c17501edbc189692 ] + +With the recent PHYLINK changes requiring supported_interfaces to be set, +MV88E6250 family switches like the 88E6020 fail to probe - cmode is +never initialized on these devices, so mv88e6250_phylink_get_caps() does +not set any supported_interfaces flags. + +Instead of a cmode, on 88E6250 we have a read-only port mode value that +encodes similar information. There is no reason to bother mapping port +mode to the cmodes of other switch models; instead we introduce a +mv88e6250_setup_supported_interfaces() that is called directly from +mv88e6250_phylink_get_caps(). + +Fixes: de5c9bf40c45 ("net: phylink: require supported_interfaces to be filled") +Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> +Link: https://lore.kernel.org/r/20240417103737.166651-1-matthias.schiffer@ew.tq-group.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/dsa/mv88e6xxx/chip.c | 56 +++++++++++++++++++++++++++++--- + drivers/net/dsa/mv88e6xxx/port.h | 23 ++++++++++--- + 2 files changed, 71 insertions(+), 8 deletions(-) + +diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c +index b8fde22aebf93..8556502f06721 100644 +--- a/drivers/net/dsa/mv88e6xxx/chip.c ++++ b/drivers/net/dsa/mv88e6xxx/chip.c +@@ -566,13 +566,61 @@ static void mv88e6xxx_translate_cmode(u8 cmode, unsigned long *supported) + phy_interface_set_rgmii(supported); + } + +-static void mv88e6250_phylink_get_caps(struct mv88e6xxx_chip *chip, int port, +- struct phylink_config *config) ++static void ++mv88e6250_setup_supported_interfaces(struct mv88e6xxx_chip *chip, int port, ++ struct phylink_config *config) + { + unsigned long *supported = config->supported_interfaces; ++ int err; ++ u16 reg; + +- /* Translate the default cmode */ +- mv88e6xxx_translate_cmode(chip->ports[port].cmode, supported); ++ err = mv88e6xxx_port_read(chip, port, MV88E6XXX_PORT_STS, ®); ++ if (err) { ++ dev_err(chip->dev, "p%d: failed to read port status\n", port); ++ return; ++ } ++ ++ switch (reg & MV88E6250_PORT_STS_PORTMODE_MASK) { ++ case MV88E6250_PORT_STS_PORTMODE_MII_10_HALF_PHY: ++ case MV88E6250_PORT_STS_PORTMODE_MII_100_HALF_PHY: ++ case MV88E6250_PORT_STS_PORTMODE_MII_10_FULL_PHY: ++ case MV88E6250_PORT_STS_PORTMODE_MII_100_FULL_PHY: ++ __set_bit(PHY_INTERFACE_MODE_REVMII, supported); ++ break; ++ ++ case MV88E6250_PORT_STS_PORTMODE_MII_HALF: ++ case MV88E6250_PORT_STS_PORTMODE_MII_FULL: ++ __set_bit(PHY_INTERFACE_MODE_MII, supported); ++ break; ++ ++ case MV88E6250_PORT_STS_PORTMODE_MII_DUAL_100_RMII_FULL_PHY: ++ case MV88E6250_PORT_STS_PORTMODE_MII_200_RMII_FULL_PHY: ++ case MV88E6250_PORT_STS_PORTMODE_MII_10_100_RMII_HALF_PHY: ++ case MV88E6250_PORT_STS_PORTMODE_MII_10_100_RMII_FULL_PHY: ++ __set_bit(PHY_INTERFACE_MODE_REVRMII, supported); ++ break; ++ ++ case MV88E6250_PORT_STS_PORTMODE_MII_DUAL_100_RMII_FULL: ++ case MV88E6250_PORT_STS_PORTMODE_MII_10_100_RMII_FULL: ++ __set_bit(PHY_INTERFACE_MODE_RMII, supported); ++ break; ++ ++ case MV88E6250_PORT_STS_PORTMODE_MII_100_RGMII: ++ __set_bit(PHY_INTERFACE_MODE_RGMII, supported); ++ break; ++ ++ default: ++ dev_err(chip->dev, ++ "p%d: invalid port mode in status register: %04x\n", ++ port, reg); ++ } ++} ++ ++static void mv88e6250_phylink_get_caps(struct mv88e6xxx_chip *chip, int port, ++ struct phylink_config *config) ++{ ++ if (!mv88e6xxx_phy_is_internal(chip, port)) ++ mv88e6250_setup_supported_interfaces(chip, port, config); + + config->mac_capabilities = MAC_SYM_PAUSE | MAC_10 | MAC_100; + } +diff --git a/drivers/net/dsa/mv88e6xxx/port.h b/drivers/net/dsa/mv88e6xxx/port.h +index 86deeb347cbc1..ddadeb9bfdaee 100644 +--- a/drivers/net/dsa/mv88e6xxx/port.h ++++ b/drivers/net/dsa/mv88e6xxx/port.h +@@ -25,10 +25,25 @@ + #define MV88E6250_PORT_STS_PORTMODE_PHY_100_HALF 0x0900 + #define MV88E6250_PORT_STS_PORTMODE_PHY_10_FULL 0x0a00 + #define MV88E6250_PORT_STS_PORTMODE_PHY_100_FULL 0x0b00 +-#define MV88E6250_PORT_STS_PORTMODE_MII_10_HALF 0x0c00 +-#define MV88E6250_PORT_STS_PORTMODE_MII_100_HALF 0x0d00 +-#define MV88E6250_PORT_STS_PORTMODE_MII_10_FULL 0x0e00 +-#define MV88E6250_PORT_STS_PORTMODE_MII_100_FULL 0x0f00 ++/* - Modes with PHY suffix use output instead of input clock ++ * - Modes without RMII or RGMII use MII ++ * - Modes without speed do not have a fixed speed specified in the manual ++ * ("DC to x MHz" - variable clock support?) ++ */ ++#define MV88E6250_PORT_STS_PORTMODE_MII_DISABLED 0x0000 ++#define MV88E6250_PORT_STS_PORTMODE_MII_100_RGMII 0x0100 ++#define MV88E6250_PORT_STS_PORTMODE_MII_DUAL_100_RMII_FULL_PHY 0x0200 ++#define MV88E6250_PORT_STS_PORTMODE_MII_200_RMII_FULL_PHY 0x0400 ++#define MV88E6250_PORT_STS_PORTMODE_MII_DUAL_100_RMII_FULL 0x0600 ++#define MV88E6250_PORT_STS_PORTMODE_MII_10_100_RMII_FULL 0x0700 ++#define MV88E6250_PORT_STS_PORTMODE_MII_HALF 0x0800 ++#define MV88E6250_PORT_STS_PORTMODE_MII_10_100_RMII_HALF_PHY 0x0900 ++#define MV88E6250_PORT_STS_PORTMODE_MII_FULL 0x0a00 ++#define MV88E6250_PORT_STS_PORTMODE_MII_10_100_RMII_FULL_PHY 0x0b00 ++#define MV88E6250_PORT_STS_PORTMODE_MII_10_HALF_PHY 0x0c00 ++#define MV88E6250_PORT_STS_PORTMODE_MII_100_HALF_PHY 0x0d00 ++#define MV88E6250_PORT_STS_PORTMODE_MII_10_FULL_PHY 0x0e00 ++#define MV88E6250_PORT_STS_PORTMODE_MII_100_FULL_PHY 0x0f00 + #define MV88E6XXX_PORT_STS_LINK 0x0800 + #define MV88E6XXX_PORT_STS_DUPLEX 0x0400 + #define MV88E6XXX_PORT_STS_SPEED_MASK 0x0300 +-- +2.43.0 + diff --git a/queue-6.6/net-ethernet-ti-am65-cpts-fix-ptpv1-message-type-on-.patch b/queue-6.6/net-ethernet-ti-am65-cpts-fix-ptpv1-message-type-on-.patch new file mode 100644 index 0000000000..b4d1062f10 --- /dev/null +++ b/queue-6.6/net-ethernet-ti-am65-cpts-fix-ptpv1-message-type-on-.patch @@ -0,0 +1,58 @@ +From f3c95af1e7f1b6f52b3036457781f27776b50949 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 12:46:26 +0530 +Subject: net: ethernet: ti: am65-cpts: Fix PTPv1 message type on TX packets + +From: Jason Reeder <jreeder@ti.com> + +[ Upstream commit 1b9e743e923b256e353a9a644195372285e5a6c0 ] + +The CPTS, by design, captures the messageType (Sync, Delay_Req, etc.) +field from the second nibble of the PTP header which is defined in the +PTPv2 (1588-2008) specification. In the PTPv1 (1588-2002) specification +the first two bytes of the PTP header are defined as the versionType +which is always 0x0001. This means that any PTPv1 packets that are +tagged for TX timestamping by the CPTS will have their messageType set +to 0x0 which corresponds to a Sync message type. This causes issues +when a PTPv1 stack is expecting a Delay_Req (messageType: 0x1) +timestamp that never appears. + +Fix this by checking if the ptp_class of the timestamped TX packet is +PTP_CLASS_V1 and then matching the PTP sequence ID to the stored +sequence ID in the skb->cb data structure. If the sequence IDs match +and the packet is of type PTPv1 then there is a chance that the +messageType has been incorrectly stored by the CPTS so overwrite the +messageType stored by the CPTS with the messageType from the skb->cb +data structure. This allows the PTPv1 stack to receive TX timestamps +for Delay_Req packets which are necessary to lock onto a PTP Leader. + +Signed-off-by: Jason Reeder <jreeder@ti.com> +Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com> +Tested-by: Ed Trexel <ed.trexel@hp.com> +Fixes: f6bd59526ca5 ("net: ethernet: ti: introduce am654 common platform time sync driver") +Link: https://lore.kernel.org/r/20240424071626.32558-1-r-gunasekaran@ti.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/ti/am65-cpts.c | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/drivers/net/ethernet/ti/am65-cpts.c b/drivers/net/ethernet/ti/am65-cpts.c +index c66618d91c28f..f89716b1cfb64 100644 +--- a/drivers/net/ethernet/ti/am65-cpts.c ++++ b/drivers/net/ethernet/ti/am65-cpts.c +@@ -784,6 +784,11 @@ static bool am65_cpts_match_tx_ts(struct am65_cpts *cpts, + struct am65_cpts_skb_cb_data *skb_cb = + (struct am65_cpts_skb_cb_data *)skb->cb; + ++ if ((ptp_classify_raw(skb) & PTP_CLASS_V1) && ++ ((mtype_seqid & AM65_CPTS_EVENT_1_SEQUENCE_ID_MASK) == ++ (skb_cb->skb_mtype_seqid & AM65_CPTS_EVENT_1_SEQUENCE_ID_MASK))) ++ mtype_seqid = skb_cb->skb_mtype_seqid; ++ + if (mtype_seqid == skb_cb->skb_mtype_seqid) { + u64 ns = event->timestamp; + +-- +2.43.0 + diff --git a/queue-6.6/net-fix-sk_memory_allocated_-add-sub-vs-softirqs.patch b/queue-6.6/net-fix-sk_memory_allocated_-add-sub-vs-softirqs.patch new file mode 100644 index 0000000000..1b4b071090 --- /dev/null +++ b/queue-6.6/net-fix-sk_memory_allocated_-add-sub-vs-softirqs.patch @@ -0,0 +1,102 @@ +From a8ca60debb0f2ef1726c2a61120ac7f458e75221 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 21 Apr 2024 17:52:48 +0000 +Subject: net: fix sk_memory_allocated_{add|sub} vs softirqs + +From: Eric Dumazet <edumazet@google.com> + +[ Upstream commit 3584718cf2ec7e79b6814f2596dcf398c5fb2eca ] + +Jonathan Heathcote reported a regression caused by blamed commit +on aarch64 architecture. + +x86 happens to have irq-safe __this_cpu_add_return() +and __this_cpu_sub(), but this is not generic. + +I think my confusion came from "struct sock" argument, +because these helpers are called with a locked socket. +But the memory accounting is per-proto (and per-cpu after +the blamed commit). We might cleanup these helpers later +to directly accept a "struct proto *proto" argument. + +Switch to this_cpu_add_return() and this_cpu_xchg() +operations, and get rid of preempt_disable()/preempt_enable() pairs. + +Fast path becomes a bit faster as a result :) + +Many thanks to Jonathan Heathcote for his awesome report and +investigations. + +Fixes: 3cd3399dd7a8 ("net: implement per-cpu reserves for memory_allocated") +Reported-by: Jonathan Heathcote <jonathan.heathcote@bbc.co.uk> +Closes: https://lore.kernel.org/netdev/VI1PR01MB42407D7947B2EA448F1E04EFD10D2@VI1PR01MB4240.eurprd01.prod.exchangelabs.com/ +Signed-off-by: Eric Dumazet <edumazet@google.com> +Acked-by: Soheil Hassas Yeganeh <soheil@google.com> +Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev> +Link: https://lore.kernel.org/r/20240421175248.1692552-1-edumazet@google.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + include/net/sock.h | 38 ++++++++++++++++++++------------------ + 1 file changed, 20 insertions(+), 18 deletions(-) + +diff --git a/include/net/sock.h b/include/net/sock.h +index 4372a7225ae6a..53b81e0a89810 100644 +--- a/include/net/sock.h ++++ b/include/net/sock.h +@@ -1460,32 +1460,34 @@ sk_memory_allocated(const struct sock *sk) + #define SK_MEMORY_PCPU_RESERVE (1 << (20 - PAGE_SHIFT)) + extern int sysctl_mem_pcpu_rsv; + ++static inline void proto_memory_pcpu_drain(struct proto *proto) ++{ ++ int val = this_cpu_xchg(*proto->per_cpu_fw_alloc, 0); ++ ++ if (val) ++ atomic_long_add(val, proto->memory_allocated); ++} ++ + static inline void +-sk_memory_allocated_add(struct sock *sk, int amt) ++sk_memory_allocated_add(const struct sock *sk, int val) + { +- int local_reserve; ++ struct proto *proto = sk->sk_prot; + +- preempt_disable(); +- local_reserve = __this_cpu_add_return(*sk->sk_prot->per_cpu_fw_alloc, amt); +- if (local_reserve >= READ_ONCE(sysctl_mem_pcpu_rsv)) { +- __this_cpu_sub(*sk->sk_prot->per_cpu_fw_alloc, local_reserve); +- atomic_long_add(local_reserve, sk->sk_prot->memory_allocated); +- } +- preempt_enable(); ++ val = this_cpu_add_return(*proto->per_cpu_fw_alloc, val); ++ ++ if (unlikely(val >= READ_ONCE(sysctl_mem_pcpu_rsv))) ++ proto_memory_pcpu_drain(proto); + } + + static inline void +-sk_memory_allocated_sub(struct sock *sk, int amt) ++sk_memory_allocated_sub(const struct sock *sk, int val) + { +- int local_reserve; ++ struct proto *proto = sk->sk_prot; + +- preempt_disable(); +- local_reserve = __this_cpu_sub_return(*sk->sk_prot->per_cpu_fw_alloc, amt); +- if (local_reserve <= -READ_ONCE(sysctl_mem_pcpu_rsv)) { +- __this_cpu_sub(*sk->sk_prot->per_cpu_fw_alloc, local_reserve); +- atomic_long_add(local_reserve, sk->sk_prot->memory_allocated); +- } +- preempt_enable(); ++ val = this_cpu_sub_return(*proto->per_cpu_fw_alloc, val); ++ ++ if (unlikely(val <= -READ_ONCE(sysctl_mem_pcpu_rsv))) ++ proto_memory_pcpu_drain(proto); + } + + #define SK_ALLOC_PERCPU_COUNTER_BATCH 16 +-- +2.43.0 + diff --git a/queue-6.6/net-gtp-fix-use-after-free-in-gtp_dellink.patch b/queue-6.6/net-gtp-fix-use-after-free-in-gtp_dellink.patch new file mode 100644 index 0000000000..c467cc5f60 --- /dev/null +++ b/queue-6.6/net-gtp-fix-use-after-free-in-gtp_dellink.patch @@ -0,0 +1,46 @@ +From 2b2b34fd1725427b2385211762b23e9eb5e20bbe Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 05:39:30 -0400 +Subject: net: gtp: Fix Use-After-Free in gtp_dellink + +From: Hyunwoo Kim <v4bel@theori.io> + +[ Upstream commit f2a904107ee2b647bb7794a1a82b67740d7c8a64 ] + +Since call_rcu, which is called in the hlist_for_each_entry_rcu traversal +of gtp_dellink, is not part of the RCU read critical section, it +is possible that the RCU grace period will pass during the traversal and +the key will be free. + +To prevent this, it should be changed to hlist_for_each_entry_safe. + +Fixes: 94dc550a5062 ("gtp: fix an use-after-free in ipv4_pdp_find()") +Signed-off-by: Hyunwoo Kim <v4bel@theori.io> +Reviewed-by: Eric Dumazet <edumazet@google.com> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/gtp.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/drivers/net/gtp.c b/drivers/net/gtp.c +index 2b5357d94ff56..63f932256c9f5 100644 +--- a/drivers/net/gtp.c ++++ b/drivers/net/gtp.c +@@ -1111,11 +1111,12 @@ static int gtp_newlink(struct net *src_net, struct net_device *dev, + static void gtp_dellink(struct net_device *dev, struct list_head *head) + { + struct gtp_dev *gtp = netdev_priv(dev); ++ struct hlist_node *next; + struct pdp_ctx *pctx; + int i; + + for (i = 0; i < gtp->hash_size; i++) +- hlist_for_each_entry_rcu(pctx, >p->tid_hash[i], hlist_tid) ++ hlist_for_each_entry_safe(pctx, next, >p->tid_hash[i], hlist_tid) + pdp_context_delete(pctx); + + list_del_rcu(>p->list); +-- +2.43.0 + diff --git a/queue-6.6/net-libwx-fix-alloc-msix-vectors-failed.patch b/queue-6.6/net-libwx-fix-alloc-msix-vectors-failed.patch new file mode 100644 index 0000000000..790ec995fe --- /dev/null +++ b/queue-6.6/net-libwx-fix-alloc-msix-vectors-failed.patch @@ -0,0 +1,43 @@ +From 8d0b92827ffaa1a7debdb7dd02ee838cb667d4b0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 10:15:56 +0800 +Subject: net: libwx: fix alloc msix vectors failed + +From: Duanqiang Wen <duanqiangwen@net-swift.com> + +[ Upstream commit 69197dfc64007b5292cc960581548f41ccd44828 ] + +driver needs queue msix vectors and one misc irq vector, +but only queue vectors need irq affinity. +when num_online_cpus is less than chip max msix vectors, +driver will acquire (num_online_cpus + 1) vecotrs, and +call pci_alloc_irq_vectors_affinity functions with affinity +params without setting pre_vectors or post_vectors, it will +cause return error code -ENOSPC. +Misc irq vector is vector 0, driver need to set affinity params +.pre_vectors = 1. + +Fixes: 3f703186113f ("net: libwx: Add irq flow functions") +Signed-off-by: Duanqiang Wen <duanqiangwen@net-swift.com> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/wangxun/libwx/wx_lib.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/wangxun/libwx/wx_lib.c b/drivers/net/ethernet/wangxun/libwx/wx_lib.c +index e078f4071dc23..be434c833c69c 100644 +--- a/drivers/net/ethernet/wangxun/libwx/wx_lib.c ++++ b/drivers/net/ethernet/wangxun/libwx/wx_lib.c +@@ -1585,7 +1585,7 @@ static void wx_set_num_queues(struct wx *wx) + */ + static int wx_acquire_msix_vectors(struct wx *wx) + { +- struct irq_affinity affd = {0, }; ++ struct irq_affinity affd = { .pre_vectors = 1 }; + int nvecs, i; + + nvecs = min_t(int, num_online_cpus(), wx->mac.max_msix_vectors); +-- +2.43.0 + diff --git a/queue-6.6/net-make-sk_memory_pcpu_reserv-tunable.patch b/queue-6.6/net-make-sk_memory_pcpu_reserv-tunable.patch new file mode 100644 index 0000000000..311a416dff --- /dev/null +++ b/queue-6.6/net-make-sk_memory_pcpu_reserv-tunable.patch @@ -0,0 +1,126 @@ +From aee57f42066c1cb7e2f171f1c0ceff11adeb7cfe Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 26 Feb 2024 02:24:52 +0000 +Subject: net: make SK_MEMORY_PCPU_RESERV tunable + +From: Adam Li <adamli@os.amperecomputing.com> + +[ Upstream commit 12a686c2e761f1f1f6e6e2117a9ab9c6de2ac8a7 ] + +This patch adds /proc/sys/net/core/mem_pcpu_rsv sysctl file, +to make SK_MEMORY_PCPU_RESERV tunable. + +Commit 3cd3399dd7a8 ("net: implement per-cpu reserves for +memory_allocated") introduced per-cpu forward alloc cache: + +"Implement a per-cpu cache of +1/-1 MB, to reduce number +of changes to sk->sk_prot->memory_allocated, which +would otherwise be cause of false sharing." + +sk_prot->memory_allocated points to global atomic variable: +atomic_long_t tcp_memory_allocated ____cacheline_aligned_in_smp; + +If increasing the per-cpu cache size from 1MB to e.g. 16MB, +changes to sk->sk_prot->memory_allocated can be further reduced. +Performance may be improved on system with many cores. + +Signed-off-by: Adam Li <adamli@os.amperecomputing.com> +Reviewed-by: Christoph Lameter (Ampere) <cl@linux.com> +Signed-off-by: David S. Miller <davem@davemloft.net> +Stable-dep-of: 3584718cf2ec ("net: fix sk_memory_allocated_{add|sub} vs softirqs") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + Documentation/admin-guide/sysctl/net.rst | 5 +++++ + include/net/sock.h | 5 +++-- + net/core/sock.c | 1 + + net/core/sysctl_net_core.c | 9 +++++++++ + 4 files changed, 18 insertions(+), 2 deletions(-) + +diff --git a/Documentation/admin-guide/sysctl/net.rst b/Documentation/admin-guide/sysctl/net.rst +index 4877563241f3b..5f1748f33d9a2 100644 +--- a/Documentation/admin-guide/sysctl/net.rst ++++ b/Documentation/admin-guide/sysctl/net.rst +@@ -205,6 +205,11 @@ Will increase power usage. + + Default: 0 (off) + ++mem_pcpu_rsv ++------------ ++ ++Per-cpu reserved forward alloc cache size in page units. Default 1MB per CPU. ++ + rmem_default + ------------ + +diff --git a/include/net/sock.h b/include/net/sock.h +index 25780942ec8bf..4372a7225ae6a 100644 +--- a/include/net/sock.h ++++ b/include/net/sock.h +@@ -1458,6 +1458,7 @@ sk_memory_allocated(const struct sock *sk) + + /* 1 MB per cpu, in page units */ + #define SK_MEMORY_PCPU_RESERVE (1 << (20 - PAGE_SHIFT)) ++extern int sysctl_mem_pcpu_rsv; + + static inline void + sk_memory_allocated_add(struct sock *sk, int amt) +@@ -1466,7 +1467,7 @@ sk_memory_allocated_add(struct sock *sk, int amt) + + preempt_disable(); + local_reserve = __this_cpu_add_return(*sk->sk_prot->per_cpu_fw_alloc, amt); +- if (local_reserve >= SK_MEMORY_PCPU_RESERVE) { ++ if (local_reserve >= READ_ONCE(sysctl_mem_pcpu_rsv)) { + __this_cpu_sub(*sk->sk_prot->per_cpu_fw_alloc, local_reserve); + atomic_long_add(local_reserve, sk->sk_prot->memory_allocated); + } +@@ -1480,7 +1481,7 @@ sk_memory_allocated_sub(struct sock *sk, int amt) + + preempt_disable(); + local_reserve = __this_cpu_sub_return(*sk->sk_prot->per_cpu_fw_alloc, amt); +- if (local_reserve <= -SK_MEMORY_PCPU_RESERVE) { ++ if (local_reserve <= -READ_ONCE(sysctl_mem_pcpu_rsv)) { + __this_cpu_sub(*sk->sk_prot->per_cpu_fw_alloc, local_reserve); + atomic_long_add(local_reserve, sk->sk_prot->memory_allocated); + } +diff --git a/net/core/sock.c b/net/core/sock.c +index 383e30fe79f41..1471c0a862b36 100644 +--- a/net/core/sock.c ++++ b/net/core/sock.c +@@ -283,6 +283,7 @@ __u32 sysctl_rmem_max __read_mostly = SK_RMEM_MAX; + EXPORT_SYMBOL(sysctl_rmem_max); + __u32 sysctl_wmem_default __read_mostly = SK_WMEM_MAX; + __u32 sysctl_rmem_default __read_mostly = SK_RMEM_MAX; ++int sysctl_mem_pcpu_rsv __read_mostly = SK_MEMORY_PCPU_RESERVE; + + /* Maximal space eaten by iovec or ancillary data plus some space */ + int sysctl_optmem_max __read_mostly = sizeof(unsigned long)*(2*UIO_MAXIOV+512); +diff --git a/net/core/sysctl_net_core.c b/net/core/sysctl_net_core.c +index 03f1edb948d7d..373b5b2231c49 100644 +--- a/net/core/sysctl_net_core.c ++++ b/net/core/sysctl_net_core.c +@@ -30,6 +30,7 @@ static int int_3600 = 3600; + static int min_sndbuf = SOCK_MIN_SNDBUF; + static int min_rcvbuf = SOCK_MIN_RCVBUF; + static int max_skb_frags = MAX_SKB_FRAGS; ++static int min_mem_pcpu_rsv = SK_MEMORY_PCPU_RESERVE; + + static int net_msg_warn; /* Unused, but still a sysctl */ + +@@ -407,6 +408,14 @@ static struct ctl_table net_core_table[] = { + .proc_handler = proc_dointvec_minmax, + .extra1 = &min_rcvbuf, + }, ++ { ++ .procname = "mem_pcpu_rsv", ++ .data = &sysctl_mem_pcpu_rsv, ++ .maxlen = sizeof(int), ++ .mode = 0644, ++ .proc_handler = proc_dointvec_minmax, ++ .extra1 = &min_mem_pcpu_rsv, ++ }, + { + .procname = "dev_weight", + .data = &weight_p, +-- +2.43.0 + diff --git a/queue-6.6/net-openvswitch-fix-use-after-free-in-ovs_ct_exit.patch b/queue-6.6/net-openvswitch-fix-use-after-free-in-ovs_ct_exit.patch new file mode 100644 index 0000000000..1d456592ce --- /dev/null +++ b/queue-6.6/net-openvswitch-fix-use-after-free-in-ovs_ct_exit.patch @@ -0,0 +1,46 @@ +From b5689222983ca515c7169942aee325ae38a7e12c Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 22 Apr 2024 05:37:17 -0400 +Subject: net: openvswitch: Fix Use-After-Free in ovs_ct_exit + +From: Hyunwoo Kim <v4bel@theori.io> + +[ Upstream commit 5ea7b72d4fac2fdbc0425cd8f2ea33abe95235b2 ] + +Since kfree_rcu, which is called in the hlist_for_each_entry_rcu traversal +of ovs_ct_limit_exit, is not part of the RCU read critical section, it +is possible that the RCU grace period will pass during the traversal and +the key will be free. + +To prevent this, it should be changed to hlist_for_each_entry_safe. + +Fixes: 11efd5cb04a1 ("openvswitch: Support conntrack zone limit") +Signed-off-by: Hyunwoo Kim <v4bel@theori.io> +Reviewed-by: Eric Dumazet <edumazet@google.com> +Reviewed-by: Aaron Conole <aconole@redhat.com> +Link: https://lore.kernel.org/r/ZiYvzQN/Ry5oeFQW@v4bel-B760M-AORUS-ELITE-AX +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/openvswitch/conntrack.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c +index 74b63cdb59923..2928c142a2ddb 100644 +--- a/net/openvswitch/conntrack.c ++++ b/net/openvswitch/conntrack.c +@@ -1593,9 +1593,9 @@ static void ovs_ct_limit_exit(struct net *net, struct ovs_net *ovs_net) + for (i = 0; i < CT_LIMIT_HASH_BUCKETS; ++i) { + struct hlist_head *head = &info->limits[i]; + struct ovs_ct_limit *ct_limit; ++ struct hlist_node *next; + +- hlist_for_each_entry_rcu(ct_limit, head, hlist_node, +- lockdep_ovsl_is_held()) ++ hlist_for_each_entry_safe(ct_limit, next, head, hlist_node) + kfree_rcu(ct_limit, rcu); + } + kfree(info->limits); +-- +2.43.0 + diff --git a/queue-6.6/net-phy-dp83869-fix-mii-mode-failure.patch b/queue-6.6/net-phy-dp83869-fix-mii-mode-failure.patch new file mode 100644 index 0000000000..8e648faf34 --- /dev/null +++ b/queue-6.6/net-phy-dp83869-fix-mii-mode-failure.patch @@ -0,0 +1,50 @@ +From b631ab019b997d84fa187be157dc81b62457e9c5 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 14:18:28 +0530 +Subject: net: phy: dp83869: Fix MII mode failure + +From: MD Danish Anwar <danishanwar@ti.com> + +[ Upstream commit 6c9cd59dbcb09a2122b5ce0dfc07c74e6fc00dc0 ] + +The DP83869 driver sets the MII bit (needed for PHY to work in MII mode) +only if the op-mode is either DP83869_100M_MEDIA_CONVERT or +DP83869_RGMII_100_BASE. + +Some drivers i.e. ICSSG support MII mode with op-mode as +DP83869_RGMII_COPPER_ETHERNET for which the MII bit is not set in dp83869 +driver. As a result MII mode on ICSSG doesn't work and below log is seen. + +TI DP83869 300b2400.mdio:0f: selected op-mode is not valid with MII mode +icssg-prueth icssg1-eth: couldn't connect to phy ethernet-phy@0 +icssg-prueth icssg1-eth: can't phy connect port MII0 + +Fix this by setting MII bit for DP83869_RGMII_COPPER_ETHERNET op-mode as +well. + +Fixes: 94e86ef1b801 ("net: phy: dp83869: support mii mode when rgmii strap cfg is used") +Signed-off-by: MD Danish Anwar <danishanwar@ti.com> +Reviewed-by: Ravi Gunasekaran <r-gunasekaran@ti.com> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/phy/dp83869.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/drivers/net/phy/dp83869.c b/drivers/net/phy/dp83869.c +index fa8c6fdcf3018..d7aaefb5226b6 100644 +--- a/drivers/net/phy/dp83869.c ++++ b/drivers/net/phy/dp83869.c +@@ -695,7 +695,8 @@ static int dp83869_configure_mode(struct phy_device *phydev, + phy_ctrl_val = dp83869->mode; + if (phydev->interface == PHY_INTERFACE_MODE_MII) { + if (dp83869->mode == DP83869_100M_MEDIA_CONVERT || +- dp83869->mode == DP83869_RGMII_100_BASE) { ++ dp83869->mode == DP83869_RGMII_100_BASE || ++ dp83869->mode == DP83869_RGMII_COPPER_ETHERNET) { + phy_ctrl_val |= DP83869_OP_MODE_MII; + } else { + phydev_err(phydev, "selected op-mode is not valid with MII mode\n"); +-- +2.43.0 + diff --git a/queue-6.6/net-phy-mediatek-ge-soc-follow-netdev-led-trigger-se.patch b/queue-6.6/net-phy-mediatek-ge-soc-follow-netdev-led-trigger-se.patch new file mode 100644 index 0000000000..d7bcab1a95 --- /dev/null +++ b/queue-6.6/net-phy-mediatek-ge-soc-follow-netdev-led-trigger-se.patch @@ -0,0 +1,133 @@ +From a6f5a36cd44e28312428f6884a2cd23ec334a935 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 21 Apr 2024 01:08:31 +0100 +Subject: net: phy: mediatek-ge-soc: follow netdev LED trigger semantics + +From: Daniel Golle <daniel@makrotopia.org> + +[ Upstream commit 5b5f724b05c550e10693a53a81cadca901aefd16 ] + +Only blink if the link is up on a LED which is programmed to also +indicate link-status. + +Otherwise, if both LEDs are in use to indicate different speeds, the +resulting blinking being inverted on LEDs which aren't switched on at +a specific speed is quite counter-intuitive. + +Also make sure that state left behind by reset or the bootloader is +recognized correctly including the half-duplex and full-duplex bits as +well as the (unsupported by Linux netdev trigger semantics) link-down +bit. + +Fixes: c66937b0f8db ("net: phy: mediatek-ge-soc: support PHY LEDs") +Signed-off-by: Daniel Golle <daniel@makrotopia.org> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/phy/mediatek-ge-soc.c | 43 +++++++++++++++++++------------ + 1 file changed, 26 insertions(+), 17 deletions(-) + +diff --git a/drivers/net/phy/mediatek-ge-soc.c b/drivers/net/phy/mediatek-ge-soc.c +index 0f3a1538a8b8e..f4f9412d0cd7e 100644 +--- a/drivers/net/phy/mediatek-ge-soc.c ++++ b/drivers/net/phy/mediatek-ge-soc.c +@@ -216,6 +216,9 @@ + #define MTK_PHY_LED_ON_LINK1000 BIT(0) + #define MTK_PHY_LED_ON_LINK100 BIT(1) + #define MTK_PHY_LED_ON_LINK10 BIT(2) ++#define MTK_PHY_LED_ON_LINK (MTK_PHY_LED_ON_LINK10 |\ ++ MTK_PHY_LED_ON_LINK100 |\ ++ MTK_PHY_LED_ON_LINK1000) + #define MTK_PHY_LED_ON_LINKDOWN BIT(3) + #define MTK_PHY_LED_ON_FDX BIT(4) /* Full duplex */ + #define MTK_PHY_LED_ON_HDX BIT(5) /* Half duplex */ +@@ -231,6 +234,12 @@ + #define MTK_PHY_LED_BLINK_100RX BIT(3) + #define MTK_PHY_LED_BLINK_10TX BIT(4) + #define MTK_PHY_LED_BLINK_10RX BIT(5) ++#define MTK_PHY_LED_BLINK_RX (MTK_PHY_LED_BLINK_10RX |\ ++ MTK_PHY_LED_BLINK_100RX |\ ++ MTK_PHY_LED_BLINK_1000RX) ++#define MTK_PHY_LED_BLINK_TX (MTK_PHY_LED_BLINK_10TX |\ ++ MTK_PHY_LED_BLINK_100TX |\ ++ MTK_PHY_LED_BLINK_1000TX) + #define MTK_PHY_LED_BLINK_COLLISION BIT(6) + #define MTK_PHY_LED_BLINK_RX_CRC_ERR BIT(7) + #define MTK_PHY_LED_BLINK_RX_IDLE_ERR BIT(8) +@@ -1247,11 +1256,9 @@ static int mt798x_phy_led_hw_control_get(struct phy_device *phydev, u8 index, + if (blink < 0) + return -EIO; + +- if ((on & (MTK_PHY_LED_ON_LINK1000 | MTK_PHY_LED_ON_LINK100 | +- MTK_PHY_LED_ON_LINK10)) || +- (blink & (MTK_PHY_LED_BLINK_1000RX | MTK_PHY_LED_BLINK_100RX | +- MTK_PHY_LED_BLINK_10RX | MTK_PHY_LED_BLINK_1000TX | +- MTK_PHY_LED_BLINK_100TX | MTK_PHY_LED_BLINK_10TX))) ++ if ((on & (MTK_PHY_LED_ON_LINK | MTK_PHY_LED_ON_FDX | MTK_PHY_LED_ON_HDX | ++ MTK_PHY_LED_ON_LINKDOWN)) || ++ (blink & (MTK_PHY_LED_BLINK_RX | MTK_PHY_LED_BLINK_TX))) + set_bit(bit_netdev, &priv->led_state); + else + clear_bit(bit_netdev, &priv->led_state); +@@ -1269,7 +1276,7 @@ static int mt798x_phy_led_hw_control_get(struct phy_device *phydev, u8 index, + if (!rules) + return 0; + +- if (on & (MTK_PHY_LED_ON_LINK1000 | MTK_PHY_LED_ON_LINK100 | MTK_PHY_LED_ON_LINK10)) ++ if (on & MTK_PHY_LED_ON_LINK) + *rules |= BIT(TRIGGER_NETDEV_LINK); + + if (on & MTK_PHY_LED_ON_LINK10) +@@ -1287,10 +1294,10 @@ static int mt798x_phy_led_hw_control_get(struct phy_device *phydev, u8 index, + if (on & MTK_PHY_LED_ON_HDX) + *rules |= BIT(TRIGGER_NETDEV_HALF_DUPLEX); + +- if (blink & (MTK_PHY_LED_BLINK_1000RX | MTK_PHY_LED_BLINK_100RX | MTK_PHY_LED_BLINK_10RX)) ++ if (blink & MTK_PHY_LED_BLINK_RX) + *rules |= BIT(TRIGGER_NETDEV_RX); + +- if (blink & (MTK_PHY_LED_BLINK_1000TX | MTK_PHY_LED_BLINK_100TX | MTK_PHY_LED_BLINK_10TX)) ++ if (blink & MTK_PHY_LED_BLINK_TX) + *rules |= BIT(TRIGGER_NETDEV_TX); + + return 0; +@@ -1323,15 +1330,19 @@ static int mt798x_phy_led_hw_control_set(struct phy_device *phydev, u8 index, + on |= MTK_PHY_LED_ON_LINK1000; + + if (rules & BIT(TRIGGER_NETDEV_RX)) { +- blink |= MTK_PHY_LED_BLINK_10RX | +- MTK_PHY_LED_BLINK_100RX | +- MTK_PHY_LED_BLINK_1000RX; ++ blink |= (on & MTK_PHY_LED_ON_LINK) ? ++ (((on & MTK_PHY_LED_ON_LINK10) ? MTK_PHY_LED_BLINK_10RX : 0) | ++ ((on & MTK_PHY_LED_ON_LINK100) ? MTK_PHY_LED_BLINK_100RX : 0) | ++ ((on & MTK_PHY_LED_ON_LINK1000) ? MTK_PHY_LED_BLINK_1000RX : 0)) : ++ MTK_PHY_LED_BLINK_RX; + } + + if (rules & BIT(TRIGGER_NETDEV_TX)) { +- blink |= MTK_PHY_LED_BLINK_10TX | +- MTK_PHY_LED_BLINK_100TX | +- MTK_PHY_LED_BLINK_1000TX; ++ blink |= (on & MTK_PHY_LED_ON_LINK) ? ++ (((on & MTK_PHY_LED_ON_LINK10) ? MTK_PHY_LED_BLINK_10TX : 0) | ++ ((on & MTK_PHY_LED_ON_LINK100) ? MTK_PHY_LED_BLINK_100TX : 0) | ++ ((on & MTK_PHY_LED_ON_LINK1000) ? MTK_PHY_LED_BLINK_1000TX : 0)) : ++ MTK_PHY_LED_BLINK_TX; + } + + if (blink || on) +@@ -1344,9 +1355,7 @@ static int mt798x_phy_led_hw_control_set(struct phy_device *phydev, u8 index, + MTK_PHY_LED0_ON_CTRL, + MTK_PHY_LED_ON_FDX | + MTK_PHY_LED_ON_HDX | +- MTK_PHY_LED_ON_LINK10 | +- MTK_PHY_LED_ON_LINK100 | +- MTK_PHY_LED_ON_LINK1000, ++ MTK_PHY_LED_ON_LINK, + on); + + if (ret) +-- +2.43.0 + diff --git a/queue-6.6/net-ti-icssg-prueth-fix-signedness-bug-in-prueth_ini.patch b/queue-6.6/net-ti-icssg-prueth-fix-signedness-bug-in-prueth_ini.patch new file mode 100644 index 0000000000..eab279f0be --- /dev/null +++ b/queue-6.6/net-ti-icssg-prueth-fix-signedness-bug-in-prueth_ini.patch @@ -0,0 +1,49 @@ +From b14375ce1c4ba32ed38a2b83127298eb0cf88d93 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Tue, 23 Apr 2024 19:15:22 +0300 +Subject: net: ti: icssg-prueth: Fix signedness bug in prueth_init_rx_chns() + +From: Dan Carpenter <dan.carpenter@linaro.org> + +[ Upstream commit 4dcd0e83ea1d1df9b2e0174a6d3e795b3477d64e ] + +The rx_chn->irq[] array is unsigned int but it should be signed for the +error handling to work. Also if k3_udma_glue_rx_get_irq() returns zero +then we should return -ENXIO instead of success. + +Fixes: 128d5874c082 ("net: ti: icssg-prueth: Add ICSSG ethernet driver") +Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org> +Reviewed-by: Roger Quadros <rogerq@kernel.org> +Reviewed-by: MD Danish Anwar <danishanwar@ti.com> +Link: https://lore.kernel.org/r/05282415-e7f4-42f3-99f8-32fde8f30936@moroto.mountain +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/ethernet/ti/icssg/icssg_prueth.c | 8 +++++--- + 1 file changed, 5 insertions(+), 3 deletions(-) + +diff --git a/drivers/net/ethernet/ti/icssg/icssg_prueth.c b/drivers/net/ethernet/ti/icssg/icssg_prueth.c +index c09ecb3da7723..925044c16c6ae 100644 +--- a/drivers/net/ethernet/ti/icssg/icssg_prueth.c ++++ b/drivers/net/ethernet/ti/icssg/icssg_prueth.c +@@ -421,12 +421,14 @@ static int prueth_init_rx_chns(struct prueth_emac *emac, + if (!i) + fdqring_id = k3_udma_glue_rx_flow_get_fdq_id(rx_chn->rx_chn, + i); +- rx_chn->irq[i] = k3_udma_glue_rx_get_irq(rx_chn->rx_chn, i); +- if (rx_chn->irq[i] <= 0) { +- ret = rx_chn->irq[i]; ++ ret = k3_udma_glue_rx_get_irq(rx_chn->rx_chn, i); ++ if (ret <= 0) { ++ if (!ret) ++ ret = -ENXIO; + netdev_err(ndev, "Failed to get rx dma irq"); + goto fail; + } ++ rx_chn->irq[i] = ret; + } + + return 0; +-- +2.43.0 + diff --git a/queue-6.6/net-usb-ax88179_178a-stop-lying-about-skb-truesize.patch b/queue-6.6/net-usb-ax88179_178a-stop-lying-about-skb-truesize.patch new file mode 100644 index 0000000000..0bf27b1cf9 --- /dev/null +++ b/queue-6.6/net-usb-ax88179_178a-stop-lying-about-skb-truesize.patch @@ -0,0 +1,64 @@ +From 0fec125ad89b9ca1a7ac0135c0ae1c6656f6e620 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Sun, 21 Apr 2024 19:38:28 +0000 +Subject: net: usb: ax88179_178a: stop lying about skb->truesize + +From: Eric Dumazet <edumazet@google.com> + +[ Upstream commit 4ce62d5b2f7aecd4900e7d6115588ad7f9acccca ] + +Some usb drivers try to set small skb->truesize and break +core networking stacks. + +In this patch, I removed one of the skb->truesize overide. + +I also replaced one skb_clone() by an allocation of a fresh +and small skb, to get minimally sized skbs, like we did +in commit 1e2c61172342 ("net: cdc_ncm: reduce skb truesize +in rx path") + +Fixes: f8ebb3ac881b ("net: usb: ax88179_178a: Fix packet receiving") +Reported-by: shironeko <shironeko@tesaguri.club> +Closes: https://lore.kernel.org/netdev/c110f41a0d2776b525930f213ca9715c@tesaguri.club/ +Signed-off-by: Eric Dumazet <edumazet@google.com> +Cc: Jose Alonso <joalonsof@gmail.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://lore.kernel.org/r/20240421193828.1966195-1-edumazet@google.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/usb/ax88179_178a.c | 11 +++-------- + 1 file changed, 3 insertions(+), 8 deletions(-) + +diff --git a/drivers/net/usb/ax88179_178a.c b/drivers/net/usb/ax88179_178a.c +index 3078511f76083..21b6c4d94a632 100644 +--- a/drivers/net/usb/ax88179_178a.c ++++ b/drivers/net/usb/ax88179_178a.c +@@ -1456,21 +1456,16 @@ static int ax88179_rx_fixup(struct usbnet *dev, struct sk_buff *skb) + /* Skip IP alignment pseudo header */ + skb_pull(skb, 2); + +- skb->truesize = SKB_TRUESIZE(pkt_len_plus_padd); + ax88179_rx_checksum(skb, pkt_hdr); + return 1; + } + +- ax_skb = skb_clone(skb, GFP_ATOMIC); ++ ax_skb = netdev_alloc_skb_ip_align(dev->net, pkt_len); + if (!ax_skb) + return 0; +- skb_trim(ax_skb, pkt_len); ++ skb_put(ax_skb, pkt_len); ++ memcpy(ax_skb->data, skb->data + 2, pkt_len); + +- /* Skip IP alignment pseudo header */ +- skb_pull(ax_skb, 2); +- +- skb->truesize = pkt_len_plus_padd + +- SKB_DATA_ALIGN(sizeof(struct sk_buff)); + ax88179_rx_checksum(ax_skb, pkt_hdr); + usbnet_skb_return(dev, ax_skb); + +-- +2.43.0 + diff --git a/queue-6.6/netfilter-nf_tables-honor-table-dormant-flag-from-ne.patch b/queue-6.6/netfilter-nf_tables-honor-table-dormant-flag-from-ne.patch new file mode 100644 index 0000000000..5900bce07c --- /dev/null +++ b/queue-6.6/netfilter-nf_tables-honor-table-dormant-flag-from-ne.patch @@ -0,0 +1,73 @@ +From a52b8b1eb61fd5172882d884991e10575837317f Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 20:45:01 +0200 +Subject: netfilter: nf_tables: honor table dormant flag from netdev release + event path + +From: Pablo Neira Ayuso <pablo@netfilter.org> + +[ Upstream commit 8e30abc9ace4f0add4cd761dfdbfaebae5632dd2 ] + +Check for table dormant flag otherwise netdev release event path tries +to unregister an already unregistered hook. + +[524854.857999] ------------[ cut here ]------------ +[524854.858010] WARNING: CPU: 0 PID: 3386599 at net/netfilter/core.c:501 __nf_unregister_net_hook+0x21a/0x260 +[...] +[524854.858848] CPU: 0 PID: 3386599 Comm: kworker/u32:2 Not tainted 6.9.0-rc3+ #365 +[524854.858869] Workqueue: netns cleanup_net +[524854.858886] RIP: 0010:__nf_unregister_net_hook+0x21a/0x260 +[524854.858903] Code: 24 e8 aa 73 83 ff 48 63 43 1c 83 f8 01 0f 85 3d ff ff ff e8 98 d1 f0 ff 48 8b 3c 24 e8 8f 73 83 ff 48 63 43 1c e9 26 ff ff ff <0f> 0b 48 83 c4 18 48 c7 c7 00 68 e9 82 5b 5d 41 5c 41 5d 41 5e 41 +[524854.858914] RSP: 0018:ffff8881e36d79e0 EFLAGS: 00010246 +[524854.858926] RAX: 0000000000000000 RBX: ffff8881339ae790 RCX: ffffffff81ba524a +[524854.858936] RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff8881c8a16438 +[524854.858945] RBP: ffff8881c8a16438 R08: 0000000000000001 R09: ffffed103c6daf34 +[524854.858954] R10: ffff8881e36d79a7 R11: 0000000000000000 R12: 0000000000000005 +[524854.858962] R13: ffff8881c8a16000 R14: 0000000000000000 R15: ffff8881351b5a00 +[524854.858971] FS: 0000000000000000(0000) GS:ffff888390800000(0000) knlGS:0000000000000000 +[524854.858982] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[524854.858991] CR2: 00007fc9be0f16f4 CR3: 00000001437cc004 CR4: 00000000001706f0 +[524854.859000] Call Trace: +[524854.859006] <TASK> +[524854.859013] ? __warn+0x9f/0x1a0 +[524854.859027] ? __nf_unregister_net_hook+0x21a/0x260 +[524854.859044] ? report_bug+0x1b1/0x1e0 +[524854.859060] ? handle_bug+0x3c/0x70 +[524854.859071] ? exc_invalid_op+0x17/0x40 +[524854.859083] ? asm_exc_invalid_op+0x1a/0x20 +[524854.859100] ? __nf_unregister_net_hook+0x6a/0x260 +[524854.859116] ? __nf_unregister_net_hook+0x21a/0x260 +[524854.859135] nf_tables_netdev_event+0x337/0x390 [nf_tables] +[524854.859304] ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables] +[524854.859461] ? packet_notifier+0xb3/0x360 +[524854.859476] ? _raw_spin_unlock_irqrestore+0x11/0x40 +[524854.859489] ? dcbnl_netdevice_event+0x35/0x140 +[524854.859507] ? __pfx_nf_tables_netdev_event+0x10/0x10 [nf_tables] +[524854.859661] notifier_call_chain+0x7d/0x140 +[524854.859677] unregister_netdevice_many_notify+0x5e1/0xae0 + +Fixes: d54725cd11a5 ("netfilter: nf_tables: support for multiple devices per netdev hook") +Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/netfilter/nft_chain_filter.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/net/netfilter/nft_chain_filter.c b/net/netfilter/nft_chain_filter.c +index 274b6f7e6bb57..d170758a1eb5d 100644 +--- a/net/netfilter/nft_chain_filter.c ++++ b/net/netfilter/nft_chain_filter.c +@@ -338,7 +338,9 @@ static void nft_netdev_event(unsigned long event, struct net_device *dev, + return; + + if (n > 1) { +- nf_unregister_net_hook(ctx->net, &found->ops); ++ if (!(ctx->chain->table->flags & NFT_TABLE_F_DORMANT)) ++ nf_unregister_net_hook(ctx->net, &found->ops); ++ + list_del_rcu(&found->list); + kfree_rcu(found, rcu); + return; +-- +2.43.0 + diff --git a/queue-6.6/nfc-trf7970a-disable-all-regulators-on-removal.patch b/queue-6.6/nfc-trf7970a-disable-all-regulators-on-removal.patch new file mode 100644 index 0000000000..4d339fdaab --- /dev/null +++ b/queue-6.6/nfc-trf7970a-disable-all-regulators-on-removal.patch @@ -0,0 +1,145 @@ +From a84de60cba30bd25370c70e267f6626b6abf76cc Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 21:25:38 +0200 +Subject: NFC: trf7970a: disable all regulators on removal + +From: Paul Geurts <paul_geurts@live.nl> + +[ Upstream commit 6bea4f03c6a4e973ef369e15aac88f37981db49e ] + +During module probe, regulator 'vin' and 'vdd-io' are used and enabled, +but the vdd-io regulator overwrites the 'vin' regulator pointer. During +remove, only the vdd-io is disabled, as the vin regulator pointer is not +available anymore. When regulator_put() is called during resource +cleanup a kernel warning is given, as the regulator is still enabled. + +Store the two regulators in separate pointers and disable both the +regulators on module remove. + +Fixes: 49d22c70aaf0 ("NFC: trf7970a: Add device tree option of 1.8 Volt IO voltage") +Signed-off-by: Paul Geurts <paul_geurts@live.nl> +Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> +Link: https://lore.kernel.org/r/DB7PR09MB26847A4EBF88D9EDFEB1DA0F950E2@DB7PR09MB2684.eurprd09.prod.outlook.com +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/nfc/trf7970a.c | 42 +++++++++++++++++++++++------------------- + 1 file changed, 23 insertions(+), 19 deletions(-) + +diff --git a/drivers/nfc/trf7970a.c b/drivers/nfc/trf7970a.c +index 7eb17f46a8153..9e1a34e23af26 100644 +--- a/drivers/nfc/trf7970a.c ++++ b/drivers/nfc/trf7970a.c +@@ -424,7 +424,8 @@ struct trf7970a { + enum trf7970a_state state; + struct device *dev; + struct spi_device *spi; +- struct regulator *regulator; ++ struct regulator *vin_regulator; ++ struct regulator *vddio_regulator; + struct nfc_digital_dev *ddev; + u32 quirks; + bool is_initiator; +@@ -1883,7 +1884,7 @@ static int trf7970a_power_up(struct trf7970a *trf) + if (trf->state != TRF7970A_ST_PWR_OFF) + return 0; + +- ret = regulator_enable(trf->regulator); ++ ret = regulator_enable(trf->vin_regulator); + if (ret) { + dev_err(trf->dev, "%s - Can't enable VIN: %d\n", __func__, ret); + return ret; +@@ -1926,7 +1927,7 @@ static int trf7970a_power_down(struct trf7970a *trf) + if (trf->en2_gpiod && !(trf->quirks & TRF7970A_QUIRK_EN2_MUST_STAY_LOW)) + gpiod_set_value_cansleep(trf->en2_gpiod, 0); + +- ret = regulator_disable(trf->regulator); ++ ret = regulator_disable(trf->vin_regulator); + if (ret) + dev_err(trf->dev, "%s - Can't disable VIN: %d\n", __func__, + ret); +@@ -2065,37 +2066,37 @@ static int trf7970a_probe(struct spi_device *spi) + mutex_init(&trf->lock); + INIT_DELAYED_WORK(&trf->timeout_work, trf7970a_timeout_work_handler); + +- trf->regulator = devm_regulator_get(&spi->dev, "vin"); +- if (IS_ERR(trf->regulator)) { +- ret = PTR_ERR(trf->regulator); ++ trf->vin_regulator = devm_regulator_get(&spi->dev, "vin"); ++ if (IS_ERR(trf->vin_regulator)) { ++ ret = PTR_ERR(trf->vin_regulator); + dev_err(trf->dev, "Can't get VIN regulator: %d\n", ret); + goto err_destroy_lock; + } + +- ret = regulator_enable(trf->regulator); ++ ret = regulator_enable(trf->vin_regulator); + if (ret) { + dev_err(trf->dev, "Can't enable VIN: %d\n", ret); + goto err_destroy_lock; + } + +- uvolts = regulator_get_voltage(trf->regulator); ++ uvolts = regulator_get_voltage(trf->vin_regulator); + if (uvolts > 4000000) + trf->chip_status_ctrl = TRF7970A_CHIP_STATUS_VRS5_3; + +- trf->regulator = devm_regulator_get(&spi->dev, "vdd-io"); +- if (IS_ERR(trf->regulator)) { +- ret = PTR_ERR(trf->regulator); ++ trf->vddio_regulator = devm_regulator_get(&spi->dev, "vdd-io"); ++ if (IS_ERR(trf->vddio_regulator)) { ++ ret = PTR_ERR(trf->vddio_regulator); + dev_err(trf->dev, "Can't get VDD_IO regulator: %d\n", ret); +- goto err_destroy_lock; ++ goto err_disable_vin_regulator; + } + +- ret = regulator_enable(trf->regulator); ++ ret = regulator_enable(trf->vddio_regulator); + if (ret) { + dev_err(trf->dev, "Can't enable VDD_IO: %d\n", ret); +- goto err_destroy_lock; ++ goto err_disable_vin_regulator; + } + +- if (regulator_get_voltage(trf->regulator) == 1800000) { ++ if (regulator_get_voltage(trf->vddio_regulator) == 1800000) { + trf->io_ctrl = TRF7970A_REG_IO_CTRL_IO_LOW; + dev_dbg(trf->dev, "trf7970a config vdd_io to 1.8V\n"); + } +@@ -2108,7 +2109,7 @@ static int trf7970a_probe(struct spi_device *spi) + if (!trf->ddev) { + dev_err(trf->dev, "Can't allocate NFC digital device\n"); + ret = -ENOMEM; +- goto err_disable_regulator; ++ goto err_disable_vddio_regulator; + } + + nfc_digital_set_parent_dev(trf->ddev, trf->dev); +@@ -2137,8 +2138,10 @@ static int trf7970a_probe(struct spi_device *spi) + trf7970a_shutdown(trf); + err_free_ddev: + nfc_digital_free_device(trf->ddev); +-err_disable_regulator: +- regulator_disable(trf->regulator); ++err_disable_vddio_regulator: ++ regulator_disable(trf->vddio_regulator); ++err_disable_vin_regulator: ++ regulator_disable(trf->vin_regulator); + err_destroy_lock: + mutex_destroy(&trf->lock); + return ret; +@@ -2157,7 +2160,8 @@ static void trf7970a_remove(struct spi_device *spi) + nfc_digital_unregister_device(trf->ddev); + nfc_digital_free_device(trf->ddev); + +- regulator_disable(trf->regulator); ++ regulator_disable(trf->vddio_regulator); ++ regulator_disable(trf->vin_regulator); + + mutex_destroy(&trf->lock); + } +-- +2.43.0 + diff --git a/queue-6.6/series b/queue-6.6/series new file mode 100644 index 0000000000..7a1566dbe4 --- /dev/null +++ b/queue-6.6/series @@ -0,0 +1,95 @@ +cifs-fix-reacquisition-of-volume-cookie-on-still-liv.patch +smb-client-fix-rename-2-regression-against-samba.patch +cifs-reinstate-original-behavior-again-for-forceuid-.patch +hid-intel-ish-hid-ipc-fix-dev_err-usage-with-uniniti.patch +hid-logitech-dj-allow-mice-to-use-all-types-of-repor.patch +arm64-dts-rockchip-set-phy-address-of-mt7531-switch-.patch +arm64-dts-rockchip-enable-internal-pull-up-on-q7_usb.patch +arm64-dts-rockchip-fix-alphabetical-ordering-rk3399-.patch +arm64-dts-rockchip-enable-internal-pull-up-on-pcie_w.patch +arm64-dts-rockchip-remove-unsupported-node-from-the-.patch +arm64-dts-mediatek-mt8183-add-power-domains-properit.patch +arm64-dts-mediatek-mt8192-add-missing-gce-client-reg.patch +arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch +arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-15253 +arm64-dts-mediatek-mt8195-add-missing-gce-client-reg.patch-7739 +arm64-dts-mediatek-cherry-add-platform-thermal-confi.patch +arm64-dts-mediatek-cherry-describe-cpu-supplies.patch +arm64-dts-mediatek-mt8192-asurada-update-min-voltage.patch +arm64-dts-mediatek-mt8195-cherry-update-min-voltage-.patch +arm64-dts-mediatek-mt8183-kukui-use-default-min-volt.patch +arm64-dts-mediatek-mt7622-fix-clock-controllers.patch +arm64-dts-mediatek-mt7622-fix-ir-nodename.patch +arm64-dts-mediatek-mt7622-fix-ethernet-controller-co.patch +arm64-dts-mediatek-mt7622-drop-reset-names-from-ther.patch +arm64-dts-mediatek-mt7986-reorder-properties.patch +arm64-dts-mediatek-mt7986-drop-invalid-properties-fr.patch +arm64-dts-mediatek-mt7986-drop-reset-cells-from-ethe.patch +arm64-dts-mediatek-mt7986-reorder-nodes.patch +arm64-dts-mediatek-mt7986-drop-invalid-thermal-block.patch +arm64-dts-mediatek-mt7986-prefix-bpi-r3-cooling-maps.patch +arm64-dts-mediatek-mt2712-fix-validation-errors.patch +arm64-dts-rockchip-regulator-for-sd-needs-to-be-alwa.patch +arm64-dts-qcom-sc8180x-fix-ss_phy_irq-for-secondary-.patch +gpio-tangier-use-correct-type-for-the-irq-chip-data.patch +arc-plat-hsdk-remove-misplaced-interrupt-cells-prope.patch +wifi-mac80211-clean-up-assignments-to-pointer-cache.patch +wifi-mac80211-split-mesh-fast-tx-cache-into-local-pr.patch +wifi-iwlwifi-mvm-remove-old-pasn-station-when-adding.patch +wifi-iwlwifi-mvm-return-uid-from-iwl_mvm_build_scan_.patch +drm-gma500-remove-lid-code.patch +wifi-mac80211_hwsim-init-peer-measurement-result.patch +wifi-mac80211-remove-link-before-ap.patch +wifi-mac80211-fix-unaligned-le16-access.patch +net-libwx-fix-alloc-msix-vectors-failed.patch +vxlan-drop-packets-from-invalid-src-address.patch +net-bcmasp-fix-memory-leak-when-bringing-down-interf.patch +mlxsw-core-unregister-emad-trap-using-forward-action.patch +mlxsw-core_env-fix-driver-initialization-with-old-fi.patch +arm-dts-microchip-at91-sama7g5ek-replace-regulator-s.patch +icmp-prevent-possible-null-dereferences-from-icmp_bu.patch +bridge-br_netlink.c-no-need-to-return-void-function.patch +bnxt_en-refactor-reset-close-code.patch +bnxt_en-fix-the-pci-aer-routines.patch +cxl-core-fix-potential-payload-size-confusion-in-cxl.patch +net-dsa-mv88e6xx-fix-supported_interfaces-setup-in-m.patch +nfc-trf7970a-disable-all-regulators-on-removal.patch +ax25-fix-netdev-refcount-issue.patch +tools-ynl-don-t-ignore-errors-in-nlmsg_done-messages.patch +net-make-sk_memory_pcpu_reserv-tunable.patch +net-fix-sk_memory_allocated_-add-sub-vs-softirqs.patch +ipv4-check-for-null-idev-in-ip_route_use_hint.patch +net-usb-ax88179_178a-stop-lying-about-skb-truesize.patch +net-gtp-fix-use-after-free-in-gtp_dellink.patch +net-phy-mediatek-ge-soc-follow-netdev-led-trigger-se.patch +gpio-tegra186-fix-tegra186_gpio_is_accessible-check.patch +bluetooth-btusb-fix-triggering-coredump-implementati.patch +bluetooth-hci_event-fix-sending-hci_op_read_enc_key_.patch +bluetooth-mgmt-fix-failing-to-mgmt_op_add_uuid-mgmt_.patch +bluetooth-btusb-mediatek-fix-double-free-of-skb-in-c.patch +bluetooth-hci_sync-using-hci_cmd_sync_submit-when-re.patch +bluetooth-qca-set-power_ctrl_enabled-on-null-returne.patch +ipvs-fix-checksumming-on-gso-of-sctp-packets.patch +net-openvswitch-fix-use-after-free-in-ovs_ct_exit.patch +mlxsw-use-refcount_t-for-reference-counting.patch +mlxsw-spectrum_acl_tcam-fix-race-in-region-id-alloca.patch +mlxsw-spectrum_acl_tcam-fix-race-during-rehash-delay.patch +mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch +mlxsw-spectrum_acl_tcam-fix-possible-use-after-free-.patch-19343 +mlxsw-spectrum_acl_tcam-rate-limit-error-message.patch +mlxsw-spectrum_acl_tcam-fix-memory-leak-during-rehas.patch +mlxsw-spectrum_acl_tcam-fix-warning-during-rehash.patch +mlxsw-spectrum_acl_tcam-fix-incorrect-list-api-usage.patch +mlxsw-spectrum_acl_tcam-fix-memory-leak-when-canceli.patch +eth-bnxt-fix-counting-packets-discarded-due-to-oom-a.patch +arm-dts-imx6ull-tarragon-fix-usb-over-current-polari.patch +netfilter-nf_tables-honor-table-dormant-flag-from-ne.patch +net-phy-dp83869-fix-mii-mode-failure.patch +net-ti-icssg-prueth-fix-signedness-bug-in-prueth_ini.patch +i40e-do-not-use-wq_mem_reclaim-flag-for-workqueue.patch +i40e-report-mfs-in-decimal-base-instead-of-hex.patch +iavf-fix-tc-config-comparison-with-existing-adapter-.patch +ice-fix-lag-and-vf-lock-dependency-in-ice_reset_vf.patch +net-ethernet-ti-am65-cpts-fix-ptpv1-message-type-on-.patch +tls-fix-lockless-read-of-strp-msg_ready-in-poll.patch +af_unix-suppress-false-positive-lockdep-splat-for-sp.patch diff --git a/queue-6.6/smb-client-fix-rename-2-regression-against-samba.patch b/queue-6.6/smb-client-fix-rename-2-regression-against-samba.patch new file mode 100644 index 0000000000..6a731faa09 --- /dev/null +++ b/queue-6.6/smb-client-fix-rename-2-regression-against-samba.patch @@ -0,0 +1,56 @@ +From 2cd8e11aa7ba60d650753559ea6a6fccbfcd3cc6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 19 Apr 2024 12:05:07 -0300 +Subject: smb: client: fix rename(2) regression against samba + +From: Paulo Alcantara <pc@manguebit.com> + +[ Upstream commit 18d86965e31f9be4d477da0744a7cdc9815858de ] + +After commit 2c7d399e551c ("smb: client: reuse file lease key in +compound operations") the client started reusing lease keys for +rename, unlink and set path size operations to prevent it from +breaking its own leases and thus causing unnecessary lease breaks to +same connection. + +The implementation relies on positive dentries and +cifsInodeInfo::lease_granted to decide whether reusing lease keys for +the compound requests. cifsInodeInfo::lease_granted was introduced by +commit 0ab95c2510b6 ("Defer close only when lease is enabled.") to +indicate whether lease caching is granted for a specific file, but +that can only happen until file is open, so +cifsInodeInfo::lease_granted was left uninitialised in ->alloc_inode +and then client started sending random lease keys for files that +hadn't any leases. + +This fixes the following test case against samba: + +mount.cifs //srv/share /mnt/1 -o ...,nosharesock +mount.cifs //srv/share /mnt/2 -o ...,nosharesock +touch /mnt/1/foo; tail -f /mnt/1/foo & pid=$! +mv /mnt/2/foo /mnt/2/bar # fails with -EIO +kill $pid + +Fixes: 0ab95c2510b6 ("Defer close only when lease is enabled.") +Signed-off-by: Paulo Alcantara (Red Hat) <pc@manguebit.com> +Signed-off-by: Steve French <stfrench@microsoft.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + fs/smb/client/cifsfs.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/fs/smb/client/cifsfs.c b/fs/smb/client/cifsfs.c +index fcb93a66e47cb..44e2cc37a8b63 100644 +--- a/fs/smb/client/cifsfs.c ++++ b/fs/smb/client/cifsfs.c +@@ -392,6 +392,7 @@ cifs_alloc_inode(struct super_block *sb) + * server, can not assume caching of file data or metadata. + */ + cifs_set_oplock_level(cifs_inode, 0); ++ cifs_inode->lease_granted = false; + cifs_inode->flags = 0; + spin_lock_init(&cifs_inode->writers_lock); + cifs_inode->writers = 0; +-- +2.43.0 + diff --git a/queue-6.6/tls-fix-lockless-read-of-strp-msg_ready-in-poll.patch b/queue-6.6/tls-fix-lockless-read-of-strp-msg_ready-in-poll.patch new file mode 100644 index 0000000000..606a8f235e --- /dev/null +++ b/queue-6.6/tls-fix-lockless-read-of-strp-msg_ready-in-poll.patch @@ -0,0 +1,86 @@ +From f0c8cc443bcb8b03edfea499f6b3b3d6b17df00e Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Wed, 24 Apr 2024 12:25:47 +0200 +Subject: tls: fix lockless read of strp->msg_ready in ->poll + +From: Sabrina Dubroca <sd@queasysnail.net> + +[ Upstream commit 0844370f8945086eb9335739d10205dcea8d707b ] + +tls_sk_poll is called without locking the socket, and needs to read +strp->msg_ready (via tls_strp_msg_ready). Convert msg_ready to a bool +and use READ_ONCE/WRITE_ONCE where needed. The remaining reads are +only performed when the socket is locked. + +Fixes: 121dca784fc0 ("tls: suppress wakeups unless we have a full record") +Signed-off-by: Sabrina Dubroca <sd@queasysnail.net> +Link: https://lore.kernel.org/r/0b7ee062319037cf86af6b317b3d72f7bfcd2e97.1713797701.git.sd@queasysnail.net +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + include/net/tls.h | 3 ++- + net/tls/tls.h | 2 +- + net/tls/tls_strp.c | 6 +++--- + 3 files changed, 6 insertions(+), 5 deletions(-) + +diff --git a/include/net/tls.h b/include/net/tls.h +index 5fdd5dd251df2..2ad28545b15f0 100644 +--- a/include/net/tls.h ++++ b/include/net/tls.h +@@ -110,7 +110,8 @@ struct tls_strparser { + u32 stopped : 1; + u32 copy_mode : 1; + u32 mixed_decrypted : 1; +- u32 msg_ready : 1; ++ ++ bool msg_ready; + + struct strp_msg stm; + +diff --git a/net/tls/tls.h b/net/tls/tls.h +index 28a8c0e80e3c5..02038d0381b75 100644 +--- a/net/tls/tls.h ++++ b/net/tls/tls.h +@@ -212,7 +212,7 @@ static inline struct sk_buff *tls_strp_msg(struct tls_sw_context_rx *ctx) + + static inline bool tls_strp_msg_ready(struct tls_sw_context_rx *ctx) + { +- return ctx->strp.msg_ready; ++ return READ_ONCE(ctx->strp.msg_ready); + } + + static inline bool tls_strp_msg_mixed_decrypted(struct tls_sw_context_rx *ctx) +diff --git a/net/tls/tls_strp.c b/net/tls/tls_strp.c +index ca1e0e198ceb4..5df08d848b5c9 100644 +--- a/net/tls/tls_strp.c ++++ b/net/tls/tls_strp.c +@@ -360,7 +360,7 @@ static int tls_strp_copyin(read_descriptor_t *desc, struct sk_buff *in_skb, + if (strp->stm.full_len && strp->stm.full_len == skb->len) { + desc->count = 0; + +- strp->msg_ready = 1; ++ WRITE_ONCE(strp->msg_ready, 1); + tls_rx_msg_ready(strp); + } + +@@ -528,7 +528,7 @@ static int tls_strp_read_sock(struct tls_strparser *strp) + if (!tls_strp_check_queue_ok(strp)) + return tls_strp_read_copy(strp, false); + +- strp->msg_ready = 1; ++ WRITE_ONCE(strp->msg_ready, 1); + tls_rx_msg_ready(strp); + + return 0; +@@ -580,7 +580,7 @@ void tls_strp_msg_done(struct tls_strparser *strp) + else + tls_strp_flush_anchor_copy(strp); + +- strp->msg_ready = 0; ++ WRITE_ONCE(strp->msg_ready, 0); + memset(&strp->stm, 0, sizeof(strp->stm)); + + tls_strp_check_rcv(strp); +-- +2.43.0 + diff --git a/queue-6.6/tools-ynl-don-t-ignore-errors-in-nlmsg_done-messages.patch b/queue-6.6/tools-ynl-don-t-ignore-errors-in-nlmsg_done-messages.patch new file mode 100644 index 0000000000..d69be9c03b --- /dev/null +++ b/queue-6.6/tools-ynl-don-t-ignore-errors-in-nlmsg_done-messages.patch @@ -0,0 +1,38 @@ +From 10d73a5475faf6ad8f4445abfcf519bf08273d59 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Fri, 19 Apr 2024 19:08:26 -0700 +Subject: tools: ynl: don't ignore errors in NLMSG_DONE messages + +From: Jakub Kicinski <kuba@kernel.org> + +[ Upstream commit a44f2eb106a46f2275a79de54ce0ea63e4f3d8c8 ] + +NLMSG_DONE contains an error code, it has to be extracted. +Prior to this change all dumps will end in success, +and in case of failure the result is silently truncated. + +Fixes: e4b48ed460d3 ("tools: ynl: add a completely generic client") +Signed-off-by: Jakub Kicinski <kuba@kernel.org> +Reviewed-by: Donald Hunter <donald.hunter@gmail.com> +Link: https://lore.kernel.org/r/20240420020827.3288615-1-kuba@kernel.org +Signed-off-by: Paolo Abeni <pabeni@redhat.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + tools/net/ynl/lib/ynl.py | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/tools/net/ynl/lib/ynl.py b/tools/net/ynl/lib/ynl.py +index 13c4b019a881f..44ea0965c9d9c 100644 +--- a/tools/net/ynl/lib/ynl.py ++++ b/tools/net/ynl/lib/ynl.py +@@ -201,6 +201,7 @@ class NlMsg: + self.done = 1 + extack_off = 20 + elif self.nl_type == Netlink.NLMSG_DONE: ++ self.error = struct.unpack("i", self.raw[0:4])[0] + self.done = 1 + extack_off = 4 + +-- +2.43.0 + diff --git a/queue-6.6/vxlan-drop-packets-from-invalid-src-address.patch b/queue-6.6/vxlan-drop-packets-from-invalid-src-address.patch new file mode 100644 index 0000000000..bdc35d2b2a --- /dev/null +++ b/queue-6.6/vxlan-drop-packets-from-invalid-src-address.patch @@ -0,0 +1,52 @@ +From 6b9390d107de11dc5fcfc289bd411f269abd6e58 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 15:29:08 +0200 +Subject: vxlan: drop packets from invalid src-address + +From: David Bauer <mail@david-bauer.net> + +[ Upstream commit f58f45c1e5b92975e91754f5407250085a6ae7cf ] + +The VXLAN driver currently does not check if the inner layer2 +source-address is valid. + +In case source-address snooping/learning is enabled, a entry in the FDB +for the invalid address is created with the layer3 address of the tunnel +endpoint. + +If the frame happens to have a non-unicast address set, all this +non-unicast traffic is subsequently not flooded to the tunnel network +but sent to the learnt host in the FDB. To make matters worse, this FDB +entry does not expire. + +Apply the same filtering for packets as it is done for bridges. This not +only drops these invalid packets but avoids them from being learnt into +the FDB. + +Fixes: d342894c5d2f ("vxlan: virtual extensible lan") +Suggested-by: Ido Schimmel <idosch@nvidia.com> +Signed-off-by: David Bauer <mail@david-bauer.net> +Signed-off-by: David S. Miller <davem@davemloft.net> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/vxlan/vxlan_core.c | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/drivers/net/vxlan/vxlan_core.c b/drivers/net/vxlan/vxlan_core.c +index 99ede13124194..ecdf0276004f9 100644 +--- a/drivers/net/vxlan/vxlan_core.c ++++ b/drivers/net/vxlan/vxlan_core.c +@@ -1615,6 +1615,10 @@ static bool vxlan_set_mac(struct vxlan_dev *vxlan, + if (ether_addr_equal(eth_hdr(skb)->h_source, vxlan->dev->dev_addr)) + return false; + ++ /* Ignore packets from invalid src-address */ ++ if (!is_valid_ether_addr(eth_hdr(skb)->h_source)) ++ return false; ++ + /* Get address from the outer IP header */ + if (vxlan_get_sk_family(vs) == AF_INET) { + saddr.sin.sin_addr.s_addr = ip_hdr(skb)->saddr; +-- +2.43.0 + diff --git a/queue-6.6/wifi-iwlwifi-mvm-remove-old-pasn-station-when-adding.patch b/queue-6.6/wifi-iwlwifi-mvm-remove-old-pasn-station-when-adding.patch new file mode 100644 index 0000000000..fc6b72bbec --- /dev/null +++ b/queue-6.6/wifi-iwlwifi-mvm-remove-old-pasn-station-when-adding.patch @@ -0,0 +1,40 @@ +From 119703ea7b760c62836bf8171e4f5ea7bd7f06bc Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 15 Apr 2024 11:54:43 +0300 +Subject: wifi: iwlwifi: mvm: remove old PASN station when adding a new one + +From: Avraham Stern <avraham.stern@intel.com> + +[ Upstream commit dbfff5bf9292714f02ace002fea8ce6599ea1145 ] + +If a PASN station is added, and an old PASN station already exists +for the same mac address, remove the old station before adding the +new one. Keeping the old station caueses old security context to +be used in measurements. + +Fixes: 0739a7d70e00 ("iwlwifi: mvm: initiator: add option for adding a PASN responder") +Signed-off-by: Avraham Stern <avraham.stern@intel.com> +Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com> +Link: https://msgid.link/20240415114847.ef3544a416f2.I4e8c7c8ca22737f4f908ae5cd4fc0b920c703dd3@changeid +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c b/drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c +index 233ae81884a0e..ae0eb585b61ee 100644 +--- a/drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c ++++ b/drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c +@@ -53,6 +53,8 @@ int iwl_mvm_ftm_add_pasn_sta(struct iwl_mvm *mvm, struct ieee80211_vif *vif, + if (!pasn) + return -ENOBUFS; + ++ iwl_mvm_ftm_remove_pasn_sta(mvm, addr); ++ + pasn->cipher = iwl_mvm_cipher_to_location_cipher(cipher); + + switch (pasn->cipher) { +-- +2.43.0 + diff --git a/queue-6.6/wifi-iwlwifi-mvm-return-uid-from-iwl_mvm_build_scan_.patch b/queue-6.6/wifi-iwlwifi-mvm-return-uid-from-iwl_mvm_build_scan_.patch new file mode 100644 index 0000000000..9a412ce17e --- /dev/null +++ b/queue-6.6/wifi-iwlwifi-mvm-return-uid-from-iwl_mvm_build_scan_.patch @@ -0,0 +1,44 @@ +From 5c5dfa42df268571191ad846bddc990e08840d0a Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 15 Apr 2024 11:54:44 +0300 +Subject: wifi: iwlwifi: mvm: return uid from iwl_mvm_build_scan_cmd + +From: Miri Korenblit <miriam.rachel.korenblit@intel.com> + +[ Upstream commit bada85a3f584763deadd201147778c3e791d279c ] + +This function is supposed to return a uid on success, and an errno in +failure. +But it currently returns the return value of the specific cmd version +handler, which in turn returns 0 on success and errno otherwise. +This means that on success, iwl_mvm_build_scan_cmd will return 0 +regardless if the actual uid. +Fix this by returning the uid if the handler succeeded. + +Fixes: 687db6ff5b70 ("iwlwifi: scan: make new scan req versioning flow") +Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com> +Reviewed-by: Ilan Peer <ilan.peer@intel.com> +Link: https://msgid.link/20240415114847.5e2d602b3190.I4c4931021be74a67a869384c8f8ee7463e0c7857@changeid +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/wireless/intel/iwlwifi/mvm/scan.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/scan.c b/drivers/net/wireless/intel/iwlwifi/mvm/scan.c +index 3cbe2c0b8d6bc..03ec900a33433 100644 +--- a/drivers/net/wireless/intel/iwlwifi/mvm/scan.c ++++ b/drivers/net/wireless/intel/iwlwifi/mvm/scan.c +@@ -2819,7 +2819,8 @@ static int iwl_mvm_build_scan_cmd(struct iwl_mvm *mvm, + if (ver_handler->version != scan_ver) + continue; + +- return ver_handler->handler(mvm, vif, params, type, uid); ++ err = ver_handler->handler(mvm, vif, params, type, uid); ++ return err ? : uid; + } + + err = iwl_mvm_scan_umac(mvm, vif, params, type, uid); +-- +2.43.0 + diff --git a/queue-6.6/wifi-mac80211-clean-up-assignments-to-pointer-cache.patch b/queue-6.6/wifi-mac80211-clean-up-assignments-to-pointer-cache.patch new file mode 100644 index 0000000000..5e4bc023e0 --- /dev/null +++ b/queue-6.6/wifi-mac80211-clean-up-assignments-to-pointer-cache.patch @@ -0,0 +1,73 @@ +From 27fb810cc75036e5583ce939243283379d8c0e03 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 15 Feb 2024 23:21:51 +0000 +Subject: wifi: mac80211: clean up assignments to pointer cache. + +From: Colin Ian King <colin.i.king@intel.com> + +[ Upstream commit ba4b1fa3128b2fbf14e167230315cbd9074b629b ] + +The assignment to pointer cache in function mesh_fast_tx_gc can +be made at the declaration time rather than a later assignment. +There are also 3 functions where pointer cache is being initialized +at declaration time and later re-assigned again with the same +value, these are redundant and can be removed. + +Cleans up code and three clang scan build warnings: +warning: Value stored to 'cache' during its initialization is never +read [deadcode.DeadStores] + +Signed-off-by: Colin Ian King <colin.i.king@intel.com> +Reviewed-by: Simon Horman <horms@kernel.org> +Link: https://msgid.link/20240215232151.2075483-1-colin.i.king@gmail.com +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Stable-dep-of: 8c75cdcdf869 ("wifi: mac80211: split mesh fast tx cache into local/proxied/forwarded") +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/mac80211/mesh_pathtbl.c | 6 +----- + 1 file changed, 1 insertion(+), 5 deletions(-) + +diff --git a/net/mac80211/mesh_pathtbl.c b/net/mac80211/mesh_pathtbl.c +index 3e52aaa57b1fc..c7173190f9b93 100644 +--- a/net/mac80211/mesh_pathtbl.c ++++ b/net/mac80211/mesh_pathtbl.c +@@ -595,11 +595,10 @@ void mesh_fast_tx_cache(struct ieee80211_sub_if_data *sdata, + void mesh_fast_tx_gc(struct ieee80211_sub_if_data *sdata) + { + unsigned long timeout = msecs_to_jiffies(MESH_FAST_TX_CACHE_TIMEOUT); +- struct mesh_tx_cache *cache; ++ struct mesh_tx_cache *cache = &sdata->u.mesh.tx_cache; + struct ieee80211_mesh_fast_tx *entry; + struct hlist_node *n; + +- cache = &sdata->u.mesh.tx_cache; + if (atomic_read(&cache->rht.nelems) < MESH_FAST_TX_CACHE_THRESHOLD_SIZE) + return; + +@@ -617,7 +616,6 @@ void mesh_fast_tx_flush_mpath(struct mesh_path *mpath) + struct ieee80211_mesh_fast_tx *entry; + struct hlist_node *n; + +- cache = &sdata->u.mesh.tx_cache; + spin_lock_bh(&cache->walk_lock); + hlist_for_each_entry_safe(entry, n, &cache->walk_head, walk_list) + if (entry->mpath == mpath) +@@ -632,7 +630,6 @@ void mesh_fast_tx_flush_sta(struct ieee80211_sub_if_data *sdata, + struct ieee80211_mesh_fast_tx *entry; + struct hlist_node *n; + +- cache = &sdata->u.mesh.tx_cache; + spin_lock_bh(&cache->walk_lock); + hlist_for_each_entry_safe(entry, n, &cache->walk_head, walk_list) + if (rcu_access_pointer(entry->mpath->next_hop) == sta) +@@ -646,7 +643,6 @@ void mesh_fast_tx_flush_addr(struct ieee80211_sub_if_data *sdata, + struct mesh_tx_cache *cache = &sdata->u.mesh.tx_cache; + struct ieee80211_mesh_fast_tx *entry; + +- cache = &sdata->u.mesh.tx_cache; + spin_lock_bh(&cache->walk_lock); + entry = rhashtable_lookup_fast(&cache->rht, addr, fast_tx_rht_params); + if (entry) +-- +2.43.0 + diff --git a/queue-6.6/wifi-mac80211-fix-unaligned-le16-access.patch b/queue-6.6/wifi-mac80211-fix-unaligned-le16-access.patch new file mode 100644 index 0000000000..bc0a4f9001 --- /dev/null +++ b/queue-6.6/wifi-mac80211-fix-unaligned-le16-access.patch @@ -0,0 +1,40 @@ +From a0009f8555591e118cea7e295d64a55f6cd13363 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 10:52:26 +0200 +Subject: wifi: mac80211: fix unaligned le16 access + +From: Johannes Berg <johannes.berg@intel.com> + +[ Upstream commit c53d8a59351e4347452e263e2e5d7446ec93da83 ] + +The AP removal timer field need not be aligned, so the +code shouldn't access it directly, but use unaligned +loads. Use get_unaligned_le16(), which even is shorter +than the current code since it doesn't need a cast. + +Fixes: 8eb8dd2ffbbb ("wifi: mac80211: Support link removal using Reconfiguration ML element") +Reviewed-by: Ilan Peer <ilan.peer@intel.com> +Reviewed-by: Miriam Rachel Korenblit <miriam.rachel.korenblit@intel.com> +Link: https://msgid.link/20240418105220.356788ba0045.I2b3cdb3644e205d5bb10322c345c0499171cf5d2@changeid +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/mac80211/mlme.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c +index e3e769b2f2ef1..6e574e2adc22e 100644 +--- a/net/mac80211/mlme.c ++++ b/net/mac80211/mlme.c +@@ -5859,7 +5859,7 @@ static void ieee80211_ml_reconfiguration(struct ieee80211_sub_if_data *sdata, + */ + if (control & + IEEE80211_MLE_STA_RECONF_CONTROL_AP_REM_TIMER_PRESENT) +- link_removal_timeout[link_id] = le16_to_cpu(*(__le16 *)pos); ++ link_removal_timeout[link_id] = get_unaligned_le16(pos); + } + + removed_links &= sdata->vif.valid_links; +-- +2.43.0 + diff --git a/queue-6.6/wifi-mac80211-remove-link-before-ap.patch b/queue-6.6/wifi-mac80211-remove-link-before-ap.patch new file mode 100644 index 0000000000..b6740ccee2 --- /dev/null +++ b/queue-6.6/wifi-mac80211-remove-link-before-ap.patch @@ -0,0 +1,54 @@ +From 839a0b0932e247d073b0cf064cd1ba00f84d366a Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 10:52:25 +0200 +Subject: wifi: mac80211: remove link before AP + +From: Johannes Berg <johannes.berg@intel.com> + +[ Upstream commit cb55e08dba3526796e35d24a6d5db4ed6dcb8a4b ] + +If the AP removal timer is long, we don't really want to +remove the link immediately. However, we really should do +it _before_ the AP removes it (which happens at or after +count reaches 0), so subtract 1 from the countdown when +scheduling the timer. This causes the link removal work +to run just after the beacon with value 1 is received. If +the counter is already zero, do it immediately. + +This fixes an issue where we do the removal too late and +receive a beacon from the AP that's no longer associated +with the MLD, but thus removed EHT and ML elements, and +then we disconnect instead from the whole MLD, since one +of the associated APs changed mode from EHT to HE. + +Fixes: 8eb8dd2ffbbb ("wifi: mac80211: Support link removal using Reconfiguration ML element") +Reviewed-by: Ilan Peer <ilan.peer@intel.com> +Reviewed-by: Miriam Rachel Korenblit <miriam.rachel.korenblit@intel.com> +Link: https://msgid.link/20240418105220.03ac4a09fa74.Ifb8c8d38e3402721a81ce5981568f47b5c5889cb@changeid +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/mac80211/mlme.c | 7 +++++-- + 1 file changed, 5 insertions(+), 2 deletions(-) + +diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c +index c6044ab4e7fc1..e3e769b2f2ef1 100644 +--- a/net/mac80211/mlme.c ++++ b/net/mac80211/mlme.c +@@ -5884,8 +5884,11 @@ static void ieee80211_ml_reconfiguration(struct ieee80211_sub_if_data *sdata, + continue; + } + +- link_delay = link_conf->beacon_int * +- link_removal_timeout[link_id]; ++ if (link_removal_timeout[link_id] < 1) ++ link_delay = 0; ++ else ++ link_delay = link_conf->beacon_int * ++ (link_removal_timeout[link_id] - 1); + + if (!delay) + delay = link_delay; +-- +2.43.0 + diff --git a/queue-6.6/wifi-mac80211-split-mesh-fast-tx-cache-into-local-pr.patch b/queue-6.6/wifi-mac80211-split-mesh-fast-tx-cache-into-local-pr.patch new file mode 100644 index 0000000000..00112088f5 --- /dev/null +++ b/queue-6.6/wifi-mac80211-split-mesh-fast-tx-cache-into-local-pr.patch @@ -0,0 +1,249 @@ +From f8ef0de44bc62c99207c6c1a247918848049c92e Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Mon, 15 Apr 2024 14:18:11 +0200 +Subject: wifi: mac80211: split mesh fast tx cache into local/proxied/forwarded + +From: Felix Fietkau <nbd@nbd.name> + +[ Upstream commit 8c75cdcdf869acabfdc7858827099dcde9f24e6c ] + +Depending on the origin of the packets (and their SA), 802.11 + mesh headers +could be filled in differently. In order to properly deal with that, add a +new field to the lookup key, indicating the type (local, proxied or +forwarded). This can fix spurious packet drop issues that depend on the order +in which nodes/hosts communicate with each other. + +Fixes: d5edb9ae8d56 ("wifi: mac80211: mesh fast xmit support") +Signed-off-by: Felix Fietkau <nbd@nbd.name> +Link: https://msgid.link/20240415121811.13391-1-nbd@nbd.name +[use sizeof_field() for key_len] +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + net/mac80211/mesh.c | 8 +++++++- + net/mac80211/mesh.h | 36 +++++++++++++++++++++++++++++++++--- + net/mac80211/mesh_pathtbl.c | 31 ++++++++++++++++++++++--------- + net/mac80211/rx.c | 13 ++++++++++--- + 4 files changed, 72 insertions(+), 16 deletions(-) + +diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c +index e31c312c124a1..7b3ecc288f09d 100644 +--- a/net/mac80211/mesh.c ++++ b/net/mac80211/mesh.c +@@ -765,6 +765,9 @@ bool ieee80211_mesh_xmit_fast(struct ieee80211_sub_if_data *sdata, + struct sk_buff *skb, u32 ctrl_flags) + { + struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh; ++ struct ieee80211_mesh_fast_tx_key key = { ++ .type = MESH_FAST_TX_TYPE_LOCAL ++ }; + struct ieee80211_mesh_fast_tx *entry; + struct ieee80211s_hdr *meshhdr; + u8 sa[ETH_ALEN] __aligned(2); +@@ -800,7 +803,10 @@ bool ieee80211_mesh_xmit_fast(struct ieee80211_sub_if_data *sdata, + return false; + } + +- entry = mesh_fast_tx_get(sdata, skb->data); ++ ether_addr_copy(key.addr, skb->data); ++ if (!ether_addr_equal(skb->data + ETH_ALEN, sdata->vif.addr)) ++ key.type = MESH_FAST_TX_TYPE_PROXIED; ++ entry = mesh_fast_tx_get(sdata, &key); + if (!entry) + return false; + +diff --git a/net/mac80211/mesh.h b/net/mac80211/mesh.h +index ad8469293d712..58c619874ca6a 100644 +--- a/net/mac80211/mesh.h ++++ b/net/mac80211/mesh.h +@@ -133,10 +133,39 @@ struct mesh_path { + #define MESH_FAST_TX_CACHE_THRESHOLD_SIZE 384 + #define MESH_FAST_TX_CACHE_TIMEOUT 8000 /* msecs */ + ++/** ++ * enum ieee80211_mesh_fast_tx_type - cached mesh fast tx entry type ++ * ++ * @MESH_FAST_TX_TYPE_LOCAL: tx from the local vif address as SA ++ * @MESH_FAST_TX_TYPE_PROXIED: local tx with a different SA (e.g. bridged) ++ * @MESH_FAST_TX_TYPE_FORWARDED: forwarded from a different mesh point ++ * @NUM_MESH_FAST_TX_TYPE: number of entry types ++ */ ++enum ieee80211_mesh_fast_tx_type { ++ MESH_FAST_TX_TYPE_LOCAL, ++ MESH_FAST_TX_TYPE_PROXIED, ++ MESH_FAST_TX_TYPE_FORWARDED, ++ ++ /* must be last */ ++ NUM_MESH_FAST_TX_TYPE ++}; ++ ++ ++/** ++ * struct ieee80211_mesh_fast_tx_key - cached mesh fast tx entry key ++ * ++ * @addr: The Ethernet DA for this entry ++ * @type: cache entry type ++ */ ++struct ieee80211_mesh_fast_tx_key { ++ u8 addr[ETH_ALEN] __aligned(2); ++ u16 type; ++}; ++ + /** + * struct ieee80211_mesh_fast_tx - cached mesh fast tx entry + * @rhash: rhashtable pointer +- * @addr_key: The Ethernet DA which is the key for this entry ++ * @key: the lookup key for this cache entry + * @fast_tx: base fast_tx data + * @hdr: cached mesh and rfc1042 headers + * @hdrlen: length of mesh + rfc1042 +@@ -147,7 +176,7 @@ struct mesh_path { + */ + struct ieee80211_mesh_fast_tx { + struct rhash_head rhash; +- u8 addr_key[ETH_ALEN] __aligned(2); ++ struct ieee80211_mesh_fast_tx_key key; + + struct ieee80211_fast_tx fast_tx; + u8 hdr[sizeof(struct ieee80211s_hdr) + sizeof(rfc1042_header)]; +@@ -333,7 +362,8 @@ void mesh_path_tx_root_frame(struct ieee80211_sub_if_data *sdata); + + bool mesh_action_is_path_sel(struct ieee80211_mgmt *mgmt); + struct ieee80211_mesh_fast_tx * +-mesh_fast_tx_get(struct ieee80211_sub_if_data *sdata, const u8 *addr); ++mesh_fast_tx_get(struct ieee80211_sub_if_data *sdata, ++ struct ieee80211_mesh_fast_tx_key *key); + bool ieee80211_mesh_xmit_fast(struct ieee80211_sub_if_data *sdata, + struct sk_buff *skb, u32 ctrl_flags); + void mesh_fast_tx_cache(struct ieee80211_sub_if_data *sdata, +diff --git a/net/mac80211/mesh_pathtbl.c b/net/mac80211/mesh_pathtbl.c +index c7173190f9b93..59f7264194ce3 100644 +--- a/net/mac80211/mesh_pathtbl.c ++++ b/net/mac80211/mesh_pathtbl.c +@@ -36,8 +36,8 @@ static const struct rhashtable_params mesh_rht_params = { + static const struct rhashtable_params fast_tx_rht_params = { + .nelem_hint = 10, + .automatic_shrinking = true, +- .key_len = ETH_ALEN, +- .key_offset = offsetof(struct ieee80211_mesh_fast_tx, addr_key), ++ .key_len = sizeof_field(struct ieee80211_mesh_fast_tx, key), ++ .key_offset = offsetof(struct ieee80211_mesh_fast_tx, key), + .head_offset = offsetof(struct ieee80211_mesh_fast_tx, rhash), + .hashfn = mesh_table_hash, + }; +@@ -426,20 +426,21 @@ static void mesh_fast_tx_entry_free(struct mesh_tx_cache *cache, + } + + struct ieee80211_mesh_fast_tx * +-mesh_fast_tx_get(struct ieee80211_sub_if_data *sdata, const u8 *addr) ++mesh_fast_tx_get(struct ieee80211_sub_if_data *sdata, ++ struct ieee80211_mesh_fast_tx_key *key) + { + struct ieee80211_mesh_fast_tx *entry; + struct mesh_tx_cache *cache; + + cache = &sdata->u.mesh.tx_cache; +- entry = rhashtable_lookup(&cache->rht, addr, fast_tx_rht_params); ++ entry = rhashtable_lookup(&cache->rht, key, fast_tx_rht_params); + if (!entry) + return NULL; + + if (!(entry->mpath->flags & MESH_PATH_ACTIVE) || + mpath_expired(entry->mpath)) { + spin_lock_bh(&cache->walk_lock); +- entry = rhashtable_lookup(&cache->rht, addr, fast_tx_rht_params); ++ entry = rhashtable_lookup(&cache->rht, key, fast_tx_rht_params); + if (entry) + mesh_fast_tx_entry_free(cache, entry); + spin_unlock_bh(&cache->walk_lock); +@@ -484,18 +485,24 @@ void mesh_fast_tx_cache(struct ieee80211_sub_if_data *sdata, + if (!sta) + return; + ++ build.key.type = MESH_FAST_TX_TYPE_LOCAL; + if ((meshhdr->flags & MESH_FLAGS_AE) == MESH_FLAGS_AE_A5_A6) { + /* This is required to keep the mppath alive */ + mppath = mpp_path_lookup(sdata, meshhdr->eaddr1); + if (!mppath) + return; + build.mppath = mppath; ++ if (!ether_addr_equal(meshhdr->eaddr2, sdata->vif.addr)) ++ build.key.type = MESH_FAST_TX_TYPE_PROXIED; + } else if (ieee80211_has_a4(hdr->frame_control)) { + mppath = mpath; + } else { + return; + } + ++ if (!ether_addr_equal(hdr->addr4, sdata->vif.addr)) ++ build.key.type = MESH_FAST_TX_TYPE_FORWARDED; ++ + /* rate limit, in case fast xmit can't be enabled */ + if (mppath->fast_tx_check == jiffies) + return; +@@ -542,7 +549,7 @@ void mesh_fast_tx_cache(struct ieee80211_sub_if_data *sdata, + } + } + +- memcpy(build.addr_key, mppath->dst, ETH_ALEN); ++ memcpy(build.key.addr, mppath->dst, ETH_ALEN); + build.timestamp = jiffies; + build.fast_tx.band = info->band; + build.fast_tx.da_offs = offsetof(struct ieee80211_hdr, addr3); +@@ -641,12 +648,18 @@ void mesh_fast_tx_flush_addr(struct ieee80211_sub_if_data *sdata, + const u8 *addr) + { + struct mesh_tx_cache *cache = &sdata->u.mesh.tx_cache; ++ struct ieee80211_mesh_fast_tx_key key = {}; + struct ieee80211_mesh_fast_tx *entry; ++ int i; + ++ ether_addr_copy(key.addr, addr); + spin_lock_bh(&cache->walk_lock); +- entry = rhashtable_lookup_fast(&cache->rht, addr, fast_tx_rht_params); +- if (entry) +- mesh_fast_tx_entry_free(cache, entry); ++ for (i = 0; i < NUM_MESH_FAST_TX_TYPE; i++) { ++ key.type = i; ++ entry = rhashtable_lookup_fast(&cache->rht, &key, fast_tx_rht_params); ++ if (entry) ++ mesh_fast_tx_entry_free(cache, entry); ++ } + spin_unlock_bh(&cache->walk_lock); + } + +diff --git a/net/mac80211/rx.c b/net/mac80211/rx.c +index 26ca2f5dc52b2..604863cebc198 100644 +--- a/net/mac80211/rx.c ++++ b/net/mac80211/rx.c +@@ -2726,7 +2726,10 @@ ieee80211_rx_mesh_fast_forward(struct ieee80211_sub_if_data *sdata, + struct sk_buff *skb, int hdrlen) + { + struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh; +- struct ieee80211_mesh_fast_tx *entry = NULL; ++ struct ieee80211_mesh_fast_tx_key key = { ++ .type = MESH_FAST_TX_TYPE_FORWARDED ++ }; ++ struct ieee80211_mesh_fast_tx *entry; + struct ieee80211s_hdr *mesh_hdr; + struct tid_ampdu_tx *tid_tx; + struct sta_info *sta; +@@ -2735,9 +2738,13 @@ ieee80211_rx_mesh_fast_forward(struct ieee80211_sub_if_data *sdata, + + mesh_hdr = (struct ieee80211s_hdr *)(skb->data + sizeof(eth)); + if ((mesh_hdr->flags & MESH_FLAGS_AE) == MESH_FLAGS_AE_A5_A6) +- entry = mesh_fast_tx_get(sdata, mesh_hdr->eaddr1); ++ ether_addr_copy(key.addr, mesh_hdr->eaddr1); + else if (!(mesh_hdr->flags & MESH_FLAGS_AE)) +- entry = mesh_fast_tx_get(sdata, skb->data); ++ ether_addr_copy(key.addr, skb->data); ++ else ++ return false; ++ ++ entry = mesh_fast_tx_get(sdata, &key); + if (!entry) + return false; + +-- +2.43.0 + diff --git a/queue-6.6/wifi-mac80211_hwsim-init-peer-measurement-result.patch b/queue-6.6/wifi-mac80211_hwsim-init-peer-measurement-result.patch new file mode 100644 index 0000000000..096fbcec3f --- /dev/null +++ b/queue-6.6/wifi-mac80211_hwsim-init-peer-measurement-result.patch @@ -0,0 +1,38 @@ +From daac930fcd954bddc352b2c61f6fb59a70d34644 Mon Sep 17 00:00:00 2001 +From: Sasha Levin <sashal@kernel.org> +Date: Thu, 18 Apr 2024 10:52:24 +0200 +Subject: wifi: mac80211_hwsim: init peer measurement result + +From: Johannes Berg <johannes.berg@intel.com> + +[ Upstream commit 2a4e01e5270b9fa9f6e6e0a4c24ac51a758636f9 ] + +If we don't get all the values here, we might pass them to +cfg80211 uninitialized. Fix that, even if the input might +then not make much sense. + +Fixes: 2af3b2a631b1 ("mac80211_hwsim: add PMSR report support via virtio") +Reviewed-by: Miriam Rachel Korenblit <miriam.rachel.korenblit@intel.com> +Link: https://msgid.link/20240418105220.e1317621c1f9.If7dd447de24d7493d133284db5e9e482e4e299f8@changeid +Signed-off-by: Johannes Berg <johannes.berg@intel.com> +Signed-off-by: Sasha Levin <sashal@kernel.org> +--- + drivers/net/wireless/virtual/mac80211_hwsim.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/wireless/virtual/mac80211_hwsim.c b/drivers/net/wireless/virtual/mac80211_hwsim.c +index f5a0880da3fcc..07be0adc13ec5 100644 +--- a/drivers/net/wireless/virtual/mac80211_hwsim.c ++++ b/drivers/net/wireless/virtual/mac80211_hwsim.c +@@ -3795,7 +3795,7 @@ static int hwsim_pmsr_report_nl(struct sk_buff *msg, struct genl_info *info) + } + + nla_for_each_nested(peer, peers, rem) { +- struct cfg80211_pmsr_result result; ++ struct cfg80211_pmsr_result result = {}; + + err = mac80211_hwsim_parse_pmsr_result(peer, &result, info); + if (err) +-- +2.43.0 + |