Skip to contentSkip to conversation

5.15.221-rc1 review

PATCH In review Greg Kroah-Hartman 12 participants 972 messages Sep 12 – Sep 20 Page 8 of 8

Subsystems (6)
lore
Share & tools
lore
author maintainer
#963 lore raw

PATCH 933/935 kselftest/arm64: mte: Use the correct naming for tag check modes in check_hugetlb_options.c

In reply to Greg Kroah-Hartman

5.15-stable review patch. If anyone has any objections, please let me know.

------------------

From: Catalin Marinas <[email protected]>

[ Upstream commit 7ae95109c64d64cdcf195788cf466ec0b3019a94 ]

The architecture doesn't define precise/imprecise MTE tag check modes, only synchronous and asynchronous. Use the correct naming and also ensure they match the MTE_{ASYNC,SYNC}_ERR type.

Fixes 27879e8cb6b0 ("selftests: arm64: add hugetlb mte tests")
Cc Yang Shi <[email protected]>
---
 tools/testing/selftests/arm64/mte/check_hugetlb_options.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
tools/testing/selftests/arm64/mte/check_hugetlb_options.c +4 -4
index d1dc587b18254..cd7667187ed5b 100644
@@ -283,13 +283,13 @@ int main(int argc, char *argv[])
 	"Check clear PROT_MTE flags with private mapping and sync error mode and mmap/mprotect memory\n");
 
 	evaluate_test(check_child_hugetlb_memory_mapping(USE_MMAP, MTE_SYNC_ERR, MAP_PRIVATE | MAP_HUGETLB),
-		"Check child hugetlb memory with private mapping, precise mode and mmap memory\n");
+		"Check child hugetlb memory with private mapping, sync error mode and mmap memory\n");
 	evaluate_test(check_child_hugetlb_memory_mapping(USE_MMAP, MTE_ASYNC_ERR, MAP_PRIVATE | MAP_HUGETLB),
-		"Check child hugetlb memory with private mapping, precise mode and mmap memory\n");
+		"Check child hugetlb memory with private mapping, async error mode and mmap memory\n");
 	evaluate_test(check_child_hugetlb_memory_mapping(USE_MPROTECT, MTE_SYNC_ERR, MAP_PRIVATE | MAP_HUGETLB),
-		"Check child hugetlb memory with private mapping, precise mode and mmap/mprotect memory\n");
+		"Check child hugetlb memory with private mapping, sync error mode and mmap/mprotect memory\n");
 	evaluate_test(check_child_hugetlb_memory_mapping(USE_MPROTECT, MTE_ASYNC_ERR, MAP_PRIVATE | MAP_HUGETLB),
-		"Check child hugetlb memory with private mapping, precise mode and mmap/mprotect memory\n");
+		"Check child hugetlb memory with private mapping, async error mode and mmap/mprotect memory\n");
 
 	mte_restore_setup();
 	free_hugetlb();
Signature · 1 line
2.53.0
author maintainer
#964 lore raw

PATCH 934/935 nvmet-rdma: fix queue leak when connect backlog is exceeded

In reply to Greg Kroah-Hartman

5.15-stable review patch. If anyone has any objections, please let me know.

------------------

From: Xixin Liu <[email protected]>

commit fb1ed67788e21832b614c23767a088c08cfdd2f2 upstream.

When pending disconnecting queues exceed the backlog limit, the connect path only drops the device reference and leaks the newly allocated queue and its IB resources.

Fixes badc53620fe8 ("nvme: target: rdma: fix ndev refcount leak on queue connect")
---
 drivers/nvme/target/rdma.c |   15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)
drivers/nvme/target/rdma.c +7 -8
@@ -1627,19 +1627,13 @@ static int nvmet_rdma_queue_connect(stru
 		mutex_unlock(&nvmet_rdma_queue_mutex);
 		if (pending > NVMET_RDMA_BACKLOG) {
 			ret = NVME_SC_CONNECT_CTRL_BUSY;
-			goto put_device;
+			goto free_queue;
 		}
 	}
 
 	ret = nvmet_rdma_cm_accept(cm_id, queue, &event->param.conn);
-	if (ret) {
-		/*
-		 * Don't destroy the cm_id in free path, as we implicitly
-		 * destroy the cm_id here with non-zero ret code.
-		 */
-		queue->cm_id = NULL;
+	if (ret)
 		goto free_queue;
-	}
 
 	mutex_lock(&nvmet_rdma_queue_mutex);
 	list_add_tail(&queue->queue_list, &nvmet_rdma_queue_list);
@@ -1648,6 +1642,11 @@ static int nvmet_rdma_queue_connect(stru
 	return 0;
 
 free_queue:
+	/*
+	 * Don't destroy the cm_id in free path, as we implicitly
+	 * destroy the cm_id here with non-zero ret code.
+	 */
+	queue->cm_id = NULL;
 	nvmet_rdma_free_queue(queue);
 put_device:
 	kref_put(&ndev->ref, nvmet_rdma_free_dev);
author maintainer
#965 lore raw

PATCH 935/935 clk: qcom: gdsc: Bump parent usage count when GDSC is found enabled

In reply to Greg Kroah-Hartman

5.15-stable review patch. If anyone has any objections, please let me know.

------------------

From: Bjorn Andersson <[email protected]>

commit 41fff779d7948147f2440c4bb134cdf8b45b22d7 upstream.

When a GDSC is found to be enabled at boot the pm_runtime state will be unbalanced as the GDSC is later turned off. Fix this by increasing the usage counter on the power-domain, in line with how we handled the regulator state.

Fixes 1b771839de05 ("clk: qcom: gdsc: enable optional power domain support")
---
 drivers/clk/qcom/gdsc.c |    8 ++++++++
 1 file changed, 8 insertions(+)
drivers/clk/qcom/gdsc.c +8 -0
@@ -427,6 +427,14 @@ static int gdsc_init(struct gdsc *sc)
 				return ret;
 		}
 
+		/* ...and the power-domain */
+		ret = gdsc_pm_runtime_get(sc);
+		if (ret) {
+			if (sc->rsupply)
+				regulator_disable(sc->rsupply);
+			return ret;
+		}
+
 		/*
 		 * Votable GDSCs can be ON due to Vote from other masters.
 		 * If a Votable GDSC is ON, make sure we have a Vote.
#966 lore raw
In reply to Greg Kroah-Hartman
Quoted 9 lines · Greg Kroah-Hartman

This is the start of the stable review cycle for the 5.15.221 release. There are 935 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.

Responses should be made by Mon, 14 Sep 2026 06:54:17 +0000. Anything received after that time might be too late.

The whole patch series can be found in one patch at:

Quoted 10 lines
	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.221-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
and the diffstat can be found below.

thanks,

greg k-h

The build fails with:

sound/soc/fsl/fsl_audmix.c:469:12: warning: 'fsl_audmix_runtime_resume' used but never defined 469 | static int fsl_audmix_runtime_resume(struct device *dev);
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~
sound/soc/fsl/fsl_audmix.c:470:12: warning: 'fsl_audmix_runtime_suspend' used but never defined 470 | static int fsl_audmix_runtime_suspend(struct device *dev);
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: modpost: "fsl_audmix_runtime_resume" [sound/soc/fsl/snd-soc-fsl-audmix.ko] undefined!
ERROR: modpost: "fsl_audmix_runtime_suspend" [sound/soc/fsl/snd-soc-fsl-audmix.ko] undefined! make[1]: *** [scripts/Makefile.modpost:133: modules-only.symvers] Error 1 make[1]: *** Deleting file 'modules-only.symvers'
make: *** [Makefile:1843: modules] Error 2

This is due to commit "ASoC: fsl_audmix: rework runtime PM handling in probe" commit id 9145b2e38db943434df708bb818190f4a9e003b0 and I have CONFIG_PM=n in my config.

maintainer
#967 lore raw
Quoted 2 lines

ERROR: modpost: "fsl_audmix_runtime_suspend" [sound/soc/fsl/snd-soc-fsl-audmix.ko] undefined!
ERROR: modpost: "fsl_audmix_runtime_resume" [sound/soc/fsl/snd-soc-fsl-audmix.ko] undefined!

Dropped from the 5.15 queue. Same CONFIG_PM=n build break also hit the 6.1 and 6.6 queues, both dropped as well.

Thanks for the report.

Signature · 2 lines
Thanks,
Sasha
Tested-by on the v1 series
#968 lore raw
In reply to Greg Kroah-Hartman
Quoted 9 lines · Greg Kroah-Hartman

This is the start of the stable review cycle for the 5.15.221 release. There are 935 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.

Responses should be made by Mon, 14 Sep 2026 06:54:17 +0000. Anything received after that time might be too late.

The whole patch series can be found in one patch at:

Quoted 8 lines
	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.221-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
and the diffstat can be found below.

thanks,

greg k-h

Built and booted successfully on RISC-V RV64 (HiFive Unmatched).

Tested-by on the v1 series
#969 lore raw
In reply to Greg Kroah-Hartman
Quoted 9 lines · Greg Kroah-Hartman

This is the start of the stable review cycle for the 5.15.221 release. There are 935 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.

Responses should be made by Mon, 14 Sep 2026 06:54:17 +0000. Anything received after that time might be too late.

The whole patch series can be found in one patch at:

Quoted 8 lines
	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.221-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
and the diffstat can be found below.

thanks,

greg k-h

On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:

Signature · 1 line
Florian
#970 lore raw
In reply to Greg Kroah-Hartman
Quoted 8 lines · Greg Kroah-Hartman

This is the start of the stable review cycle for the 5.15.221 release. There are 935 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.

Responses should be made by Mon, 14 Sep 2026 06:54:17 +0000. Anything received after that time might be too late.

All alpha images:

Error log:
arch/alpha/kernel/traps.c: In function 'do_entIF':
arch/alpha/kernel/traps.c:373:35: error: too few arguments to function 'alpha_fp_emul'
373 | si_code = alpha_fp_emul(regs->pc - 4);

This affects v5.15.221, v6.1.188, and v6.6.157.

$ git log --oneline v5.15.220.. arch/alpha/kernel/traps.c arch/alpha/math-emu/math.c
f55e039ce84f alpha: don't leak hardware-fabricated FP exception bits to user space

is the culprit. One of the calls to alpha_fp_emul() was not updated to add the second argument.

Guenter

maintainer
#971 lore raw
Quoted 8 lines

All alpha images:

Error log:
arch/alpha/kernel/traps.c: In function 'do_entIF':
arch/alpha/kernel/traps.c:373:35: error: too few arguments to function 'alpha_fp_emul'
373 | si_code = alpha_fp_emul(regs->pc - 4);

This affects v5.15.221, v6.1.188, and v6.6.157.

Reverted on 6.6, 6.1 and 5.15, along with 49672d026cc4 ("alpha: fix ieee_swcr_to_fpcr setting FPCR_DNOD unconditionally"), since both changelogs say the two must not be separated. 7.2, 6.18 and 6.12 are unaffected: the second call site lives in do_entIF(), which only exists on trees predating a4184174be36 ("alpha: drop pre-EV56 support").

Matt, could you send a version of bcfe3187412e ("alpha: don't leak hardware-fabricated FP exception bits to user space") for 5.15, 6.1 and 6.6 that updates the do_entIF() call site as well? Otherwise the fix stays out of those three trees.

Signature · 2 lines
Thanks,
Sasha