6.18.40-rc1 review
Subsystems (13)
Greg Kroah-Hartman
maintainerPATCH 263/1611 crypto: inside-secure/eip93 - Add check for devm_request_threaded_irq
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aleksander Jan Bajkowski <[email protected]>
[ Upstream commit 85a61bf9145d4097c740ffcf3aa832d930a8913b ]
As the potential failure of the devm_request_threaded_irq(), it should be better to check the return value and return error if fails.
--- drivers/crypto/inside-secure/eip93/eip93-main.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/crypto/inside-secure/eip93/eip93-main.c +2 -0
@@ -433,6 +433,8 @@ static int eip93_crypto_probe(struct platform_device *pdev) ret =devm_request_threaded_irq (eip93->dev, eip93->irq, eip93_irq_handler,NULL ,IRQF_ONESHOT ,dev_name (eip93->dev), eip93); +if (ret) +return ret; eip93->ring =devm_kcalloc (eip93->dev,1 ,sizeof (*eip93->ring),GFP_KERNEL );if (!eip93->ring)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 264/1611 crypto: tegra - Fix dma_free_coherent size error
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Herbert Xu <[email protected]>
[ Upstream commit 03215b8457784540acc741e6331e355b62c6c8ab ]
When freeing a coherent DMA buffer, the size must match the value that was used during the allocation.
Unfortunately the size field in the tegra driver gets overwritten by this point so it no longer matches and creates a warning.
Fix this by saving a copy of the size on the stack.
Note that the ccm function actually mixes up the inbuf and outbuf sizes, but it doesn't matter because the two sizes are actually equal.
--- drivers/crypto/tegra/tegra-se-aes.c | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-)
drivers/crypto/tegra/tegra-se-aes.c +16 -12
@@ -1201,6 +1201,7 @@ static int tegra_ccm_do_one_req(struct crypto_engine *engine, void *areq)struct crypto_aead *tfm =crypto_aead_reqtfm (req);struct tegra_aead_ctx *ctx =crypto_aead_ctx (tfm);struct tegra_se *se = ctx->se; +unsigned int bufsize;int ret; ret =tegra_ccm_crypt_init (req, se, rctx);
@@ -1210,14 +1211,15 @@ static int tegra_ccm_do_one_req(struct crypto_engine *engine, void *areq) rctx->key_id = ctx->key_id;/* Allocate buffers required */ - rctx->inbuf.size = rctx->assoclen + rctx->authsize + rctx->cryptlen +100 ; - rctx->inbuf.buf =dma_alloc_coherent (ctx->se->dev, rctx->inbuf.size, + bufsize = rctx->assoclen + rctx->authsize + rctx->cryptlen +100 ; + rctx->inbuf.size = bufsize; + rctx->inbuf.buf =dma_alloc_coherent (ctx->se->dev, bufsize, &rctx->inbuf.addr,GFP_KERNEL );if (!rctx->inbuf.buf) goto out_finalize; - rctx->outbuf.size = rctx->assoclen + rctx->authsize + rctx->cryptlen +100 ; - rctx->outbuf.buf =dma_alloc_coherent (ctx->se->dev, rctx->outbuf.size, + rctx->outbuf.size = bufsize; + rctx->outbuf.buf =dma_alloc_coherent (ctx->se->dev, bufsize, &rctx->outbuf.addr,GFP_KERNEL );if (!rctx->outbuf.buf) { ret = -ENOMEM ;
@@ -1254,11 +1256,11 @@ static int tegra_ccm_do_one_req(struct crypto_engine *engine, void *areq) } out: -dma_free_coherent (ctx->se->dev, rctx->inbuf.size, +dma_free_coherent (ctx->se->dev, bufsize, rctx->outbuf.buf, rctx->outbuf.addr); out_free_inbuf: -dma_free_coherent (ctx->se->dev, rctx->outbuf.size, +dma_free_coherent (ctx->se->dev, bufsize, rctx->inbuf.buf, rctx->inbuf.addr);if (tegra_key_is_reserved (rctx->key_id))
@@ -1278,6 +1280,7 @@ static int tegra_gcm_do_one_req(struct crypto_engine *engine, void *areq)struct crypto_aead *tfm =crypto_aead_reqtfm (req);struct tegra_aead_ctx *ctx =crypto_aead_ctx (tfm);struct tegra_aead_reqctx *rctx =aead_request_ctx (req); +unsigned int bufsize;int ret; rctx->src_sg = req->src;
@@ -1296,16 +1299,17 @@ static int tegra_gcm_do_one_req(struct crypto_engine *engine, void *areq) rctx->key_id = ctx->key_id;/* Allocate buffers required */ - rctx->inbuf.size = rctx->assoclen + rctx->authsize + rctx->cryptlen; - rctx->inbuf.buf =dma_alloc_coherent (ctx->se->dev, rctx->inbuf.size, + bufsize = rctx->assoclen + rctx->authsize + rctx->cryptlen; + rctx->inbuf.size = bufsize; + rctx->inbuf.buf =dma_alloc_coherent (ctx->se->dev, bufsize, &rctx->inbuf.addr,GFP_KERNEL );if (!rctx->inbuf.buf) { ret = -ENOMEM ; goto out_finalize; } - rctx->outbuf.size = rctx->assoclen + rctx->authsize + rctx->cryptlen; - rctx->outbuf.buf =dma_alloc_coherent (ctx->se->dev, rctx->outbuf.size, + rctx->outbuf.size = bufsize; + rctx->outbuf.buf =dma_alloc_coherent (ctx->se->dev, bufsize, &rctx->outbuf.addr,GFP_KERNEL );if (!rctx->outbuf.buf) { ret = -ENOMEM ;
@@ -1342,11 +1346,11 @@ static int tegra_gcm_do_one_req(struct crypto_engine *engine, void *areq) ret =tegra_gcm_do_verify (ctx->se, rctx); out: -dma_free_coherent (ctx->se->dev, rctx->outbuf.size, +dma_free_coherent (ctx->se->dev, bufsize, rctx->outbuf.buf, rctx->outbuf.addr); out_free_inbuf: -dma_free_coherent (ctx->se->dev, rctx->inbuf.size, +dma_free_coherent (ctx->se->dev, bufsize, rctx->inbuf.buf, rctx->inbuf.addr);if (tegra_key_is_reserved (rctx->key_id))
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 265/1611 crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Herbert Xu <[email protected]>
[ Upstream commit 690a5f9e5c972a580565ce544ed1627ccf1e84de ]
Ensure the ENOMEM error value is set when the input buffer allocation fails in tegra_ccm_do_one_req.
--- drivers/crypto/tegra/tegra-se-aes.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/crypto/tegra/tegra-se-aes.c +2 -3
@@ -1215,16 +1215,15 @@ static int tegra_ccm_do_one_req(struct crypto_engine *engine, void *areq) rctx->inbuf.size = bufsize; rctx->inbuf.buf =dma_alloc_coherent (ctx->se->dev, bufsize, &rctx->inbuf.addr,GFP_KERNEL ); + ret = -ENOMEM ;if (!rctx->inbuf.buf) goto out_finalize; rctx->outbuf.size = bufsize; rctx->outbuf.buf =dma_alloc_coherent (ctx->se->dev, bufsize, &rctx->outbuf.addr,GFP_KERNEL ); -if (!rctx->outbuf.buf) { - ret = -ENOMEM ; +if (!rctx->outbuf.buf) goto out_free_inbuf; - }if (!ctx->key_id) { ret = tegra_key_submit_reserved_aes(ctx->se, ctx->key,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 266/1611 sched/deadline: Reject debugfs dl_server writes for offline CPUs
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrea Righi <[email protected]>
[ Upstream commit 4043f549841619a01999bf5d4e0b7931ef87f6cc ]
Writing runtime or period via the per-CPU dl_server debugfs files (/sys/kernel/debug/sched/{fair,ext}_server/cpu*/{runtime,period}) on an offline CPU can trigger two distinct kernel issues:
1) Divide-by-zero in dl_server_apply_params():
Oops: divide error: 0000 [#1] SMP NOPTI RIP: 0010:dl_server_apply_params+0x239/0x3a0 Call Trace: sched_server_write_common.isra.0+0x21a/0x3c0 full_proxy_write+0x78/0xd0 vfs_write+0xe7/0x6e0
Both __dl_sub() and __dl_add() divide by cpus internally, which can be 0 once the CPU has been removed from any active root-domain span (this has been latent since the debugfs interface was introduced).
2) WARN_ON_ONCE in dl_server_start():
WARNING: kernel/sched/deadline.c:1805 at dl_server_start+0x232/0x270
Commit ee6e44dfe6e5 ("sched/deadline: Stop dl_server before CPU goes offline") added this check to catch enqueueing the server on an offline rq.
There's no meaningful semantics for re-configuring the per-CPU dl_server bandwidth while the CPU is offline, so simply reject the write with -EBUSY so userspace gets a clear error.
--- kernel/sched/debug.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/sched/debug.c +3 -0
@@ -376,6 +376,9 @@ static ssize_t sched_fair_server_write(struct file *filp, const char __user *ubureturn -EINVAL ; } +if (!cpu_online (cpu_of (rq))) +return -EBUSY ; +update_rq_clock (rq);dl_server_stop (&rq->fair_server);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 267/1611 drm/msm/dp: fix HPD state status bit shift value
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jessica Zhang <[email protected]>
[ Upstream commit 2e6c2e81d81251623c458a60e2a57447dcbc988e ]
The HPD state status is the 3 most significant bits, not 4 bits of the HPD_INT_STATUS register.
Fix the bit shift macro so that the correct bits are returned in msm_dp_aux_is_link_connected().
Patchwork: https://patchwork.freedesktop.org/patch/727611/
--- drivers/gpu/drm/msm/dp/dp_reg.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/msm/dp/dp_reg.h +2 -2
@@ -68,8 +68,8 @@#define DP_DP_IRQ_HPD_INT_ACK (0x00000002)#define DP_DP_HPD_REPLUG_INT_ACK (0x00000004)#define DP_DP_HPD_UNPLUG_INT_ACK (0x00000008) -#define DP_DP_HPD_STATE_STATUS_BITS_MASK (0x0000000F) -#define DP_DP_HPD_STATE_STATUS_BITS_SHIFT (0x1C) +#define DP_DP_HPD_STATE_STATUS_BITS_MASK (0x00000007) +#define DP_DP_HPD_STATE_STATUS_BITS_SHIFT (0x1D)#define REG_DP_DP_HPD_INT_MASK (0x0000000C)#define DP_DP_HPD_PLUG_INT_MASK (0x00000001)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 268/1611 drm/msm/dp: Fix the ISR_* enum values
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jessica Zhang <[email protected]>
[ Upstream commit 3fbfdc3b1d48cc115a86953e5df0c76cd2efc42b ]
The ISR_HPD_* enum should represent values that can be read from the REG_DP_DP_HPD_INT_STATUS register. Swap ISR_HPD_IO_GLITCH_COUNT and ISR_HPD_REPLUG_COUNT to map them correctly to register values.
While we are at it, correct the spelling for ISR_HPD_REPLUG_COUNT.
Patchwork: https://patchwork.freedesktop.org/patch/727602/
--- drivers/gpu/drm/msm/dp/dp_display.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/msm/dp/dp_display.c +2 -2
@@ -38,9 +38,9 @@ enum {ISR_DISCONNECTED ,ISR_CONNECT_PENDING ,ISR_CONNECTED , -ISR_HPD_REPLUG_COUNT , +ISR_HPD_IO_GLITCH_COUNT ,ISR_IRQ_HPD_PULSE_COUNT , - ISR_HPD_LO_GLITH_COUNT, + ISR_HPD_REPLUG_COUNT, };/* event thread connection state */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 269/1611 EDAC/igen6: Fix call trace due to missing release()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Qiuxu Zhuo <[email protected]>
[ Upstream commit ab1f9d466c7d83ab0d2a529e07984e53b5960dcd ]
When unloading the igen6_edac driver, there is a call trace:
Device '(null)' does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.
WARNING: drivers/base/core.c:2567 at device_release+0x84/0x90, CPU#5: rmmod/127209 ... RIP: 0010:device_release+0x84/0x90 Call Trace: <TASK> kobject_put+0x8c/0x220 put_device+0x17/0x30 igen6_unregister_mcis+0xa2/0xe0 [igen6_edac] igen6_remove+0x82/0xb0 [igen6_edac] ...
Fix the call trace by providing empty release() functions for the memory controller devices.
--- drivers/edac/igen6_edac.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/edac/igen6_edac.c +6 -0
@@ -1255,6 +1255,11 @@ static bool igen6_imc_absent(void __iomem *window)return readl (window +MAD_INTER_CHANNEL_OFFSET ) == ~0 ; } +static void imc_release (struct device *dev) +{ +/* Nothing to do, the 'imc' owns the 'dev' and will also release it. */ +} +static int igen6_register_mci (int mc,void __iomem *window,struct pci_dev *pdev) {struct edac_mc_layer layers[2 ];
@@ -1293,6 +1298,7 @@ static int igen6_register_mci(int mc, void __iomem *window, struct pci_dev *pdev mci->pvt_info = &igen6_pvt->imc[mc]; imc = mci->pvt_info; + imc->dev.release = imc_release;device_initialize (&imc->dev);/* * EDAC core uses mci->pdev(pointer of structure device) as
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 270/1611 EDAC/{skx_common,skx}: Fix UBSAN shift-out-of-bounds in skx_get_dimm_info
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: zhoumin <[email protected]>
[ Upstream commit c63ed6e1f5fe648a4a099b6717f679999be482ef ]
When the skx_get_dimm_attr() helper returns -EINVAL, skx_get_dimm_info() does not validate these return values before using them in a shift operation:
size = ((1ull << (rows + cols + ranks)) * banks) >> (20 - 3);
If all three values are -22, the shift exponent becomes -66, triggering a UBSAN shift-out-of-bounds error:
UBSAN: shift-out-of-bounds in drivers/edac/skx_common.c
shift exponent -66 is negative--- drivers/edac/skx_common.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/edac/skx_common.c +3 -0
@@ -452,6 +452,9 @@ int skx_get_dimm_info(u32 mtr, u32 mcmtr, u32 amap, struct dimm_info *dimm, rows =numrow (mtr); cols = imc->hbm_mc ?6 :numcol (mtr); +if (ranks <0 || rows <0 || cols <0 ) +return 0 ; +if (imc->hbm_mc) { banks =32 ; mtype =MEM_HBM2 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 271/1611 arm64: dts: st: Fix SAI addresses on stm32mp251
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marek Vasut <[email protected]>
[ Upstream commit fba4a31a7f3b6b29b01c83180f83e7ed4c398738 ]
The second field of SAI register addresses should be within 0x3f0 bytes from the start of the SAI register addresses, the second field describes the ID registers which are at that addrses. Currently, the second field does not match RM, fix it.
--- arch/arm64/boot/dts/st/stm32mp251.dtsi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
arch/arm64/boot/dts/st/stm32mp251.dtsi +4 -4
@@ -1176,7 +1176,7 @@ spi5: spi@40280000 { sai1: sai@40290000 { compatible = "st,stm32mp25-sai"; - reg = <0x40290000 0x4>, <0x4029a3f0 0x10>; + reg = <0x40290000 0x4>, <0x402903f0 0x10>; ranges = <0 0x40290000 0x400>; #address-cells = <1>; #size-cells = <1>;
@@ -1210,7 +1210,7 @@ sai1b: audio-controller@40290024 { sai2: sai@402a0000 { compatible = "st,stm32mp25-sai"; - reg = <0x402a0000 0x4>, <0x402aa3f0 0x10>; + reg = <0x402a0000 0x4>, <0x402a03f0 0x10>; ranges = <0 0x402a0000 0x400>; #address-cells = <1>; #size-cells = <1>;
@@ -1244,7 +1244,7 @@ sai2b: audio-controller@402a0024 { sai3: sai@402b0000 { compatible = "st,stm32mp25-sai"; - reg = <0x402b0000 0x4>, <0x402ba3f0 0x10>; + reg = <0x402b0000 0x4>, <0x402b03f0 0x10>; ranges = <0 0x402b0000 0x400>; #address-cells = <1>; #size-cells = <1>;
@@ -1336,7 +1336,7 @@ usart1: serial@40330000 { sai4: sai@40340000 { compatible = "st,stm32mp25-sai"; - reg = <0x40340000 0x4>, <0x4034a3f0 0x10>; + reg = <0x40340000 0x4>, <0x403403f0 0x10>; ranges = <0 0x40340000 0x400>; #address-cells = <1>; #size-cells = <1>;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 272/1611 RDMA/umem: Add ib_umem_is_contiguous() stub for !CONFIG_INFINIBAND_USER_MEM
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jiri Pirko <[email protected]>
[ Upstream commit 2cc10972f5f4f123e5a7658824db4f7b5abfc410 ]
ib_umem_is_contiguous() is defined under #ifdef CONFIG_INFINIBAND_USER_MEM, but the #else branch lacks a stub.
Add the missing inline to fix potential broken build.
--- include/rdma/ib_umem.h | 4 ++++ 1 file changed, 4 insertions(+)
include/rdma/ib_umem.h +4 -0
@@ -181,6 +181,10 @@ static inline unsigned long ib_umem_find_best_pgoff(struct ib_umem *umem, {return 0 ; } +static inline bool ib_umem_is_contiguous (struct ib_umem *umem) +{ +return false; +}static inline struct ib_umem_dmabuf *ib_umem_dmabuf_get(struct ib_device *device, unsigned long offset,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 273/1611 RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tristan Madani <[email protected]>
[ Upstream commit 22b8fbded65b8c441b634a185f8da67657df6c50 ]
get_srq_wqe() reads wqe->dma.num_sge from the shared receive queue buffer, which is mapped into userspace. It validates num_sge against max_sge, but then re-reads the same field to calculate the memcpy size. A concurrent userspace thread can modify num_sge between validation and use, causing a heap buffer overflow when copying the WQE into qp->resp.srq_wqe.
Read num_sge into a local variable and use it for both the bounds check and the size calculation.
--- drivers/infiniband/sw/rxe/rxe_resp.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/infiniband/sw/rxe/rxe_resp.c +4 -2
@@ -263,6 +263,7 @@ static enum resp_states get_srq_wqe(struct rxe_qp *qp)struct rxe_recv_wqe *wqe;struct ib_event ev;unsigned int count; +unsigned int num_sge;size_t size;unsigned long flags;
@@ -278,12 +279,13 @@ static enum resp_states get_srq_wqe(struct rxe_qp *qp) }/* don't trust user space data */ -if (unlikely (wqe->dma.num_sge > srq->rq.max_sge)) { + num_sge = wqe->dma.num_sge; +if (unlikely (num_sge > srq->rq.max_sge)) {spin_unlock_irqrestore (&srq->rq.consumer_lock, flags);rxe_dbg_qp (qp,"invalid num_sge in SRQ entry\n" );return RESPST_ERR_MALFORMED_WQE ; } - size =sizeof (*wqe) + wqe->dma.num_sge*sizeof (struct rxe_sge ); + size =sizeof (*wqe) + num_sge *sizeof (struct rxe_sge );memcpy (&qp->resp.srq_wqe, wqe, size); qp->resp.wqe = &qp->resp.srq_wqe.wqe;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 274/1611 RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tristan Madani <[email protected]>
[ Upstream commit d6ab440240a04b8737ee4c7bb21af9182e451733 ]
For non-SRQ QPs, the responder reads WQE fields directly from the shared queue buffer mapped into userspace. This allows a malicious user to modify fields like num_sge or sge entries while the kernel is processing the WQE, leading to out-of-bounds reads in rxe_resp_check_length() and copy_data().
Introduce get_recv_wqe() that validates num_sge and copies the WQE to a kernel-local buffer before processing, matching the approach already used for SRQ WQEs in get_srq_wqe(). The srq_wqe buffer is reused since SRQ and non-SRQ paths are mutually exclusive per QP.
--- drivers/infiniband/sw/rxe/rxe_resp.c | 27 ++++++++++++++++++++++++--- 1 file changed, 24 insertions(+), 3 deletions(-)
drivers/infiniband/sw/rxe/rxe_resp.c +24 -3
@@ -309,6 +309,29 @@ static enum resp_states get_srq_wqe(struct rxe_qp *qp)return RESPST_CHK_LENGTH ; } +static enum resp_states rxe_get_recv_wqe (struct rxe_qp *qp) +{ +struct rxe_queue *q = qp->rq.queue; +struct rxe_recv_wqe *wqe; +unsigned int num_sge; +size_t size; + + wqe =queue_head (q,QUEUE_TYPE_FROM_CLIENT ); +if (!wqe) +return RESPST_ERR_RNR ; + + num_sge = wqe->dma.num_sge; +if (unlikely (num_sge > qp->rq.max_sge)) { +rxe_dbg_qp (qp,"invalid num_sge in recv WQE\n" ); +return RESPST_ERR_MALFORMED_WQE ; + } + size =sizeof (*wqe) + num_sge *sizeof (struct rxe_sge ); +memcpy (&qp->resp.srq_wqe, wqe, size); + + qp->resp.wqe = &qp->resp.srq_wqe.wqe; +return RESPST_CHK_LENGTH ; +} +static enum resp_states check_resource (struct rxe_qp *qp,struct rxe_pkt_info *pkt) {
@@ -329,9 +352,7 @@ static enum resp_states check_resource(struct rxe_qp *qp,if (srq)return get_srq_wqe (qp); - qp->resp.wqe =queue_head (qp->rq.queue, -QUEUE_TYPE_FROM_CLIENT ); -return (qp->resp.wqe) ?RESPST_CHK_LENGTH :RESPST_ERR_RNR ; +return rxe_get_recv_wqe (qp); }return RESPST_CHK_LENGTH ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 275/1611 Revert "media: venus: hfi_platform: Correct supported codecs for sc7280"
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Baryshkov <[email protected]>
[ Upstream commit 3eb9ba0da0ab73e135f93ffccf07381ba11f100e ]
This reverts commit c0ab2901fc68 ("media: venus: hfi_platform: Correct supported codecs for sc7280"). The codecs might be deprecated, but they still work (somewhat) perfectly and don't cause any issues with the rest of the system. Reenable VP8 codecs by reverting the offending commit.
Tested with fluster:
|Test|FFmpeg-VP8-v4l2m2m|GStreamer-VP8-V4L2| |TOTAL|50/61|50/61| |TOTAL TIME|12.171s|11.824s|
--- .../media/platform/qcom/venus/hfi_parser.c | 6 ++--- .../media/platform/qcom/venus/hfi_platform.c | 24 ------------------- .../media/platform/qcom/venus/hfi_platform.h | 2 -- 3 files changed, 2 insertions(+), 30 deletions(-)
drivers/media/platform/qcom/venus/hfi_parser.c +2 -4
@@ -268,7 +268,6 @@ static int hfi_platform_parser(struct venus_core *core, struct venus_inst *inst)const struct hfi_plat_caps *caps =NULL ;u32 enc_codecs, dec_codecs, count =0 ;unsigned int entries; -int ret; plat =hfi_platform_get (core->res->hfi_version);if (!plat)
@@ -277,9 +276,8 @@ static int hfi_platform_parser(struct venus_core *core, struct venus_inst *inst)if (inst)return 0 ; - ret =hfi_platform_get_codecs (core, &enc_codecs, &dec_codecs, &count); -if (ret) -return ret; +if (plat->codecs) + plat->codecs (core, &enc_codecs, &dec_codecs, &count);if (plat->capabilities) caps = plat->capabilities (core, &entries);
drivers/media/platform/qcom/venus/hfi_platform.c +0 -24
@@ -2,9 +2,7 @@/* * Copyright (c) 2020, The Linux Foundation. All rights reserved. */ -#include <linux/of.h> #include "hfi_platform.h" -#include "core.h" const struct hfi_platform *hfi_platform_get (enum hfi_version version) {
@@ -73,25 +71,3 @@ hfi_platform_get_codec_lp_freq(struct venus_core *core,return freq; } - -int -hfi_platform_get_codecs (struct venus_core *core,u32 *enc_codecs, -u32 *dec_codecs,u32 *count) -{ -const struct hfi_platform *plat; - - plat =hfi_platform_get (core->res->hfi_version); -if (!plat) -return -EINVAL ; - -if (plat->codecs) - plat->codecs (core, enc_codecs, dec_codecs, count); - -if (IS_IRIS2_1 (core)) { - *enc_codecs &= ~HFI_VIDEO_CODEC_VP8 ; - *dec_codecs &= ~HFI_VIDEO_CODEC_VP8 ; - } - -return 0 ; -} -
drivers/media/platform/qcom/venus/hfi_platform.h +0 -2
@@ -74,6 +74,4 @@ unsigned long hfi_platform_get_codec_vsp_freq(struct venus_core *core,unsigned long hfi_platform_get_codec_lp_freq (struct venus_core *core,enum hfi_version version,u32 codec,u32 session_type); -int hfi_platform_get_codecs (struct venus_core *core,u32 *enc_codecs, -u32 *dec_codecs,u32 *count);#endif
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 276/1611 media: qcom: venus: drop extra padding in NV12 raw size calculation
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Renjiang Han <[email protected]>
[ Upstream commit e1c9adabb268cc5d56723b7df1da49e59070f309 ]
get_framesize_raw_nv12() currently adds SZ_4K to the UV plane size and an additional SZ_8K to the total buffer size. This inflates the calculated sizeimage and leads userspace to over-allocate buffers without a clear requirement.
Remove the extra SZ_4K/SZ_8K padding and compute the NV12 size as the sum of Y and UV planes, keeping the final ALIGN(size, SZ_4K) intact.
--- drivers/media/platform/qcom/venus/helpers.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/media/platform/qcom/venus/helpers.c +2 -2
@@ -954,8 +954,8 @@ static u32 get_framesize_raw_nv12(u32 width, u32 height) uv_sclines =ALIGN (((height +1 ) >>1 ),16 ); y_plane = y_stride * y_sclines; - uv_plane = uv_stride * uv_sclines +SZ_4K ; - size = y_plane + uv_plane +SZ_8K ; + uv_plane = uv_stride * uv_sclines; + size = y_plane + uv_plane;return ALIGN (size,SZ_4K ); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 277/1611 media: qcom: venus: relax encoder frame/blur dimension steps on v4
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Renjiang Han <[email protected]>
[ Upstream commit 35428ae3a6a40912f1f7b47bb6c65f1a63d0b8f8 ]
Encoder HFI capabilities on v4 advertise a 16-pixel step for frame and blur dimensions. This is overly restrictive and can cause userspace caps negotiation to fail even for valid resolutions.
Relax the advertised step size to 1 and keep alignment enforcement in buffer layout and size calculations.
--- .../platform/qcom/venus/hfi_platform_v4.c | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-)
drivers/media/platform/qcom/venus/hfi_platform_v4.c +10 -10
@@ -136,8 +136,8 @@ static const struct hfi_plat_caps caps[] = { .codec = HFI_VIDEO_CODEC_H264, .domain = VIDC_SESSION_TYPE_ENC, .cap_bufs_mode_dynamic = true, - .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 96, 4096, 16}, - .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 96, 4096, 16}, + .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 96, 4096, 1}, + .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 96, 4096, 1}, .caps[2] = {HFI_CAPABILITY_MBS_PER_FRAME, 1, 36864, 1}, .caps[3] = {HFI_CAPABILITY_BITRATE, 1, 120000000, 1}, .caps[4] = {HFI_CAPABILITY_SCALE_X, 8192, 65536, 1},
@@ -173,8 +173,8 @@ static const struct hfi_plat_caps caps[] = { .codec = HFI_VIDEO_CODEC_HEVC, .domain = VIDC_SESSION_TYPE_ENC, .cap_bufs_mode_dynamic = true, - .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 96, 4096, 16}, - .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 96, 4096, 16}, + .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 96, 4096, 1}, + .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 96, 4096, 1}, .caps[2] = {HFI_CAPABILITY_MBS_PER_FRAME, 1, 36864, 1}, .caps[3] = {HFI_CAPABILITY_BITRATE, 1, 120000000, 1}, .caps[4] = {HFI_CAPABILITY_SCALE_X, 8192, 65536, 1},
@@ -195,8 +195,8 @@ static const struct hfi_plat_caps caps[] = { .caps[19] = {HFI_CAPABILITY_RATE_CONTROL_MODES, 0x1000001, 0x1000005, 1}, .caps[20] = {HFI_CAPABILITY_COLOR_SPACE_CONVERSION, 0, 2, 1}, .caps[21] = {HFI_CAPABILITY_ROTATION, 1, 4, 90}, - .caps[22] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 16}, - .caps[23] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 16}, + .caps[22] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 1}, + .caps[23] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 1}, .num_caps = 24, .pl[0] = {HFI_HEVC_PROFILE_MAIN, HFI_HEVC_LEVEL_6 | HFI_HEVC_TIER_HIGH0}, .pl[1] = {HFI_HEVC_PROFILE_MAIN10, HFI_HEVC_LEVEL_6 | HFI_HEVC_TIER_HIGH0},
@@ -210,8 +210,8 @@ static const struct hfi_plat_caps caps[] = { .codec = HFI_VIDEO_CODEC_VP8, .domain = VIDC_SESSION_TYPE_ENC, .cap_bufs_mode_dynamic = true, - .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 96, 4096, 16}, - .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 96, 4096, 16}, + .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 96, 4096, 1}, + .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 96, 4096, 1}, .caps[2] = {HFI_CAPABILITY_MBS_PER_FRAME, 1, 36864, 1}, .caps[3] = {HFI_CAPABILITY_BITRATE, 1, 120000000, 1}, .caps[4] = {HFI_CAPABILITY_SCALE_X, 8192, 65536, 1},
@@ -229,8 +229,8 @@ static const struct hfi_plat_caps caps[] = { .caps[16] = {HFI_CAPABILITY_P_FRAME_QP, 0, 127, 1}, .caps[17] = {HFI_CAPABILITY_MAX_WORKMODES, 1, 2, 1}, .caps[18] = {HFI_CAPABILITY_RATE_CONTROL_MODES, 0x1000001, 0x1000005, 1}, - .caps[19] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 16}, - .caps[20] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 16}, + .caps[19] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 1}, + .caps[20] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 1}, .caps[21] = {HFI_CAPABILITY_COLOR_SPACE_CONVERSION, 0, 2, 1}, .caps[22] = {HFI_CAPABILITY_ROTATION, 1, 4, 90}, .num_caps = 23,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 278/1611 media: qcom: venus: relax encoder frame/blur step size on v6
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Renjiang Han <[email protected]>
[ Upstream commit c53e0550288b2e08b984b24035c471941b7820c7 ]
Encoder HFI capabilities on v6 enforce a 16-pixel step for frame and blur dimensions, which does not reflect actual hardware requirements and can reject valid userspace configurations.
Relax the step size to 1 while leaving min/max limits unchanged.
--- .../media/platform/qcom/venus/hfi_platform_v6.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/media/platform/qcom/venus/hfi_platform_v6.c +8 -8
@@ -173,8 +173,8 @@ static const struct hfi_plat_caps caps[] = { .codec = HFI_VIDEO_CODEC_HEVC, .domain = VIDC_SESSION_TYPE_ENC, .cap_bufs_mode_dynamic = true, - .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 128, 8192, 16}, - .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 128, 8192, 16}, + .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 128, 8192, 1}, + .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 128, 8192, 1}, .caps[2] = {HFI_CAPABILITY_MBS_PER_FRAME, 64, 138240, 1}, .caps[3] = {HFI_CAPABILITY_BITRATE, 1, 160000000, 1}, .caps[4] = {HFI_CAPABILITY_SCALE_X, 8192, 65536, 1},
@@ -195,8 +195,8 @@ static const struct hfi_plat_caps caps[] = { .caps[19] = {HFI_CAPABILITY_RATE_CONTROL_MODES, 0x1000001, 0x1000005, 1}, .caps[20] = {HFI_CAPABILITY_COLOR_SPACE_CONVERSION, 0, 2, 1}, .caps[21] = {HFI_CAPABILITY_ROTATION, 1, 4, 90}, - .caps[22] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 16}, - .caps[23] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 16}, + .caps[22] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 1}, + .caps[23] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 1}, .num_caps = 24, .pl[0] = {HFI_HEVC_PROFILE_MAIN, HFI_HEVC_LEVEL_6 | HFI_HEVC_TIER_HIGH0}, .pl[1] = {HFI_HEVC_PROFILE_MAIN10, HFI_HEVC_LEVEL_6 | HFI_HEVC_TIER_HIGH0},
@@ -210,8 +210,8 @@ static const struct hfi_plat_caps caps[] = { .codec = HFI_VIDEO_CODEC_VP8, .domain = VIDC_SESSION_TYPE_ENC, .cap_bufs_mode_dynamic = true, - .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 128, 4096, 16}, - .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 128, 4096, 16}, + .caps[0] = {HFI_CAPABILITY_FRAME_WIDTH, 128, 4096, 1}, + .caps[1] = {HFI_CAPABILITY_FRAME_HEIGHT, 128, 4096, 1}, .caps[2] = {HFI_CAPABILITY_MBS_PER_FRAME, 64, 36864, 1}, .caps[3] = {HFI_CAPABILITY_BITRATE, 1, 74000000, 1}, .caps[4] = {HFI_CAPABILITY_SCALE_X, 8192, 65536, 1},
@@ -229,8 +229,8 @@ static const struct hfi_plat_caps caps[] = { .caps[16] = {HFI_CAPABILITY_P_FRAME_QP, 0, 127, 1}, .caps[17] = {HFI_CAPABILITY_MAX_WORKMODES, 1, 2, 1}, .caps[18] = {HFI_CAPABILITY_RATE_CONTROL_MODES, 0x1000001, 0x1000005, 1}, - .caps[19] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 16}, - .caps[20] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 16}, + .caps[19] = {HFI_CAPABILITY_BLUR_WIDTH, 96, 4096, 1}, + .caps[20] = {HFI_CAPABILITY_BLUR_HEIGHT, 96, 4096, 1}, .caps[21] = {HFI_CAPABILITY_COLOR_SPACE_CONVERSION, 0, 2, 1}, .caps[22] = {HFI_CAPABILITY_ROTATION, 1, 4, 90}, .num_caps = 23,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 279/1611 amba: use generic driver_override infrastructure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Danilo Krummrich <[email protected]>
[ Upstream commit 1947229f5f2a8d4ecf8c971aca68a1242bb7b37c ]
When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.
Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.
Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
--- drivers/amba/bus.c | 37 ++++++------------------------------- include/linux/amba/bus.h | 5 ----- 2 files changed, 6 insertions(+), 36 deletions(-)
drivers/amba/bus.c +6 -31
@@ -82,33 +82,6 @@ static void amba_put_disable_pclk(struct amba_device *pcdev) } -static ssize_t driver_override_show (struct device *_dev, -struct device_attribute *attr,char *buf) -{ -struct amba_device *dev =to_amba_device (_dev); -ssize_t len; - -device_lock (_dev); - len =sprintf (buf,"%s\n" , dev->driver_override); -device_unlock (_dev); -return len; -} - -static ssize_t driver_override_store (struct device *_dev, -struct device_attribute *attr, -const char *buf,size_t count) -{ -struct amba_device *dev =to_amba_device (_dev); -int ret; - - ret =driver_set_override (_dev, &dev->driver_override, buf, count); -if (ret) -return ret; - -return count; -} -static DEVICE_ATTR_RW (driver_override); - #define amba_attr_func(name,fmt,arg...) \ static ssize_t name##_show(struct device *_dev, \ struct device_attribute *attr, char *buf) \
@@ -126,7 +99,6 @@ amba_attr_func(resource, "\t%016llx\t%016llx\t%016lx\n",static struct attribute *amba_dev_attrs[] = { &dev_attr_id.attr, &dev_attr_resource.attr, - &dev_attr_driver_override.attr,NULL , };ATTRIBUTE_GROUPS (amba_dev);
@@ -209,10 +181,11 @@ static int amba_match(struct device *dev, const struct device_driver *drv) {struct amba_device *pcdev =to_amba_device (dev);const struct amba_driver *pcdrv =to_amba_driver (drv); +int ret;mutex_lock (&pcdev->periphid_lock);if (!pcdev->periphid) { -int ret =amba_read_periphid (pcdev); + ret =amba_read_periphid (pcdev);/* * Returning any error other than -EPROBE_DEFER from bus match
@@ -230,8 +203,9 @@ static int amba_match(struct device *dev, const struct device_driver *drv)mutex_unlock (&pcdev->periphid_lock);/* When driver_override is set, only bind to the matching driver */ -if (pcdev->driver_override) -return !strcmp (pcdev->driver_override, drv->name); + ret =device_match_driver_override (dev, drv); +if (ret >=0 ) +return ret;return amba_lookup (pcdrv->id_table, pcdev) !=NULL ; }
@@ -439,6 +413,7 @@ static const struct dev_pm_ops amba_pm = {const struct bus_type amba_bustype = { .name ="amba" , .dev_groups = amba_dev_groups, + .driver_override = true, .match = amba_match, .uevent = amba_uevent, .probe = amba_probe,
include/linux/amba/bus.h +0 -5
@@ -71,11 +71,6 @@ struct amba_device {unsigned int cid;struct amba_cs_uci_id uci;unsigned int irq[AMBA_NR_IRQS ]; -/* -* Driver name to force a match. Do not set directly, because core -* frees it. Use driver_set_override() to set or clear it. -*/ -const char *driver_override; };struct amba_driver {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 280/1611 cdx: use generic driver_override infrastructure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Danilo Krummrich <[email protected]>
[ Upstream commit d541aa1897f67f4f14c805785bff894bcc61dca1 ]
When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.
Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.
Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
--- drivers/cdx/cdx.c | 40 +++++-------------------------------- include/linux/cdx/cdx_bus.h | 4 ---- 2 files changed, 5 insertions(+), 39 deletions(-)
drivers/cdx/cdx.c +5 -35
@@ -156,8 +156,6 @@ static int cdx_unregister_device(struct device *dev, }else {cdx_destroy_res_attr (cdx_dev,MAX_CDX_DEV_RESOURCES );debugfs_remove_recursive (cdx_dev->debugfs_dir); -kfree (cdx_dev->driver_override); - cdx_dev->driver_override =NULL ; }/*
@@ -268,6 +266,7 @@ static int cdx_bus_match(struct device *dev, const struct device_driver *drv)const struct cdx_driver *cdx_drv =to_cdx_driver (drv);const struct cdx_device_id *found_id =NULL ;const struct cdx_device_id *ids; +int ret;if (cdx_dev->is_bus)return false;
@@ -275,7 +274,8 @@ static int cdx_bus_match(struct device *dev, const struct device_driver *drv) ids = cdx_drv->match_id_table;/* When driver_override is set, only bind to the matching driver */ -if (cdx_dev->driver_override &&strcmp (cdx_dev->driver_override, drv->name)) + ret =device_match_driver_override (dev, drv); +if (ret ==0 )return false; found_id =cdx_match_id (ids, cdx_dev);
@@ -289,7 +289,7 @@ static int cdx_bus_match(struct device *dev, const struct device_driver *drv)*/ if (!found_id->override_only)return true; -if (cdx_dev->driver_override) +if (ret >0 )return true; ids = found_id +1 ;
@@ -453,36 +453,6 @@ static ssize_t modalias_show(struct device *dev, struct device_attribute *attr, }static DEVICE_ATTR_RO (modalias); -static ssize_t driver_override_store (struct device *dev, -struct device_attribute *attr, -const char *buf,size_t count) -{ -struct cdx_device *cdx_dev =to_cdx_device (dev); -int ret; - -if (WARN_ON (dev->bus != &cdx_bus_type)) -return -EINVAL ; - - ret =driver_set_override (dev, &cdx_dev->driver_override, buf, count); -if (ret) -return ret; - -return count; -} - -static ssize_t driver_override_show (struct device *dev, -struct device_attribute *attr,char *buf) -{ -struct cdx_device *cdx_dev =to_cdx_device (dev); -ssize_t len; - -device_lock (dev); - len =sysfs_emit (buf,"%s\n" , cdx_dev->driver_override); -device_unlock (dev); -return len; -} -static DEVICE_ATTR_RW (driver_override); -static ssize_t enable_store (struct device *dev,struct device_attribute *attr,const char *buf,size_t count) {
@@ -552,7 +522,6 @@ static struct attribute *cdx_dev_attrs[] = { &dev_attr_class.attr, &dev_attr_revision.attr, &dev_attr_modalias.attr, - &dev_attr_driver_override.attr, NULL, };
@@ -653,6 +622,7 @@ ATTRIBUTE_GROUPS(cdx_bus);struct bus_type cdx_bus_type = { .name ="cdx" , + .driver_override = true, .match = cdx_bus_match, .probe = cdx_probe, .remove = cdx_remove,
include/linux/cdx/cdx_bus.h +0 -4
@@ -137,9 +137,6 @@ struct cdx_controller {* @enabled: is this bus enabled * @msi_dev_id: MSI Device ID associated with CDX device * @num_msi: Number of MSI's supported by the device -* @driver_override: driver name to force a match; do not set directly, -* because core frees it; use driver_set_override() to -* set or clear it. * @irqchip_lock: lock to synchronize irq/msi configuration * @msi_write_pending: MSI write pending for this device */
@@ -165,7 +162,6 @@ struct cdx_device {bool enabled;u32 msi_dev_id;u32 num_msi; -const char *driver_override;struct mutex irqchip_lock;bool msi_write_pending; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 281/1611 Drivers: hv: vmbus: use generic driver_override infrastructure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Danilo Krummrich <[email protected]>
[ Upstream commit 331d8900121a1d74ecd45cd2db742ddcb5a0a565 ]
When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.
Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.
Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
--- drivers/hv/vmbus_drv.c | 43 ++++++++++-------------------------------- include/linux/hyperv.h | 5 ----- 2 files changed, 10 insertions(+), 38 deletions(-)
drivers/hv/vmbus_drv.c +10 -33
@@ -550,34 +550,6 @@ static ssize_t device_show(struct device *dev, }static DEVICE_ATTR_RO (device); -static ssize_t driver_override_store (struct device *dev, -struct device_attribute *attr, -const char *buf,size_t count) -{ -struct hv_device *hv_dev =device_to_hv_device (dev); -int ret; - - ret =driver_set_override (dev, &hv_dev->driver_override, buf, count); -if (ret) -return ret; - -return count; -} - -static ssize_t driver_override_show (struct device *dev, -struct device_attribute *attr,char *buf) -{ -struct hv_device *hv_dev =device_to_hv_device (dev); -ssize_t len; - -device_lock (dev); - len =sysfs_emit (buf,"%s\n" , hv_dev->driver_override); -device_unlock (dev); - -return len; -} -static DEVICE_ATTR_RW (driver_override); -/* Set up per device attributes in /sys/bus/vmbus/devices/<bus device> */ static struct attribute *vmbus_dev_attrs[] = { &dev_attr_id.attr,
@@ -608,7 +580,6 @@ static struct attribute *vmbus_dev_attrs[] = { &dev_attr_channel_vp_mapping.attr, &dev_attr_vendor.attr, &dev_attr_device.attr, - &dev_attr_driver_override.attr, NULL, };
@@ -720,9 +691,11 @@ static const struct hv_vmbus_device_id *hv_vmbus_get_id(const struct hv_driver * {const guid_t *guid = &dev->dev_type;const struct hv_vmbus_device_id *id; +int ret; -/* When driver_override is set, only bind to the matching driver */ -if (dev->driver_override &&strcmp (dev->driver_override, drv->name)) +/* If a driver override is set, only bind to the matching driver */ + ret =device_match_driver_override (&dev->device, &drv->driver); +if (ret ==0 )return NULL ;/* Look at the dynamic ids first, before the static ones */
@@ -730,8 +703,11 @@ static const struct hv_vmbus_device_id *hv_vmbus_get_id(const struct hv_driver *if (!id) id =hv_vmbus_dev_match (drv->id_table, guid); -/* driver_override will always match, send a dummy id */ -if (!id && dev->driver_override) +/* +* If there's a matching driver override, this function should succeed, +* thus return a dummy device ID if no matching ID is found. +*/ +if (!id && ret >0 ) id = &vmbus_device_null;return id;
@@ -1033,6 +1009,7 @@ static const struct dev_pm_ops vmbus_pm = {/* The one and only one */ static const struct bus_type hv_bus = { .name ="vmbus" , + .driver_override = true, .match = vmbus_match, .shutdown = vmbus_shutdown, .remove = vmbus_remove,
include/linux/hyperv.h +0 -5
@@ -1272,11 +1272,6 @@ struct hv_device {u16 device_id;struct device device; -/* -* Driver name to force a match. Do not set directly, because core -* frees it. Use driver_set_override() to set or clear it. -*/ -const char *driver_override;struct vmbus_channel *channel;struct kset *channels_kset;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 282/1611 rpmsg: use generic driver_override infrastructure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Danilo Krummrich <[email protected]>
[ Upstream commit 55ced13c42921714e90f8fae94b6ed803330dc6a ]
When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.
Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.
Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
--- drivers/rpmsg/qcom_glink_native.c | 2 -- drivers/rpmsg/rpmsg_core.c | 43 +++++-------------------------- drivers/rpmsg/virtio_rpmsg_bus.c | 1 - include/linux/rpmsg.h | 4 --- 4 files changed, 7 insertions(+), 43 deletions(-)
drivers/rpmsg/qcom_glink_native.c +0 -2
@@ -1618,7 +1618,6 @@ static void qcom_glink_rpdev_release(struct device *dev) {struct rpmsg_device *rpdev =to_rpmsg_device (dev); -kfree (rpdev->driver_override);kfree (rpdev); }
@@ -1870,7 +1869,6 @@ static void qcom_glink_device_release(struct device *dev)/* Release qcom_glink_alloc_channel() reference */ kref_put (&channel->refcount, qcom_glink_channel_release); -kfree (rpdev->driver_override);kfree (rpdev); }
drivers/rpmsg/rpmsg_core.c +7 -36
81 lines not on this page · raw message
drivers/rpmsg/virtio_rpmsg_bus.c +0 -1
@@ -372,7 +372,6 @@ static void virtio_rpmsg_release_device(struct device *dev)struct rpmsg_device *rpdev =to_rpmsg_device (dev);struct virtio_rpmsg_channel *vch =to_virtio_rpmsg_channel (rpdev); -kfree (rpdev->driver_override);kfree (vch); }
include/linux/rpmsg.h +0 -4
@@ -41,9 +41,6 @@ struct rpmsg_channel_info {* rpmsg_device - device that belong to the rpmsg bus * @dev: the device struct * @id: device id (used to match between rpmsg drivers and devices) -* @driver_override: driver name to force a match; do not set directly, -* because core frees it; use driver_set_override() to -* set or clear it. * @src: local address * @dst: destination address * @ept: the rpmsg endpoint of this channel
@@ -53,7 +50,6 @@ struct rpmsg_channel_info {struct rpmsg_device {struct device dev;struct rpmsg_device_id id; -const char *driver_override;u32 src;u32 dst;struct rpmsg_endpoint *ept;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 283/1611 md/raid10: reset read_slot when reusing r10bio for discard
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chen Cheng <[email protected]>
[ Upstream commit 6b8a26af065ddc93de2aa5c9f0df98dce9723442 ]
put_all_bios() always drops devs[i].bio, but it only drops devs[i].repl_bio when r10_bio->read_slot < 0. If discard reuses an r10bio that was previously used for a read, read_slot can still be non-negative, and discard cleanup can skip bio_put() on repl_bio.
Reset read_slot to -1 when preparing an r10bio for discard so the replacement bio is always released correctly.
--- drivers/md/raid10.c | 1 + 1 file changed, 1 insertion(+)
drivers/md/raid10.c +1 -0
@@ -1727,6 +1727,7 @@ static int raid10_handle_discard(struct mddev *mddev, struct bio *bio) r10_bio->mddev = mddev; r10_bio->state =0 ; r10_bio->sectors =0 ; + r10_bio->read_slot =-1 ;memset (r10_bio->devs,0 ,sizeof (r10_bio->devs[0 ]) * geo->raid_disks);wait_blocked_dev (mddev, r10_bio);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 284/1611 raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Abd-Alrhman Masalkhi <[email protected]>
[ Upstream commit 909d9dc3b5730c8ed7b764c68bc788342df2a07b ]
In raid1_write_request(), each per-mirror loop iteration begins by incrementing rdev->nr_pending. If a REQ_ATOMIC write encounters a badblock within the requested range, the code jumps to err_handle without dropping the reference taken for the current mirror.
err_handle's cleanup loop will only decrements for k < i and r1_bio->bios[k] is non-NULL. The current slot is therefore skipped, leaving its nr_pending reference leaked permanently. The reference prevents the rdev from ever being removed, since raid1_remove_conf() refuses to remove an rdev with nr_pending > 0.
Fix this by calling rdev_dec_pending() before jumping to err_handle.
--- drivers/md/raid1.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/md/raid1.c +3 -1
@@ -1581,8 +1581,10 @@ static void raid1_write_request(struct mddev *mddev, struct bio *bio,* complexity of supporting that is not worth * the benefit. */ -if (bio->bi_opf &REQ_ATOMIC ) +if (bio->bi_opf &REQ_ATOMIC ) { +rdev_dec_pending (rdev, mddev); goto err_handle; + } good_sectors = first_bad - r1_bio->sector;if (good_sectors < max_sectors)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 285/1611 bpf: fix BPF_PROG_QUERY OOB write and cgroup backward compat
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuyang Huang <[email protected]>
[ Upstream commit 21c4b99b27f3f85b89256e81b3e997dec0a460d0 ]
BPF_PROG_QUERY writes back the 'query.revision' field unconditionally to userspace. If userspace passes a smaller 'bpf_attr' structure (e.g. 40 bytes, which was the layout before the addition of 'query.revision'), the kernel performs an out-of-bounds write.
Fix this by propagating the user-provided attribute size 'uattr_size' down to the cgroup query handlers, and conditionally skipping writing the revision field to userspace when the provided buffer size is insufficient.
query.revision in bpf_mprog_query is structurally identical to the cgroup case: a late tail field, written unconditionally.
But the backward-compat hazard is not the same.
The min-historical-size test is per command, and bpf_mprog_query only serves attach types that were born with revision in the struct:
- tcx_prog_query -> BPF_TCX_INGRESS/EGRESS
- netkit_prog_query -> BPF_NETKIT_PRIMARY/PEER
tcx, netkit, the revision field, and bpf_mprog_query itself all landed in the same v6.6 merge window (053c8e1f235d added the mprog query API + revision; tcx in e420bed02507, netkit in 35dfaad7188c). There has never been a tcx/netkit BPF_PROG_QUERY userspace that doesn't know about revision. So for these commands the minimum legitimate struct already covers offset 56-64 — no old binary can be broken here.
Contrast with cgroup: BPF_PROG_QUERY on cgroup attach types shipped in 2017; revision write-back was bolted on years later (120933984460). That path has a real population of pre-revision callers.
--- include/linux/bpf-cgroup.h | 5 +++-- kernel/bpf/cgroup.c | 13 +++++++------ kernel/bpf/syscall.c | 6 +++--- 3 files changed, 13 insertions(+), 11 deletions(-)
include/linux/bpf-cgroup.h +3 -2
@@ -418,7 +418,7 @@ int cgroup_bpf_prog_detach(const union bpf_attr *attr, enum bpf_prog_type ptype);int cgroup_bpf_link_attach (const union bpf_attr *attr,struct bpf_prog *prog);int cgroup_bpf_prog_query (const union bpf_attr *attr, -union bpf_attr __user *uattr); +union bpf_attr __user *uattr,u32 uattr_size);const struct bpf_func_proto *cgroup_common_func_proto (enum bpf_func_id func_id,const struct bpf_prog *prog);
@@ -449,7 +449,8 @@ static inline int cgroup_bpf_link_attach(const union bpf_attr *attr, }static inline int cgroup_bpf_prog_query (const union bpf_attr *attr, -union bpf_attr __user *uattr) +union bpf_attr __user *uattr, +u32 uattr_size) {return -EINVAL ; }
kernel/bpf/cgroup.c +7 -6
@@ -1208,7 +1208,7 @@ static int cgroup_bpf_detach(struct cgroup *cgrp, struct bpf_prog *prog,/* Must be called with cgroup_mutex held to avoid races. */ static int __cgroup_bpf_query (struct cgroup *cgrp,const union bpf_attr *attr, -union bpf_attr __user *uattr) +union bpf_attr __user *uattr,u32 uattr_size) {__u32 __user *prog_attach_flags =u64_to_user_ptr (attr->query.prog_attach_flags);bool effective_query = attr->query.query_flags &BPF_F_QUERY_EFFECTIVE ;
@@ -1259,7 +1259,8 @@ static int __cgroup_bpf_query(struct cgroup *cgrp, const union bpf_attr *attr,return -EFAULT ;if (!effective_query && from_atype == to_atype) revision = cgrp->bpf.revisions[from_atype]; -if (copy_to_user (&uattr->query.revision, &revision,sizeof (revision))) + if (uattr_size >= offsetofend(union bpf_attr, query.revision) && +copy_to_user (&uattr->query.revision, &revision,sizeof (revision)))return -EFAULT ;if (attr->query.prog_cnt ==0 || !prog_ids || !total_cnt)/* return early if user requested only program count + flags */
@@ -1312,12 +1313,12 @@ static int __cgroup_bpf_query(struct cgroup *cgrp, const union bpf_attr *attr, }static int cgroup_bpf_query (struct cgroup *cgrp,const union bpf_attr *attr, -union bpf_attr __user *uattr) +union bpf_attr __user *uattr,u32 uattr_size) {int ret;cgroup_lock (); - ret =__cgroup_bpf_query (cgrp, attr, uattr); + ret =__cgroup_bpf_query (cgrp, attr, uattr, uattr_size);cgroup_unlock ();return ret; }
@@ -1520,7 +1521,7 @@ int cgroup_bpf_link_attach(const union bpf_attr *attr, struct bpf_prog *prog) }int cgroup_bpf_prog_query (const union bpf_attr *attr, -union bpf_attr __user *uattr) +union bpf_attr __user *uattr,u32 uattr_size) {struct cgroup *cgrp;int ret;
@@ -1529,7 +1530,7 @@ int cgroup_bpf_prog_query(const union bpf_attr *attr,if (IS_ERR (cgrp))return PTR_ERR (cgrp); - ret =cgroup_bpf_query (cgrp, attr, uattr); + ret =cgroup_bpf_query (cgrp, attr, uattr, uattr_size);cgroup_put (cgrp);return ret;
kernel/bpf/syscall.c +3 -3
@@ -4625,7 +4625,7 @@ static int bpf_prog_detach(const union bpf_attr *attr)#define BPF_PROG_QUERY_LAST_FIELD query.revisionstatic int bpf_prog_query (const union bpf_attr *attr, -union bpf_attr __user *uattr) +union bpf_attr __user *uattr,u32 uattr_size) {if (!bpf_net_capable ())return -EPERM ;
@@ -4664,7 +4664,7 @@ static int bpf_prog_query(const union bpf_attr *attr,case BPF_CGROUP_GETSOCKOPT :case BPF_CGROUP_SETSOCKOPT :case BPF_LSM_CGROUP : -return cgroup_bpf_prog_query (attr, uattr); +return cgroup_bpf_prog_query (attr, uattr, uattr_size);case BPF_LIRC_MODE2 :return lirc_prog_query (attr, uattr);case BPF_FLOW_DISSECTOR :
@@ -6189,7 +6189,7 @@ static int __sys_bpf(enum bpf_cmd cmd, bpfptr_t uattr, unsigned int size) err =bpf_prog_detach (&attr);break ;case BPF_PROG_QUERY : - err =bpf_prog_query (&attr, uattr.user); + err =bpf_prog_query (&attr, uattr.user, size);break ;case BPF_PROG_TEST_RUN : err =bpf_prog_test_run (&attr, uattr.user);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 286/1611 selftests/bpf: add verification for BPF_PROG_QUERY attr size boundaries
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuyang Huang <[email protected]>
[ Upstream commit 5add3a4ad1a3bc15404e8bd338813ed0a636f5c9 ]
Add a new selftest to verify that the BPF syscall (specifically BPF_PROG_QUERY) correctly handles different user-declared attribute sizes.
Specifically, verify that:
- For cgroup queries, a query with a size that covers 'prog_cnt' but is smaller than 'revision' (OLD_QUERY_SIZE) succeeds, but does not write to 'revision' (verifying backward compatibility).
- A query with full size (FULL_QUERY_SIZE) succeeds and writes both 'prog_cnt' and 'revision'.
--- .../selftests/bpf/prog_tests/bpf_attr_size.c | 69 +++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 tools/testing/selftests/bpf/prog_tests/bpf_attr_size.c
tools/testing/selftests/bpf/prog_tests/bpf_attr_size.c new file +69 -0
@@ -0,0 +1,69 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Copyright (c) 2026 Google LLC */ +#include <linux/bpf.h> +#include <unistd.h> +#include <sys/syscall.h> +#include <test_progs.h> +#include <cgroup_helpers.h> +#include "cgroup_skb_direct_packet_access.skel.h" + +#define OLD_QUERY_SIZE offsetofend(union bpf_attr, query.prog_cnt) +#define FULL_QUERY_SIZE offsetofend(union bpf_attr, query.revision) + +static void test_query_size_boundaries (void ) +{ +struct cgroup_skb_direct_packet_access *skel; +struct bpf_link *link =NULL ; +union bpf_attr attr; +int cg_fd =-1 ; +int err; + + skel =cgroup_skb_direct_packet_access__open_and_load (); +if (!ASSERT_OK_PTR (skel,"skel_load" )) +return ; + + cg_fd =test__join_cgroup ("/attr_size_cg" ); +if (!ASSERT_GE (cg_fd,0 ,"join_cgroup" )) + goto cleanup; + + link =bpf_program__attach_cgroup (skel->progs.direct_packet_access, + cg_fd); +if (!ASSERT_OK_PTR (link,"cg_attach" )) + goto cleanup; + +memset (&attr,0 ,sizeof (attr)); + attr.query.target_fd = cg_fd; + attr.query.attach_type =BPF_CGROUP_INET_INGRESS ; + attr.query.revision =0xdeadbeefdeadbeefULL ; + + err =syscall (__NR_bpf,BPF_PROG_QUERY , &attr,OLD_QUERY_SIZE ); +if (ASSERT_OK (err,"query_old_size" )) { +ASSERT_EQ (attr.query.prog_cnt,1 ,"prog_cnt_written_old" ); +ASSERT_EQ (attr.query.revision,0xdeadbeefdeadbeefULL , +"revision_not_written_old" ); + } + +memset (&attr,0 ,sizeof (attr)); + attr.query.target_fd = cg_fd; + attr.query.attach_type =BPF_CGROUP_INET_INGRESS ; + + err =syscall (__NR_bpf,BPF_PROG_QUERY , &attr,FULL_QUERY_SIZE ); +if (!ASSERT_OK (err,"query_full_size" )) + goto cleanup; + +ASSERT_EQ (attr.query.prog_cnt,1 ,"prog_cnt_written" ); +ASSERT_GT (attr.query.revision,0 ,"revision_written" ); + +cleanup: +if (link) +bpf_link__destroy (link); +if (cg_fd >=0 ) +close (cg_fd); +cgroup_skb_direct_packet_access__destroy (skel); +} + +void test_bpf_attr_size (void ) +{ +if (test__start_subtest ("query_size_boundaries" )) +test_query_size_boundaries (); +}
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 287/1611 libbpf: Skip hash computation when loader generation failed
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 3c5e2f1a85844abbb65df4694f5ebad0a13e219c ]
bpf_gen__finish() calls compute_sha_update_offsets() gated only on the gen_hash option, without first consulting gen->error. On a failed generation this is buggy: a failed realloc_data_buf() sets gen->data_start to NULL (leaving gen->data_cur dangling), so compute_sha_update_offsets() runs libbpf_sha256() over a NULL buffer with a bogus length; a failed realloc_insn_buf() likewise sets gen->insn_start to NULL and the hash immediates get patched through that NULL base.
The computed program is discarded in either case, since the following "if (!gen->error)" block does not publish opts->insns once an error is set. Thus, skip the hash pass when generation has already failed.
--- tools/lib/bpf/gen_loader.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
tools/lib/bpf/gen_loader.c +4 -4
@@ -398,13 +398,12 @@ int bpf_gen__finish(struct bpf_gen *gen, int nr_progs, int nr_maps) blob_fd_array_off(gen, i));emit (gen,BPF_MOV64_IMM (BPF_REG_0 ,0 ));emit (gen,BPF_EXIT_INSN ()); -if (OPTS_GET (gen->opts, gen_hash, false)) -compute_sha_update_offsets (gen); - -pr_debug ("gen: finish %s\n" ,errstr (gen->error));if (!gen->error) {struct gen_loader_opts *opts = gen->opts; +if (OPTS_GET (opts, gen_hash, false)) +compute_sha_update_offsets (gen); + opts->insns = gen->insn_start; opts->insns_sz = gen->insn_cur - gen->insn_start; opts->data = gen->data_start;
@@ -419,6 +418,7 @@ int bpf_gen__finish(struct bpf_gen *gen, int nr_progs, int nr_maps)bpf_insn_bswap (insn++); } } +pr_debug ("gen: finish %s\n" ,errstr (gen->error));return gen->error; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 288/1611 libbpf: Skip endianness swap when loader generation failed
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 41300d032a1b1d91a3ed996ad21905463e344beb ]
bpf_gen__prog_load() byte-swaps the program insns and the {func,line}_info and CO-RE relo blobs in place for cross-endian targets. The blob offsets come from add_data(), which returns 0 on failure: realloc_data_buf() either frees and NULLs gen->data_start (realloc OOM) or returns early on an already-latched gen->error, leaving a stale, possibly too-small buffer.
Neither bswap site checked for this. With gen->swapped_endian set and a failed generation, "gen->data_start + off" becomes NULL + 0. Guard the same way via !gen->error so they are skipped once generation has failed.
--- tools/lib/bpf/gen_loader.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/lib/bpf/gen_loader.c +2 -2
@@ -1054,7 +1054,7 @@ void bpf_gen__prog_load(struct bpf_gen *gen, prog_idx, prog_type, insns_off, insn_cnt, license_off);/* convert blob insns to target endianness */ -if (gen->swapped_endian) { +if (gen->swapped_endian && !gen->error) {struct bpf_insn *insn = gen->data_start + insns_off;int i;
@@ -1092,7 +1092,7 @@ void bpf_gen__prog_load(struct bpf_gen *gen, sizeof(struct bpf_core_relo));/* convert all info blobs to target endianness */ -if (gen->swapped_endian) +if (gen->swapped_endian && !gen->error)info_blob_bswap (gen, func_info, line_info, core_relos, load_attr);libbpf_strlcpy (attr.prog_name, prog_name,sizeof (attr.prog_name));
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 289/1611 ext4: fix LOGFLUSH shutdown ordering to allow ordered-mode data writeback
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Yi <[email protected]>
[ Upstream commit d99748ef1695ce17eaf51c64b7a06952fa7cddab ]
In EXT4_GOING_FLAGS_LOGFLUSH mode, the EXT4_FLAGS_SHUTDOWN flag was set before calling ext4_force_commit(). This caused ordered-mode data writeback (triggered by journal commit) to fail with -EIO, since ext4_do_writepages() checks for the shutdown flag. The journal would then be aborted prematurely before the commit could succeed.
Fix this by calling ext4_force_commit() first, then setting the shutdown flag, so that pending data can be written back correctly.
Note that moving ext4_force_commit() before setting the shutdown flag creates a small window in which new writes may occur and generate new journal transactions. When the journal is subsequently aborted, the new transactions will not be able to write to disk. This is intentional because LOGFLUSH's semantics are to flush pre-existing journal entries before shutdown, not to guarantee atomicity for writes that race with the ioctl.
--- fs/ext4/ioctl.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
fs/ext4/ioctl.c +9 -3
@@ -829,11 +829,17 @@ int ext4_force_shutdown(struct super_block *sb, u32 flags)bdev_thaw (sb->s_bdev);break ;case EXT4_GOING_FLAGS_LOGFLUSH : +/* +* Call ext4_force_commit() before setting EXT4_FLAGS_SHUTDOWN. +* This is because in data=ordered mode, journal commit +* triggers data writeback which fails if shutdown is already +* set, causing the journal to be aborted prematurely before +* the commit succeeds. +*/ + (void )ext4_force_commit (sb);set_bit (EXT4_FLAGS_SHUTDOWN , &sbi->s_ext4_flags); -if (sbi->s_journal && !is_journal_aborted (sbi->s_journal)) { - (void )ext4_force_commit (sb); +if (sbi->s_journal && !is_journal_aborted (sbi->s_journal))jbd2_journal_abort (sbi->s_journal, -ESHUTDOWN ); - }break ;case EXT4_GOING_FLAGS_NOLOGFLUSH :set_bit (EXT4_FLAGS_SHUTDOWN , &sbi->s_ext4_flags);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 290/1611 spi: atmel: fix DMA channel and bounce buffer leaks
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felix Gu <[email protected]>
[ Upstream commit bd7e9843ec95bffe2643c901dd625f0bab32e639 ]
The original code set use_dma to false when dma_alloc_coherent() for bounce buffers failed, but DMA channels acquired earlier via atmel_spi_configure_dma() were never freed.
When devm_request_irq() or clk_prepare_enable() failed later in probe, the driver also did not release DMA channels or bounce buffers already allocated.
The out_free_dma error path released DMA channels but did not free the bounce buffers.
Fix by moving bounce buffer allocation into atmel_spi_configure_dma() and registering the devres cleanup for DMA channels and bounce buffers.
--- drivers/spi/spi-atmel.c | 133 ++++++++++++++++++++-------------------- 1 file changed, 68 insertions(+), 65 deletions(-)
drivers/spi/spi-atmel.c +68 -65
@@ -559,6 +559,38 @@ static int atmel_spi_dma_slave_config(struct atmel_spi *as, u8 bits_per_word)return err; } +static void atmel_spi_release_dma (void *data) +{ +struct spi_controller *host = data; +struct atmel_spi *as =spi_controller_get_devdata (host); +struct device *dev = &as->pdev->dev; + +if (host->dma_tx) { +dma_release_channel (host->dma_tx); + host->dma_tx =NULL ; + } + +if (host->dma_rx) { +dma_release_channel (host->dma_rx); + host->dma_rx =NULL ; + } + +if (IS_ENABLED (CONFIG_SOC_SAM_V4_V5 )) { +if (as->addr_tx_bbuf) { +dma_free_coherent (dev,SPI_MAX_DMA_XFER , + as->addr_tx_bbuf, + as->dma_addr_tx_bbuf); + as->addr_tx_bbuf =NULL ; + } +if (as->addr_rx_bbuf) { +dma_free_coherent (dev,SPI_MAX_DMA_XFER , + as->addr_rx_bbuf, + as->dma_addr_rx_bbuf); + as->addr_rx_bbuf =NULL ; + } + } +} +static int atmel_spi_configure_dma (struct spi_controller *host,struct atmel_spi *as) {
@@ -569,7 +601,8 @@ static int atmel_spi_configure_dma(struct spi_controller *host,if (IS_ERR (host->dma_tx)) { err =PTR_ERR (host->dma_tx);dev_dbg (dev,"No TX DMA channel, DMA is disabled\n" ); - goto error_clear; + host->dma_tx =NULL ; +return err; } host->dma_rx =dma_request_chan (dev,"rx" );
@@ -580,26 +613,45 @@ static int atmel_spi_configure_dma(struct spi_controller *host,* requested tx channel. */ dev_dbg (dev,"No RX DMA channel, DMA is disabled\n" ); - goto error; + host->dma_rx =NULL ; + goto err_release_dma; } err =atmel_spi_dma_slave_config (as,8 );if (err) - goto error; + goto err_release_dma; + +if (IS_ENABLED (CONFIG_SOC_SAM_V4_V5 )) { + as->addr_tx_bbuf =dma_alloc_coherent (dev,SPI_MAX_DMA_XFER , + &as->dma_addr_tx_bbuf, +GFP_KERNEL |GFP_DMA ); +if (!as->addr_tx_bbuf) { + err = -ENOMEM ; + goto err_release_dma; + } + + as->addr_rx_bbuf =dma_alloc_coherent (dev,SPI_MAX_DMA_XFER , + &as->dma_addr_rx_bbuf, +GFP_KERNEL |GFP_DMA ); +if (!as->addr_rx_bbuf) { + err = -ENOMEM ; + goto err_release_dma; + } + } + + err =devm_add_action_or_reset (dev, atmel_spi_release_dma, host); +if (err) +return err;dev_info (&as->pdev->dev, -"Using %s (tx) and %s (rx) for DMA transfers\n" , -dma_chan_name (host->dma_tx), -dma_chan_name (host->dma_rx)); +"Using %s (tx) and %s (rx) for DMA transfers\n" , +dma_chan_name (host->dma_tx),dma_chan_name (host->dma_rx));return 0 ; -error: -if (!IS_ERR (host->dma_rx)) -dma_release_channel (host->dma_rx); -if (!IS_ERR (host->dma_tx)) -dma_release_channel (host->dma_tx); -error_clear: - host->dma_tx = host->dma_rx =NULL ; + +err_release_dma: +atmel_spi_release_dma (host); +return err; }
@@ -611,18 +663,6 @@ static void atmel_spi_stop_dma(struct spi_controller *host)dmaengine_terminate_all (host->dma_tx); } -static void atmel_spi_release_dma (struct spi_controller *host) -{ -if (host->dma_rx) { -dma_release_channel (host->dma_rx); - host->dma_rx =NULL ; - } -if (host->dma_tx) { -dma_release_channel (host->dma_tx); - host->dma_tx =NULL ; - } -} -/* This function is called by the DMA driver from tasklet context */ static void dma_callback (void *data) {
@@ -1586,30 +1626,6 @@ static int atmel_spi_probe(struct platform_device *pdev) as->use_pdc = true; } -if (IS_ENABLED (CONFIG_SOC_SAM_V4_V5 )) { - as->addr_rx_bbuf =dma_alloc_coherent (&pdev->dev, -SPI_MAX_DMA_XFER , - &as->dma_addr_rx_bbuf, -GFP_KERNEL |GFP_DMA ); -if (!as->addr_rx_bbuf) { - as->use_dma = false; - }else { - as->addr_tx_bbuf =dma_alloc_coherent (&pdev->dev, -SPI_MAX_DMA_XFER , - &as->dma_addr_tx_bbuf, -GFP_KERNEL |GFP_DMA ); -if (!as->addr_tx_bbuf) { - as->use_dma = false; -dma_free_coherent (&pdev->dev,SPI_MAX_DMA_XFER , - as->addr_rx_bbuf, - as->dma_addr_rx_bbuf); - } - } -if (!as->use_dma) -dev_info (host->dev.parent, -" can not allocate dma coherent memory\n" ); - } -if (as->caps.has_dma_support && !as->use_dma)dev_info (&pdev->dev,"Atmel SPI Controller using PIO only\n" );
@@ -1669,13 +1685,10 @@ static int atmel_spi_probe(struct platform_device *pdev) out_free_dma:pm_runtime_disable (&pdev->dev);pm_runtime_set_suspended (&pdev->dev); - -if (as->use_dma) -atmel_spi_release_dma (host); -spi_writel (as,CR ,SPI_BIT (SWRST ));spi_writel (as,CR ,SPI_BIT (SWRST ));/* AT91SAM9263 Rev B workaround */ -clk_disable_unprepare (as->gclk); +if (as->gclk) +clk_disable_unprepare (as->gclk); out_disable_clk:clk_disable_unprepare (clk); out_free_irq:
@@ -1696,18 +1709,8 @@ static void atmel_spi_remove(struct platform_device *pdev)spi_unregister_controller (host);/* reset the hardware and block queue progress */ -if (as->use_dma) { +if (as->use_dma)atmel_spi_stop_dma (host); -atmel_spi_release_dma (host); -if (IS_ENABLED (CONFIG_SOC_SAM_V4_V5 )) { -dma_free_coherent (&pdev->dev,SPI_MAX_DMA_XFER , - as->addr_tx_bbuf, - as->dma_addr_tx_bbuf); -dma_free_coherent (&pdev->dev,SPI_MAX_DMA_XFER , - as->addr_rx_bbuf, - as->dma_addr_rx_bbuf); - } - }spin_lock_irq (&as->lock);spi_writel (as,CR ,SPI_BIT (SWRST ));
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 291/1611 ASoC: rsnd: Fix RSND_SOC_MASK width to single nibble
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: John Madieu <[email protected]>
[ Upstream commit c0758279367e9d82eb7d7b4959718d7d32e96b7d ]
RSND_SOC_MASK was defined as (0xFF << 4), spanning bits 4-11. This is wider than needed since only nibble B (bits 7:4) is used for SoC identifiers. Narrow it to (0xF << 4) to match the intended single-nibble allocation and prevent overlap with bits 8-11 which will be used by upcoming RZ series flags.
No functional change, since the only current user (RSND_SOC_E) fits within a single nibble.
--- sound/soc/renesas/rcar/rsnd.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/renesas/rcar/rsnd.h +1 -1
@@ -624,7 +624,7 @@ struct rsnd_priv {#define RSND_GEN2 (2 << 0)#define RSND_GEN3 (3 << 0)#define RSND_GEN4 (4 << 0) -#define RSND_SOC_MASK (0xFF << 4) +#define RSND_SOC_MASK (0xF << 4)#define RSND_SOC_E (1 << 4)/* E1/E2/E3 */ /*
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 292/1611 NFSD: Fix delegation reference leak in nfsd4_revoke_states
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chuck Lever <[email protected]>
[ Upstream commit 625981c8f3da0cc2d236d7b46c39dd75554b8276 ]
When revoking delegation state, nfsd4_revoke_states() takes an extra reference on the stid before calling unhash_delegation_locked(). If unhash_delegation_locked() returns false (the delegation was already unhashed by a concurrent path), dp is set to NULL and revoke_delegation() is skipped, but the extra reference is never released. Each occurrence permanently pins the stid in memory. The leaked reference also prevents nfs4_put_stid() from decrementing cl_admin_revoked, leaving the counter permanently inflated.
Drop the extra reference in the failure path.
--- fs/nfsd/nfs4state.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
fs/nfsd/nfs4state.c +8 -1
@@ -1375,7 +1375,8 @@ static void destroy_delegation(struct nfs4_delegation *dp)* stateid or it's called from a laundromat thread (nfsd4_landromat()) that * determined that this specific state has expired and needs to be revoked * (both mark state with the appropriate stid sc_status mode). It is also -* assumed that a reference was taken on the @dp state. +* assumed that a reference was taken on the @dp state. This function +* consumes that reference. * * If this function finds that the @dp state is SC_STATUS_FREED it means * that a FREE_STATEID operation for this stateid has been processed and
@@ -1822,6 +1823,10 @@ void nfsd4_revoke_states(struct nfsd_net *nn, struct super_block *sb)mutex_unlock (&stp->st_mutex);break ;case SC_TYPE_DELEG : +/* Extra reference guards against concurrent +* FREE_STATEID; revoke_delegation() consumes +* it, otherwise release it directly. +*/ refcount_inc (&stid->sc_count); dp =delegstateid (stid);spin_lock (&state_lock);
@@ -1831,6 +1836,8 @@ void nfsd4_revoke_states(struct nfsd_net *nn, struct super_block *sb)spin_unlock (&state_lock);if (dp)revoke_delegation (dp); +else +nfs4_put_stid (stid);break ;case SC_TYPE_LAYOUT : ls =layoutstateid (stid);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 293/1611 ARM: imx3: Fix CCM node reference leak
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuho Choi <[email protected]>
[ Upstream commit 36d46348eb5fc4bc505cd2290ddd70c25fbe6bb3 ]
of_find_compatible_node() returns a referenced device node. The i.MX31 and i.MX35 early init paths use the node to map the CCM registers with of_iomap(), but never drop the node reference.
Release the node after the mapping is created.
--- arch/arm/mach-imx/mm-imx3.c | 2 ++ 1 file changed, 2 insertions(+)
arch/arm/mach-imx/mm-imx3.c +2 -0
@@ -106,6 +106,7 @@ void __init imx31_init_early(void) arm_pm_idle = imx31_idle; np =of_find_compatible_node (NULL ,NULL ,"fsl,imx31-ccm" ); mx3_ccm_base =of_iomap (np,0 ); +of_node_put (np); BUG_ON(!mx3_ccm_base); }#endif /* ifdef CONFIG_SOC_IMX31 */
@@ -143,6 +144,7 @@ void __init imx35_init_early(void) arch_ioremap_caller = imx3_ioremap_caller; np =of_find_compatible_node (NULL ,NULL ,"fsl,imx35-ccm" ); mx3_ccm_base =of_iomap (np,0 ); +of_node_put (np); BUG_ON(!mx3_ccm_base); }#endif /* ifdef CONFIG_SOC_IMX35 */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 294/1611 HID: wiimote: Fix table layout and whitespace errors
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: J. Neuschäfer <[email protected]>
[ Upstream commit 12b7731995ca577d86e02196e99ba9c126f47282 ]
Some tab characters snuck into the data layout table for turntable extensions, which resulted in the table only looking right at a tabstop of 4, which is uncommon in the kernel. Change them to the equivalent amount of spaces, which should look correct in any editor.
While at it, also fix the other whitespace errors (trailing spaces at end of line) introduced in the same commit.
--- drivers/hid/hid-wiimote-modules.c | 58 +++++++++++++++---------------- 1 file changed, 29 insertions(+), 29 deletions(-)
drivers/hid/hid-wiimote-modules.c +29 -29
@@ -2403,7 +2403,7 @@ static const struct wiimod_ops wiimod_guitar = { .in_ext = wiimod_guitar_in_ext, }; -/* +/* * Turntable * DJ Hero came with a Turntable Controller that was plugged in * as an extension.
@@ -2439,15 +2439,15 @@ static const __u16 wiimod_turntable_map[] = {static void wiimod_turntable_in_ext (struct wiimote_data *wdata,const __u8 *ext) {__u8 be, cs, sx, sy, ed, rtt, rbg, rbr, rbb, ltt, lbg, lbr, lbb, bp, bm; -/* +/* * Byte | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | *------+------+-----+-----+-----+-----+------+------+--------+ -* 0 | RTT<4:3> | SX <5:0> | -* 1 | RTT<2:1> | SY <5:0> | +* 0 | RTT<4:3> | SX <5:0> | +* 1 | RTT<2:1> | SY <5:0> | *------+------+-----+-----+-----+-----+------+------+--------+ * 2 |RTT<0>| ED<4:3> | CS<3:0> | RTT<5> | *------+------+-----+-----+-----+-----+------+------+--------+ -* 3 | ED<2:0> | LTT<4:0> | +* 3 | ED<2:0> | LTT<4:0> | *------+------+-----+-----+-----+-----+------+------+--------+ * 4 | 0 | 0 | LBR | B- | 0 | B+ | RBR | LTT<5> | *------+------+-----+-----+-----+-----+------+------+--------+
@@ -2458,20 +2458,20 @@ static void wiimod_turntable_in_ext(struct wiimote_data *wdata, const __u8 *ext)* With Motion+ enabled, it will look like this: * Byte | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | *------+------+-----+-----+-----+-----+------+------+--------+ -* 1 | RTT<4:3> | SX <5:1> | 0 | -* 2 | RTT<2:1> | SY <5:1> | 0 | +* 1 | RTT<4:3> | SX <5:1> | 0 | +* 2 | RTT<2:1> | SY <5:1> | 0 | *------+------+-----+-----+-----+-----+------+------+--------+ * 3 |RTT<0>| ED<4:3> | CS<3:0> | RTT<5> | *------+------+-----+-----+-----+-----+------+------+--------+ -* 4 | ED<2:0> | LTT<4:0> | +* 4 | ED<2:0> | LTT<4:0> | *------+------+-----+-----+-----+-----+------+------+--------+ * 5 | 0 | 0 | LBR | B- | 0 | B+ | RBR | XXXX | *------+------+-----+-----+-----+-----+------+------+--------+ * 6 | LBB | 0 | RBG | BE | LBG | RBB | XXXX | XXXX | *------+------+-----+-----+-----+-----+------+------+--------+ */ - - be = !(ext[5 ] &0x10 ); + + be = !(ext[5 ] &0x10 ); cs = ((ext[2 ] &0x1e )); sx = ext[0 ] &0x3f ; sy = ext[1 ] &0x3f ;
@@ -2499,32 +2499,32 @@ static void wiimod_turntable_in_ext(struct wiimote_data *wdata, const __u8 *ext)input_report_abs (wdata->extension.input,ABS_HAT1X , ltt);input_report_abs (wdata->extension.input,ABS_HAT2X , cs);input_report_abs (wdata->extension.input,ABS_HAT3X , ed); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_G_RIGHT ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_G_RIGHT ], rbg);input_report_key (wdata->extension.input, wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_R_RIGHT ], rbr); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_B_RIGHT ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_B_RIGHT ], rbb); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_G_LEFT ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_G_LEFT ], lbg); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_R_LEFT ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_R_LEFT ], lbr); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_B_LEFT ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_B_LEFT ], lbb); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_EUPHORIA ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_EUPHORIA ], be); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_PLUS ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_PLUS ], bp); -input_report_key (wdata->extension.input, - wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_MINUS ], +input_report_key (wdata->extension.input, + wiimod_turntable_map[WIIMOD_TURNTABLE_KEY_MINUS ], bm);input_sync (wdata->extension.input);
@@ -2557,7 +2557,7 @@ static void wiimod_turntable_close(struct input_dev *dev)static int wiimod_turntable_probe (const struct wiimod_ops *ops,struct wiimote_data *wdata) { -int ret, i; +int ret, i; wdata->extension.input =input_allocate_device ();if (!wdata->extension.input)
@@ -2594,9 +2594,9 @@ static int wiimod_turntable_probe(const struct wiimod_ops *ops,input_set_abs_params (wdata->extension.input,ABS_HAT1X ,-8 ,8 ,0 ,0 );input_set_abs_params (wdata->extension.input, -ABS_HAT2X ,0 ,31 ,1 ,1 ); +ABS_HAT2X ,0 ,31 ,1 ,1 );input_set_abs_params (wdata->extension.input, -ABS_HAT3X ,0 ,7 ,0 ,0 ); +ABS_HAT3X ,0 ,7 ,0 ,0 ); ret =input_register_device (wdata->extension.input);if (ret) goto err_free;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 295/1611 wifi: ath12k: fix incorrect HT/VHT/HE/EHT MCS reporting in monitor mode
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kwan Lai Chee Hou <[email protected]>
[ Upstream commit 10085a654a4c2331d5f0cdc20bfc839a49fbb886 ]
In monitor mode, the driver incorrectly assigns the legacy rate to the rate_idx field of the radiotap header for HT/VHT/HE/EHT frames, ignoring the actual MCS value parsed from the hardware.
This causes packet analyzers (like Wireshark) to display incorrect MCS values (e.g., legacy base rates instead of the true MCS).
Fix this by assigning ppdu_info->mcs as the default rate_mcs in ath12k_dp_mon_fill_rx_rate(), and remove rate_idx assignments in ath12k_dp_mon_update_radiotap() to preserve
the previously calculated MCS values (including the HT NSS offset).
Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ
--- drivers/net/wireless/ath/ath12k/dp_mon.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/net/wireless/ath/ath12k/dp_mon.c +2 -4
@@ -1905,13 +1905,14 @@ ath12k_dp_mon_fill_rx_rate(struct ath12k *ar,bool is_cck; pkt_type = ppdu_info->preamble_type; - rate_mcs = ppdu_info->rate; + rate_mcs = ppdu_info->mcs; nss = ppdu_info->nss; sgi = ppdu_info->gi;switch (pkt_type) {case RX_MSDU_START_PKT_TYPE_11A :case RX_MSDU_START_PKT_TYPE_11B : + rate_mcs = ppdu_info->rate; is_cck = (pkt_type ==RX_MSDU_START_PKT_TYPE_11B );if (rx_status->band <NUM_NL80211_BANDS ) { sband = &ar->mac.sbands[rx_status->band];
@@ -2254,13 +2255,10 @@ static void ath12k_dp_mon_update_radiotap(struct ath12k *ar, rxs->encoding =RX_ENC_HE ; ptr =skb_push (mon_skb,sizeof (struct ieee80211_radiotap_he ));ath12k_dp_mon_rx_update_radiotap_he (ppduinfo, ptr); - rxs->rate_idx = ppduinfo->rate; }else if (ppduinfo->vht_flags) { rxs->encoding =RX_ENC_VHT ; - rxs->rate_idx = ppduinfo->rate; }else if (ppduinfo->ht_flags) { rxs->encoding =RX_ENC_HT ; - rxs->rate_idx = ppduinfo->rate; }else { rxs->encoding =RX_ENC_LEGACY ; sband = &ar->mac.sbands[rxs->band];
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 296/1611 wifi: ath12k: fix NULL deref in change_sta_links for unready link
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wei Zhang <[email protected]>
[ Upstream commit 47809a7c8348bc4a332ccc26a37c7145a5f609f8 ]
_ieee80211_set_active_links() calls _ieee80211_link_use_channel() for each newly-added link and WARN_ON_ONCE()s if it fails. The call uses assign_on_failure=true, which allows mac80211 to continue despite driver failures, but when a mac80211-level channel validation fails (e.g., combinations check, DFS, or no available radio), drv_assign_vif_chanctx() is never reached. Since ath12k_mac_vdev_create() is only called from that path, arvif->is_created remains false and arvif->ar remains NULL for the failed link.
The subsequent drv_change_sta_links() call reaches ath12k_mac_op_change_sta_links(), which allocates an arsta and sets ahsta->links_map |= BIT(link_id) for the broken link before checking whether the link is ready. When the vdev was never created, only station_add() is skipped, but the link remains in links_map.
Any subsequent operation iterating links_map and dereferencing arvif->ar without a NULL check will crash. Two observed examples are NULL deref in ath12k_mac_ml_station_remove() on disconnect and in ath12k_mac_op_set_key() when wpa_supplicant installs PTK keys.
BUG: Unable to handle kernel NULL pointer dereference at 0x00000000 pc : ath12k_mac_station_post_remove+0x40/0xe8 [ath12k] Call trace: ath12k_mac_station_post_remove+0x40/0xe8 [ath12k] ath12k_mac_op_sta_state+0xb60/0x1720 [ath12k] drv_sta_state+0x100/0xbd8 [mac80211] __sta_info_destroy_part2+0x148/0x178 [mac80211] ieee80211_set_disassoc+0x500/0x678 [mac80211] BUG: Unable to handle kernel NULL pointer dereference at 0x00000000 pc : ath12k_mac_op_set_key+0x1f8/0x2c0 [ath12k] Call trace: ath12k_mac_op_set_key+0x1f8/0x2c0 [ath12k] drv_set_key+0x70/0x100 [mac80211] ieee80211_key_enable_hw_accel+0x78/0x260 [mac80211] ieee80211_add_key+0x16c/0x2ac [mac80211] nl80211_new_key+0x138/0x280 [cfg80211]
Fix this by checking arvif->is_created before calling ath12k_mac_alloc_assign_link_sta(). This prevents the broken link from entering links_map, so all subsequent operations iterating the bitmap are protected. The reliability of arvif->is_created across all error paths is ensured by the preceding patch.
Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3
--- drivers/net/wireless/ath/ath12k/mac.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/net/wireless/ath/ath12k/mac.c +4 -4
@@ -7330,16 +7330,16 @@ static int ath12k_mac_op_change_sta_links(struct ieee80211_hw *hw,continue ; arvif =wiphy_dereference (hw->wiphy, ahvif->link[link_id]); - arsta =ath12k_mac_alloc_assign_link_sta (ah, ahsta, ahvif, link_id); +if (!arvif || !arvif->is_created) +continue ; -if (!arvif || !arsta) { + arsta =ath12k_mac_alloc_assign_link_sta (ah, ahsta, ahvif, link_id); +if (!arsta) {ath12k_hw_warn (ah,"Failed to alloc/assign link sta" );continue ; } ar = arvif->ar; -if (!ar) -continue ; ret =ath12k_mac_station_add (ar, arvif, arsta);if (ret) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 297/1611 ata: libata: Fix ata_exec_internal()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bart Van Assche <[email protected]>
[ Upstream commit aa0ae1c35f7b3e9afed2324bed5f5c87ad55b92c ]
Some but not all ata_exec_internal() calls happen from the context of the ATA error handler. Commit c0c362b60e25 ("libata: implement cross-port EH exclusion") added ata_eh_release() and ata_eh_acquire() calls in ata_exec_internal(). Calling these functions is necessary if the caller holds the eh_mutex but is not allowed if the caller doesn't hold that mutex. Fix this by only calling ata_eh_release() and ata_eh_acquire() if the caller holds the eh_mutex. An example of an indirect caller of ata_exec_internal() that does not hold the eh_mutex is ata_host_register().
--- drivers/ata/libata-core.c | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-)
drivers/ata/libata-core.c +17 -2
@@ -1526,6 +1526,7 @@ unsigned int ata_exec_internal(struct ata_device *dev, struct ata_taskfile *tf, {struct ata_link *link = dev->link;struct ata_port *ap = link->ap; +const bool owns_eh_mutex = ap->host->eh_owner == current;u8 command = tf->command;struct ata_queued_cmd *qc;struct scatterlist sgl;
@@ -1603,11 +1604,25 @@ unsigned int ata_exec_internal(struct ata_device *dev, struct ata_taskfile *tf, } } -ata_eh_release (ap); +if (owns_eh_mutex) { +/* +* To prevent that the compiler complains about the +* ata_eh_release() call below. +*/ +__acquire (&ap->host->eh_mutex); +ata_eh_release (ap); + } rc =wait_for_completion_timeout (&wait,msecs_to_jiffies (timeout)); -ata_eh_acquire (ap); +if (owns_eh_mutex) { +ata_eh_acquire (ap); +/* +* To prevent that the compiler complains about the above +* ata_eh_acquire() call. +*/ +__release (&ap->host->eh_mutex); + }ata_sff_flush_pio_task (ap);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 298/1611 ARM: imx31: Fix IIM mapping leak in revision check
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuho Choi <[email protected]>
[ Upstream commit ccb4b54b8ecf1ebafef96d538cd6c5c8455bb390 ]
mx31_read_cpu_rev() maps the IIM registers with of_iomap() to read the silicon revision, but returns without unmapping the MMIO mapping.
Keep the normalized revision value in a local variable and route the return path through iounmap() after the revision register has been read.
--- arch/arm/mach-imx/cpu-imx31.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
arch/arm/mach-imx/cpu-imx31.c +7 -2
@@ -36,6 +36,7 @@ static int mx31_read_cpu_rev(void)void __iomem *iim_base;struct device_node *np;u32 i, srev; +int rev =IMX_CHIP_REVISION_UNKNOWN ; np =of_find_compatible_node (NULL ,NULL ,"fsl,imx31-iim" ); iim_base =of_iomap (np,0 );
@@ -48,13 +49,17 @@ static int mx31_read_cpu_rev(void)for (i =0 ; i <ARRAY_SIZE (mx31_cpu_type); i++)if (srev == mx31_cpu_type[i].srev) { + rev = mx31_cpu_type[i].rev;imx_print_silicon_rev (mx31_cpu_type[i].name, mx31_cpu_type[i].rev); -return mx31_cpu_type[i].rev; + goto out; }imx_print_silicon_rev ("i.MX31" ,IMX_CHIP_REVISION_UNKNOWN ); -return IMX_CHIP_REVISION_UNKNOWN ; + +out: +iounmap (iim_base); +return rev; }int mx31_revision (void )
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 299/1611 x86/cpu: Keep the PROCESSOR_SELECT menu together
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Randy Dunlap <[email protected]>
[ Upstream commit 1df61a8b2d01c560822a0421f2a76af7fda34c1f ]
Having a stray kconfig symbol in the middle of the PROCESSOR_SELECT menu (this symbol plus its dependent symbols) causes the menu dependencies not to be displayed correctly in "make {menu,n,g,x}config".
Move the BROADCAST_TLB_FLUSH symbol away from the PROCESSOR_SELECT menu so that the list of processors is displayed correctly.
--- arch/x86/Kconfig.cpu | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
arch/x86/Kconfig.cpu +4 -4
@@ -358,10 +358,6 @@ menuconfig PROCESSOR_SELECT This lets you choose what x86 vendor support code your kernel will include. -config BROADCAST_TLB_FLUSH - def_bool y - depends on CPU_SUP_AMD && 64BIT - config CPU_SUP_INTEL default y bool "Support Intel processors" if PROCESSOR_SELECT
@@ -482,3 +478,7 @@ config CPU_SUP_VORTEX_32 makes the kernel a tiny bit smaller. If unsure, say N. + +config BROADCAST_TLB_FLUSH + def_bool y + depends on CPU_SUP_AMD && 64BIT
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 300/1611 nvdimm/btt: Handle preemption in BTT lane acquisition
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alison Schofield <[email protected]>
[ Upstream commit 8d4b989d9c9afe5f185aa5853b666fc4617afe9e ]
BTT lanes serialize access to per-lane metadata and workspace state during BTT I/O. The btt-check unit test reports data mismatches during BTT writes due to a race in lane acquisition that can lead to silent data corruption.
The existing lane model uses a spinlock together with a per-CPU recursion count. That recursion model stopped being valid after BTT lanes became preemptible: another task can run on the same CPU, observe a non-zero recursion count, bypass locking, and use the same lane concurrently.
BTT lanes are also held across arena_write_bytes() calls. That path reaches nsio_rw_bytes(), which flushes writes with nvdimm_flush(). Some provider flush callbacks can sleep, making a spinlock the wrong primitive for the lane lifetime.
Replace the spinlock-based recursion model with a dynamically allocated per-lane mutex array and take the lane lock unconditionally.
Add might_sleep() to catch any future atomic-context caller.
Found with the ndctl unit test btt-check.sh.
--- Documentation/driver-api/nvdimm/btt.rst | 5 +- drivers/nvdimm/nd.h | 11 ++--- drivers/nvdimm/region_devs.c | 66 +++++++++---------------- 3 files changed, 29 insertions(+), 53 deletions(-)
Documentation/driver-api/nvdimm/btt.rst +2 -3
@@ -161,9 +161,8 @@ process:: nlanes = min(nfree, num_cpus) A lane number is obtained at the start of any IO, and is used for indexing into -all the on-disk and in-memory data structures for the duration of the IO. If -there are more CPUs than the max number of available lanes, than lanes are -protected by spinlocks. +all the on-disk and in-memory data structures for the duration of the IO. Lanes +are protected by mutexes. d. In-memory data structure: Read Tracking Table (RTT)
drivers/nvdimm/nd.h +5 -6
@@ -365,11 +365,6 @@ unsigned sizeof_namespace_label(struct nvdimm_drvdata *ndd);for (res = (ndd)->dpa.child, next = res ? res->sibling :NULL ; \ res; res = next, next = next ? next->sibling :NULL ) -struct nd_percpu_lane { -int count; -spinlock_t lock; -}; - enum nd_label_flags { ND_LABEL_REAP, };
@@ -400,6 +395,10 @@ struct nd_mapping {struct nvdimm_drvdata *ndd; }; +struct nd_lane { +struct mutex lock;/* serialize lane access */ +}____cacheline_aligned_in_smp ; +struct nd_region {struct device dev;struct ida ns_ida;
@@ -420,7 +419,7 @@ struct nd_region {struct kernfs_node *bb_state;struct badblocks bb;struct nd_interleave_set *nd_set; -struct nd_percpu_lane __percpu *lane; +struct nd_lane *lane;int (*flush)(struct nd_region *nd_region,struct bio *bio); struct nd_mapping mapping[] __counted_by(ndr_mappings); };
drivers/nvdimm/region_devs.c +22 -44
105 lines not on this page · raw message
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 301/1611 scsi: Revert "scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans"
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Martin Wilck <[email protected]>
[ Upstream commit 8c292e89bd831c8a13e92f3429ef66bbe0b83677 ]
This reverts commit 37c4e72b0651e7697eb338cd1fb09feef472cc1a.
Said commit causes excessive resource usage and even system freeze with some controllers, e.g. smartpqi and hisi_sas. The justification provided by the patch authors [1] was supporting a special mode of the mpi3mr and mpt3sas, so-called "Tri-mode", in which NVMe drives are exposed as SCSI devices on a separate channel. While that's useful for these drivers, it seems wrong to cause major breakage for other drivers for the sake of this feature.
--- drivers/scsi/scsi_scan.c | 2 +- drivers/scsi/scsi_transport_sas.c | 60 +++++++------------------------ 2 files changed, 13 insertions(+), 49 deletions(-)
drivers/scsi/scsi_scan.c +1 -1
@@ -1897,7 +1897,7 @@ int scsi_scan_host_selected(struct Scsi_Host *shost, unsigned int channel,return 0 ; } -EXPORT_SYMBOL (scsi_scan_host_selected); +static void scsi_sysfs_add_devices (struct Scsi_Host *shost) {struct scsi_device *sdev;
drivers/scsi/scsi_transport_sas.c +12 -48
83 lines not on this page · raw message
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 302/1611 bpf: Reject exclusive maps as inner maps in map-in-map
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 9a3c3c49c333760c8944dadacbe114c1884546ef ]
An exclusive map (created with excl_prog_hash) is bound to a single program by hash: check_map_prog_compatibility() refuses to load any program whose digest does not match map->excl_prog_sha. That check only runs for maps a program references directly, i.e. its used_maps. A map reached at runtime through a map-of-maps is never in used_maps, and bpf_map_meta_equal() does not consider excl_prog_sha, so an exclusive map can be inserted into a non-exclusive outer map and then looked up and mutated by an unrelated program, bypassing the exclusivity guarantee.
For the signed loader this defeats the metadata map exclusivity check added in the signed loader: the cached map->sha[] is validated against the signed hash while another program on a hostile host rewrites the frozen map's contents through the outer map.
--- kernel/bpf/map_in_map.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
kernel/bpf/map_in_map.c +4 -1
@@ -20,7 +20,8 @@ struct bpf_map *bpf_map_meta_alloc(int inner_map_ufd)/* Does not support >1 level map-in-map */ if (inner_map->inner_map_meta)return ERR_PTR (-EINVAL ); - +if (inner_map->excl_prog_sha) +return ERR_PTR (-ENOTSUPP );if (!inner_map->ops->map_meta_equal)return ERR_PTR (-ENOTSUPP );
@@ -101,6 +102,8 @@ void *bpf_map_fd_get_ptr(struct bpf_map *map, inner_map =__bpf_map_get (f);if (IS_ERR (inner_map))return inner_map; +if (inner_map->excl_prog_sha) +return ERR_PTR (-ENOTSUPP ); inner_map_meta = map->inner_map_meta;if (inner_map_meta->ops->map_meta_equal (inner_map_meta, inner_map))
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 303/1611 libbpf: Reject non-exclusive metadata maps in the signed loader
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: KP Singh <[email protected]>
[ Upstream commit 0fb6c9ed6493b4af01be8bb0a384574eba7df636 ]
The loader verifies map->sha against the metadata hash in its instructions. map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map.
While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data.
With the extra check as part of the signed loader, it now refuses to move on with map->sha validation if the host set it up wrongly.
--- include/linux/bpf.h | 1 + kernel/bpf/syscall.c | 7 +++++++ tools/lib/bpf/gen_loader.c | 17 +++++++++++++++++ 3 files changed, 25 insertions(+)
include/linux/bpf.h +1 -0
@@ -294,6 +294,7 @@ struct bpf_map_owner {struct bpf_map {u8 sha[SHA256_DIGEST_SIZE ]; +u32 excl;const struct bpf_map_ops *ops;struct bpf_map *inner_map_meta;#ifdef CONFIG_SECURITY
kernel/bpf/syscall.c +7 -0
@@ -1579,6 +1579,13 @@ static int map_create(union bpf_attr *attr, bpfptr_t uattr) err = -EFAULT ; goto free_map; } + +/* See libbpf: emit_signature_match() */ +BUILD_BUG_ON (offsetof(struct bpf_map , excl) !=SHA256_DIGEST_SIZE ); +BUILD_BUG_ON (!__same_type (map->excl, u32)); +BUILD_BUG_ON (offsetof(struct bpf_map , sha) !=0 ); +BUILD_BUG_ON (!__same_type (map->sha, u8[SHA256_DIGEST_SIZE ])); + map->excl =1 ; }else if (attr->excl_prog_hash_size) { err = -EINVAL ; goto free_map;
tools/lib/bpf/gen_loader.c +17 -0
@@ -585,6 +585,23 @@ static void emit_signature_match(struct bpf_gen *gen)__s64 off;int i; +/* +* Reject if the metadata map is not exclusive. Without exclusivity +* the cached map->sha[] verified above can be stale: another BPF +* program with map access could have mutated the contents between +* BPF_OBJ_GET_INFO_BY_FD and loader execution. +*/ +emit2 (gen,BPF_LD_IMM64_RAW_FULL (BPF_REG_1 ,BPF_PSEUDO_MAP_IDX , +0 ,0 ,0 ,0 )); +emit (gen,BPF_LDX_MEM (BPF_W ,BPF_REG_2 ,BPF_REG_1 ,SHA256_DIGEST_LENGTH )); + off = -(gen->insn_cur - gen->insn_start - gen->cleanup_label) /8 -2 ; +if (is_simm16 (off)) { +emit (gen,BPF_MOV64_IMM (BPF_REG_7 , -EINVAL )); +emit (gen,BPF_JMP_IMM (BPF_JNE ,BPF_REG_2 ,1 , off)); + }else { + gen->error = -ERANGE ; + } +for (i =0 ; i <SHA256_DWORD_SIZE ; i++) {emit2 (gen,BPF_LD_IMM64_RAW_FULL (BPF_REG_1 ,BPF_PSEUDO_MAP_IDX ,0 ,0 ,0 ,0 ));
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 304/1611 libbpf: Skip initial_value override on signed loaders
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 61e084152328867fe2279cc790573aae39959cd5 ]
bpf_gen__map_update_elem() emits code that, when the host-supplied loader ctx provides a non-NULL map_desc[idx].initial_value, overwrites the blob value with bytes read from the host (bpf_copy_from_user / bpf_probe_read_kernel) before the BPF_MAP_UPDATE_ELEM that populates the program's .data/.rodata/.bss maps.
This override runs after emit_signature_match() has validated map->sha[], and initial_value is part of neither the signed loader instructions nor the hashed data blob. For a signed loader this lets an untrusted host substitute global-variable contents into a program whose code carries a valid signature, thus weakening what the signature attests to.
The blob already contains the signer-provided value (added via add_data() and covered by the embedded, signed hash), so simply skip emitting the override for signed loaders (gen_hash). Runtime initialization stays available for the unsigned light-skeleton path as before. The jump offsets within the override block are internal to it, so guarding the whole block leaves them unchanged.
--- tools/lib/bpf/gen_loader.c | 39 +++++++++++++++++++++++--------------- 1 file changed, 24 insertions(+), 15 deletions(-)
tools/lib/bpf/gen_loader.c +24 -15
@@ -1187,27 +1187,36 @@ void bpf_gen__map_update_elem(struct bpf_gen *gen, int map_idx, void *pvalue, value =add_data (gen, pvalue, value_size); key =add_data (gen, &zero,sizeof (zero)); -/* if (map_desc[map_idx].initial_value) { +/* +* if (map_desc[map_idx].initial_value) { * if (ctx->flags & BPF_SKEL_KERNEL) * bpf_probe_read_kernel(value, value_size, initial_value); * else * bpf_copy_from_user(value, value_size, initial_value); * } +* +* The runtime initial_value comes from the host-supplied loader +* ctx and would overwrite the blob value after emit_signature_match() +* has already validated map->sha[]. For a signed loader (gen_hash) +* the attested blob value must be authoritative, so skip the override +* and leave the hashed value in place. */ -emit (gen,BPF_LDX_MEM (BPF_DW ,BPF_REG_3 ,BPF_REG_6 , -sizeof (struct bpf_loader_ctx ) + -sizeof (struct bpf_map_desc ) * map_idx + - offsetof(struct bpf_map_desc , initial_value))); -emit (gen,BPF_JMP_IMM (BPF_JEQ ,BPF_REG_3 ,0 ,8 )); -emit2 (gen,BPF_LD_IMM64_RAW_FULL (BPF_REG_1 ,BPF_PSEUDO_MAP_IDX_VALUE , -0 ,0 ,0 , value)); -emit (gen,BPF_MOV64_IMM (BPF_REG_2 , value_size)); -emit (gen,BPF_LDX_MEM (BPF_W ,BPF_REG_0 ,BPF_REG_6 , - offsetof(struct bpf_loader_ctx , flags))); -emit (gen,BPF_JMP_IMM (BPF_JSET ,BPF_REG_0 ,BPF_SKEL_KERNEL ,2 )); -emit (gen,BPF_EMIT_CALL (BPF_FUNC_copy_from_user)); -emit (gen,BPF_JMP_IMM (BPF_JA ,0 ,0 ,1 )); -emit (gen,BPF_EMIT_CALL (BPF_FUNC_probe_read_kernel)); +if (!OPTS_GET (gen->opts, gen_hash, false)) { +emit (gen,BPF_LDX_MEM (BPF_DW ,BPF_REG_3 ,BPF_REG_6 , +sizeof (struct bpf_loader_ctx ) + +sizeof (struct bpf_map_desc ) * map_idx + + offsetof(struct bpf_map_desc , initial_value))); +emit (gen,BPF_JMP_IMM (BPF_JEQ ,BPF_REG_3 ,0 ,8 )); +emit2 (gen,BPF_LD_IMM64_RAW_FULL (BPF_REG_1 ,BPF_PSEUDO_MAP_IDX_VALUE , +0 ,0 ,0 , value)); +emit (gen,BPF_MOV64_IMM (BPF_REG_2 , value_size)); +emit (gen,BPF_LDX_MEM (BPF_W ,BPF_REG_0 ,BPF_REG_6 , + offsetof(struct bpf_loader_ctx , flags))); +emit (gen,BPF_JMP_IMM (BPF_JSET ,BPF_REG_0 ,BPF_SKEL_KERNEL ,2 )); +emit (gen,BPF_EMIT_CALL (BPF_FUNC_copy_from_user)); +emit (gen,BPF_JMP_IMM (BPF_JA ,0 ,0 ,1 )); +emit (gen,BPF_EMIT_CALL (BPF_FUNC_probe_read_kernel)); + } map_update_attr =add_data (gen, &attr, attr_size); pr_debug("gen: map_update_elem: idx %d, value: off %d size %d, attr: off %d size %d\n",
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 305/1611 libbpf: Skip max_entries override on signed loaders
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 60214435b365ecdd40b2f96d4e54564b5c927645 ]
bpf_gen__map_create() lets the host-supplied loader ctx override a map's max_entries at runtime (map_desc[idx].max_entries, when non-zero). This is how the light skeleton sizes maps to the target machine, but it happens after emit_signature_match() and is covered by neither the signed loader instructions nor the hashed blob.
For a signed loader this means an untrusted host can re-dimension the program's maps, outside what the signature attests to. Gate the override on gen_hash so signed loaders use the signer-provided max_entries baked into the blob.
--- tools/lib/bpf/gen_loader.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
tools/lib/bpf/gen_loader.c +11 -2
@@ -545,13 +545,22 @@ void bpf_gen__map_create(struct bpf_gen *gen,default :break ; } -/* conditionally update max_entries */ -if (map_idx >=0 ) + +/* +* Conditionally update max_entries from the host-supplied loader +* ctx. This sizes the map at runtime, but for a signed loader +* (gen_hash) it would let an untrusted host re-dimension the +* program's maps after emit_signature_match(), outside what the +* signature attests to. Keep the signer-provided max_entries +* baked into the blob in that case. +*/ +if (map_idx >=0 && !OPTS_GET (gen->opts, gen_hash, false))move_ctx2blob (gen,attr_field (map_create_attr, max_entries),4 ,sizeof (struct bpf_loader_ctx ) +sizeof (struct bpf_map_desc ) * map_idx + offsetof(struct bpf_map_desc , max_entries), true/* check that max_entries != 0 */ ); +/* emit MAP_CREATE command */ emit_sys_bpf (gen,BPF_MAP_CREATE , map_create_attr, attr_size); debug_ret(gen, "map_create %s idx %d type %d value_size %d value_btf_id %d",
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 306/1611 scsi: pm8001: Fix error code in non_fatal_log_show()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
[ Upstream commit 1b6f03b7ae9ee27054c55bb55a69d05555a78516 ]
The non_fatal_log_show() function is supposed to return negative error codes on failure. But because the error codes are saved in a u32 and then cast to signed long, they end up being high positive values instead of negative. Remove the intermediary u32 variable to fix this bug.
--- drivers/scsi/pm8001/pm8001_ctl.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
drivers/scsi/pm8001/pm8001_ctl.c +1 -4
@@ -588,10 +588,7 @@ static DEVICE_ATTR(fatal_log, S_IRUGO, pm8001_ctl_fatal_log_show, NULL);static ssize_t non_fatal_log_show (struct device *cdev,struct device_attribute *attr,char *buf) { -u32 count; - - count =pm80xx_get_non_fatal_dump (cdev, attr, buf); -return count; +return pm80xx_get_non_fatal_dump (cdev, attr, buf); }static DEVICE_ATTR_RO (non_fatal_log);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 307/1611 scsi: ufs: Fix wrong value printed in unexpected UPIU response case
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chanwoo Lee <[email protected]>
[ Upstream commit 2483ae0a56231a915c706411421c6c002a2bf83e ]
In ufshcd_transfer_rsp_status(), the default case of the inner switch statement prints the UPIU response code when an unexpected response is received. However, the code was printing 'result' variable which is always 0 at that point, making the error message useless for debugging.
Fix this by printing the actual UPIU response code returned by ufshcd_get_req_rsp().
--- drivers/ufs/core/ufshcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/ufs/core/ufshcd.c +1 -1
@@ -5494,7 +5494,7 @@ ufshcd_transfer_rsp_status(struct ufs_hba *hba, struct ufshcd_lrb *lrbp,default :dev_err (hba->dev,"Unexpected request response code = %x\n" , - result); +ufshcd_get_req_rsp (lrbp->ucd_rsp_ptr)); result =DID_ERROR <<16 ;break ; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 308/1611 bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Deepanshu Kartikey <[email protected]>
[ Upstream commit b93c55b4932dd7e32dca8cf34a3443cc87a02906 ]
commit 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs") moved inode cleanup from ->free_inode() into ->destroy_inode() to avoid sleeping in RCU context when calling bpf_any_put(). However this removed the RCU delay on freeing the inode itself and the cached symlink body (i_link), both of which can be accessed by RCU pathwalk (pick_link, may_lookup etc.).
This causes a use-after-free when a concurrent unlinkat() drops the last inode reference and destroy_inode() frees the inode immediately, while another task is still walking the path in RCU mode and reads inode->i_opflags (offset +2) inside current_time() -> is_mgtime().
KASAN reports:
BUG: KASAN: slab-use-after-free in is_mgtime include/linux/fs.h:2313 Read of size 2 at addr ffff8880407e4282 (offset +2 = i_opflags)
The rules (per Al Viro):
->destroy_inode() called immediately, can sleep, use for blocking
cleanup e.g. bpf_any_put()
->free_inode() called after RCU grace period, use for freeing
inode and anything RCU-accessible e.g. i_link
Fix: split the two concerns properly:
- keep bpf_any_put() in bpf_destroy_inode() since it is blocking and needs to run promptly
- introduce bpf_free_inode() to handle kfree(i_link) and free_inode_nonrcu() with proper RCU delay, preventing the UAF
--- kernel/bpf/inode.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
kernel/bpf/inode.c +11 -2
@@ -779,10 +779,18 @@ static void bpf_destroy_inode(struct inode *inode) {enum bpf_type type; -if (S_ISLNK (inode->i_mode)) -kfree (inode->i_link);if (!bpf_inode_type (inode, &type))bpf_any_put (inode->i_private, type); +} + +/* +* Called after RCU grace period - safe to free inode and anything +* that might be accessed by RCU pathwalk (inode fields, i_link). +*/ +static void bpf_free_inode (struct inode *inode) +{ +if (S_ISLNK (inode->i_mode)) +kfree (inode->i_link);free_inode_nonrcu (inode); }
@@ -791,6 +799,7 @@ const struct super_operations bpf_super_ops = { .drop_inode = inode_just_drop, .show_options = bpf_show_options, .destroy_inode = bpf_destroy_inode, + .free_inode = bpf_free_inode, };enum {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 309/1611 mm/fake-numa: fix under-allocation detection in uniform split
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sang-Heon Jeon <[email protected]>
[ Upstream commit 3a3fc1dfd6a958615ebaab8fb251e89fc2b3f2f2 ]
When splitting NUMA node uniformly, split_nodes_size_interleave_uniform() returns the next absolute node ID, not the number of nodes created.
The existing under-allocation detection logic compares next absolute node ID (ret) and request count (n), which only works when nid starts at 0.
For example, on a system with 2 physical NUMA nodes (node 0: 2GB, node 1: 128MB) and numa=fake=8U, 8 fake nodes are successfully created from node 0 and split_nodes_size_interleave_uniform() returns 8. For node 1, fake node nid starts at 8, but only 4 fake nodes are created due to current FAKE_NODE_MIN_SIZE being 32MB, and split_nodes_size_interleave_uniform() returns 12. By existing under-allocation detection logic, "ret < n" (12 < 8) is false, so the under-allocation will not be detected.
Fix under-allocation detection logic to compare the number of actually created nodes (ret - nid) against the request count (n). Also skip under-allocation detection logic for memoryless physical nodes where no fake nodes are created.
Also, fix the outdated comment describing split_nodes_size_interleave_uniform() to match the actual return value.
--- mm/numa_emulation.c | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-)
mm/numa_emulation.c +13 -4
@@ -214,7 +214,7 @@ static u64 uniform_size(u64 max_addr, u64 base, u64 hole, int nr_nodes)* Sets up fake nodes of `size' interleaved over physical nodes ranging from * `addr' to `max_addr'. * -* Returns zero on success or negative on error. +* Returns node ID of the next node on success or negative error code. */ static int __init split_nodes_size_interleave_uniform(struct numa_meminfo *ei, struct numa_meminfo *pi,
@@ -398,7 +398,7 @@ void __init numa_emulation(struct numa_meminfo *numa_meminfo, int numa_dist_cnt)*/ if (strchr (emu_cmdline,'U' )) {unsigned long n; -int nid =0 ; +int nid =0 , nr_created; n =simple_strtoul (emu_cmdline, &emu_cmdline,0 ); ret =-1 ;
@@ -416,9 +416,18 @@ void __init numa_emulation(struct numa_meminfo *numa_meminfo, int numa_dist_cnt) n, &pi.blk[0], nid);if (ret <0 )break ; -if (ret < n) { + +/* +* If no memory was found for this physical node, +* skip the under-allocation check. +*/ +if (ret == nid) +continue ; + + nr_created = ret - nid; +if (nr_created < n) {pr_info ("%s: phys: %d only got %d of %ld nodes, failing\n" , - __func__, i, ret, n); + __func__, i, nr_created, n); ret =-1 ;break ; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 310/1611 ext2: fix ignored return value of generic_write_sync()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Danila Chernetsov <[email protected]>
[ Upstream commit a4659be0bc7cb1856ffb15b67f903229ae8891ec ]
Fix ext2_dio_write_iter() to propagate the error returned by generic_write_sync() instead of silently discarding it, which could cause write(2) to return success to userspace on O_SYNC/O_DSYNC files even when the sync failed.
The correct pattern, already used in ext2_dax_write_iter() in the same file and in ext4, xfs, f2fs among others, is:
if (ret > 0)
ret = generic_write_sync(iocb, ret);Found by Linux Verification Center (linuxtesting.org) with SVACE.
[JK: Reflect also filemap_write_and_wait() return value]
--- fs/ext2/file.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
fs/ext2/file.c +6 -3
@@ -264,12 +264,15 @@ static ssize_t ext2_dio_write_iter(struct kiocb *iocb, struct iov_iter *from) endbyte = pos + status -1 ; ret2 =filemap_write_and_wait_range (inode->i_mapping, pos, endbyte); -if (!ret2) +if (!ret2) {invalidate_mapping_pages (inode->i_mapping, pos >>PAGE_SHIFT , endbyte >>PAGE_SHIFT ); -if (ret >0 ) -generic_write_sync (iocb, ret); +if (ret >0 ) + ret =generic_write_sync (iocb, ret); + }else { + ret = ret2; + } } out_unlock:
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 311/1611 sched: restore timer_slack_ns when resetting RT policy on fork
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Guanyou.Chen <[email protected]>
[ Upstream commit 63c1a12bc0e09af7dee919c4fb4a300a719d5125 ]
Commit ed4fb6d7ef68 ("hrtimer: Use and report correct timerslack values for realtime tasks") sets timer_slack_ns to 0 for RT tasks in __setscheduler_params(). However, when an RT task with SCHED_RESET_ON_FORK creates child threads, the children inherit timer_slack_ns=0 from the parent. sched_fork() resets the child's policy to SCHED_NORMAL but does not restore timer_slack_ns, leaving the child permanently running with zero slack.
Fix this by restoring timer_slack_ns from default_timer_slack_ns in sched_fork() when resetting from RT/DL to NORMAL policy, matching the existing behavior in __setscheduler_params().
Note: this fix alone requires a correct default_timer_slack_ns to be effective. See the following patch for that fix.
--- kernel/sched/core.c | 1 + 1 file changed, 1 insertion(+)
kernel/sched/core.c +1 -0
@@ -4706,6 +4706,7 @@ int sched_fork(u64 clone_flags, struct task_struct *p) p->policy =SCHED_NORMAL ; p->static_prio =NICE_TO_PRIO (0 ); p->rt_priority =0 ; + p->timer_slack_ns = p->default_timer_slack_ns; }else if (PRIO_TO_NICE (p->static_prio) <0 ) p->static_prio =NICE_TO_PRIO (0 );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 312/1611 nvme: fix FDP fdpcidx bounds check
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: liuxixin <[email protected]>
[ Upstream commit 0967074f6830718fd2597404ef119bddd0dbfd00 ]
The fdpcidx bounds check sets n = NUMFDPC + 1 but used > instead of >=, incorrectly accepting fdp_idx when it equals n (i.e. NUMFDPC + 1).
--- drivers/nvme/host/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/nvme/host/core.c +1 -1
@@ -2229,7 +2229,7 @@ static int nvme_query_fdp_granularity(struct nvme_ctrl *ctrl, } n =le16_to_cpu (h->numfdpc) +1 ; -if (fdp_idx > n) { +if (fdp_idx >= n) {dev_warn (ctrl->device,"FDP index:%d out of range:%d\n" , fdp_idx, n);/* Proceed without registering FDP streams */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 313/1611 driver core: Use system_percpu_wq instead of system_wq
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nathan Chancellor <[email protected]>
[ Upstream commit fda8355f13ea3c0f9499acdeff3024995b474948 ]
Commit 1137838865bf ("driver core: Use mod_delayed_work to prevent lost deferred probe work") added a use of system_wq, which is deprecated in favor of system_percpu_wq added by commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq"). An upcoming warning in the workqueue tree flags this with:
workqueue: work func deferred_probe_timeout_work_func enqueued on deprecated workqueue. Use system_{percpu|dfl}_wq instead.
Switch to system_percpu_wq to clear up the warning.
--- drivers/base/dd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/base/dd.c +1 -1
@@ -328,7 +328,7 @@ void deferred_probe_extend_timeout(void)* start a new one. */ if (delayed_work_pending (&deferred_probe_timeout_work) && -mod_delayed_work (system_wq, &deferred_probe_timeout_work, +mod_delayed_work (system_percpu_wq, &deferred_probe_timeout_work,secs_to_jiffies (driver_deferred_probe_timeout)))pr_debug ("Extended deferred probe timeout by %d secs\n" , driver_deferred_probe_timeout);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 314/1611 bpf: Reject exclusive maps for bpf_map_elem iterators
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 3c56ee343f9412d81918635c3e25e22a5dd6d87e ]
Exclusive maps (aka excl_prog_hash) are meant to be reachable only from the single program whose hash matches. This is enforced by check_map_prog_compatibility() when the map is referenced from a program such as signed BPF loaders.
A bpf_map_elem iterator, however, binds its target map at attach time in bpf_iter_attach_map() instead of referencing it from the program, so the exclusivity check is never reached. On top of that, the iterator exposes the map value as a writable buffer.
--- kernel/bpf/map_iter.c | 4 ++++ 1 file changed, 4 insertions(+)
kernel/bpf/map_iter.c +4 -0
@@ -112,6 +112,10 @@ static int bpf_iter_attach_map(struct bpf_prog *prog, map =bpf_map_get_with_uref (linfo->map.map_fd);if (IS_ERR (map))return PTR_ERR (map); +if (map->excl_prog_sha) { + err = -EPERM ; + goto put_map; + } if (map->map_type == BPF_MAP_TYPE_PERCPU_HASH || map->map_type == BPF_MAP_TYPE_LRU_PERCPU_HASH ||
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 315/1611 tick/sched: Fix TOCTOU in nohz idle time fetch
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Frederic Weisbecker <[email protected]>
[ Upstream commit 86db4084b4b5d1a074bcc66c108a4c9d266812d4 ]
When the nohz idle time is fetched, the current clock timestamp is taken outside the seqcount, which can result in a race as reported by Sashiko:
get_cpu_sleep_time_us() tick_nohz_start_idle()
----------------------- ---------------------
now = ktime_get()
write_seqcount_begin(idle_sleeptime_seq);
idle_entrytime = ktime_get()
tick_sched_flag_set(ts, TS_FLAG_IDLE_ACTIVE);
write_seqcount_end(&ts->idle_sleeptime_seq);
read_seqcount_begin(idle_sleeptime_seq)
delta = now - idle_entrytime);
//!! But now < idle_entrytime
idle = *sleeptime + delta;
read_seqcount_retry(&ts->idle_sleeptime_seq, seq)Here the read side fetches the timestamp before the write side and its update. As a result the time delta computed on the read side is negative (ktime_t is signed) and breaks the cputime monotonicity guarantee.
This could possibly be fixed with reading the current clock timestamp inside the seqcount but the reader overhead might then increase. Also simply checking that the current timestamp is above the idle entry time is enough to prevent any issue of the like.
--- kernel/time/tick-sched.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)
kernel/time/tick-sched.c +6 -5
@@ -766,15 +766,16 @@ static u64 get_cpu_sleep_time_us(struct tick_sched *ts, ktime_t *sleeptime, *last_update_time =ktime_to_us (now);do { +ktime_t delta =0 ; + seq =read_seqcount_begin (&ts->idle_sleeptime_seq);if (tick_sched_flag_test (ts,TS_FLAG_IDLE_ACTIVE ) && compute_delta) { -ktime_t delta =ktime_sub (now, ts->idle_entrytime); - - idle =ktime_add (*sleeptime, delta); - }else { - idle = *sleeptime; +if (now > ts->idle_entrytime) + delta =ktime_sub (now, ts->idle_entrytime); } + + idle =ktime_add (*sleeptime, delta); }while (read_seqcount_retry (&ts->idle_sleeptime_seq, seq));return ktime_to_us (idle);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 316/1611 lib/test_meminit: use && for bools
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Potapenko <[email protected]>
[ Upstream commit 8e0c2085c978ed6d9764d79fc785920360096f21 ]
As pointed out by Dan Carpenter, test_kmemcache() was using a bitwise AND on two bools instead of a boolean AND. Fix this for the sake of code cleanliness.
--- lib/test_meminit.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
lib/test_meminit.c +1 -1
@@ -387,7 +387,7 @@ static int __init test_kmemcache(int *total_failures) ctor = flags &1 ; rcu = flags &2 ; zero = flags &4 ; -if (ctor & zero) +if (ctor && zero)continue ; num_tests +=do_kmem_cache_size (size, ctor, rcu, zero, &failures);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 317/1611 riscv: dts: sophgo: sg2044: use hex for CPU unit address
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Inochi Amaoto <[email protected]>
[ Upstream commit 207cbc477406a72952e27ace2eadbae55164f129 ]
Previous the CPU unit address cpu of sg2044 use decimal, it is not following the general convention for unit addresses of the OF. Convent the unit address to hex to resolve this problem.
The introduces a small change for the CPU node name, but it should nothing since there is no direct full-path reference to these CPU nodes.
--- arch/riscv/boot/dts/sophgo/sg2044-cpus.dtsi | 236 ++++++++++---------- 1 file changed, 118 insertions(+), 118 deletions(-)
arch/riscv/boot/dts/sophgo/sg2044-cpus.dtsi +118 -118
@@ -14,7 +14,7 @@ cpus { cpu0: cpu@0 { compatible = "thead,c920", "riscv"; - reg = <0>; + reg = <0x0>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -50,7 +50,7 @@ cpu0_intc: interrupt-controller { cpu1: cpu@1 { compatible = "thead,c920", "riscv"; - reg = <1>; + reg = <0x1>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -86,7 +86,7 @@ cpu1_intc: interrupt-controller { cpu2: cpu@2 { compatible = "thead,c920", "riscv"; - reg = <2>; + reg = <0x2>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -122,7 +122,7 @@ cpu2_intc: interrupt-controller { cpu3: cpu@3 { compatible = "thead,c920", "riscv"; - reg = <3>; + reg = <0x3>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -158,7 +158,7 @@ cpu3_intc: interrupt-controller { cpu4: cpu@4 { compatible = "thead,c920", "riscv"; - reg = <4>; + reg = <0x4>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -194,7 +194,7 @@ cpu4_intc: interrupt-controller { cpu5: cpu@5 { compatible = "thead,c920", "riscv"; - reg = <5>; + reg = <0x5>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -230,7 +230,7 @@ cpu5_intc: interrupt-controller { cpu6: cpu@6 { compatible = "thead,c920", "riscv"; - reg = <6>; + reg = <0x6>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -266,7 +266,7 @@ cpu6_intc: interrupt-controller { cpu7: cpu@7 { compatible = "thead,c920", "riscv"; - reg = <7>; + reg = <0x7>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -302,7 +302,7 @@ cpu7_intc: interrupt-controller { cpu8: cpu@8 { compatible = "thead,c920", "riscv"; - reg = <8>; + reg = <0x8>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -338,7 +338,7 @@ cpu8_intc: interrupt-controller { cpu9: cpu@9 { compatible = "thead,c920", "riscv"; - reg = <9>; + reg = <0x9>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -372,9 +372,9 @@ cpu9_intc: interrupt-controller { }; }; - cpu10: cpu@10 { + cpu10: cpu@a { compatible = "thead,c920", "riscv"; - reg = <10>; + reg = <0xa>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -408,9 +408,9 @@ cpu10_intc: interrupt-controller { }; }; - cpu11: cpu@11 { + cpu11: cpu@b { compatible = "thead,c920", "riscv"; - reg = <11>; + reg = <0xb>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -444,9 +444,9 @@ cpu11_intc: interrupt-controller { }; }; - cpu12: cpu@12 { + cpu12: cpu@c { compatible = "thead,c920", "riscv"; - reg = <12>; + reg = <0xc>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -480,9 +480,9 @@ cpu12_intc: interrupt-controller { }; }; - cpu13: cpu@13 { + cpu13: cpu@d { compatible = "thead,c920", "riscv"; - reg = <13>; + reg = <0xd>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -516,9 +516,9 @@ cpu13_intc: interrupt-controller { }; }; - cpu14: cpu@14 { + cpu14: cpu@e { compatible = "thead,c920", "riscv"; - reg = <14>; + reg = <0xe>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -552,9 +552,9 @@ cpu14_intc: interrupt-controller { }; }; - cpu15: cpu@15 { + cpu15: cpu@f { compatible = "thead,c920", "riscv"; - reg = <15>; + reg = <0xf>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -588,9 +588,9 @@ cpu15_intc: interrupt-controller { }; }; - cpu16: cpu@16 { + cpu16: cpu@10 { compatible = "thead,c920", "riscv"; - reg = <16>; + reg = <0x10>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -624,9 +624,9 @@ cpu16_intc: interrupt-controller { }; }; - cpu17: cpu@17 { + cpu17: cpu@11 { compatible = "thead,c920", "riscv"; - reg = <17>; + reg = <0x11>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -660,9 +660,9 @@ cpu17_intc: interrupt-controller { }; }; - cpu18: cpu@18 { + cpu18: cpu@12 { compatible = "thead,c920", "riscv"; - reg = <18>; + reg = <0x12>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -696,9 +696,9 @@ cpu18_intc: interrupt-controller { }; }; - cpu19: cpu@19 { + cpu19: cpu@13 { compatible = "thead,c920", "riscv"; - reg = <19>; + reg = <0x13>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -732,9 +732,9 @@ cpu19_intc: interrupt-controller { }; }; - cpu20: cpu@20 { + cpu20: cpu@14 { compatible = "thead,c920", "riscv"; - reg = <20>; + reg = <0x14>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -768,9 +768,9 @@ cpu20_intc: interrupt-controller { }; }; - cpu21: cpu@21 { + cpu21: cpu@15 { compatible = "thead,c920", "riscv"; - reg = <21>; + reg = <0x15>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -804,9 +804,9 @@ cpu21_intc: interrupt-controller { }; }; - cpu22: cpu@22 { + cpu22: cpu@16 { compatible = "thead,c920", "riscv"; - reg = <22>; + reg = <0x16>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -840,9 +840,9 @@ cpu22_intc: interrupt-controller { }; }; - cpu23: cpu@23 { + cpu23: cpu@17 { compatible = "thead,c920", "riscv"; - reg = <23>; + reg = <0x17>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -876,9 +876,9 @@ cpu23_intc: interrupt-controller { }; }; - cpu24: cpu@24 { + cpu24: cpu@18 { compatible = "thead,c920", "riscv"; - reg = <24>; + reg = <0x18>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -912,9 +912,9 @@ cpu24_intc: interrupt-controller { }; }; - cpu25: cpu@25 { + cpu25: cpu@19 { compatible = "thead,c920", "riscv"; - reg = <25>; + reg = <0x19>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -948,9 +948,9 @@ cpu25_intc: interrupt-controller { }; }; - cpu26: cpu@26 { + cpu26: cpu@1a { compatible = "thead,c920", "riscv"; - reg = <26>; + reg = <0x1a>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -984,9 +984,9 @@ cpu26_intc: interrupt-controller { }; }; - cpu27: cpu@27 { + cpu27: cpu@1b { compatible = "thead,c920", "riscv"; - reg = <27>; + reg = <0x1b>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1020,9 +1020,9 @@ cpu27_intc: interrupt-controller { }; }; - cpu28: cpu@28 { + cpu28: cpu@1c { compatible = "thead,c920", "riscv"; - reg = <28>; + reg = <0x1c>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1056,9 +1056,9 @@ cpu28_intc: interrupt-controller { }; }; - cpu29: cpu@29 { + cpu29: cpu@1d { compatible = "thead,c920", "riscv"; - reg = <29>; + reg = <0x1d>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1092,9 +1092,9 @@ cpu29_intc: interrupt-controller { }; }; - cpu30: cpu@30 { + cpu30: cpu@1e { compatible = "thead,c920", "riscv"; - reg = <30>; + reg = <0x1e>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1128,9 +1128,9 @@ cpu30_intc: interrupt-controller { }; }; - cpu31: cpu@31 { + cpu31: cpu@1f { compatible = "thead,c920", "riscv"; - reg = <31>; + reg = <0x1f>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1164,9 +1164,9 @@ cpu31_intc: interrupt-controller { }; }; - cpu32: cpu@32 { + cpu32: cpu@20 { compatible = "thead,c920", "riscv"; - reg = <32>; + reg = <0x20>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1200,9 +1200,9 @@ cpu32_intc: interrupt-controller { }; }; - cpu33: cpu@33 { + cpu33: cpu@21 { compatible = "thead,c920", "riscv"; - reg = <33>; + reg = <0x21>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1236,9 +1236,9 @@ cpu33_intc: interrupt-controller { }; }; - cpu34: cpu@34 { + cpu34: cpu@22 { compatible = "thead,c920", "riscv"; - reg = <34>; + reg = <0x22>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1272,9 +1272,9 @@ cpu34_intc: interrupt-controller { }; }; - cpu35: cpu@35 { + cpu35: cpu@23 { compatible = "thead,c920", "riscv"; - reg = <35>; + reg = <0x23>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1308,9 +1308,9 @@ cpu35_intc: interrupt-controller { }; }; - cpu36: cpu@36 { + cpu36: cpu@24 { compatible = "thead,c920", "riscv"; - reg = <36>; + reg = <0x24>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1344,9 +1344,9 @@ cpu36_intc: interrupt-controller { }; }; - cpu37: cpu@37 { + cpu37: cpu@25 { compatible = "thead,c920", "riscv"; - reg = <37>; + reg = <0x25>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1380,9 +1380,9 @@ cpu37_intc: interrupt-controller { }; }; - cpu38: cpu@38 { + cpu38: cpu@26 { compatible = "thead,c920", "riscv"; - reg = <38>; + reg = <0x26>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1416,9 +1416,9 @@ cpu38_intc: interrupt-controller { }; }; - cpu39: cpu@39 { + cpu39: cpu@27 { compatible = "thead,c920", "riscv"; - reg = <39>; + reg = <0x27>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1452,9 +1452,9 @@ cpu39_intc: interrupt-controller { }; }; - cpu40: cpu@40 { + cpu40: cpu@28 { compatible = "thead,c920", "riscv"; - reg = <40>; + reg = <0x28>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1488,9 +1488,9 @@ cpu40_intc: interrupt-controller { }; }; - cpu41: cpu@41 { + cpu41: cpu@29 { compatible = "thead,c920", "riscv"; - reg = <41>; + reg = <0x29>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1524,9 +1524,9 @@ cpu41_intc: interrupt-controller { }; }; - cpu42: cpu@42 { + cpu42: cpu@2a { compatible = "thead,c920", "riscv"; - reg = <42>; + reg = <0x2a>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1560,9 +1560,9 @@ cpu42_intc: interrupt-controller { }; }; - cpu43: cpu@43 { + cpu43: cpu@2b { compatible = "thead,c920", "riscv"; - reg = <43>; + reg = <0x2b>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1596,9 +1596,9 @@ cpu43_intc: interrupt-controller { }; }; - cpu44: cpu@44 { + cpu44: cpu@2c { compatible = "thead,c920", "riscv"; - reg = <44>; + reg = <0x2c>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1632,9 +1632,9 @@ cpu44_intc: interrupt-controller { }; }; - cpu45: cpu@45 { + cpu45: cpu@2d { compatible = "thead,c920", "riscv"; - reg = <45>; + reg = <0x2d>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1668,9 +1668,9 @@ cpu45_intc: interrupt-controller { }; }; - cpu46: cpu@46 { + cpu46: cpu@2e { compatible = "thead,c920", "riscv"; - reg = <46>; + reg = <0x2e>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1704,9 +1704,9 @@ cpu46_intc: interrupt-controller { }; }; - cpu47: cpu@47 { + cpu47: cpu@2f { compatible = "thead,c920", "riscv"; - reg = <47>; + reg = <0x2f>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1740,9 +1740,9 @@ cpu47_intc: interrupt-controller { }; }; - cpu48: cpu@48 { + cpu48: cpu@30 { compatible = "thead,c920", "riscv"; - reg = <48>; + reg = <0x30>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1776,9 +1776,9 @@ cpu48_intc: interrupt-controller { }; }; - cpu49: cpu@49 { + cpu49: cpu@31 { compatible = "thead,c920", "riscv"; - reg = <49>; + reg = <0x31>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1812,9 +1812,9 @@ cpu49_intc: interrupt-controller { }; }; - cpu50: cpu@50 { + cpu50: cpu@32 { compatible = "thead,c920", "riscv"; - reg = <50>; + reg = <0x32>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1848,9 +1848,9 @@ cpu50_intc: interrupt-controller { }; }; - cpu51: cpu@51 { + cpu51: cpu@33 { compatible = "thead,c920", "riscv"; - reg = <51>; + reg = <0x33>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1884,9 +1884,9 @@ cpu51_intc: interrupt-controller { }; }; - cpu52: cpu@52 { + cpu52: cpu@34 { compatible = "thead,c920", "riscv"; - reg = <52>; + reg = <0x34>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1920,9 +1920,9 @@ cpu52_intc: interrupt-controller { }; }; - cpu53: cpu@53 { + cpu53: cpu@35 { compatible = "thead,c920", "riscv"; - reg = <53>; + reg = <0x35>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1956,9 +1956,9 @@ cpu53_intc: interrupt-controller { }; }; - cpu54: cpu@54 { + cpu54: cpu@36 { compatible = "thead,c920", "riscv"; - reg = <54>; + reg = <0x36>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1992,9 +1992,9 @@ cpu54_intc: interrupt-controller { }; }; - cpu55: cpu@55 { + cpu55: cpu@37 { compatible = "thead,c920", "riscv"; - reg = <55>; + reg = <0x37>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2028,9 +2028,9 @@ cpu55_intc: interrupt-controller { }; }; - cpu56: cpu@56 { + cpu56: cpu@38 { compatible = "thead,c920", "riscv"; - reg = <56>; + reg = <0x38>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2064,9 +2064,9 @@ cpu56_intc: interrupt-controller { }; }; - cpu57: cpu@57 { + cpu57: cpu@39 { compatible = "thead,c920", "riscv"; - reg = <57>; + reg = <0x39>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2100,9 +2100,9 @@ cpu57_intc: interrupt-controller { }; }; - cpu58: cpu@58 { + cpu58: cpu@3a { compatible = "thead,c920", "riscv"; - reg = <58>; + reg = <0x3a>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2136,9 +2136,9 @@ cpu58_intc: interrupt-controller { }; }; - cpu59: cpu@59 { + cpu59: cpu@3b { compatible = "thead,c920", "riscv"; - reg = <59>; + reg = <0x3b>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2172,9 +2172,9 @@ cpu59_intc: interrupt-controller { }; }; - cpu60: cpu@60 { + cpu60: cpu@3c { compatible = "thead,c920", "riscv"; - reg = <60>; + reg = <0x3c>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2208,9 +2208,9 @@ cpu60_intc: interrupt-controller { }; }; - cpu61: cpu@61 { + cpu61: cpu@3d { compatible = "thead,c920", "riscv"; - reg = <61>; + reg = <0x3d>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2244,9 +2244,9 @@ cpu61_intc: interrupt-controller { }; }; - cpu62: cpu@62 { + cpu62: cpu@3e { compatible = "thead,c920", "riscv"; - reg = <62>; + reg = <0x3e>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2280,9 +2280,9 @@ cpu62_intc: interrupt-controller { }; }; - cpu63: cpu@63 { + cpu63: cpu@3f { compatible = "thead,c920", "riscv"; - reg = <63>; + reg = <0x3f>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 318/1611 riscv: dts: sophgo: sg2042: use hex for CPU unit address
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Inochi Amaoto <[email protected]>
[ Upstream commit a7e658907686528fe06a11828b04a3e42df9ef18 ]
Previous the CPU unit address cpu of sg2042 use decimal, it is not following the general convention for unit addresses of the OF. Convent the unit address to hex to resolve this problem.
The introduces a small change for the CPU node name, but it should affect nothing since there is no direct full-path reference to these CPU nodes.
--- arch/riscv/boot/dts/sophgo/sg2042-cpus.dtsi | 236 ++++++++++---------- 1 file changed, 118 insertions(+), 118 deletions(-)
arch/riscv/boot/dts/sophgo/sg2042-cpus.dtsi +118 -118
@@ -263,7 +263,7 @@ cpu0: cpu@0 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <0>; + reg = <0x0>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -291,7 +291,7 @@ cpu1: cpu@1 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <1>; + reg = <0x1>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -319,7 +319,7 @@ cpu2: cpu@2 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <2>; + reg = <0x2>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -347,7 +347,7 @@ cpu3: cpu@3 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <3>; + reg = <0x3>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -375,7 +375,7 @@ cpu4: cpu@4 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <4>; + reg = <0x4>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -403,7 +403,7 @@ cpu5: cpu@5 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <5>; + reg = <0x5>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -431,7 +431,7 @@ cpu6: cpu@6 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <6>; + reg = <0x6>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -459,7 +459,7 @@ cpu7: cpu@7 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <7>; + reg = <0x7>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -487,7 +487,7 @@ cpu8: cpu@8 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <8>; + reg = <0x8>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -515,7 +515,7 @@ cpu9: cpu@9 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <9>; + reg = <0x9>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -533,7 +533,7 @@ cpu9_intc: interrupt-controller { }; }; - cpu10: cpu@10 { + cpu10: cpu@a { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -543,7 +543,7 @@ cpu10: cpu@10 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <10>; + reg = <0xa>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -561,7 +561,7 @@ cpu10_intc: interrupt-controller { }; }; - cpu11: cpu@11 { + cpu11: cpu@b { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -571,7 +571,7 @@ cpu11: cpu@11 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <11>; + reg = <0xb>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -589,7 +589,7 @@ cpu11_intc: interrupt-controller { }; }; - cpu12: cpu@12 { + cpu12: cpu@c { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -599,7 +599,7 @@ cpu12: cpu@12 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <12>; + reg = <0xc>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -617,7 +617,7 @@ cpu12_intc: interrupt-controller { }; }; - cpu13: cpu@13 { + cpu13: cpu@d { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -627,7 +627,7 @@ cpu13: cpu@13 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <13>; + reg = <0xd>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -645,7 +645,7 @@ cpu13_intc: interrupt-controller { }; }; - cpu14: cpu@14 { + cpu14: cpu@e { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -655,7 +655,7 @@ cpu14: cpu@14 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <14>; + reg = <0xe>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -673,7 +673,7 @@ cpu14_intc: interrupt-controller { }; }; - cpu15: cpu@15 { + cpu15: cpu@f { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -683,7 +683,7 @@ cpu15: cpu@15 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <15>; + reg = <0xf>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -701,7 +701,7 @@ cpu15_intc: interrupt-controller { }; }; - cpu16: cpu@16 { + cpu16: cpu@10 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -711,7 +711,7 @@ cpu16: cpu@16 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <16>; + reg = <0x10>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -729,7 +729,7 @@ cpu16_intc: interrupt-controller { }; }; - cpu17: cpu@17 { + cpu17: cpu@11 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -739,7 +739,7 @@ cpu17: cpu@17 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <17>; + reg = <0x11>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -757,7 +757,7 @@ cpu17_intc: interrupt-controller { }; }; - cpu18: cpu@18 { + cpu18: cpu@12 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -767,7 +767,7 @@ cpu18: cpu@18 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <18>; + reg = <0x12>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -785,7 +785,7 @@ cpu18_intc: interrupt-controller { }; }; - cpu19: cpu@19 { + cpu19: cpu@13 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -795,7 +795,7 @@ cpu19: cpu@19 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <19>; + reg = <0x13>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -813,7 +813,7 @@ cpu19_intc: interrupt-controller { }; }; - cpu20: cpu@20 { + cpu20: cpu@14 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -823,7 +823,7 @@ cpu20: cpu@20 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <20>; + reg = <0x14>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -841,7 +841,7 @@ cpu20_intc: interrupt-controller { }; }; - cpu21: cpu@21 { + cpu21: cpu@15 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -851,7 +851,7 @@ cpu21: cpu@21 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <21>; + reg = <0x15>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -869,7 +869,7 @@ cpu21_intc: interrupt-controller { }; }; - cpu22: cpu@22 { + cpu22: cpu@16 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -879,7 +879,7 @@ cpu22: cpu@22 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <22>; + reg = <0x16>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -897,7 +897,7 @@ cpu22_intc: interrupt-controller { }; }; - cpu23: cpu@23 { + cpu23: cpu@17 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -907,7 +907,7 @@ cpu23: cpu@23 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <23>; + reg = <0x17>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -925,7 +925,7 @@ cpu23_intc: interrupt-controller { }; }; - cpu24: cpu@24 { + cpu24: cpu@18 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -935,7 +935,7 @@ cpu24: cpu@24 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <24>; + reg = <0x18>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -953,7 +953,7 @@ cpu24_intc: interrupt-controller { }; }; - cpu25: cpu@25 { + cpu25: cpu@19 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -963,7 +963,7 @@ cpu25: cpu@25 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <25>; + reg = <0x19>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -981,7 +981,7 @@ cpu25_intc: interrupt-controller { }; }; - cpu26: cpu@26 { + cpu26: cpu@1a { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -991,7 +991,7 @@ cpu26: cpu@26 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <26>; + reg = <0x1a>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1009,7 +1009,7 @@ cpu26_intc: interrupt-controller { }; }; - cpu27: cpu@27 { + cpu27: cpu@1b { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1019,7 +1019,7 @@ cpu27: cpu@27 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <27>; + reg = <0x1b>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1037,7 +1037,7 @@ cpu27_intc: interrupt-controller { }; }; - cpu28: cpu@28 { + cpu28: cpu@1c { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1047,7 +1047,7 @@ cpu28: cpu@28 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <28>; + reg = <0x1c>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1065,7 +1065,7 @@ cpu28_intc: interrupt-controller { }; }; - cpu29: cpu@29 { + cpu29: cpu@1d { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1075,7 +1075,7 @@ cpu29: cpu@29 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <29>; + reg = <0x1d>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1093,7 +1093,7 @@ cpu29_intc: interrupt-controller { }; }; - cpu30: cpu@30 { + cpu30: cpu@1e { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1103,7 +1103,7 @@ cpu30: cpu@30 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <30>; + reg = <0x1e>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1121,7 +1121,7 @@ cpu30_intc: interrupt-controller { }; }; - cpu31: cpu@31 { + cpu31: cpu@1f { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1131,7 +1131,7 @@ cpu31: cpu@31 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <31>; + reg = <0x1f>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1149,7 +1149,7 @@ cpu31_intc: interrupt-controller { }; }; - cpu32: cpu@32 { + cpu32: cpu@20 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1159,7 +1159,7 @@ cpu32: cpu@32 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <32>; + reg = <0x20>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1177,7 +1177,7 @@ cpu32_intc: interrupt-controller { }; }; - cpu33: cpu@33 { + cpu33: cpu@21 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1187,7 +1187,7 @@ cpu33: cpu@33 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <33>; + reg = <0x21>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1205,7 +1205,7 @@ cpu33_intc: interrupt-controller { }; }; - cpu34: cpu@34 { + cpu34: cpu@22 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1215,7 +1215,7 @@ cpu34: cpu@34 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <34>; + reg = <0x22>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1233,7 +1233,7 @@ cpu34_intc: interrupt-controller { }; }; - cpu35: cpu@35 { + cpu35: cpu@23 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1243,7 +1243,7 @@ cpu35: cpu@35 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <35>; + reg = <0x23>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1261,7 +1261,7 @@ cpu35_intc: interrupt-controller { }; }; - cpu36: cpu@36 { + cpu36: cpu@24 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1271,7 +1271,7 @@ cpu36: cpu@36 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <36>; + reg = <0x24>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1289,7 +1289,7 @@ cpu36_intc: interrupt-controller { }; }; - cpu37: cpu@37 { + cpu37: cpu@25 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1299,7 +1299,7 @@ cpu37: cpu@37 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <37>; + reg = <0x25>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1317,7 +1317,7 @@ cpu37_intc: interrupt-controller { }; }; - cpu38: cpu@38 { + cpu38: cpu@26 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1327,7 +1327,7 @@ cpu38: cpu@38 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <38>; + reg = <0x26>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1345,7 +1345,7 @@ cpu38_intc: interrupt-controller { }; }; - cpu39: cpu@39 { + cpu39: cpu@27 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1355,7 +1355,7 @@ cpu39: cpu@39 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <39>; + reg = <0x27>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1373,7 +1373,7 @@ cpu39_intc: interrupt-controller { }; }; - cpu40: cpu@40 { + cpu40: cpu@28 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1383,7 +1383,7 @@ cpu40: cpu@40 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <40>; + reg = <0x28>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1401,7 +1401,7 @@ cpu40_intc: interrupt-controller { }; }; - cpu41: cpu@41 { + cpu41: cpu@29 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1411,7 +1411,7 @@ cpu41: cpu@41 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <41>; + reg = <0x29>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1429,7 +1429,7 @@ cpu41_intc: interrupt-controller { }; }; - cpu42: cpu@42 { + cpu42: cpu@2a { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1439,7 +1439,7 @@ cpu42: cpu@42 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <42>; + reg = <0x2a>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1457,7 +1457,7 @@ cpu42_intc: interrupt-controller { }; }; - cpu43: cpu@43 { + cpu43: cpu@2b { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1467,7 +1467,7 @@ cpu43: cpu@43 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <43>; + reg = <0x2b>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1485,7 +1485,7 @@ cpu43_intc: interrupt-controller { }; }; - cpu44: cpu@44 { + cpu44: cpu@2c { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1495,7 +1495,7 @@ cpu44: cpu@44 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <44>; + reg = <0x2c>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1513,7 +1513,7 @@ cpu44_intc: interrupt-controller { }; }; - cpu45: cpu@45 { + cpu45: cpu@2d { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1523,7 +1523,7 @@ cpu45: cpu@45 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <45>; + reg = <0x2d>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1541,7 +1541,7 @@ cpu45_intc: interrupt-controller { }; }; - cpu46: cpu@46 { + cpu46: cpu@2e { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1551,7 +1551,7 @@ cpu46: cpu@46 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <46>; + reg = <0x2e>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1569,7 +1569,7 @@ cpu46_intc: interrupt-controller { }; }; - cpu47: cpu@47 { + cpu47: cpu@2f { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1579,7 +1579,7 @@ cpu47: cpu@47 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <47>; + reg = <0x2f>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1597,7 +1597,7 @@ cpu47_intc: interrupt-controller { }; }; - cpu48: cpu@48 { + cpu48: cpu@30 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1607,7 +1607,7 @@ cpu48: cpu@48 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <48>; + reg = <0x30>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1625,7 +1625,7 @@ cpu48_intc: interrupt-controller { }; }; - cpu49: cpu@49 { + cpu49: cpu@31 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1635,7 +1635,7 @@ cpu49: cpu@49 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <49>; + reg = <0x31>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1653,7 +1653,7 @@ cpu49_intc: interrupt-controller { }; }; - cpu50: cpu@50 { + cpu50: cpu@32 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1663,7 +1663,7 @@ cpu50: cpu@50 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <50>; + reg = <0x32>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1681,7 +1681,7 @@ cpu50_intc: interrupt-controller { }; }; - cpu51: cpu@51 { + cpu51: cpu@33 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1691,7 +1691,7 @@ cpu51: cpu@51 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <51>; + reg = <0x33>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1709,7 +1709,7 @@ cpu51_intc: interrupt-controller { }; }; - cpu52: cpu@52 { + cpu52: cpu@34 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1719,7 +1719,7 @@ cpu52: cpu@52 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <52>; + reg = <0x34>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1737,7 +1737,7 @@ cpu52_intc: interrupt-controller { }; }; - cpu53: cpu@53 { + cpu53: cpu@35 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1747,7 +1747,7 @@ cpu53: cpu@53 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <53>; + reg = <0x35>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1765,7 +1765,7 @@ cpu53_intc: interrupt-controller { }; }; - cpu54: cpu@54 { + cpu54: cpu@36 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1775,7 +1775,7 @@ cpu54: cpu@54 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <54>; + reg = <0x36>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1793,7 +1793,7 @@ cpu54_intc: interrupt-controller { }; }; - cpu55: cpu@55 { + cpu55: cpu@37 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1803,7 +1803,7 @@ cpu55: cpu@55 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <55>; + reg = <0x37>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1821,7 +1821,7 @@ cpu55_intc: interrupt-controller { }; }; - cpu56: cpu@56 { + cpu56: cpu@38 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1831,7 +1831,7 @@ cpu56: cpu@56 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <56>; + reg = <0x38>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1849,7 +1849,7 @@ cpu56_intc: interrupt-controller { }; }; - cpu57: cpu@57 { + cpu57: cpu@39 { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1859,7 +1859,7 @@ cpu57: cpu@57 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <57>; + reg = <0x39>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1877,7 +1877,7 @@ cpu57_intc: interrupt-controller { }; }; - cpu58: cpu@58 { + cpu58: cpu@3a { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1887,7 +1887,7 @@ cpu58: cpu@58 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <58>; + reg = <0x3a>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1905,7 +1905,7 @@ cpu58_intc: interrupt-controller { }; }; - cpu59: cpu@59 { + cpu59: cpu@3b { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1915,7 +1915,7 @@ cpu59: cpu@59 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <59>; + reg = <0x3b>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1933,7 +1933,7 @@ cpu59_intc: interrupt-controller { }; }; - cpu60: cpu@60 { + cpu60: cpu@3c { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1943,7 +1943,7 @@ cpu60: cpu@60 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <60>; + reg = <0x3c>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1961,7 +1961,7 @@ cpu60_intc: interrupt-controller { }; }; - cpu61: cpu@61 { + cpu61: cpu@3d { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1971,7 +1971,7 @@ cpu61: cpu@61 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <61>; + reg = <0x3d>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -1989,7 +1989,7 @@ cpu61_intc: interrupt-controller { }; }; - cpu62: cpu@62 { + cpu62: cpu@3e { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -1999,7 +1999,7 @@ cpu62: cpu@62 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <62>; + reg = <0x3e>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
@@ -2017,7 +2017,7 @@ cpu62_intc: interrupt-controller { }; }; - cpu63: cpu@63 { + cpu63: cpu@3f { compatible = "thead,c920", "riscv"; device_type = "cpu"; riscv,isa = "rv64imafdc";
@@ -2027,7 +2027,7 @@ cpu63: cpu@63 { "zifencei", "zihpm", "zfh", "xtheadvector"; thead,vlenb = <16>; - reg = <63>; + reg = <0x3f>; i-cache-block-size = <64>; i-cache-size = <65536>; i-cache-sets = <512>;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 319/1611 configfs_lookup(): dont leave ->s_dentry dangling on failure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
[ Upstream commit 10da12d352b7b2bb330a8609fdda9a58bf0e9856 ]
Normally ->s_dentry is cleared when dentry it's pointing to becomes negative (on eviction, realistically). However, that only happens if dentry gets to be positive in the first place; in case of inode allocation failure dentry never becomes positive, so ->d_iput() is not called at all.
We do part of what normally would've been done by configfs_d_iput() (dropping the reference to configfs_dirent) manually, but we do not clear ->s_dentry there. Sloppy as it is, it does not matter in case of configfs_create_{dir,link}() - there configfs_dirent does not survive dropping the sole reference to it.
However, for configfs_lookup() it *does* survive, with a dangling pointer to soon to be freed dentry sitting it its ->s_dentry.
Subsequent getdents(2) in that directory will end up dereferencing that pointer in order to pick the inode number. Use after free...
This is the minimal fix; the right approach is to set the linkage between dentry and configfs_dirent only after we know that we have an inode, but that takes more surgery and the bug had been there since 2006, so...
--- fs/configfs/dir.c | 3 +++ 1 file changed, 3 insertions(+)
fs/configfs/dir.c +3 -0
@@ -480,6 +480,9 @@ static struct dentry * configfs_lookup(struct inode *dir, inode =configfs_create (dentry, mode);if (IS_ERR (inode)) { +spin_lock (&configfs_dirent_lock); + sd->s_dentry =NULL ; +spin_unlock (&configfs_dirent_lock);configfs_put (sd);return ERR_CAST (inode); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 320/1611 lockdep/selftests: Restore migrate_disable() state on PREEMPT_RT
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Karl Mehltretter <[email protected]>
[ Upstream commit d8c897b20bf4d4cbb1e935a8ceb666bcc0f82580 ]
The lockdep selftests deliberately run unbalanced locking patterns. dotest() restores the task state they leave behind before running the next testcase.
On PREEMPT_RT, spin_lock() uses migrate_disable() instead of disabling preemption. dotest() cleans up the resulting migration-disabled state, but that cleanup is still guarded by CONFIG_SMP.
That used to match the scheduler data model, where migration_disabled was also CONFIG_SMP-only. The commit referenced below made SMP scheduler state unconditional, so CONFIG_SMP=n PREEMPT_RT kernels with CONFIG_DEBUG_LOCKING_API_SELFTESTS=y report success from the selftests and then trip over stale current->migration_disabled state:
releasing a pinned lock
bad: scheduling from the idle thread!
Kernel panic - not syncing: Fatal exception
Save and restore current->migration_disabled for every PREEMPT_RT build.
--- lib/locking-selftest.c | 4 ---- 1 file changed, 4 deletions(-)
lib/locking-selftest.c +0 -4
@@ -1431,9 +1431,7 @@ static void dotest(void (*testcase_fn)(void), int expected, int lockclass_mask) {int saved_preempt_count =preempt_count ();#ifdef CONFIG_PREEMPT_RT -#ifdef CONFIG_SMP int saved_mgd_count = current->migration_disabled; -#endif int saved_rcu_count = current->rcu_read_lock_nesting;#endif
@@ -1471,10 +1469,8 @@ static void dotest(void (*testcase_fn)(void), int expected, int lockclass_mask)preempt_count_set (saved_preempt_count);#ifdef CONFIG_PREEMPT_RT -#ifdef CONFIG_SMP while (current->migration_disabled > saved_mgd_count)migrate_enable (); -#endif while (current->rcu_read_lock_nesting > saved_rcu_count)rcu_read_unlock ();
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 321/1611 lockdep/selftests: Restore sched_rt_mutex state on PREEMPT_RT
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Karl Mehltretter <[email protected]>
[ Upstream commit 06961d60a0e410bf8df69ccff7eb1bd824912b8f ]
The WW-mutex selftests deliberately exercise failing lock paths. On PREEMPT_RT, some of those paths enter the RT-mutex scheduler helpers.
The change referenced by the Fixes tag made those helpers track RT-mutex scheduling state in current->sched_rt_mutex. The bit is normally cleared by the matching post-schedule helper, but some WW-mutex selftests disable the runtime debug_locks flag before that happens. With debug_locks cleared, lockdep_assert() does not evaluate the expression that clears the bit, leaving stale state for the next testcase.
With CONFIG_PREEMPT_RT=y and CONFIG_DEBUG_LOCKING_API_SELFTESTS=y, that stale state produces warnings such as:
WARNING: kernel/sched/core.c:7557 at rt_mutex_pre_schedule+0x26/0x2d RIP: 0010:rt_mutex_pre_schedule+0x26/0x2d
Save and restore current->sched_rt_mutex around each testcase, matching the existing PREEMPT_RT cleanup for task-local migration and RCU state.
--- lib/locking-selftest.c | 3 +++ 1 file changed, 3 insertions(+)
lib/locking-selftest.c +3 -0
@@ -1433,6 +1433,7 @@ static void dotest(void (*testcase_fn)(void), int expected, int lockclass_mask)#ifdef CONFIG_PREEMPT_RT int saved_mgd_count = current->migration_disabled;int saved_rcu_count = current->rcu_read_lock_nesting; +int saved_sched_rt_mutex = current->sched_rt_mutex;#endif WARN_ON (irqs_disabled ());
@@ -1469,6 +1470,8 @@ static void dotest(void (*testcase_fn)(void), int expected, int lockclass_mask)preempt_count_set (saved_preempt_count);#ifdef CONFIG_PREEMPT_RT + current->sched_rt_mutex = saved_sched_rt_mutex; +while (current->migration_disabled > saved_mgd_count)migrate_enable ();
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 322/1611 ext4: fix fast commit wait/wake bit mapping on 64-bit
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Li Chen <[email protected]>
[ Upstream commit 8b3bc93fee6771775243665a0cf31857d6659775 ]
On 64-bit, ext4 dynamic inode states live in the upper half of i_flags, and ext4_test_inode_state() applies the corresponding +32 offset.
The fast-commit wait and wake paths open-coded the wait key with the raw EXT4_STATE_* value. Add small helpers for the state wait word and bit, and use them for the FC_COMMITTING and FC_FLUSHING_DATA waits so the wait key follows the same mapping as the state helpers.
--- fs/ext4/ext4.h | 20 +++++++++++++++++ fs/ext4/fast_commit.c | 50 ++++++++++++++++--------------------------- 2 files changed, 38 insertions(+), 32 deletions(-)
fs/ext4/ext4.h +20 -0
@@ -1990,6 +1990,8 @@ EXT4_INODE_BIT_FNS(flag, flags, 0)static inline int ext4_test_inode_state (struct inode *inode,int bit);static inline void ext4_set_inode_state (struct inode *inode,int bit);static inline void ext4_clear_inode_state (struct inode *inode,int bit); +static inline unsigned long *ext4_inode_state_wait_word (struct inode *inode); +static inline int ext4_inode_state_wait_bit (int bit);#if (BITS_PER_LONG <64 )EXT4_INODE_BIT_FNS (state, state_flags,0 )
@@ -2005,6 +2007,24 @@ static inline void ext4_clear_state_flags(struct ext4_inode_info *ei) /* We depend on the fact that callers will set i_flags */ }#endif + +static inline unsigned long *ext4_inode_state_wait_word (struct inode *inode) +{ +#if (BITS_PER_LONG <64 ) +return &EXT4_I (inode)->i_state_flags; +#else +return &EXT4_I (inode)->i_flags; +#endif +} + +static inline int ext4_inode_state_wait_bit (int bit) +{ +#if (BITS_PER_LONG <64 ) +return bit; +#else +return bit +32 ; +#endif +}#else /* Assume that user mode programs are passing in an ext4fs superblock, not * a kernel struct super_block. This will allow us to call the feature-test
fs/ext4/fast_commit.c +18 -32
98 lines not on this page · raw message
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 323/1611 drm/amdgpu: set sub_block_index for mca ras sub-blocks
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yunxiang Li <[email protected]>
[ Upstream commit baa286df5fb366e4aee5b747443dfc7194fdaa59 ]
The mca ras sub-blocks (mp0, mp1, mpio) all share the AMDGPU_RAS_BLOCK__MCA block id and are distinguished only by sub_block_index. The ras manager object for an mca block is selected with:
con->objs[AMDGPU_RAS_BLOCK__LAST + head->sub_block_index]
Since the rework in commit 7f544c5488cf ("drm/amdgpu: Rework mca ras sw_init") moved the ras_comm setup into amdgpu_mca_mp*_ras_sw_init() but left sub_block_index unset, mp0/mp1/mpio all default to index 0 and collide on the same object slot. mp0 grabs the slot and creates its sysfs node first; mp1 (and mpio) then find the slot already in use, so amdgpu_ras_block_late_init() -> amdgpu_ras_sysfs_create() returns -EINVAL:
amdgpu: mca.mp1 failed to execute ras_block_late_init_default! ret:-22
amdgpu: amdgpu_ras_late_init failed -22
amdgpu: amdgpu_device_ip_late_init failed
amdgpu: Fatal error during GPU init
The error is currently masked because amdgpu_ras_late_init() does not check the return value of amdgpu_ras_block_late_init_default(), but it already leaves mp1/mpio without their sysfs nodes and becomes a fatal init failure as soon as that return value is honored.
Restore the per-sub-block sub_block_index assignment so each mca sub-block maps to its own object slot.
--- drivers/gpu/drm/amd/amdgpu/amdgpu_mca.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu_mca.c +3 -0
@@ -99,6 +99,7 @@ int amdgpu_mca_mp0_ras_sw_init(struct amdgpu_device *adev)strcpy (ras->ras_block.ras_comm.name,"mca.mp0" ); ras->ras_block.ras_comm.block =AMDGPU_RAS_BLOCK__MCA ; + ras->ras_block.ras_comm.sub_block_index =AMDGPU_RAS_MCA_BLOCK__MP0 ; ras->ras_block.ras_comm.type =AMDGPU_RAS_ERROR__MULTI_UNCORRECTABLE ; adev->mca.mp0.ras_if = &ras->ras_block.ras_comm;
@@ -123,6 +124,7 @@ int amdgpu_mca_mp1_ras_sw_init(struct amdgpu_device *adev)strcpy (ras->ras_block.ras_comm.name,"mca.mp1" ); ras->ras_block.ras_comm.block =AMDGPU_RAS_BLOCK__MCA ; + ras->ras_block.ras_comm.sub_block_index =AMDGPU_RAS_MCA_BLOCK__MP1 ; ras->ras_block.ras_comm.type =AMDGPU_RAS_ERROR__MULTI_UNCORRECTABLE ; adev->mca.mp1.ras_if = &ras->ras_block.ras_comm;
@@ -147,6 +149,7 @@ int amdgpu_mca_mpio_ras_sw_init(struct amdgpu_device *adev)strcpy (ras->ras_block.ras_comm.name,"mca.mpio" ); ras->ras_block.ras_comm.block =AMDGPU_RAS_BLOCK__MCA ; + ras->ras_block.ras_comm.sub_block_index =AMDGPU_RAS_MCA_BLOCK__MPIO ; ras->ras_block.ras_comm.type =AMDGPU_RAS_ERROR__MULTI_UNCORRECTABLE ; adev->mca.mpio.ras_if = &ras->ras_block.ras_comm;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 324/1611 bpftool: Use libbpf error code for flow dissector query
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Woojin Ji <[email protected]>
[ Upstream commit 8a7f2bff2165e53595d1e91c160b340f978c0ab7 ]
bpf_prog_query() returns a negative errno on failure. query_flow_dissector() currently closes the namespace fd and then reads errno to decide whether -EINVAL means that the running kernel does not support flow dissector queries.
That errno check controls behavior, not just diagnostics: -EINVAL is handled as a non-fatal old-kernel case, while any other error makes bpftool net fail.
The namespace fd is opened read-only, so close() is not expected to commonly fail in normal use. Still, the BPF_PROG_QUERY error is already available in err, and reading errno after an intervening close() is fragile. If close() does change errno, the compatibility branch may be based on close()'s error instead of the BPF_PROG_QUERY result.
This was reproduced with an LD_PRELOAD fault injector that forced BPF_PROG_QUERY for BPF_FLOW_DISSECTOR to fail with EINVAL and then forced close() on the netns fd to fail with EIO. The unpatched bpftool reported "can't query prog: Input/output error". With this change, the same injected failure is handled as the intended non-fatal EINVAL compatibility case.
Use the libbpf-returned error code instead. Keep the existing errno reset in the non-fatal path to preserve batch mode behavior. The success path is unchanged.
--- tools/bpf/bpftool/net.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/bpf/bpftool/net.c +2 -2
@@ -603,14 +603,14 @@ static int query_flow_dissector(struct bpf_attach_info *attach_info) &attach_flags, prog_ids, &prog_cnt);close (fd);if (err) { -if (errno ==EINVAL ) { +if (err == -EINVAL ) {/* Older kernel's don't support querying * flow dissector programs. */ errno =0 ;return 0 ; } -p_err ("can't query prog: %s" ,strerror (errno)); +p_err ("can't query prog: %s" ,strerror (-err));return -1 ; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 325/1611 vhost: fix vhost_get_avail_idx for a non empty ring
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michael S. Tsirkin <[email protected]>
[ Upstream commit 09861858a68342f851f71c669ac0f69865c32151 ]
vhost_get_avail_idx is supposed to report whether it has updated vq->avail_idx. Instead, it returns whether all entries have been consumed, which is usually the same. But not always - in drivers/vhost/net.c and when mergeable buffers have been enabled, the driver checks whether the combined entries are big enough to store an incoming packet. If not, the driver re-enables notifications with available entries still in the ring. The incorrect return value from vhost_get_avail_idx propagates through vhost_enable_notify and causes the host to livelock if the guest is not making progress, as vhost will immediately disable notifications and retry using the available entries.
This goes back to commit d3bb267bbdcb ("vhost: cache avail index in vhost_enable_notify()") which changed vhost_enable_notify() to compare the freshly read avail index against vq->last_avail_idx instead of the previously cached vq->avail_idx. Commit 7ad472397667 ("vhost: move smp_rmb() into vhost_get_avail_idx()") then carried over the same comparison when refactoring vhost_enable_notify() to call the unified vhost_get_avail_idx().
The obvious fix is to make vhost_get_avail_idx do what the comment says it does and report whether new entries have been added.
Message-Id: <559b04ae6ce52973c535dc47e461638b7f4c3d63.1772441455.git.mst@redhat.com>
--- drivers/vhost/vhost.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/vhost/vhost.c +7 -4
@@ -1526,6 +1526,7 @@ static void vhost_dev_unlock_vqs(struct vhost_dev *d)static inline int vhost_get_avail_idx (struct vhost_virtqueue *vq) {__virtio16 idx; +u16 avail_idx;int r; r =vhost_get_avail (vq, idx, &vq->avail->idx);
@@ -1536,17 +1537,19 @@ static inline int vhost_get_avail_idx(struct vhost_virtqueue *vq) }/* Check it isn't doing very strange thing with available indexes */ - vq->avail_idx =vhost16_to_cpu (vq, idx); -if (unlikely ((u16)(vq->avail_idx - vq->last_avail_idx) > vq->num)) { + avail_idx =vhost16_to_cpu (vq, idx); +if (unlikely ((u16)(avail_idx - vq->last_avail_idx) > vq->num)) {vq_err (vq,"Invalid available index change from %u to %u" , - vq->last_avail_idx, vq->avail_idx); + vq->last_avail_idx, avail_idx);return -EINVAL ; }/* We're done if there is nothing new */ -if (vq->avail_idx == vq->last_avail_idx) +if (avail_idx == vq->avail_idx)return 0 ; + vq->avail_idx = avail_idx; +/* * We updated vq->avail_idx so we need a memory barrier between * the index read above and the caller reading avail ring entries.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 326/1611 iommu/vt-d: Fix RB-tree corruption in probe error path
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pranjal Shrivastava <[email protected]>
[ Upstream commit 43bd9e6d5513cb1edbafdeef146a1edc3aaced56 ]
The info->node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the device_rbtree_insert() call is skipped. If a subsequent probe step fails, the error path jumps to device_rbtree_remove(), which misinterprets the zeroed node as a tree root and corrupts the device RB-tree.
Fix this by explicitly initializing the RB-node as empty using RB_CLEAR_NODE() during initialization and guarding the removal with RB_EMPTY_NODE().
--- drivers/iommu/intel/iommu.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/iommu/intel/iommu.c +5 -1
@@ -164,7 +164,10 @@ static void device_rbtree_remove(struct device_domain_info *info)unsigned long flags;spin_lock_irqsave (&iommu->device_rbtree_lock, flags); -rb_erase (&info->node, &iommu->device_rbtree); +if (!RB_EMPTY_NODE (&info->node)) { +rb_erase (&info->node, &iommu->device_rbtree); +RB_CLEAR_NODE (&info->node); + }spin_unlock_irqrestore (&iommu->device_rbtree_lock, flags); }
@@ -3787,6 +3790,7 @@ static struct iommu_device *intel_iommu_probe_device(struct device *dev) info->dev = dev; info->iommu = iommu; +RB_CLEAR_NODE (&info->node);if (dev_is_pci (dev)) { if (ecap_dev_iotlb_support(iommu->ecap) && pci_ats_supported(pdev) &&
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 327/1611 perf/x86/amd/core: Always use the NMI latency mitigation
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sandipan Das <[email protected]>
[ Upstream commit 73a4c02f94a98d94480c3e5c81450215a4da05ba ]
Commit df4d29732fda ("perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp") fixed handling of late-arriving NMIs but limited the mitigation to processors having X86_FEATURE_PERFCTR_CORE. However, it is unclear if processors without this feature are also affected. When Mediated vPMU is enabled on affected hardware, it is also possible to bypass the fix inside KVM guests if X86_FEATURE_PERFCTR_CORE is removed from the guest CPUID (e.g. using "-cpu host,-perfctr-core" with QEMU). Hence, use the mitigation at all times.
--- arch/x86/events/amd/core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/x86/events/amd/core.c +3 -3
@@ -1411,12 +1411,12 @@ static int __init amd_core_pmu_init(void)u64 even_ctr_mask =0ULL ;int i; -if (!boot_cpu_has (X86_FEATURE_PERFCTR_CORE )) -return 0 ; -/* Avoid calculating the value each time in the NMI handler */ perf_nmi_window =msecs_to_jiffies (100 ); +if (!boot_cpu_has (X86_FEATURE_PERFCTR_CORE )) +return 0 ; +/* * If core performance counter extensions exists, we must use * MSR_F15H_PERF_CTL/MSR_F15H_PERF_CTR msrs. See also
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 328/1611 perf/x86/intel/uncore: Fix discovery unit lookup for multi-die systems
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zide Chen <[email protected]>
[ Upstream commit 63f48abd55d0417996bca86022925c853a2b436b ]
In uncore_find_add_unit(), PMON units with the same unit ID may be added to the uncore discovery RB-tree for different dies. These units are distinguished by node->die.
However, intel_generic_uncore_box_ctl() uses a fixed die ID of -1 when looking up the discovery unit, which may retrieve the wrong node on multi-die systems.
Use box->dieid instead so the correct discovery unit is selected.
No functional issue has been observed so far because currently supported platforms happen to use the same unit control register for such units.
Remove WARN_ON_ONCE() because with the above change a NULL unit can be expected, e.g. when a CPU die is offline during uncore enumeration and the unit is not added to the RB-tree. In this case, intel_uncore_find_discovery_unit() returns NULL once the die becomes online, and it is expected that the PMU box is not functional for that die.
--- arch/x86/events/intel/uncore_discovery.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/events/intel/uncore_discovery.c +2 -2
@@ -480,8 +480,8 @@ static u64 intel_generic_uncore_box_ctl(struct intel_uncore_box *box)struct intel_uncore_discovery_unit *unit; unit =intel_uncore_find_discovery_unit (box->pmu->type->boxes, --1 , box->pmu->pmu_idx); -if (WARN_ON_ONCE (!unit)) + box->dieid, box->pmu->pmu_idx); +if (!unit)return 0 ;return unit->addr;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 329/1611 perf/x86/amd/uncore: Use Node ID to identify DF and UMC domains
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sandipan Das <[email protected]>
[ Upstream commit 67d27727854def4a7e2b386429941f5c4741ccc4 ]
For DF and UMC PMUs, a single context is shared across all CPUs that are connected to the same Data Fabric (DF) instance. Currently, the Package ID, which also happens to be the Socket ID, is used to identify DF instances. This approach works for configurations having a single IO Die (IOD) but fails in the following cases.
* Older Zen 1 processors, where each chiplet has its own DF instance.
* Any configurations with multiple DF instances or multiple IODs in the same package.
The correct way to identify DF instances is through the Node ID (not to be confused with NUMA Node ID). This is available in ECX[7:0] of CPUID leaf 0x8000001e and returned via topology_amd_node_id(). Hence, replace usage of topology_logical_package_id() with topology_amd_node_id().
--- arch/x86/events/amd/uncore.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/x86/events/amd/uncore.c +3 -3
@@ -700,7 +700,7 @@ void amd_uncore_df_ctx_scan(struct amd_uncore *uncore, unsigned int cpu) info.split.aux_data =0 ; info.split.num_pmcs =NUM_COUNTERS_NB ; info.split.gid =0 ; - info.split.cid =topology_logical_package_id (cpu); + info.split.cid =topology_amd_node_id (cpu);if (pmu_version >=2 ) { ebx.full =cpuid_ebx (EXT_PERFMON_DEBUG_FEATURES );
@@ -999,8 +999,8 @@ void amd_uncore_umc_ctx_scan(struct amd_uncore *uncore, unsigned int cpu)cpuid (EXT_PERFMON_DEBUG_FEATURES , &eax, &ebx.full, &ecx, &edx); info.split.aux_data = ecx;/* stash active mask */ info.split.num_pmcs = ebx.split.num_umc_pmc; - info.split.gid =topology_logical_package_id (cpu); - info.split.cid =topology_logical_package_id (cpu); + info.split.gid =topology_amd_node_id (cpu); + info.split.cid =topology_amd_node_id (cpu); *per_cpu_ptr (uncore->info, cpu) = info; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 330/1611 xfrm: fix NAT-related field inheritance in SA migration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Antony Antony <[email protected]>
[ Upstream commit 364e165e0b63e8142e76de83e96ae8e36c3b955a ]
During SA migration via xfrm_state_clone_and_setup(), nat_keepalive_interval was silently dropped and never copied to the new SA. mapping_maxage was unconditionally copied even when migrating to a non-encapsulated SA.
Both fields are only meaningful when UDP encapsulation (NAT-T) is in use. Move mapping_maxage and add nat_keepalive_interval inside the existing if (encap) block, so both are inherited when migrating with encapsulation and correctly absent when migrating without it.
--- net/xfrm/xfrm_state.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/xfrm/xfrm_state.c +2 -1
@@ -2020,6 +2020,8 @@ static struct xfrm_state *xfrm_state_clone_and_setup(struct xfrm_state *orig,if (!x->encap) goto error; + x->mapping_maxage = orig->mapping_maxage; + x->nat_keepalive_interval = orig->nat_keepalive_interval; }if (orig->security)
@@ -2054,7 +2056,6 @@ static struct xfrm_state *xfrm_state_clone_and_setup(struct xfrm_state *orig, x->km.seq = orig->km.seq; x->replay = orig->replay; x->preplay = orig->preplay; - x->mapping_maxage = orig->mapping_maxage; x->lastused = orig->lastused; x->new_mapping =0 ; x->new_mapping_sport =0 ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 331/1611 cxl/fwctl: Fix __fortify_panic
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Williams <[email protected]>
[ Upstream commit 6c9d2e87df40d606f1c85143e9acb1ecff463d5e ]
Fix a runtime assertion in cxlctl_get_supported_features(). Fortify complains that it is potentially overflowing the entries array per __counted_by_le(num_entries). Quiet the false positive by initializing @num_entries earlier.
memcpy: detected buffer overflow: 48 byte write of buffer size 0
WARNING: lib/string_helpers.c:1036 at __fortify_report+0x4d/0xa0, CPU#7: fwctl/1398 RIP: 0010:__fortify_report+0x50/0xa0 Call Trace: __fortify_panic+0xd/0xf cxlctl_get_supported_features.cold+0x23/0x35 [cxl_core]
--- drivers/cxl/core/features.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/cxl/core/features.c +1 -1
@@ -423,6 +423,7 @@ static void *cxlctl_get_supported_features(struct cxl_features_state *cxlfs, rpc_out->size =struct_size (feat_out, ents, requested); feat_out = &rpc_out->get_sup_feats_out; + feat_out->num_entries =cpu_to_le16 (requested);for (i = start, pos = &feat_out->ents[0 ]; i < cxlfs->entries->num_features; i++, pos++) {
@@ -444,7 +445,6 @@ static void *cxlctl_get_supported_features(struct cxl_features_state *cxlfs, } } - feat_out->num_entries =cpu_to_le16 (requested); feat_out->supported_feats =cpu_to_le16 (cxlfs->entries->num_features); rpc_out->retval =CXL_MBOX_CMD_RC_SUCCESS ; *out_len = out_size;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 332/1611 drm/amdkfd: always resume_all after suspend_all
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
[ Upstream commit 56ae73c92e200e630c2bdf1e98c88b86c8483b37 ]
Need to restore any good queues even if the suspend_all failed for some. Always run remove_queue as that will schedule a GPU reset is removing the queue fails.
v2: move resume_all after remove
--- .../drm/amd/amdkfd/kfd_device_queue_manager.c | 20 ++++++------------- 1 file changed, 6 insertions(+), 14 deletions(-)
drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c +6 -14
@@ -3073,32 +3073,24 @@ int kfd_dqm_suspend_bad_queue_mes(struct kfd_node *knode, u32 pasid, u32 doorbellist_for_each_entry (q, &qpd->queues_list, list) {if (q->doorbell_id == doorbell_id && q->properties.is_active) { - ret =suspend_all_queues_mes (dqm); -if (ret) { -dev_err (dev,"Suspending all queues failed" ); - goto out; - } +/* suspend all queues will save any good queues and mark the rest as bad */ +suspend_all_queues_mes (dqm); q->properties.is_evicted = true; q->properties.is_active = false;decrement_queue_count (dqm, qpd, q); +/* this will remove the bad queue and sched a GPU reset if needed */ ret =remove_queue_mes (dqm, q, qpd); -if (ret) { -dev_err (dev,"Removing bad queue failed" ); - goto out; - } - - ret =resume_all_queues_mes (dqm);if (ret) -dev_err (dev,"Resuming all queues failed" ); - +dev_err (dev,"Removing bad queue failed" ); +/* resume the good queues */ +resume_all_queues_mes (dqm);break ; } } } -out:dqm_unlock (dqm);kfd_unref_process (p);return ret;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 333/1611 of: reserved_mem: avoid post-init UAF when alloc_reserved_mem_array() fails
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wandun Chen <[email protected]>
[ Upstream commit e1686ca81dbf3edbde589b7daf312b45cbf76e03 ]
The global pointer 'reserved_mem' continues to reference the reserved_mem_array which lives in __initdata if alloc_reserved_mem_array() fails. of_reserved_mem_lookup() is exported for post-init use, that would dereference freed memory and trigger a use-after-free.
So reset reserved_mem_count to 0 when alloc_reserved_mem_array() fails.
--- drivers/of/of_reserved_mem.c | 28 +++++++++++++++++++--------- 1 file changed, 19 insertions(+), 9 deletions(-)
drivers/of/of_reserved_mem.c +19 -9
@@ -71,29 +71,32 @@ static int __init early_init_dt_alloc_reserved_memory_arch(phys_addr_t size,* the initial static array is copied over to this new array and * the new array is used from this point on. */ -static void __init alloc_reserved_mem_array (void ) +static int __init alloc_reserved_mem_array (void ) {struct reserved_mem *new_array;size_t alloc_size, copy_size, memset_size; +int ret; + +if (!total_reserved_mem_cnt) +return 0 ; alloc_size =array_size (total_reserved_mem_cnt,sizeof (*new_array));if (alloc_size ==SIZE_MAX ) { -pr_err ("Failed to allocate memory for reserved_mem array with err: %d" , -EOVERFLOW ); -return ; + ret = -EOVERFLOW ; + goto fail; } new_array =memblock_alloc (alloc_size,SMP_CACHE_BYTES );if (!new_array) { -pr_err ("Failed to allocate memory for reserved_mem array with err: %d" , -ENOMEM ); -return ; + ret = -ENOMEM ; + goto fail; } copy_size =array_size (reserved_mem_count,sizeof (*new_array));if (copy_size ==SIZE_MAX ) {memblock_free (new_array, alloc_size); - total_reserved_mem_cnt =MAX_RESERVED_REGIONS ; -pr_err ("Failed to allocate memory for reserved_mem array with err: %d" , -EOVERFLOW ); -return ; + ret = -EOVERFLOW ; + goto fail; } memset_size = alloc_size - copy_size;
@@ -102,6 +105,12 @@ static void __init alloc_reserved_mem_array(void)memset (new_array + reserved_mem_count,0 , memset_size); reserved_mem = new_array; +return 0 ; + +fail: +pr_err ("Failed to allocate memory for reserved_mem array with err: %d" , ret); + reserved_mem_count =0 ; +return ret; }static void __init fdt_init_reserved_mem_node (struct reserved_mem *rmem);
@@ -250,7 +259,8 @@ void __init fdt_scan_reserved_mem_reg_nodes(void) }/* Attempt dynamic allocation of a new reserved_mem array */ -alloc_reserved_mem_array (); +if (alloc_reserved_mem_array ()) +return ;if (__reserved_mem_check_root (node)) {pr_err ("Reserved memory: unsupported node format, ignoring\n" );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 334/1611 ocfs2: rebase copied fsdlm LVB pointers in locking_state
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Cen <[email protected]>
[ Upstream commit 93612d48fa42b3d1a637eb9279e15281c611c000 ]
The locking_state debugfs iterator snapshots struct ocfs2_lock_res by value under ocfs2_dlm_tracking_lock and later formats that copy in ocfs2_dlm_seq_show(). That is fine for the inline fields, but the userspace fsdlm stack stores the LVB through lksb_fsdlm.sb_lvbptr. Once the iterator drops the tracking lock, a copied non-NULL sb_lvbptr still points into the original lockres owner, so teardown can free that container before the debugfs dump walks the raw LVB bytes.
Rebase the copied sb_lvbptr to the copied l_lksb before dumping the raw LVB. The seq snapshot already carries the inline LVB storage reserved in struct ocfs2_dlm_lksb, so the debugfs reader can dump the copied bytes without borrowing the original lockres lifetime.
The buggy scenario involves two paths, with each column showing the order within that path:
locking_state reader: lockres teardown:
1. ocfs2_dlm_seq_start()/next() 1. file release or another owner
copies struct ocfs2_lock_res teardown reaches
2. ocfs2_dlm_seq_show() formats ocfs2_lock_res_free()
the copied row 2. the lockres is removed from the
3. ocfs2_dlm_lvb() follows the tracking list
copied sb_lvbptr 3. the owner frees the original
lockres container
Validation reproduced this kernel report:
KASAN slab-use-after-free in ocfs2_dlm_seq_show+0x1bd/0x430
RIP: 0033:0x7f8ec4b1e29d The buggy address belongs to the object at ffff88810a1e0800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 368 bytes inside of freed 1024-byte region [ffff88810a1e0800, ffff88810a1e0c00) Read of size 1 Call trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 ocfs2_dlm_seq_show+0x1bd/0x430 (fs/ocfs2/dlmglue.c:3137) srso_alias_return_thunk+0x5/0xfbef5 __virt_addr_valid+0x19f/0x330 kasan_report+0xe0/0x110 seq_read_iter+0x29d/0x790 seq_read+0x20a/0x280 find_held_lock+0x2b/0x80 rcu_read_unlock+0x18/0x70 full_proxy_read+0x9e/0xd0 vfs_read+0x12c/0x590 ksys_read+0xd2/0x170 do_user_addr_fault+0x65a/0x890 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated by task stack: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 ocfs2_file_open+0x13e/0x300 do_dentry_open+0x233/0x7f0 vfs_open+0x5a/0x1b0 path_openat+0x66d/0x1540 do_file_open+0x186/0x2b0 do_sys_openat2+0xce/0x150 __x64_sys_openat+0xd0/0x140 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task stack: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x5f/0x80 kfree+0x313/0x590 ocfs2_file_release+0x138/0x260 __fput+0x1df/0x4b0 fput_close_sync+0xd2/0x170 __x64_sys_close+0x55/0x90 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f
--- fs/ocfs2/dlmglue.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
fs/ocfs2/dlmglue.c +17 -0
@@ -3134,6 +3134,22 @@ static void *ocfs2_dlm_seq_next(struct seq_file *m, void *v, loff_t *pos)* - Add last pr/ex unlock times and first lock wait time in usecs */ #define OCFS2_DLM_DEBUG_STR_VERSION 4 + +/* +* The debug iterator snapshots lockres by value, so a userspace-stack LVB +* pointer copied from the original lockres must be rebased to the copied +* lksb before the dump walks the raw bytes. +*/ +static void ocfs2_dlm_seq_rebase_lvb (struct ocfs2_lock_res *lockres) +{ +if (!ocfs2_stack_supports_plocks ()) +return ; + +if (lockres->l_lksb.lksb_fsdlm.sb_lvbptr) + lockres->l_lksb.lksb_fsdlm.sb_lvbptr = + (char *)&lockres->l_lksb +sizeof (struct dlm_lksb ); +} +static int ocfs2_dlm_seq_show (struct seq_file *m,void *v) {int i;
@@ -3191,6 +3207,7 @@ static int ocfs2_dlm_seq_show(struct seq_file *m, void *v) lockres->l_blocking);/* Dump the raw LVB */ +ocfs2_dlm_seq_rebase_lvb (lockres); lvb =ocfs2_dlm_lvb (&lockres->l_lksb);for (i =0 ; i <DLM_LVB_LEN ; i++)seq_printf (m,"0x%x\t" , lvb[i]);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 335/1611 lib: kunit_iov_iter: repeatedly call alloc_pages_bulk()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Weißschuh <[email protected]>
[ Upstream commit 9ac9a08e4ac4bc063e56e1aff266c5e8aa5c6c03 ]
alloc_pages_bulk() is not guaranteed to return all requested pages in a single call.
Call it repeatedly until all pages have been allocated or no more progress is being made.
--- lib/tests/kunit_iov_iter.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
lib/tests/kunit_iov_iter.c +10 -2
@@ -50,14 +50,22 @@ static void *__init iov_kunit_create_buffer(struct kunit *test, size_t npages) {struct page **pages; -unsigned long got; +unsigned long got, last;void *buffer; pages = kzalloc_objs(struct page *, npages, GFP_KERNEL);KUNIT_ASSERT_NOT_ERR_OR_NULL (test, pages); *ppages = pages; - got =alloc_pages_bulk (GFP_KERNEL , npages, pages); + got =0 ; +while (true) { + last = got; + got =alloc_pages_bulk (GFP_KERNEL , npages, pages); + +if (last == got || got == npages) +break ; + } +if (got != npages) {release_pages (pages, got);kvfree (pages);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 336/1611 ocfs2: fix buffer head management in ocfs2_read_blocks()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Antipov <[email protected]>
[ Upstream commit 6371a07148ee979af22a9d6f4c277462953a9a4a ]
In ocfs2_read_blocks(), caller should't assume that buffer head returned by 'sb_getblk()' is exclusively owned and so 'put_bh()' always drops b_count from 1 to 0. If it is not so, buffer head remains on hold and likely to be returned by the next call to 'sb_getblk()' unchanged - that is, with BH_Uptodate bit set even if it has failed validation previously, thus allowing to insert that buffer head into OCFS2 metadata cache and submit it to upper layers. To avoid such a scenario, BH_Uptodate should be cleared immediately after 'validate()' callback has detected some data inconsistency.
--- fs/ocfs2/buffer_head_io.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
fs/ocfs2/buffer_head_io.c +4 -3
@@ -350,8 +350,6 @@ int ocfs2_read_blocks(struct ocfs2_caching_info *ci, u64 block, int nr,wait_on_buffer (bh);put_bh (bh); bhs[i] =NULL ; - }else if (bh &&buffer_uptodate (bh)) { -clear_buffer_uptodate (bh); }continue ; }
@@ -380,8 +378,11 @@ int ocfs2_read_blocks(struct ocfs2_caching_info *ci, u64 block, int nr,BUG_ON (buffer_jbd (bh));clear_buffer_needs_validate (bh); status =validate (sb, bh); -if (status) +if (status) { +if (buffer_uptodate (bh)) +clear_buffer_uptodate (bh); goto read_failure; + } } }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 337/1611 ocfs2: reject FITRIM ranges shorter than a cluster
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Cen <[email protected]>
[ Upstream commit ca1afd88f5eaaff9168e1466e5401385edf59543 ]
ocfs2_trim_mainbm() trims the global bitmap in cluster units, but its too-short range validation only checks sb->s_blocksize.
On filesystems with a cluster size larger than the block size, a FITRIM range that is at least one block but shorter than one cluster is accepted and shifted down to len == 0. The later start + len - 1 and len -= ... arithmetic then underflows and can drive trimming past the requested range.
Reject ranges shorter than s_clustersize instead. That preserves the existing -EINVAL behavior for requests that cannot discard even one allocation unit and keeps zero-cluster trims out of the group walk.
--- fs/ocfs2/alloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ocfs2/alloc.c +1 -1
@@ -7564,7 +7564,7 @@ int ocfs2_trim_mainbm(struct super_block *sb, struct fstrim_range *range) len = range->len >> osb->s_clustersize_bits; minlen = range->minlen >> osb->s_clustersize_bits; -if (minlen >= osb->bitmap_cpg || range->len < sb->s_blocksize) +if (minlen >= osb->bitmap_cpg || range->len < osb->s_clustersize)return -EINVAL ;trace_ocfs2_trim_mainbm (start, len, minlen);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 338/1611 ocfs2/dlm: require a ref for locking_state debugfs open
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhang Cen <[email protected]>
[ Upstream commit 03ad858ce8064861ea580021976dc19b7aabb549 ]
debug_lockres_open() copies inode->i_private into struct debug_lockres and debug_lockres_release() later drops that pointer with dlm_put(). That only works if open successfully pins the struct dlm_ctxt.
Today open calls dlm_grab(dlm) but ignores its return value. Once the last domain unregister has removed the context from dlm_domains, dlm_grab() returns NULL, yet open still stores the raw pointer and returns success. The later release path is outside the debugfs removal barrier, so it can call dlm_put() after dlm_free_ctxt_mem() has freed the context. KASAN reports this as a slab-use-after-free in dlm_put() called from debug_lockres_release().
Fail the open when dlm_grab() cannot acquire the reference and unwind the seq_file private state before returning. That keeps locking_state from handing out a file descriptor whose release path does not own the dlm_ctxt.
The buggy scenario involves two paths, with each column showing the order within that path:
locking_state debugfs open: last domain unregister:
1. debug_lockres_open() reads 1. dlm_unregister_domain() calls
inode->i_private. dlm_complete_dlm_shutdown().
2. debug_lockres_open() calls 2. shutdown removes the dlm_ctxt from
dlm_grab(dlm) and gets NULL. dlm_domains.
3. open still stores the raw dlm 3. final teardown reaches
pointer in dl->dl_ctxt and dlm_free_ctxt_mem() and frees it.
returns success.
4. debug_lockres_release() later
calls dlm_put(dl->dl_ctxt).
Validation reproduced this kernel report:
KASAN slab-use-after-free in dlm_put+0x82/0x200
RIP: 0033:0x7f4d349bc9e0 The buggy address belongs to the object at ffff888103a3c000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 816 bytes inside of freed 2048-byte region [ffff888103a3c000, ffff888103a3c800) Write of size 4 Call trace: dump_stack_lvl+0x66/0xa0 (?:?) print_report+0xd0/0x630 (?:?) dlm_put+0x82/0x200 (?:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x188/0x2f0 (?:?) kasan_report+0xe4/0x120 (?:?) kasan_check_range+0x105/0x1b0 (?:?) debug_lockres_release+0x53/0x80 (fs/ocfs2/dlm/dlmdebug.c:587) dlm_put+0x9/0x200 (?:?) debug_lockres_release+0x5c/0x80 (fs/ocfs2/dlm/dlmdebug.c:587) full_proxy_release+0x67/0x90 (?:?) __fput+0x1df/0x4b0 (?:?) do_raw_spin_lock+0x10f/0x1b0 (?:?) fput_close_sync+0xd2/0x170 (?:?) __x64_sys_close+0x55/0x90 (?:?) do_syscall_64+0x10c/0x640 (arch/x86/entry/syscall_64.c:87) irqentry_exit+0xac/0x6e0 (?:?) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?) Freed by task stack: kasan_save_stack+0x33/0x60 (?:?) kasan_save_track+0x14/0x30 (?:?) kasan_save_free_info+0x3b/0x60 (?:?) __kasan_slab_free+0x5f/0x80 (?:?) kfree+0x30f/0x580 (?:?) dlm_put+0x1ce/0x200 (?:?) dlm_unregister_domain+0xf6/0xb30 (?:?) o2cb_cluster_disconnect+0x6b/0x90 (?:?) ocfs2_cluster_disconnect+0x41/0x70 (?:?) ocfs2_dlm_shutdown+0x1c4/0x220 (?:?) ocfs2_dismount_volume+0x38a/0x550 (?:?) generic_shutdown_super+0xc3/0x220 (?:?) kill_block_super+0x29/0x60 (?:?) deactivate_locked_super+0x66/0xe0 (?:?) cleanup_mnt+0x13d/0x210 (?:?) task_work_run+0xfa/0x170 (?:?) exit_to_user_mode_loop+0xd6/0x430 (?:?) do_syscall_64+0x3cb/0x640 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)
--- fs/ocfs2/dlm/dlmdebug.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
fs/ocfs2/dlm/dlmdebug.c +12 -4
@@ -560,6 +560,7 @@ static int debug_lockres_open(struct inode *inode, struct file *file)struct dlm_ctxt *dlm = inode->i_private;struct debug_lockres *dl;void *buf; +int status = -ENOMEM ; buf =kmalloc (PAGE_SIZE ,GFP_KERNEL );if (!buf)
@@ -572,16 +573,23 @@ static int debug_lockres_open(struct inode *inode, struct file *file) dl->dl_len =PAGE_SIZE ; dl->dl_buf = buf; -dlm_grab (dlm); - dl->dl_ctxt = dlm; +/* ->release uses dl_ctxt after open, so it needs a real pin. */ + dl->dl_ctxt =dlm_grab (dlm); +if (!dl->dl_ctxt) { + status = -ENOENT ; + goto bailseq; + }return 0 ; +bailseq: +seq_release_private (inode, file); bailfree:kfree (buf); bail: -mlog_errno (-ENOMEM ); -return -ENOMEM ; +if (status != -ENOENT ) +mlog_errno (status); +return status; }static int debug_lockres_release (struct inode *inode,struct file *file)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 339/1611 ocfs2: fix race between ocfs2_control_install_private() and ocfs2_control_release()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Joseph Qi <[email protected]>
[ Upstream commit 57dcfd9049d497c31151787a0696d59f0a98f8e6 ]
Move atomic_inc(&ocfs2_control_opened) and the handshake state update inside ocfs2_control_lock to close a race window where ocfs2_control_release() can observe ocfs2_control_opened dropping to zero (resetting ocfs2_control_this_node and running_proto) while ocfs2_control_install_private() is about to bump the counter and mark the connection valid.
--- fs/ocfs2/stack_user.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-)
fs/ocfs2/stack_user.c +3 -7
@@ -327,18 +327,14 @@ static int ocfs2_control_install_private(struct file *file) ocfs2_control_this_node = p->op_this_node; running_proto.pv_major = p->op_proto.pv_major; running_proto.pv_minor = p->op_proto.pv_minor; - } - -out_unlock: -mutex_unlock (&ocfs2_control_lock); - -if (!rc && set_p) { -/* We set the global values successfully */ atomic_inc (&ocfs2_control_opened);ocfs2_control_set_handshake_state (file,OCFS2_CONTROL_HANDSHAKE_VALID ); } +out_unlock: +mutex_unlock (&ocfs2_control_lock); +return rc; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 340/1611 netfilter: nfnetlink_osf: fix mss parsing on big-endian architectures
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fernando Fernandez Mancera <[email protected]>
[ Upstream commit a625c94144c9b66d32e1f374f909f38db46161c1 ]
The MSS calculation in nf_osf_match_one() manually shifts bytes to construct a 16-bit value before passing it to ntohs().
This works on little-endian hosts but it does not work on big-endian as the bytes are being always shifted and set in the same way for all architectures.
Use get_unaligned_be16() to fix this on big-endian systems. It also simplifies the code.
--- net/netfilter/nfnetlink_osf.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
net/netfilter/nfnetlink_osf.c +1 -5
@@ -95,11 +95,7 @@ static bool nf_osf_match_one(const struct sk_buff *skb,switch (*optp) {case OSFOPT_MSS : - mss = optp[3 ]; - mss <<=8 ; - mss |= optp[2 ]; - - mss =ntohs ((__force __be16 )mss); + mss =get_unaligned_be16 (&optp[2 ]);break ;case OSFOPT_TS :break ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 341/1611 netfilter: nfnetlink_cthelper: use {READ,WRITE}_ONCE for accessing helper flags
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pablo Neira Ayuso <[email protected]>
[ Upstream commit f8bf5edf7157984bb8e288c8b04fdb041223b80c ]
Conntrack helper flags are accessed from packet and netlink dump path. Concurrent update of userspace helper flags is not possible, because the nfnl_mutex in held on updates. These flags are only used by userspace helpers. Use {READ,WRITE}_ONCE() to access this flags from lockless paths.
--- net/netfilter/nf_conntrack_core.c | 4 +++- net/netfilter/nfnetlink_cthelper.c | 20 +++++++++++++------- 2 files changed, 16 insertions(+), 8 deletions(-)
net/netfilter/nf_conntrack_core.c +3 -1
@@ -2211,6 +2211,7 @@ static int nf_confirm_cthelper(struct sk_buff *skb, struct nf_conn *ct, {const struct nf_conntrack_helper *helper;const struct nf_conn_help *help; +unsigned int helper_flags;int protoff; help =nfct_help (ct);
@@ -2221,7 +2222,8 @@ static int nf_confirm_cthelper(struct sk_buff *skb, struct nf_conn *ct,if (!helper)return NF_ACCEPT ; -if (!(helper->flags &NF_CT_HELPER_F_USERSPACE )) + helper_flags =READ_ONCE (helper->flags); +if (!(helper_flags &NF_CT_HELPER_F_USERSPACE ))return NF_ACCEPT ;switch (nf_ct_l3num (ct)) {
net/netfilter/nfnetlink_cthelper.c +13 -7
@@ -41,8 +41,9 @@ static int nfnl_userspace_cthelper(struct sk_buff *skb, unsigned int protoff, struct nf_conn *ct, enum ip_conntrack_info ctinfo) { - const struct nf_conn_help *help; struct nf_conntrack_helper *helper; +const struct nf_conn_help *help; +unsigned int helper_flags; help =nfct_help (ct);if (help ==NULL )
@@ -53,8 +54,10 @@ nfnl_userspace_cthelper(struct sk_buff *skb, unsigned int protoff,if (helper ==NULL )return NF_DROP ; + helper_flags =READ_ONCE (helper->flags); +/* This is a user-space helper not yet configured, skip. */ -if ((helper->flags & +if ((helper_flags & (NF_CT_HELPER_F_USERSPACE |NF_CT_HELPER_F_CONFIGURED )) ==NF_CT_HELPER_F_USERSPACE )return NF_ACCEPT ;
@@ -406,10 +409,10 @@ nfnl_cthelper_update(const struct nlattr * const tb[],switch (status) {case NFCT_HELPER_STATUS_ENABLED : - helper->flags |=NF_CT_HELPER_F_CONFIGURED ; +WRITE_ONCE (helper->flags, helper->flags |NF_CT_HELPER_F_CONFIGURED );break ;case NFCT_HELPER_STATUS_DISABLED : - helper->flags &= ~NF_CT_HELPER_F_CONFIGURED ; +WRITE_ONCE (helper->flags, helper->flags & ~NF_CT_HELPER_F_CONFIGURED );break ; } }
@@ -531,8 +534,8 @@ static int nfnl_cthelper_fill_info(struct sk_buff *skb, u32 portid, u32 seq, u32 type, int event, struct nf_conntrack_helper *helper) { - struct nlmsghdr *nlh; unsigned int flags = portid ? NLM_F_MULTI : 0; +struct nlmsghdr *nlh;int status; event =nfnl_msg_type (NFNL_SUBSYS_CTHELPER , event);
@@ -556,7 +559,7 @@ nfnl_cthelper_fill_info(struct sk_buff *skb, u32 portid, u32 seq, u32 type,if (nla_put_be32 (skb,NFCTH_PRIV_DATA_LEN ,htonl (helper->data_len))) goto nla_put_failure; -if (helper->flags &NF_CT_HELPER_F_CONFIGURED ) +if (READ_ONCE (helper->flags) &NF_CT_HELPER_F_CONFIGURED ) status =NFCT_HELPER_STATUS_ENABLED ;else status =NFCT_HELPER_STATUS_DISABLED ;
@@ -577,6 +580,7 @@ static int nfnl_cthelper_dump_table(struct sk_buff *skb, struct netlink_callback *cb) { struct nf_conntrack_helper *cur, *last; +unsigned int helper_flags;rcu_read_lock (); last = (struct nf_conntrack_helper *)cb->args[1 ];
@@ -585,8 +589,10 @@ nfnl_cthelper_dump_table(struct sk_buff *skb, struct netlink_callback *cb)hlist_for_each_entry_rcu (cur, &nf_ct_helper_hash[cb->args[0 ]], hnode) { + helper_flags =READ_ONCE (cur->flags); +/* skip non-userspace conntrack helpers. */ -if (!(cur->flags &NF_CT_HELPER_F_USERSPACE )) +if (!(helper_flags &NF_CT_HELPER_F_USERSPACE ))continue ;if (cb->args[1 ]) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 342/1611 netfilter: synproxy: drop packets if timestamp adjustment fails
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fernando Fernandez Mancera <[email protected]>
[ Upstream commit 63d29ee95c4ab5976d660182d2e4733bb4a091d8 ]
If a packet was malformed or if skb_ensure_writable() failed, the synproxy_tstamp_adjust() function returned 0 indicating an error but it was ignored on the callers.
Make the function return a boolean instead to clarify the result and drop the packet if synproxy_tstamp_adjust() failed due to ENOMEM from skb_ensure_writable(). In addition, if there are malformed options, skip the tstamp update but do not drop the packet as that should be done by the policy directly.
--- net/netfilter/nf_synproxy_core.c | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-)
net/netfilter/nf_synproxy_core.c +13 -9
@@ -183,7 +183,7 @@ synproxy_check_timestamp_cookie(struct synproxy_options *opts) opts->options |= opts->tsecr & (1 <<5 ) ?NF_SYNPROXY_OPT_ECN :0 ; } -static unsigned int +static bool synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff, struct tcphdr *th, struct nf_conn *ct, enum ip_conntrack_info ctinfo,
@@ -193,13 +193,13 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff,__be32 *ptr, old;if (synproxy->tsoff ==0 ) -return 1 ; +return true; optoff = protoff +sizeof (struct tcphdr ); optend = protoff + th->doff *4 ;if (skb_ensure_writable (skb, optend)) -return 0 ; +return false; th = (struct tcphdr *)(skb->data + protoff);
@@ -208,7 +208,7 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff,switch (op[0 ]) {case TCPOPT_EOL : -return 1 ; +return true;case TCPOPT_NOP : optoff++;continue ;
@@ -216,7 +216,7 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff,if (optoff +1 == optend || optoff + op[1 ] > optend || op[1 ] <2 ) -return 0 ; +return true;if (op[0 ] ==TCPOPT_TIMESTAMP && op[1 ] ==TCPOLEN_TIMESTAMP ) {if (CTINFO2DIR (ctinfo) ==IP_CT_DIR_REPLY ) {
@@ -232,12 +232,12 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff, }inet_proto_csum_replace4 (&th->check, skb, old, *ptr, false); -return 1 ; +return true; } optoff += op[1 ]; } } -return 1 ; +return true; }#ifdef CONFIG_PROC_FS
@@ -748,7 +748,9 @@ ipv4_synproxy_hook(void *priv, struct sk_buff *skb,break ; } -synproxy_tstamp_adjust (skb, thoff, th, ct, ctinfo, synproxy); +if (!synproxy_tstamp_adjust (skb, thoff, th, ct, ctinfo, synproxy)) +return NF_DROP_REASON (skb,SKB_DROP_REASON_NETFILTER_DROP ,ENOMEM ); +return NF_ACCEPT ; }EXPORT_SYMBOL_GPL (ipv4_synproxy_hook);
@@ -1176,7 +1178,9 @@ ipv6_synproxy_hook(void *priv, struct sk_buff *skb,break ; } -synproxy_tstamp_adjust (skb, thoff, th, ct, ctinfo, synproxy); +if (!synproxy_tstamp_adjust (skb, thoff, th, ct, ctinfo, synproxy)) +return NF_DROP_REASON (skb,SKB_DROP_REASON_NETFILTER_DROP ,ENOMEM ); +return NF_ACCEPT ; }EXPORT_SYMBOL_GPL (ipv6_synproxy_hook);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 343/1611 netfilter: synproxy: adjust duplicate timestamp options
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fernando Fernandez Mancera <[email protected]>
[ Upstream commit 22bb132cfb9b94847d52d73614284b8c5ea8d36e ]
RFC 9293 does not mention anything about duplicated options and each networking stack handles it in their own way. Currently, Linux kernel is processing options sequentially and in case of duplicated timestamp options, the value from the latest one overrides the others.
As SYNPROXY is modifying only the first timestamp option found, a packet can reach the backend server and it might parse the wrong timestamp value. Let's just continue parsing the following options and in case a duplicated timestamp is found, adjust it too.
--- net/netfilter/nf_synproxy_core.c | 1 - 1 file changed, 1 deletion(-)
net/netfilter/nf_synproxy_core.c +0 -1
@@ -232,7 +232,6 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff, }inet_proto_csum_replace4 (&th->check, skb, old, *ptr, false); -return true; } optoff += op[1 ]; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 344/1611 netfilter: synproxy: fix unaligned memory access in timestamp adjustment
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fernando Fernandez Mancera <[email protected]>
[ Upstream commit 992c20bc8a4aba220c8b95b467d049289778dad6 ]
Use get_unaligned_be32() and put_unaligned_be32() to safely read and write the timestamp fields. This prevents performance degradation due to unaligned memory access or even a crash on strict alignment architectures.
This follows the implementation of timestamp parsing in the networking stack at tcp_parse_options() and synproxy_parse_options().
--- net/netfilter/nf_synproxy_core.c | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-)
net/netfilter/nf_synproxy_core.c +9 -10
@@ -190,7 +190,7 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff, const struct nf_conn_synproxy *synproxy) {unsigned int optoff, optend; -__be32 *ptr, old; +u32 new, old;if (synproxy->tsoff ==0 )return true;
@@ -220,18 +220,17 @@ synproxy_tstamp_adjust(struct sk_buff *skb, unsigned int protoff,if (op[0 ] ==TCPOPT_TIMESTAMP && op[1 ] ==TCPOLEN_TIMESTAMP ) {if (CTINFO2DIR (ctinfo) ==IP_CT_DIR_REPLY ) { - ptr = (__be32 *)&op[2 ]; - old = *ptr; - *ptr =htonl (ntohl (*ptr) - - synproxy->tsoff); + old =get_unaligned_be32 (&op[2 ]); + new = old - synproxy->tsoff; +put_unaligned_be32 (new, &op[2 ]); }else { - ptr = (__be32 *)&op[6 ]; - old = *ptr; - *ptr =htonl (ntohl (*ptr) + - synproxy->tsoff); + old =get_unaligned_be32 (&op[6 ]); + new = old + synproxy->tsoff; +put_unaligned_be32 (new, &op[6 ]); }inet_proto_csum_replace4 (&th->check, skb, - old, *ptr, false); +cpu_to_be32 (old), +cpu_to_be32 (new), false); } optoff += op[1 ]; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 345/1611 netfilter: synproxy: protect nf_ct_seqadj_init() with conntrack lock
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fernando Fernandez Mancera <[email protected]>
[ Upstream commit 9e37388b8070afe73d4ab2d973b28593ed65f3ad ]
nf_ct_seqadj_init() is called without holding the ct lock. This can race with nf_ct_seq_adjust() when a connection is in CLOSE state due to an RST or connection reopening. In addition for SYN_RECV state, concurrent processing of packets can trigger nf_ct_seq_adjust() too. These situations create a read/write data race.
As synproxy is the only user of nf_ct_seqadj_init() at the moment, fix this by holding ct->lock inside nf_ct_seqadj_init() until all is done.
--- net/netfilter/nf_conntrack_seqadj.c | 2 ++ 1 file changed, 2 insertions(+)
net/netfilter/nf_conntrack_seqadj.c +2 -0
@@ -17,12 +17,14 @@ int nf_ct_seqadj_init(struct nf_conn *ct, enum ip_conntrack_info ctinfo,if (off ==0 )return 0 ; +spin_lock_bh (&ct->lock);set_bit (IPS_SEQ_ADJUST_BIT , &ct->status); seqadj =nfct_seqadj (ct); this_way = &seqadj->seq[dir]; this_way->offset_before = off; this_way->offset_after = off; +spin_unlock_bh (&ct->lock);return 0 ; }EXPORT_SYMBOL_GPL (nf_ct_seqadj_init);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 346/1611 ALSA: usb-audio: qcom: Initialize offload control return value
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cássio Gabriel <[email protected]>
[ Upstream commit 2b5632d72fca0841bea283da2e3a478d24118508 ]
snd_usb_offload_create_ctl() returns ret after walking the USB PCM list, but ret is only assigned after a playback stream passes the endpoint and PCM-index filters.
If all playback streams are skipped, for example because there is no playback endpoint or because all PCM indexes exceed the 0xff control range, the function returns an uninitialized stack value.
Initialize ret to 0 so the no-control-created path returns deterministic success, while preserving the existing negative error return when snd_ctl_add() fails.
--- sound/usb/qcom/mixer_usb_offload.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/usb/qcom/mixer_usb_offload.c +1 -1
@@ -113,7 +113,7 @@ int snd_usb_offload_create_ctl(struct snd_usb_audio *chip, struct device *bedev)struct snd_usb_substream *subs;struct snd_usb_stream *as;char ctl_name[48 ]; -int ret; +int ret =0 ;list_for_each_entry (as, &chip->pcm_list, list) { subs = &as->substream[SNDRV_PCM_STREAM_PLAYBACK ];
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 347/1611 x86/cpu: Remove obsolete aperfmperf_get_khz() declaration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Junxiao Chang <[email protected]>
[ Upstream commit a5f28da54f36f1a8b289d9bdd3e780b2ede0da6f ]
aperfmperf_get_khz() was replaced by arch_freq_get_on_cpu(). The remaining declaration in the header file is no longer used and should be removed.
--- arch/x86/kernel/cpu/cpu.h | 1 - 1 file changed, 1 deletion(-)
arch/x86/kernel/cpu/cpu.h +0 -1
@@ -84,7 +84,6 @@ static inline struct amd_northbridge *amd_init_l3_cache(int index) }#endif -unsigned int aperfmperf_get_khz (int cpu);void cpu_select_mitigations (void );extern void x86_spec_ctrl_setup_ap (void );
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 348/1611 netfilter: conntrack: revert ct extension genid infrastructure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pablo Neira Ayuso <[email protected]>
[ Upstream commit 35e21a4dccc5c255ba59ccfbfeb4629ed21da972 ]
This infrastructure is not used anymore after moving ct timeout and helper to use datapath refcount to track object use.
Revert commit c56716c69ce1 ("netfilter: extensions: introduce extension genid count") this patch disables all ct extensions (leading to NULL) for unconfirmed conntracks, when this is only targeted at ct helper and ct timeout. There is also codebase that dereferences the ct extension without checking for NULL which could lead to crash.
--- include/net/netfilter/nf_conntrack_extend.h | 12 ---- net/netfilter/nf_conntrack_core.c | 61 +-------------------- net/netfilter/nf_conntrack_extend.c | 32 +---------- 3 files changed, 2 insertions(+), 103 deletions(-)
include/net/netfilter/nf_conntrack_extend.h +0 -12
@@ -38,7 +38,6 @@ enum nf_ct_ext_id {struct nf_ct_ext {u8 offset[NF_CT_EXT_NUM ];u8 len; -unsigned int gen_id;char data[]__aligned(8) ; };
@@ -52,8 +51,6 @@ static inline bool nf_ct_ext_exist(const struct nf_conn *ct, u8 id)return (ct->ext &&__nf_ct_ext_exist (ct->ext, id)); } -void *__nf_ct_ext_find (const struct nf_ct_ext *ext,u8 id); -static inline void *nf_ct_ext_find (const struct nf_conn *ct,u8 id) {struct nf_ct_ext *ext = ct->ext;
@@ -61,19 +58,10 @@ static inline void *nf_ct_ext_find(const struct nf_conn *ct, u8 id)if (!ext || !__nf_ct_ext_exist (ext, id))return NULL ; -if (unlikely (ext->gen_id)) -return __nf_ct_ext_find (ext, id); - return (void *)ct->ext + ct->ext->offset[id]; }/* Add this type, returns pointer to data or NULL. */ void *nf_ct_ext_add (struct nf_conn *ct,enum nf_ct_ext_id id,gfp_t gfp); -/* ext genid. if ext->id != ext_genid, extensions cannot be used -* anymore unless conntrack has CONFIRMED bit set. -*/ -extern atomic_t nf_conntrack_ext_genid; -void nf_ct_ext_bump_genid (void ); -#endif /* _NF_CONNTRACK_EXTEND_H */
net/netfilter/nf_conntrack_core.c +1 -60
101 lines not on this page · raw message
net/netfilter/nf_conntrack_extend.c +1 -31
@@ -27,8 +27,6 @@#define NF_CT_EXT_PREALLOC 128u/* conntrack events are on by default */ -atomic_t nf_conntrack_ext_genid__read_mostly =ATOMIC_INIT (1 ); -static const u8 nf_ct_ext_type_len[NF_CT_EXT_NUM ] = { [NF_CT_EXT_HELPER ] =sizeof (struct nf_conn_help ), #if IS_ENABLED(CONFIG_NF_NAT)
@@ -118,10 +116,8 @@ void *nf_ct_ext_add(struct nf_conn *ct, enum nf_ct_ext_id id, gfp_t gfp)if (!new)return NULL ; -if (!ct->ext) { +if (!ct->ext)memset (new->offset,0 ,sizeof (new->offset)); - new->gen_id =atomic_read (&nf_conntrack_ext_genid); - } new->offset[id] = newoff; new->len = newlen;
@@ -131,29 +127,3 @@ void *nf_ct_ext_add(struct nf_conn *ct, enum nf_ct_ext_id id, gfp_t gfp)return (void *)new + newoff; }EXPORT_SYMBOL (nf_ct_ext_add); - -/* Use nf_ct_ext_find wrapper. This is only useful for unconfirmed entries. */ -void *__nf_ct_ext_find (const struct nf_ct_ext *ext,u8 id) -{ -unsigned int gen_id =atomic_read (&nf_conntrack_ext_genid); -unsigned int this_id =READ_ONCE (ext->gen_id); - -if (!__nf_ct_ext_exist (ext, id)) -return NULL ; - -if (this_id ==0 || ext->gen_id == gen_id) -return (void *)ext + ext->offset[id]; - -return NULL ; -} -EXPORT_SYMBOL (__nf_ct_ext_find); - -void nf_ct_ext_bump_genid (void ) -{ -unsigned int value =atomic_inc_return (&nf_conntrack_ext_genid); - -if (value ==UINT_MAX ) -atomic_set (&nf_conntrack_ext_genid,1 ); - -msleep (HZ ); -}
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 349/1611 netfilter: conntrack: call nf_ct_gre_keymap_destroy() if master helper is pptp
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pablo Neira Ayuso <[email protected]>
[ Upstream commit b0f02608fbcd607b5131cceb91fc0a035264e61c ]
For GRE flows, validate that the ct master helper (if any) is pptp before calling nf_ct_gre_keymap_destroy(), so the helper data area can be accessed safely. Note that only the pptp helper provides a .destroy callback.
--- net/netfilter/nf_conntrack_core.c | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-)
net/netfilter/nf_conntrack_core.c +16 -2
@@ -565,9 +565,23 @@ static void destroy_gre_conntrack(struct nf_conn *ct) {#ifdef CONFIG_NF_CT_PROTO_GRE struct nf_conn *master = ct->master; +struct nf_conn_help *help; + +if (!master) +return ; + + help =nfct_help (master); +if (help) { +struct nf_conntrack_helper *helper; -if (master) -nf_ct_gre_keymap_destroy (master); +rcu_read_lock (); + helper =rcu_dereference (help->helper); +/* Only pptp helper has a destroy callback. */ +if (helper && helper->destroy) +nf_ct_gre_keymap_destroy (master); + +rcu_read_unlock (); + }#endif }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 350/1611 RDMA/hfi1: Open-code rvt_set_ibdev_name()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Arnd Bergmann <[email protected]>
[ Upstream commit 0ee8ac903e5aa100a70bef8d0afc19a336ffa775 ]
clang warns about a function missing a printf attribute:
include/rdma/rdma_vt.h:457:47: error: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'rvt_set_ibdev_name' [-Werror,-Wmissing-format-attribute]
447 | static inline void rvt_set_ibdev_name(struct rvt_dev_info *rdi,
| __attribute__((format(printf, 2, 3)))
448 | const char *fmt, const char *name,
449 | const int unit)The helper was originally added as an abstraction for the hfi1 and qib drivers needing the same thing, but now qib is gone, and hfi1 is the only remaining user of rdma_vt.
Avoid the warning and allow the compiler to check the format string by open-coding the helper and directly assigning the device name.
--- drivers/infiniband/hw/hfi1/init.c | 13 ++++++++++++- include/rdma/rdma_vt.h | 20 -------------------- 2 files changed, 12 insertions(+), 21 deletions(-)
drivers/infiniband/hw/hfi1/init.c +12 -1
@@ -1208,6 +1208,7 @@ static struct hfi1_devdata *hfi1_alloc_devdata(struct pci_dev *pdev, size_t extra) {struct hfi1_devdata *dd; +struct ib_device *ibdev;int ret, nports;/* extra is * number of ports */
@@ -1229,7 +1230,17 @@ static struct hfi1_devdata *hfi1_alloc_devdata(struct pci_dev *pdev, "Could not allocate unit ID: error %d\n", -ret); goto bail; } -rvt_set_ibdev_name (&dd->verbs_dev.rdi,"%s_%d" ,class_name (), dd->unit); + +/* +* FIXME: rvt and its users want to touch the ibdev before +* registration and have things like the name work. We don't have the +* infrastructure in the core to support this directly today, hack it +* to work by setting the name manually here. +*/ + ibdev = &dd->verbs_dev.rdi.ibdev; +dev_set_name (&ibdev->dev,"%s_%d" ,class_name (), dd->unit); +strscpy (ibdev->name,dev_name (&ibdev->dev),IB_DEVICE_NAME_MAX ); +/* * If the BIOS does not have the NUMA node information set, select * NUMA 0 so we get consistent performance.
include/rdma/rdma_vt.h +0 -20
@@ -428,26 +428,6 @@ struct rvt_dev_info {struct rvt_wss *wss; }; -/** -* rvt_set_ibdev_name - Craft an IB device name from client info -* @rdi: pointer to the client rvt_dev_info structure -* @name: client specific name -* @unit: client specific unit number. -*/ -static inline void rvt_set_ibdev_name (struct rvt_dev_info *rdi, -const char *fmt,const char *name, -const int unit) -{ -/* -* FIXME: rvt and its users want to touch the ibdev before -* registration and have things like the name work. We don't have the -* infrastructure in the core to support this directly today, hack it -* to work by setting the name manually here. -*/ -dev_set_name (&rdi->ibdev.dev, fmt, name, unit); -strscpy (rdi->ibdev.name,dev_name (&rdi->ibdev.dev),IB_DEVICE_NAME_MAX ); -} -/** * rvt_get_ibdev_name - return the IB name * @rdi: rdmavt device
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 351/1611 IB/cm: Fix av cm device leak on an error path in cm_init_av_by_path()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Gunthorpe <[email protected]>
[ Upstream commit 9b2207bc5cdb955bdae34b3eec80f04979e17081 ]
Codex pointed out that cm_init_av_by_path() can call cm_set_av_port() which takes a reference on the cm device, but then can immediately return error if ib_init_ah_attr_from_path() fails.
Since callers like ib_send_cm_req() put the av on the stack this leaks that cm device reference.
Re-order cm_init_av_by_path() so it doesn't touch the av until it has done all its failable work, and then update the av in one shot so it is either left alone or fully init'd.
Sashiko also pointed out that the cm_destroy_av() prior to cm_init_av_by_path() is harmful as it leaves the AV broken in the error case and thus the REJ won't send. Since cm_init_av_by_path() is now atomic it is safe to delete the cm_destroy_av(). On succees the av from cm_init_av_for_response() is cleaned up by cm_init_av_by_path(), on failure the 'goto rejected' guarentees the av is destroyed during ib_destroy_cm_id().
--- drivers/infiniband/core/cm.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
drivers/infiniband/core/cm.c +8 -5
@@ -531,6 +531,7 @@ static int cm_init_av_by_path(struct sa_path_rec *path,struct rdma_ah_attr new_ah_attr;struct cm_device *cm_dev;struct cm_port *port; +u16 pkey_index;int ret; port =get_cm_port_from_path (path, sgid_attr);
@@ -539,12 +540,10 @@ static int cm_init_av_by_path(struct sa_path_rec *path, cm_dev = port->cm_dev; ret =ib_find_cached_pkey (cm_dev->ib_device, port->port_num, -be16_to_cpu (path->pkey), &av->pkey_index); +be16_to_cpu (path->pkey), &pkey_index);if (ret)return ret; -cm_set_av_port (av, port); -/* * av->ah_attr might be initialized based on wc or during * request processing time which might have reference to sgid_attr.
@@ -559,6 +558,8 @@ static int cm_init_av_by_path(struct sa_path_rec *path,if (ret)return ret; + av->pkey_index = pkey_index; +cm_set_av_port (av, port); av->timeout = path->packet_life_time +1 ;rdma_move_ah_attr (&av->ah_attr, &new_ah_attr);return 0 ;
@@ -2185,8 +2186,10 @@ static int cm_req_handler(struct cm_work *work) cm_id_priv->av.ah_attr.roce.dmac); work->path[0 ].hop_limit = grh->hop_limit; -/* This destroy call is needed to pair with cm_init_av_for_response */ -cm_destroy_av (&cm_id_priv->av); +/* +* cm_init_av_by_path() will internally pair with the above +* cm_init_av_for_response() if it succeeds. +*/ ret =cm_init_av_by_path (&work->path[0 ], gid_attr, &cm_id_priv->av);if (ret) {int err;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 352/1611 ALSA: hda: fix Kconfig dependency of HD Audio PCI
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oliver Hartkopp <[email protected]>
[ Upstream commit 1516134cb65526aba5319bb446c296fc8a192f84 ]
With commit 2d9223d2d64c ("ALSA: hda: Move controller drivers into sound/hda/controllers directory") the HD Audio drivers have been moved from linux/sound/pci/hda to linux/sound/hda.
But the Kconfig dependency for SND_HDA_INTEL stayed on SND_PCI instead of depending on PCI directly. To make the "HD Audio PCI" configuration entry visible it is currently needed to enable "PCI sound devices" although no PCI device in the submenu needs to be selected.
Make SND_HDA_INTEL directly depending on hardware/architecture like the other entries in this Kconfig.
--- sound/hda/controllers/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/hda/controllers/Kconfig +1 -1
@@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0-only config SND_HDA_INTEL tristate "HD Audio PCI" - depends on SND_PCI + depends on PCI select SND_HDA select SND_INTEL_DSP_CONFIG help
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 353/1611 RDMA/irdma: Fix OOB read during CQ MR registration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jacob Moroni <[email protected]>
[ Upstream commit 4385ddd654d90245eeb83b3cb539670ab5c85ba4 ]
Sashiko pointed out an unrelated bug during a previous patch:
https://sashiko.dev/#/patchset/20260512183852.614045-1-jmoroni%40google.com
This change fixes the bug by eliminating the cqmr->split field which was not being set properly and instead just checks the CQ resize feature flag directly.
The cqmr->split field essentially tracks whether IRDMA_FEATURE_CQ_RESIZE is set, but it was not being set until CQ creation time, which is _after_ CQ memory registration (the only other place where it is referenced).
As a result, it would always be false during MR registration and would therefore cause irdma_handle_q_mem to populate cqmr->shadow even for GEN_2 HW and beyond:
cqmr->shadow = (dma_addr_t)arr[req->cq_pages];
The issue is that for GEN_2 and beyond, req->cq_pages may be exactly equal to iwmr->page_cnt and therefore equal to the size of arr, which would cause an OOB read by one.
--- drivers/infiniband/hw/irdma/verbs.c | 4 ++-- drivers/infiniband/hw/irdma/verbs.h | 1 - 2 files changed, 2 insertions(+), 3 deletions(-)
drivers/infiniband/hw/irdma/verbs.c +2 -2
@@ -2563,7 +2563,6 @@ static int irdma_create_cq(struct ib_cq *ibcq, } cqmr_shadow = &iwpbl_shadow->cq_mr; info.shadow_area_pa = cqmr_shadow->cq_pbl.addr; - cqmr->split = true; }else { info.shadow_area_pa = cqmr->shadow; }
@@ -2965,7 +2964,8 @@ static int irdma_handle_q_mem(struct irdma_device *iwdev,case IRDMA_MEMREG_TYPE_CQ : hmc_p = &cqmr->cq_pbl; -if (!cqmr->split) +if (!(iwdev->rf->sc_dev.hw_attrs.uk_attrs.feature_flags & +IRDMA_FEATURE_CQ_RESIZE )) cqmr->shadow = (dma_addr_t )arr[req->cq_pages];if (lvl)
drivers/infiniband/hw/irdma/verbs.h +0 -1
@@ -65,7 +65,6 @@ struct irdma_hmc_pble {struct irdma_cq_mr {struct irdma_hmc_pble cq_pbl;dma_addr_t shadow; -bool split; };struct irdma_srq_mr {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 354/1611 RDMA/irdma: Initialize iwmr->access during MR registration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jacob Moroni <[email protected]>
[ Upstream commit 1521d560b7a1a39e437d37fffd9b55435d329ad1 ]
Initialize iwmr->access during initial user mem registration so that it contains a valid value during a subsequent rereg_mr.
Otherwise, a rereg_mr that doesn't set IB_MR_REREG_ACCESS (for example, one that only changes the PD) ends up clearing the access flags in HW since iwmr->access is zero-initialized, which is not intended.
--- drivers/infiniband/hw/irdma/verbs.c | 1 + 1 file changed, 1 insertion(+)
drivers/infiniband/hw/irdma/verbs.c +1 -0
@@ -3312,6 +3312,7 @@ static int irdma_reg_user_mr_type_mem(struct irdma_mr *iwmr, int access,int err; lvl = iwmr->page_cnt !=1 ?PBLE_LEVEL_1 |PBLE_LEVEL_2 :PBLE_LEVEL_0 ; + iwmr->access = access; err =irdma_setup_pbles (iwdev->rf, iwmr, lvl);if (err)
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 355/1611 arm64: dts: imx8mp-kontron: Reduce EERAM SPI clock frequency
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Frieder Schrempf <[email protected]>
[ Upstream commit 95f5bc1632ab8f243e517357b5da0dd28d1c6c92 ]
There is an onboard level shifter for the SPI signals that causes additional propagation delay and renders the SPI transmission unreliable at 20 MHz. Reduce the clock frequency to a safe value.
--- arch/arm64/boot/dts/freescale/imx8mp-kontron-bl-osm-s.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/imx8mp-kontron-bl-osm-s.dts +1 -1
@@ -63,7 +63,7 @@ &ecspi2 { eeram@0 { compatible = "microchip,48l640"; reg = <0>; - spi-max-frequency = <20000000>; + spi-max-frequency = <16000000>; }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 356/1611 arm64: dts: imx95: Correct PCIe outbound address space configuration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Richard Zhu <[email protected]>
[ Upstream commit dbecf38e60d4ef08c59836b7bc16e8efca01fc47 ]
Fix the PCIe outbound memory ranges for both pcie0 and pcie1 controllers on i.MX95.
The memory window size was incorrectly set to 256MB during initial bring-up, but the hardware supports up to 4GB of outbound address space per controller.
Additionally, the ECAM region cannot be mapped as I/O space. Use a memory-mapped region for I/O space instead, and relocate the 1MB I/O region to immediately follow the memory region at offset 0xf0000000 within each window.
Update the outbound address space layout per controller as follows:
- 3.5GB 64-bit prefetchable memory - 256MB 32-bit non-prefetchable memory - 1MB I/O
--- arch/arm64/boot/dts/freescale/imx95.dtsi | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
arch/arm64/boot/dts/freescale/imx95.dtsi +6 -4
@@ -1823,8 +1823,9 @@ pcie0: pcie@4c300000 { <0 0x4c360000 0 0x10000>, <0 0x4c340000 0 0x4000>; reg-names = "dbi", "config", "atu", "app"; - ranges = <0x81000000 0x0 0x00000000 0x0 0x6ff00000 0 0x00100000>, - <0x82000000 0x0 0x10000000 0x9 0x10000000 0 0x10000000>; + ranges = <0x43000000 0x9 0x00000000 0x9 0x00000000 0x0 0xe0000000>, + <0x82000000 0x0 0xe0000000 0x9 0xe0000000 0x0 0x10000000>, + <0x81000000 0x0 0x00000000 0x9 0xf0000000 0x0 0x00100000>; #address-cells = <3>; #size-cells = <2>; device_type = "pci";
@@ -1898,8 +1899,9 @@ pcie1: pcie@4c380000 { <0 0x4c3e0000 0 0x10000>, <0 0x4c3c0000 0 0x4000>; reg-names = "dbi", "config", "atu", "app"; - ranges = <0x81000000 0 0x00000000 0x8 0x8ff00000 0 0x00100000>, - <0x82000000 0 0x10000000 0xa 0x10000000 0 0x10000000>; + ranges = <0x43000000 0xa 0x00000000 0xa 0x00000000 0x0 0xe0000000>, + <0x82000000 0x0 0xe0000000 0xa 0xe0000000 0x0 0x10000000>, + <0x81000000 0x0 0x00000000 0xa 0xf0000000 0x0 0x00100000>; #address-cells = <3>; #size-cells = <2>; device_type = "pci";
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 357/1611 arm64: dts: lx2162a-clearfog: use rev2 SoC dtsi
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josua Mayer <[email protected]>
[ Upstream commit 13a37b30e464503515625ba891018aec0264c7d2 ]
LX2160A and LX2162A are different packages of the same silicon. While LX2160A had two revisions, LX2162A was released later based on LX2160A revision 2.
Commit a8fe6c8dfc40 ("arm64: dts: fsl-lx2160a: add rev2 support") has added a new soc dtsi for revision 2.
Update LX2162A Clearfog description to use revision 2 dtsi.
--- arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts +1 -1
@@ -6,7 +6,7 @@ /dts-v1/; -#include "fsl-lx2160a.dtsi" +#include "fsl-lx2160a-rev2.dtsi" #include "fsl-lx2162a-sr-som.dtsi" / {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 358/1611 arm64: dts: tqma8mpql-mba8mpxl: configure sai clock in audio codec as well
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Stein <[email protected]>
[ Upstream commit 748835fcb2eb2120234aef9556d282272501b96b ]
With deferrable card binding the sound card driver tries to get the mclk configuration before it is setup in sai3 node. Fix this by setting the sai clock config for the audio codec as well.
--- arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl.dts | 3 +++ 1 file changed, 3 insertions(+)
arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl.dts +3 -0
@@ -519,6 +519,9 @@ tlv320aic3x04: audio-codec@18 { reset-gpios = <&gpio4 29 GPIO_ACTIVE_LOW>; iov-supply = <®_vcc_1v8>; ldoin-supply = <®_vcc_3v3>; + assigned-clocks = <&clk IMX8MP_CLK_SAI3>; + assigned-clock-parents = <&clk IMX8MP_AUDIO_PLL1_OUT>; + assigned-clock-rates = <12288000>; }; se97_1c: temperature-sensor@1c {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 359/1611 arm64: dts: imx8mp-kontron: Fix GPIO for display power switch
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Frieder Schrempf <[email protected]>
[ Upstream commit 5b19ca527471903920d713bc48518a036a95bf6b ]
The GPIO that controls the power supply for the LVDS display connector has changed between early prototypes and the current production design of the hardware. Reflect this change in the devicetree to properly switch on the panel supply.
This was working before even with the wrong GPIO due to the bidirectional level shifter used on the board which drives the EN signal high even when the input has a (weak) pull down configured as reset condition of the SoC pad. As a result the display was working but the supply was always on.
Tested on BL i.MX8MP to show the correct voltage level on the level shifter input.
--- .../boot/dts/freescale/imx8mp-kontron-bl-osm-s.dts | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/freescale/imx8mp-kontron-bl-osm-s.dts +10 -2
@@ -49,7 +49,9 @@ pwm-beeper { reg_vcc_panel: regulator-vcc-panel { compatible = "regulator-fixed"; - gpio = <&gpio4 3 GPIO_ACTIVE_HIGH>; + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_reg_vcc_panel>; + gpio = <&gpio5 3 GPIO_ACTIVE_HIGH>; enable-active-high; regulator-max-microvolt = <3300000>; regulator-min-microvolt = <3300000>;
@@ -172,7 +174,7 @@ &gpio4 { &gpio5 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_gpio5>; - gpio-line-names = "I2S_BITCLK", "I2S_A_DATA_OUT", "I2S_MCLK", "PWM_2", + gpio-line-names = "I2S_BITCLK", "I2S_A_DATA_OUT", "I2S_MCLK", "VCC_PANEL_EN", "PWM_1", "PWM_0", "SPI_A_SCK", "CAN_ADDR1", "CAN_ADDR0", "SPI_A_CS0", "SPI_B_SCK", "SPI_B_SDO", "SPI_B_SDI", "SPI_B_CS0", "I2C_A_SCL", "I2C_A_SDA",
@@ -329,4 +331,10 @@ MX8MP_IOMUXC_ECSPI1_MOSI__GPIO5_IO07 0x46 /* CAN_ADR0 */ MX8MP_IOMUXC_ECSPI1_MISO__GPIO5_IO08 0x46 /* CAN_ADR1 */ >; }; + + pinctrl_reg_vcc_panel: regvccpanelgrp { + fsl,pins = < + MX8MP_IOMUXC_SPDIF_TX__GPIO5_IO03 0x46 + >; + }; };
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 360/1611 RDMA/siw: Fix endpoint/socket association handling
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bernard Metzler <[email protected]>
[ Upstream commit ea4f6f6c53577fb3f05dbd78b15e586772d49831 ]
Disassociating a socket from an endpoint via siw_socket_disassoc() may release the last reference on that endpoint and free it. Therefore, don't clear the endpoints socket pointer after calling that function, but within.
This fixes a:
BUG: KASAN: slab-use-after-free in siw_cm_work_handler (drivers/infiniband/sw/siw/siw_cm.c:1053 drivers/infiniband/sw/siw/siw_cm.c:1075)
which occurred after processing a malformed MPA request during connection establishment, causing the new endpoint to be closed.
--- drivers/infiniband/sw/siw/siw_cm.c | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-)
drivers/infiniband/sw/siw/siw_cm.c +15 -15
@@ -89,6 +89,7 @@ static void siw_socket_disassoc(struct socket *s) cep =sk_to_cep (sk);if (cep) {siw_sk_restore_upcalls (sk, cep); + cep->sock =NULL ;siw_cep_put (cep); }else {pr_warn ("siw: cannot restore sk callbacks: no ep\n" );
@@ -369,10 +370,11 @@ static void siw_free_cm_id(struct siw_cep *cep)static void siw_destroy_cep_sock (struct siw_cep *cep) { -if (cep->sock) { -siw_socket_disassoc (cep->sock); -sock_release (cep->sock); - cep->sock =NULL ; +struct socket *s = cep->sock; + +if (s) { +siw_socket_disassoc (s); +sock_release (s); } }
@@ -1001,7 +1003,6 @@ static void siw_accept_newconn(struct siw_cep *cep)if (new_s) {siw_socket_disassoc (new_s);sock_release (new_s); - new_cep->sock =NULL ; }siw_dbg_cep (cep,"error %d\n" , rv); }
@@ -1153,6 +1154,8 @@ static void siw_cm_work_handler(struct work_struct *w)WARN (1 ,"Undefined CM work type: %d\n" , work->type); }if (release_cep) { +struct socket *s = cep->sock; + siw_dbg_cep(cep, "release: timer=%s, QP[%u]\n", cep->mpa_timer ? "y" : "n",
@@ -1178,10 +1181,9 @@ static void siw_cm_work_handler(struct work_struct *w) cep->qp =NULL ;siw_qp_put (qp); } -if (cep->sock) { -siw_socket_disassoc (cep->sock); -sock_release (cep->sock); - cep->sock =NULL ; +if (s) { +siw_socket_disassoc (s); +sock_release (s); }if (cep->cm_id) {siw_free_cm_id (cep);
@@ -1511,7 +1513,6 @@ int siw_connect(struct iw_cm_id *id, struct iw_cm_conn_param *params)if (cep) {siw_socket_disassoc (s);sock_release (s); - cep->sock =NULL ; cep->qp =NULL ;
@@ -1886,7 +1887,6 @@ int siw_create_listen(struct iw_cm_id *id, int backlog)siw_cep_set_inuse (cep);siw_free_cm_id (cep); - cep->sock =NULL ;siw_socket_disassoc (s); cep->state =SIW_EPSTATE_CLOSED ;
@@ -1908,6 +1908,7 @@ static void siw_drop_listeners(struct iw_cm_id *id)*/ list_for_each_safe (p, tmp, (struct list_head *)id->provider_data) { struct siw_cep *cep = list_entry(p, struct siw_cep, listenq); +struct socket *s = cep->sock;list_del (p);
@@ -1916,10 +1917,9 @@ static void siw_drop_listeners(struct iw_cm_id *id)siw_cep_set_inuse (cep);siw_free_cm_id (cep); -if (cep->sock) { -siw_socket_disassoc (cep->sock); -sock_release (cep->sock); - cep->sock =NULL ; +if (s) { +siw_socket_disassoc (s); +sock_release (s); } cep->state =SIW_EPSTATE_CLOSED ;siw_cep_set_free_and_put (cep);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 361/1611 bpf: Clear rb node linkage when freeing bpf_rb_root
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kaitao Cheng <[email protected]>
[ Upstream commit 4a7910ee060d8ce55612f5b3cc267f3a265a3cec ]
bpf_rb_root_free() detaches the root by copying the current rb_root_cached and then replacing the live root with RB_ROOT_CACHED. It then walks the copied root and drops each object contained in the tree.
This leaves the rb node state intact while dropping the object. If the object is refcounted and survives the drop, its bpf_rb_node_kern still contains an owner pointer to the freed root and stale rb tree linkage. If a later bpf_rb_root allocation reuses the same address, bpf_rbtree_remove() can incorrectly pass the owner check and call rb_erase_cached() on a node whose rb pointers belong to the old tree.
Mirror the list draining behavior by marking nodes as busy while the root is being detached, then clear the rb node and release the owner before dropping the containing object. This makes surviving nodes unowned and safe to reject from remove or accept for a later add.
--- kernel/bpf/helpers.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
kernel/bpf/helpers.c +9 -2
@@ -2178,6 +2178,7 @@ void bpf_rb_root_free(const struct btf_field *field, void *rb_root, struct bpf_spin_lock *spin_lock) {struct rb_root_cached orig_root, *root = rb_root; +struct bpf_rb_node_kern *node;struct rb_node *pos, *n;void *obj;
@@ -2186,14 +2187,20 @@ void bpf_rb_root_free(const struct btf_field *field, void *rb_root,__bpf_spin_lock_irqsave (spin_lock); orig_root = *root; +bpf_rbtree_postorder_for_each_entry_safe (pos, n, &orig_root.rb_root) { + node = rb_entry(pos, struct bpf_rb_node_kern, rb_node); +WRITE_ONCE (node->owner,BPF_PTR_POISON ); + } *root =RB_ROOT_CACHED ;__bpf_spin_unlock_irqrestore (spin_lock);bpf_rbtree_postorder_for_each_entry_safe (pos, n, &orig_root.rb_root) { obj = pos; obj -= field->graph_root.node_offset; - - + node = rb_entry(pos, struct bpf_rb_node_kern, rb_node); +RB_CLEAR_NODE (pos); +/* Ensure __bpf_rbtree_add() sees the node as unlinked. */ +smp_store_release (&node->owner,NULL );__bpf_obj_drop_impl (obj, field->graph_root.value_rec, false); } }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 362/1611 bpf: Check tail zero of bpf_map_info
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Leon Hwang <[email protected]>
[ Upstream commit e2a49fdb1beed150125b4104c90eb2a96ec7f63a ]
Since there're 4 bytes padding at the end of struct bpf_map_info, they won't be checked by bpf_check_uarg_tail_zero().
pahole -C bpf_map_info ./vmlinux
struct bpf_map_info {
...
__u64 hash __attribute__((__aligned__(8))); /* 88 8 */
__u32 hash_size; /* 96 4 */
/* size: 104, cachelines: 2, members: 18 */
/* padding: 4 */
/* forced alignments: 1 */
/* last cacheline: 40 bytes */
} __attribute__((__aligned__(8)));If a future kernel extension adds a new 4-byte field, older userspace programs allocating this structure on the stack might inadvertently pass uninitialized stack garbage into the new field, permanently breaking backward compatibility. -- sashiko [1]
Fix it by changing sizeof(info) tooffsetofend(struct bpf_map_info, hash_size).
And, add "__u32 :32" to the tail of struct bpf_map_info.
[1] https://lore.kernel.org/bpf/[email protected]/
--- include/uapi/linux/bpf.h | 1 + kernel/bpf/syscall.c | 5 +++-- tools/include/uapi/linux/bpf.h | 1 + 3 files changed, 5 insertions(+), 2 deletions(-)
include/uapi/linux/bpf.h +1 -0
@@ -6684,6 +6684,7 @@ struct bpf_map_info {__u64 map_extra;__aligned_u64 hash;__u32 hash_size; + __u32 :32 ; } __attribute__((aligned(8)));struct bpf_btf_info {
kernel/bpf/syscall.c +3 -2
@@ -5282,10 +5282,11 @@ static int bpf_map_get_info_by_fd(struct file *file, {struct bpf_map_info __user *uinfo =u64_to_user_ptr (attr->info.info);struct bpf_map_info info; -u32 info_len = attr->info.info_len; +u32 info_len = attr->info.info_len, len;int err; - err =bpf_check_uarg_tail_zero (USER_BPFPTR (uinfo),sizeof (info), info_len); + len = offsetofend(struct bpf_map_info, hash_size); + err =bpf_check_uarg_tail_zero (USER_BPFPTR (uinfo), len, info_len);if (err)return err; info_len =min_t (u32,sizeof (info), info_len);
tools/include/uapi/linux/bpf.h +1 -0
@@ -6684,6 +6684,7 @@ struct bpf_map_info {__u64 map_extra;__aligned_u64 hash;__u32 hash_size; + __u32 :32 ; } __attribute__((aligned(8)));struct bpf_btf_info {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 363/1611 bpf: Check tail zero of bpf_prog_info
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Leon Hwang <[email protected]>
[ Upstream commit 786be2b05980a5828e67fc564ad7517e2adbe9bd ]
Since there're 4 bytes padding at the end of struct bpf_prog_info, they won't be checked by bpf_check_uarg_tail_zero().
pahole -C bpf_prog_info ./vmlinux
struct bpf_prog_info {
...
__u32 attach_btf_obj_id; /* 220 4 */
__u32 attach_btf_id; /* 224 4 */
/* size: 232, cachelines: 4, members: 38 */
/* sum members: 224 */
/* sum bitfield members: 1 bits, bit holes: 1, sum bit holes: 31 bits */
/* padding: 4 */
/* forced alignments: 9 */
/* last cacheline: 40 bytes */
} __attribute__((__aligned__(8)));If a future kernel extension adds a new 4-byte field, older userspace programs allocating this structure on the stack might inadvertently pass uninitialized stack garbage into the new field, permanently breaking backward compatibility. -- sashiko [1]
Fix it by changing sizeof(info) tooffsetofend(struct bpf_prog_info, attach_btf_id).
And, add "__u32 :32" to the tail of struct bpf_prog_info.
[1] https://lore.kernel.org/bpf/[email protected]/
--- include/uapi/linux/bpf.h | 1 + kernel/bpf/syscall.c | 5 +++-- tools/include/uapi/linux/bpf.h | 1 + 3 files changed, 5 insertions(+), 2 deletions(-)
include/uapi/linux/bpf.h +1 -0
@@ -6663,6 +6663,7 @@ struct bpf_prog_info {__u32 verified_insns;__u32 attach_btf_obj_id;__u32 attach_btf_id; + __u32 :32 ; } __attribute__((aligned(8)));struct bpf_map_info {
kernel/bpf/syscall.c +3 -2
@@ -4997,10 +4997,11 @@ static int bpf_prog_get_info_by_fd(struct file *file,u32 info_len = attr->info.info_len;struct bpf_prog_kstats stats;char __user *uinsns; -u32 ulen; +u32 ulen, len;int err; - err =bpf_check_uarg_tail_zero (USER_BPFPTR (uinfo),sizeof (info), info_len); + len = offsetofend(struct bpf_prog_info, attach_btf_id); + err =bpf_check_uarg_tail_zero (USER_BPFPTR (uinfo), len, info_len);if (err)return err; info_len =min_t (u32,sizeof (info), info_len);
tools/include/uapi/linux/bpf.h +1 -0
@@ -6663,6 +6663,7 @@ struct bpf_prog_info {__u32 verified_insns;__u32 attach_btf_obj_id;__u32 attach_btf_id; + __u32 :32 ; } __attribute__((aligned(8)));struct bpf_map_info {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 364/1611 bpf: Update transport_header when encapsulating UDP tunnel in lwt
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Leon Hwang <[email protected]>
[ Upstream commit 82d7d0adbc678064543e9d254864f6b4ea4a388c ]
Currently, bpf_lwt_push_ip_encap() does not update skb->transport_header. When a driver, e.g. ice, reuses the stale skb->transport_header to offload checksum computation to NIC hardware, VxLAN packets encapsulated by bpf_lwt_push_encap() helper may be dropped due to incorrect checksum.
Update skb->transport_header in bpf_lwt_push_ip_encap() whenever the encapsulated packet uses UDP, so checksum offload works correctly.
--- net/core/lwt_bpf.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
net/core/lwt_bpf.c +12 -0
@@ -595,6 +595,7 @@ static int handle_gso_encap(struct sk_buff *skb, bool ipv4, int encap_len)int bpf_lwt_push_ip_encap (struct sk_buff *skb,void *hdr,u32 len,bool ingress) { +bool is_udp_tunnel;struct iphdr *iph;bool ipv4;int err;
@@ -608,10 +609,16 @@ int bpf_lwt_push_ip_encap(struct sk_buff *skb, void *hdr, u32 len, bool ingress) ipv4 = true;if (unlikely (len < iph->ihl *4 ))return -EINVAL ; + is_udp_tunnel = iph->protocol ==IPPROTO_UDP ; +if (unlikely (is_udp_tunnel && len < iph->ihl *4 +sizeof (struct udphdr ))) +return -EINVAL ; }else if (iph->version ==6 ) { ipv4 = false;if (unlikely (len <sizeof (struct ipv6hdr )))return -EINVAL ; + is_udp_tunnel = ((struct ipv6hdr *)iph)->nexthdr ==NEXTHDR_UDP ; +if (unlikely (is_udp_tunnel && len <sizeof (struct ipv6hdr ) +sizeof (struct udphdr ))) +return -EINVAL ; }else {return -EINVAL ; }
@@ -633,6 +640,11 @@ int bpf_lwt_push_ip_encap(struct sk_buff *skb, void *hdr, u32 len, bool ingress)if (ingress)skb_postpush_rcsum (skb, iph, len);skb_reset_network_header (skb); +if (is_udp_tunnel) { +size_t iph_sz = ipv4 ? iph->ihl *4 :sizeof (struct ipv6hdr ); + +skb_set_transport_header (skb,skb_network_offset (skb) + iph_sz); + }memcpy (skb_network_header (skb), hdr, len);bpf_compute_data_pointers (skb);skb_clear_hash (skb);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 365/1611 wifi: wcn36xx: fix heap overflow from oversized firmware HAL response
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tristan Madani <[email protected]>
[ Upstream commit 88a240d86d3d64521f9194abe185ac71cc74d0bd ]
The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.
Add a bounds check on the response length.
--- drivers/net/wireless/ath/wcn36xx/smd.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/net/wireless/ath/wcn36xx/smd.c +4 -0
@@ -3353,6 +3353,10 @@ int wcn36xx_smd_rsp_process(struct rpmsg_device *rpdev,case WCN36XX_HAL_EXIT_IMPS_RSP :case WCN36XX_HAL_UPDATE_CHANNEL_LIST_RSP :case WCN36XX_HAL_ADD_BCN_FILTER_RSP : +if (len >WCN36XX_HAL_BUF_SIZE ) { +wcn36xx_warn ("HAL response too large: %d\n" , len); +break ; + }memcpy (wcn->hal_buf, buf, len); wcn->hal_rsp_len = len;complete (&wcn->hal_rsp_compl);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 366/1611 wifi: wcn36xx: fix OOB read from firmware count in PRINT_REG_INFO indication
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tristan Madani <[email protected]>
[ Upstream commit df2187acfca6c6cca372c5d35f42394d9c270b09 ]
The firmware-controlled rsp->count field is used as the loop bound for indexing into the flexible rsp->regs[] array without validation against the message length. A count exceeding the actual data causes out-of- bounds reads from the heap-allocated message buffer.
Add a check that count fits within the received message.
--- drivers/net/wireless/ath/wcn36xx/smd.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/net/wireless/ath/wcn36xx/smd.c +6 -0
@@ -2865,6 +2865,12 @@ static int wcn36xx_smd_print_reg_info_ind(struct wcn36xx *wcn,return -EIO ; } +if (rsp->count > (len -sizeof (*rsp)) /sizeof (rsp->regs[0 ])) { +wcn36xx_warn ("Truncated print reg info indication: count %u, len %zu\n" , + rsp->count, len); +return -EIO ; + } +wcn36xx_dbg (WCN36XX_DBG_HAL ,"reginfo indication, scenario: 0x%x reason: 0x%x\n" , rsp->scenario, rsp->reason);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 367/1611 wifi: wcn36xx: fix OOB read from short trigger BA firmware response
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tristan Madani <[email protected]>
[ Upstream commit b5e6f21923ca89d90256e7346301056f6502691e ]
The firmware response length is only checked against sizeof(*rsp) (20 bytes), but when candidate_cnt >= 1, a 22-byte candidate struct is read at buf + 20 without verifying the response contains it. This causes an out-of-bounds read of stale heap data, corrupting the BA session state.
Add validation that the response includes the candidate data.
--- drivers/net/wireless/ath/wcn36xx/smd.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/net/wireless/ath/wcn36xx/smd.c +3 -0
@@ -2659,6 +2659,9 @@ static int wcn36xx_smd_trigger_ba_rsp(void *buf, int len, struct add_ba_info *baif (rsp->candidate_cnt <1 )return rsp->status ? rsp->status : -EINVAL ; +if (len <sizeof (*rsp) +sizeof (*candidate)) +return -EINVAL ; + candidate = (struct wcn36xx_hal_trigger_ba_rsp_candidate *)(buf +sizeof (*rsp));for (i =0 ; i <STACFG_MAX_TC ; i++) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 368/1611 ALSA: seq: Fix partial userptr event expansion
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: HyeongJun An <[email protected]>
[ Upstream commit 2b7bd6f548292aec92a386deebe62324d21d62a9 ]
snd_seq_expand_var_event_at() clamps the number of bytes to copy to the remaining variable-event length, but passes the original buffer size to expand_var_event().
For SNDRV_SEQ_EXT_USRPTR events, expand_var_event() copies exactly the size argument from userspace. On the final chunk, when the remaining event data is shorter than the caller's buffer, this can read past the declared event data and can spuriously fail with -EFAULT if the extra bytes cross an unmapped page.
Pass the clamped length instead. The chained and kernel-backed paths already reclamp in dump_var_event(), but the user-pointer path handles the size directly.
--- sound/core/seq/seq_memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/core/seq/seq_memory.c +1 -1
@@ -211,7 +211,7 @@ int snd_seq_expand_var_event_at(const struct snd_seq_event *event, int count, len -= offset;if (len > count) len = count; - err =expand_var_event (event, offset, count, buf, true); + err =expand_var_event (event, offset, len, buf, true);if (err <0 )return err;return len;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 369/1611 riscv: cpu_ops: Change return value type of cpu_is_stopped() to bool
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hui Wang <[email protected]>
[ Upstream commit 2b2b207e1162e577cd6208e184d3d3a0fcfa9cca ]
In the original sbi_cpu_is_stopped(), if rc doesn't equal to the SBI_HSM_STATE_STOPPED, it will return rc to the caller directly. But there is a hidden problem, the rc could be SBI_HSM_STATE_STARTED, if so, this function will report cpu stopped while the cpu isn't really stopped.
Furthermore, from the name of cpu_is_stopped(), it gives a sense the return value is a bool type, true means the cpu is stopped, conversely false means the cpu is not stopped.
Here change the return value type to bool and change the callers accordingly. This could fix the above two issues.
--- arch/riscv/include/asm/cpu_ops.h | 2 +- arch/riscv/kernel/cpu-hotplug.c | 4 ++-- arch/riscv/kernel/cpu_ops_sbi.c | 11 +++++++---- 3 files changed, 10 insertions(+), 7 deletions(-)
arch/riscv/include/asm/cpu_ops.h +1 -1
@@ -24,7 +24,7 @@ struct cpu_operations { struct task_struct *tidle);#ifdef CONFIG_HOTPLUG_CPU void (*cpu_stop)(void ); -int (*cpu_is_stopped)(unsigned int cpu); +bool (*cpu_is_stopped)(unsigned int cpu);#endif };
arch/riscv/kernel/cpu-hotplug.c +2 -2
@@ -58,8 +58,8 @@ void arch_cpuhp_cleanup_dead_cpu(unsigned int cpu)/* Verify from the firmware if the cpu is really stopped*/ if (cpu_ops->cpu_is_stopped) ret = cpu_ops->cpu_is_stopped (cpu); -if (ret) -pr_warn ("CPU%u may not have stopped: %d\n" , cpu, ret); +if (!ret) +pr_warn ("CPU%u may not have stopped\n" , cpu); }/*
arch/riscv/kernel/cpu_ops_sbi.c +7 -4
@@ -88,16 +88,19 @@ static void sbi_cpu_stop(void) pr_crit("Unable to stop the cpu %u (%d)\n", smp_processor_id(), ret); } -static int sbi_cpu_is_stopped (unsigned int cpuid) +static bool sbi_cpu_is_stopped (unsigned int cpuid) {int rc;unsigned long hartid =cpuid_to_hartid_map (cpuid); rc =sbi_hsm_hart_get_status (hartid); -if (rc ==SBI_HSM_STATE_STOPPED ) -return 0 ; -return rc; +if (rc !=SBI_HSM_STATE_STOPPED ) { +pr_warn ("HART%lu isn't stopped; status %d\n" , hartid, rc); +return false; + } + +return true; }#endif
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 370/1611 riscv: stacktrace: Remove bogus -0x4 offset in non-FP walk_stackframe
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rui Qi <[email protected]>
[ Upstream commit 8ac35bac70e7e581d673b76878f7691cdadc33b8 ]
In the non-frame-pointer version of walk_stackframe, each value read from the stack is treated as a potential return address and has 0x4 subtracted before being used as the program counter. This was intended to convert the return address (the instruction after a call) back to the call site, but it is incorrect:
1. RISC-V has variable-length instructions due to the RVC (compressed instruction) extension. A call instruction can be either 4 bytes (regular) or 2 bytes (compressed, e.g. c.jal). Subtracting a fixed 0x4 assumes all call instructions are 4 bytes, which is wrong for compressed instructions.
2. Stack traces conventionally report return addresses, not call sites. Other architectures (ARM64, x86, ARM) do not subtract instruction size from return addresses in their stack unwinding code.
3. The frame-pointer version of walk_stackframe already dropped the -0x4 offset. Commit b785ec129bd9 ("riscv/ftrace: Add HAVE_FUNCTION_GRAPH_RET_ADDR_PTR support") replaced "pc = frame->ra - 0x4" with ftrace_graph_ret_addr(), and the commit message explicitly noted that "the original calculation, pc = frame->ra - 4, is buggy when the instruction at the return address happened to be a compressed inst." The non-FP version was simply overlooked.
Remove the bogus -0x4 offset to match the FP version and the conventions used by other architectures.
--- arch/riscv/kernel/stacktrace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/riscv/kernel/stacktrace.c +1 -1
@@ -129,7 +129,7 @@ void notrace walk_stackframe(struct task_struct *task,while (!kstack_end (ksp)) {if (__kernel_text_address (pc) &&unlikely (!fn (arg, pc)))break ; - pc =READ_ONCE_NOCHECK (*ksp++) -0x4 ; + pc =READ_ONCE_NOCHECK (*ksp++); } }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 371/1611 ALSA: seq: Clear variable event pointer on read
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kyle Zeng <[email protected]>
[ Upstream commit 705dd6dcbc0ea87351c660c1a6443f85f1001c76 ]
snd_seq_read() copies a queued variable-length event header to userspace before expanding the payload. Queued variable-length events use SNDRV_SEQ_EXT_CHAINED internally, and data.ext.ptr points at the first extension cell.
The read side strips SNDRV_SEQ_EXT_* bits from data.ext.len before the copy, but it leaves data.ext.ptr untouched. A userspace sequencer client can therefore write a direct variable event to itself and read back the extension-cell kernel address from the returned header.
Clear the temporary header pointer before copy_to_user(). The original queued event remains unchanged and is still passed to snd_seq_expand_var_event(), so payload expansion keeps using the internal chain.
--- sound/core/seq/seq_clientmgr.c | 1 + 1 file changed, 1 insertion(+)
sound/core/seq/seq_clientmgr.c +1 -0
@@ -441,6 +441,7 @@ static ssize_t snd_seq_read(struct file *file, char __user *buf, size_t count,memcpy (&tmpev, &cell->event, aligned_size); tmpev.data.ext.len &= ~SNDRV_SEQ_EXT_MASK ; + tmpev.data.ext.ptr =NULL ;if (copy_to_user (buf, &tmpev, aligned_size)) { err = -EFAULT ;break ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 372/1611 bpf: Fix NMI/tracepoint re-entry deadlock on lru locks
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mykyta Yatsenko <[email protected]>
[ Upstream commit 89edbdfc5d0308cef57b71359331de5c4ddbf763 ]
NMI and tracepoint BPF programs can re-enter the per-CPU or global LRU lock that bpf_lru_pop_free()/push_free() already hold on the same CPU, AA-deadlocking. Lockdep reports "inconsistent {INITIAL USE} -> {IN-NMI}" on &l->lock (syzbot c69a0a2c816716f1e0d5) and "possible recursive locking detected" on &loc_l->lock (syzbot 18b26edb69b2e19f3b33).
Prior trylock and rqspinlock based fixes (see links) were nacked because compromised on reliability.
This patch converts every LRU lock site to rqspinlock_t and adds a recovery path for some failure windows to avoid node leaks.
Failure recovery:
- *_pop_free top-level: return NULL; prealloc_lru_pop() already treats that as no-free-element (-ENOMEM).
- Cross-CPU steal: skip the victim's locked loc_l, try next CPU.
- Post-steal local lock fail: publish stolen node to lockless per-CPU free_llist; next pop on this CPU picks it up.
- push_free fail: mark node pending_free=1. __local_list_flush(), __local_list_pop_pending() reclaim the node from pending_list. __bpf_lru_list_shrink_inactive() reclaims the node from inactive list. Nodes from active list are reclaimed by __bpf_lru_list_shrink() or after __bpf_lru_list_rotate_active() demotes it to the inactive.
--- kernel/bpf/bpf_lru_list.c | 165 +++++++++++++++++++++++--------------- kernel/bpf/bpf_lru_list.h | 25 ++++-- 2 files changed, 119 insertions(+), 71 deletions(-)
kernel/bpf/bpf_lru_list.c +100 -65
@@ -13,23 +13,8 @@#define PERCPU_FREE_TARGET (4)#define PERCPU_NR_SCANS PERCPU_FREE_TARGET -/* Helpers to get the local list index */ -#define LOCAL_LIST_IDX (t) ((t) - BPF_LOCAL_LIST_T_OFFSET) -#define LOCAL_FREE_LIST_IDX LOCAL_LIST_IDX(BPF_LRU_LOCAL_LIST_T_FREE) -#define LOCAL_PENDING_LIST_IDX LOCAL_LIST_IDX(BPF_LRU_LOCAL_LIST_T_PENDING)#define IS_LOCAL_LIST_TYPE (t) ((t) >= BPF_LOCAL_LIST_T_OFFSET) -/* Local list helpers */ -static struct list_head *local_free_list (struct bpf_lru_locallist *loc_l) -{ -return &loc_l->lists[LOCAL_FREE_LIST_IDX ]; -} - -static struct list_head *local_pending_list (struct bpf_lru_locallist *loc_l) -{ -return &loc_l->lists[LOCAL_PENDING_LIST_IDX ]; -} -/* bpf_lru_node helpers */ static bool bpf_lru_node_is_ref (const struct bpf_lru_node *node) {
@@ -72,6 +57,7 @@ static void __bpf_lru_node_move_to_free(struct bpf_lru_list *l,bpf_lru_list_count_dec (l, node->type); node->type = tgt_free_type; +WRITE_ONCE (node->pending_free,0 );list_move (&node->list, free_list); }
@@ -87,6 +73,9 @@ static void __bpf_lru_node_move_in(struct bpf_lru_list *l,bpf_lru_list_count_inc (l, tgt_type); node->type = tgt_type;bpf_lru_node_clear_ref (node); +/* Reset pending_free only when moving to the free list */ +if (tgt_type ==BPF_LRU_LIST_T_FREE ) +WRITE_ONCE (node->pending_free,0 );list_move (&node->list, &l->lists[tgt_type]); }
@@ -212,9 +201,11 @@ __bpf_lru_list_shrink_inactive(struct bpf_lru *lru,unsigned int i =0 ;list_for_each_entry_safe_reverse (node, tmp_node, inactive, list) { -if (bpf_lru_node_is_ref (node)) { +if (bpf_lru_node_is_ref (node) && + !READ_ONCE (node->pending_free)) {__bpf_lru_node_move (l, node,BPF_LRU_LIST_T_ACTIVE ); - }else if (lru->del_from_htab (lru->del_arg, node)) { + }else if (READ_ONCE (node->pending_free) || + lru->del_from_htab (lru->del_arg, node)) {__bpf_lru_node_move_to_free (l, node, free_list, tgt_free_type);if (++nshrinked == tgt_nshrink)
@@ -273,7 +264,8 @@ static unsigned int __bpf_lru_list_shrink(struct bpf_lru *lru,list_for_each_entry_safe_reverse (node, tmp_node, force_shrink_list, list) { -if (lru->del_from_htab (lru->del_arg, node)) { +if (READ_ONCE (node->pending_free) || + lru->del_from_htab (lru->del_arg, node)) {__bpf_lru_node_move_to_free (l, node, free_list, tgt_free_type);return 1 ;
@@ -290,8 +282,10 @@ static void __local_list_flush(struct bpf_lru_list *l,struct bpf_lru_node *node, *tmp_node;list_for_each_entry_safe_reverse (node, tmp_node, -local_pending_list (loc_l), list) { -if (bpf_lru_node_is_ref (node)) + &loc_l->pending_list, list) { +if (READ_ONCE (node->pending_free)) +__bpf_lru_node_move_in (l, node,BPF_LRU_LIST_T_FREE ); +else if (bpf_lru_node_is_ref (node))__bpf_lru_node_move_in (l, node,BPF_LRU_LIST_T_ACTIVE );else __bpf_lru_node_move_in(l, node,
@@ -307,9 +301,12 @@ static void bpf_lru_list_push_free(struct bpf_lru_list *l,if (WARN_ON_ONCE (IS_LOCAL_LIST_TYPE (node->type)))return ; -raw_spin_lock_irqsave (&l->lock, flags); +if (raw_res_spin_lock_irqsave (&l->lock, flags)) { +WRITE_ONCE (node->pending_free,1 ); +return ; + }__bpf_lru_node_move (l, node,BPF_LRU_LIST_T_FREE ); -raw_spin_unlock_irqrestore (&l->lock, flags); +raw_res_spin_unlock_irqrestore (&l->lock, flags); } static void bpf_lru_list_pop_free_to_local(struct bpf_lru *lru,
@@ -318,8 +315,10 @@ static void bpf_lru_list_pop_free_to_local(struct bpf_lru *lru,struct bpf_lru_list *l = &lru->common_lru.lru_list;struct bpf_lru_node *node, *tmp_node;unsigned int nfree =0 ; +LIST_HEAD (tmp_free); -raw_spin_lock (&l->lock); +if (raw_res_spin_lock (&l->lock)) +return ;__local_list_flush (l, loc_l);
@@ -327,7 +326,7 @@ static void bpf_lru_list_pop_free_to_local(struct bpf_lru *lru,list_for_each_entry_safe (node, tmp_node, &l->lists[BPF_LRU_LIST_T_FREE ], list) { -__bpf_lru_node_move_to_free (l, node,local_free_list (loc_l), +__bpf_lru_node_move_to_free (l, node, &tmp_free,BPF_LRU_LOCAL_LIST_T_FREE );if (++nfree == lru->target_free)break ;
@@ -335,10 +334,19 @@ static void bpf_lru_list_pop_free_to_local(struct bpf_lru *lru,if (nfree < lru->target_free)__bpf_lru_list_shrink (lru, l, lru->target_free - nfree, -local_free_list (loc_l), + &tmp_free,BPF_LRU_LOCAL_LIST_T_FREE ); -raw_spin_unlock (&l->lock); +raw_res_spin_unlock (&l->lock); + +/* +* Transfer the harvested nodes from the temporary list_head into +* the lockless per-CPU free llist. +*/ +list_for_each_entry_safe (node, tmp_node, &tmp_free, list) { +list_del (&node->list); +llist_add (&node->llist, &loc_l->free_llist); + } } static void __local_list_add_pending(struct bpf_lru *lru,
@@ -350,22 +358,21 @@ static void __local_list_add_pending(struct bpf_lru *lru, *(u32 *)((void *)node + lru->hash_offset) = hash; node->cpu = cpu; node->type =BPF_LRU_LOCAL_LIST_T_PENDING ; +WRITE_ONCE (node->pending_free,0 );bpf_lru_node_clear_ref (node); -list_add (&node->list,local_pending_list (loc_l)); +list_add (&node->list, &loc_l->pending_list); }static struct bpf_lru_node *__local_list_pop_free (struct bpf_lru_locallist *loc_l) { -struct bpf_lru_node *node; +struct llist_node *llnode; - node =list_first_entry_or_null (local_free_list (loc_l), - struct bpf_lru_node, - list); -if (node) -list_del (&node->list); + llnode =llist_del_first (&loc_l->free_llist); +if (!llnode) +return NULL ; -return node; + return container_of(llnode, struct bpf_lru_node, llist); } static struct bpf_lru_node *
@@ -376,10 +383,10 @@ __local_list_pop_pending(struct bpf_lru *lru, struct bpf_lru_locallist *loc_l) ignore_ref:/* Get from the tail (i.e. older element) of the pending list. */ -list_for_each_entry_reverse (node,local_pending_list (loc_l), - list) { +list_for_each_entry_reverse (node, &loc_l->pending_list, list) {if ((!bpf_lru_node_is_ref (node) || force) && - lru->del_from_htab (lru->del_arg, node)) { + (READ_ONCE (node->pending_free) || + lru->del_from_htab (lru->del_arg, node))) {list_del (&node->list);return node; }
@@ -404,7 +411,8 @@ static struct bpf_lru_node *bpf_percpu_lru_pop_free(struct bpf_lru *lru, l =per_cpu_ptr (lru->percpu_lru, cpu); -raw_spin_lock_irqsave (&l->lock, flags); +if (raw_res_spin_lock_irqsave (&l->lock, flags)) +return NULL ;__bpf_lru_list_rotate (lru, l);
@@ -420,7 +428,7 @@ static struct bpf_lru_node *bpf_percpu_lru_pop_free(struct bpf_lru *lru,__bpf_lru_node_move (l, node,BPF_LRU_LIST_T_INACTIVE ); } -raw_spin_unlock_irqrestore (&l->lock, flags); +raw_res_spin_unlock_irqrestore (&l->lock, flags);return node; }
@@ -437,7 +445,8 @@ static struct bpf_lru_node *bpf_common_lru_pop_free(struct bpf_lru *lru, loc_l =per_cpu_ptr (clru->local_list, cpu); -raw_spin_lock_irqsave (&loc_l->lock, flags); +if (raw_res_spin_lock_irqsave (&loc_l->lock, flags)) +return NULL ; node =__local_list_pop_free (loc_l);if (!node) {
@@ -448,17 +457,22 @@ static struct bpf_lru_node *bpf_common_lru_pop_free(struct bpf_lru *lru,if (node)__local_list_add_pending (lru, loc_l, cpu, node, hash); -raw_spin_unlock_irqrestore (&loc_l->lock, flags); +raw_res_spin_unlock_irqrestore (&loc_l->lock, flags);if (node)return node; -/* No free nodes found from the local free list and +/* +* No free nodes found from the local free list and * the global LRU list. * * Steal from the local free/pending list of the * current CPU and remote CPU in RR. It starts * with the loc_l->next_steal CPU. +* +* Acquire the victim's lock before touching either list. On +* acquisition failure (rqspinlock AA or timeout) skip the victim +* and try the next CPU. */ first_steal = loc_l->next_steal;
@@ -466,24 +480,36 @@ static struct bpf_lru_node *bpf_common_lru_pop_free(struct bpf_lru *lru,do { steal_loc_l =per_cpu_ptr (clru->local_list, steal); -raw_spin_lock_irqsave (&steal_loc_l->lock, flags); - - node =__local_list_pop_free (steal_loc_l); -if (!node) - node =__local_list_pop_pending (lru, steal_loc_l); - -raw_spin_unlock_irqrestore (&steal_loc_l->lock, flags); +if (!raw_res_spin_lock_irqsave (&steal_loc_l->lock, flags)) { + node =__local_list_pop_free (steal_loc_l); +if (!node) + node =__local_list_pop_pending (lru, steal_loc_l); +raw_res_spin_unlock_irqrestore (&steal_loc_l->lock, flags); + } steal =cpumask_next_wrap (steal, cpu_possible_mask); }while (!node && steal != first_steal); loc_l->next_steal = steal; -if (node) { -raw_spin_lock_irqsave (&loc_l->lock, flags); -__local_list_add_pending (lru, loc_l, cpu, node, hash); -raw_spin_unlock_irqrestore (&loc_l->lock, flags); +if (!node) +return NULL ; + +if (raw_res_spin_lock_irqsave (&loc_l->lock, flags)) { +/* +* The local pending lock can't be acquired (rqspinlock AA +* or timeout). Return the stolen node to the per-CPU +* free_llist instead of orphaning it; the next pop_free on +* this CPU will pick it up. +*/ + node->type =BPF_LRU_LOCAL_LIST_T_FREE ; +bpf_lru_node_clear_ref (node); +WRITE_ONCE (node->pending_free,0 ); +llist_add (&node->llist, &loc_l->free_llist); +return NULL ; } +__local_list_add_pending (lru, loc_l, cpu, node, hash); +raw_res_spin_unlock_irqrestore (&loc_l->lock, flags);return node; }
@@ -511,18 +537,24 @@ static void bpf_common_lru_push_free(struct bpf_lru *lru, loc_l =per_cpu_ptr (lru->common_lru.local_list, node->cpu); -raw_spin_lock_irqsave (&loc_l->lock, flags); +if (raw_res_spin_lock_irqsave (&loc_l->lock, flags)) { +WRITE_ONCE (node->pending_free,1 ); +return ; + }if (unlikely (node->type !=BPF_LRU_LOCAL_LIST_T_PENDING )) { -raw_spin_unlock_irqrestore (&loc_l->lock, flags); +raw_res_spin_unlock_irqrestore (&loc_l->lock, + flags); goto check_lru_list; } node->type =BPF_LRU_LOCAL_LIST_T_FREE ;bpf_lru_node_clear_ref (node); -list_move (&node->list,local_free_list (loc_l)); +list_del (&node->list); + +raw_res_spin_unlock_irqrestore (&loc_l->lock, flags); -raw_spin_unlock_irqrestore (&loc_l->lock, flags); +llist_add (&node->llist, &loc_l->free_llist);return ; }
@@ -538,11 +570,14 @@ static void bpf_percpu_lru_push_free(struct bpf_lru *lru, l =per_cpu_ptr (lru->percpu_lru, node->cpu); -raw_spin_lock_irqsave (&l->lock, flags); +if (raw_res_spin_lock_irqsave (&l->lock, flags)) { +WRITE_ONCE (node->pending_free,1 ); +return ; + }__bpf_lru_node_move (l, node,BPF_LRU_LIST_T_FREE ); -raw_spin_unlock_irqrestore (&l->lock, flags); +raw_res_spin_unlock_irqrestore (&l->lock, flags); }void bpf_lru_push_free (struct bpf_lru *lru,struct bpf_lru_node *node)
@@ -565,6 +600,7 @@ static void bpf_common_lru_populate(struct bpf_lru *lru, void *buf, node = (struct bpf_lru_node *)(buf + node_offset); node->type =BPF_LRU_LIST_T_FREE ; + node->pending_free =0 ;bpf_lru_node_clear_ref (node);list_add (&node->list, &l->lists[BPF_LRU_LIST_T_FREE ]); buf += elem_size;
@@ -594,6 +630,7 @@ static void bpf_percpu_lru_populate(struct bpf_lru *lru, void *buf, node = (struct bpf_lru_node *)(buf + node_offset); node->cpu = cpu; node->type =BPF_LRU_LIST_T_FREE ; + node->pending_free =0 ;bpf_lru_node_clear_ref (node);list_add (&node->list, &l->lists[BPF_LRU_LIST_T_FREE ]); i++;
@@ -618,14 +655,12 @@ void bpf_lru_populate(struct bpf_lru *lru, void *buf, u32 node_offset,static void bpf_lru_locallist_init (struct bpf_lru_locallist *loc_l,int cpu) { -int i; - -for (i =0 ; i <NR_BPF_LRU_LOCAL_LIST_T ; i++) -INIT_LIST_HEAD (&loc_l->lists[i]); +INIT_LIST_HEAD (&loc_l->pending_list); +init_llist_head (&loc_l->free_llist); loc_l->next_steal = cpu; -raw_spin_lock_init (&loc_l->lock); +raw_res_spin_lock_init (&loc_l->lock); }static void bpf_lru_list_init (struct bpf_lru_list *l)
@@ -640,7 +675,7 @@ static void bpf_lru_list_init(struct bpf_lru_list *l) l->next_inactive_rotation = &l->lists[BPF_LRU_LIST_T_INACTIVE ]; -raw_spin_lock_init (&l->lock); +raw_res_spin_lock_init (&l->lock); } int bpf_lru_init(struct bpf_lru *lru, bool percpu, u32 hash_offset,
kernel/bpf/bpf_lru_list.h +19 -6
@@ -6,11 +6,11 @@#include <linux/cache.h> #include <linux/list.h> -#include <linux/spinlock_types.h> +#include <linux/llist.h> +#include <asm/rqspinlock.h> #define NR_BPF_LRU_LIST_T (3)#define NR_BPF_LRU_LIST_COUNT (2) -#define NR_BPF_LRU_LOCAL_LIST_T (2)#define BPF_LOCAL_LIST_T_OFFSET NR_BPF_LRU_LIST_Tenum bpf_lru_list_type {
@@ -22,10 +22,22 @@ enum bpf_lru_list_type { };struct bpf_lru_node { -struct list_head list; +/* +* A node is in at most one list at a time. The free path on the +* per-CPU locallist uses an llist, so share storage via a union. +*/ +union { +struct list_head list; +struct llist_node llist; + };u16 cpu;u8 type;u8 ref; +/* +* Marks nodes whose *_push_free() lock acquire failed; reclaimed +* by flush/shrink which honor the flag instead of del_from_htab(). +*/ +u8 pending_free; };struct bpf_lru_list {
@@ -34,13 +46,14 @@ struct bpf_lru_list {/* The next inactive list rotation starts from here */ struct list_head *next_inactive_rotation; -raw_spinlock_t lock____cacheline_aligned_in_smp ; +rqspinlock_t lock____cacheline_aligned_in_smp ; };struct bpf_lru_locallist { -struct list_head lists[NR_BPF_LRU_LOCAL_LIST_T ]; +struct list_head pending_list; +struct llist_head free_llist;u16 next_steal; -raw_spinlock_t lock; +rqspinlock_t lock; };struct bpf_common_lru {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 373/1611 kunit:tool: Dont write to stdout when it should be disabled
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Gow <[email protected]>
[ Upstream commit 29afed142d64e181749214072315c976f8510bd7 ]
The kunit_parser module accepts a 'printer' object which is used as a destination for all output. This is typically set to stdout, so that the parsed results are visible, but can be set to a special 'null_printer' to implement options where not all results are always printed.
However, there are a few places where use of stdout is hardcoded, notably in handling crashed tests and in outputting the colour escape sequences.
Properly use the specified printer for all output. This is okay for the colour handling (as this is already gated behind isatty() anyway), and also for the crash handling, as cases where printer != stdout are separately printed afterwards.
--- tools/testing/kunit/kunit_parser.py | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
tools/testing/kunit/kunit_parser.py +6 -6
@@ -17,7 +17,7 @@ import textwrap from enum import Enum, auto from typing import Iterable, Iterator, List, Optional, Tuple -from kunit_printer import Printer, stdout +from kunit_printer import Printer class Test: """
@@ -57,7 +57,7 @@ class Test: def add_error(self, printer: Printer, error_message: str) -> None: """Records an error that occurred while parsing this test.""" self.counts.errors += 1 - printer.print_with_timestamp(stdout.red('[ERROR]') + f' Test: {self.name}: {error_message}') + printer.print_with_timestamp(printer.red('[ERROR]') + f' Test: {self.name}: {error_message}') def ok_status(self) -> bool: """Returns true if the status was ok, i.e. passed or skipped."""
@@ -544,7 +544,7 @@ def format_test_result(test: Test, printer: Printer) -> str: return printer.yellow('[NO TESTS RUN] ') + test.name if test.status == TestStatus.TEST_CRASHED: print_log(test.log, printer) - return stdout.red('[CRASHED] ') + test.name + return printer.red('[CRASHED] ') + test.name print_log(test.log, printer) return printer.red('[FAILED] ') + test.name
@@ -651,11 +651,11 @@ def print_summary_line(test: Test, printer: Printer) -> None: printer - Printer object to output results """ if test.status == TestStatus.SUCCESS: - color = stdout.green + color = printer.green elif test.status in (TestStatus.SKIPPED, TestStatus.NO_TESTS): - color = stdout.yellow + color = printer.yellow else: - color = stdout.red + color = printer.red printer.print_with_timestamp(color(f'Testing complete. {test.counts}')) # Summarize failures that might have gone off-screen since we had a lot
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 374/1611 powerpc/8xx: implement get_direction() in cpm1
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bartosz Golaszewski <[email protected]>
[ Upstream commit 052f67a1ae6ffa6e43c82193bf2e6c0dfd2e6d8f ]
The lack of get_direction() callbacks in this driver causes GPIOLIB to emit a warning. Implement them for 16- and 32-bit variants.
--- arch/powerpc/platforms/8xx/cpm1.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
arch/powerpc/platforms/8xx/cpm1.c +26 -0
@@ -472,6 +472,18 @@ static int cpm1_gpio16_dir_in(struct gpio_chip *gc, unsigned int gpio)return 0 ; } +static int cpm1_gpio16_get_direction (struct gpio_chip *gc,unsigned int gpio) +{ +struct cpm1_gpio16_chip *cpm1_gc =gpiochip_get_data (gc); +struct cpm_ioport16 __iomem *iop = cpm1_gc->regs; +u16 pin_mask =1 << (15 - gpio); + +if (in_be16 (&iop->dir) & pin_mask) +return GPIO_LINE_DIRECTION_OUT ; + +return GPIO_LINE_DIRECTION_IN ; +} +int cpm1_gpiochip_add16 (struct device *dev) {struct device_node *np = dev->of_node;
@@ -498,6 +510,7 @@ int cpm1_gpiochip_add16(struct device *dev) gc->ngpio =16 ; gc->direction_input = cpm1_gpio16_dir_in; gc->direction_output = cpm1_gpio16_dir_out; + gc->get_direction = cpm1_gpio16_get_direction; gc->get = cpm1_gpio16_get; gc->set = cpm1_gpio16_set; gc->to_irq = cpm1_gpio16_to_irq;
@@ -604,6 +617,18 @@ static int cpm1_gpio32_dir_in(struct gpio_chip *gc, unsigned int gpio)return 0 ; } +static int cpm1_gpio32_get_direction (struct gpio_chip *gc,unsigned int gpio) +{ +struct cpm1_gpio32_chip *cpm1_gc =gpiochip_get_data (gc); +struct cpm_ioport32b __iomem *iop = cpm1_gc->regs; +u32 pin_mask =1 << (31 - gpio); + +if (in_be32 (&iop->dir) & pin_mask) +return GPIO_LINE_DIRECTION_OUT ; + +return GPIO_LINE_DIRECTION_IN ; +} +int cpm1_gpiochip_add32 (struct device *dev) {struct device_node *np = dev->of_node;
@@ -621,6 +646,7 @@ int cpm1_gpiochip_add32(struct device *dev) gc->ngpio =32 ; gc->direction_input = cpm1_gpio32_dir_in; gc->direction_output = cpm1_gpio32_dir_out; + gc->get_direction = cpm1_gpio32_get_direction; gc->get = cpm1_gpio32_get; gc->set = cpm1_gpio32_set; gc->parent = dev;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 375/1611 bpf: Fix NULL pointer dereference in bpf_task_from_vpid()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sechang Lim <[email protected]>
[ Upstream commit 50dff00615522f3ec03449680ca23beb4cfc549c ]
bpf_task_from_vpid() looks up a task in the pid namespace of the current task, via find_task_by_vpid():
find_task_by_vpid(vpid)
find_task_by_pid_ns(vpid, task_active_pid_ns(current))
find_pid_ns(nr, ns) -> idr_find(&ns->idr, nr)cgroup_skb programs run in softirq, which may interrupt a task that is itself in do_exit(). Once that task has passedexit_notify() -> release_task() -> __unhash_process(), its thread_pid is cleared, so task_active_pid_ns(current) returns NULL and find_pid_ns() dereferences &NULL->idr:
BUG: kernel NULL pointer dereference, address: 0000000000000050 RIP: 0010:idr_find+0x11/0x30 lib/idr.c:176 Call Trace: <IRQ> find_pid_ns kernel/pid.c:370 [inline] find_task_by_pid_ns+0x3b/0xe0 kernel/pid.c:485 bpf_task_from_vpid+0x5b/0x200 kernel/bpf/helpers.c:2916 bpf_prog_run_array_cg+0x17e/0x530 kernel/bpf/cgroup.c:81 __cgroup_bpf_run_filter_skb+0x12b/0x250 kernel/bpf/cgroup.c:1612 sk_filter_trim_cap+0x1dc/0x4c0 net/core/filter.c:148 tcp_v4_rcv+0x18d1/0x2200 net/ipv4/tcp_ipv4.c:2223 </IRQ> <TASK> do_exit+0xa63/0x1270 kernel/exit.c:1010 get_signal+0x141c/0x1530 kernel/signal.c:3037
Bail out when current has no pid namespace.
--- kernel/bpf/helpers.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
kernel/bpf/helpers.c +4 -2
@@ -2672,11 +2672,13 @@ __bpf_kfunc struct task_struct *bpf_task_from_vpid(s32 vpid) {struct task_struct *p; -rcu_read_lock (); +guard (rcu)(); +if (!task_active_pid_ns (current)) +return NULL ; + p =find_task_by_vpid (vpid);if (p) p =bpf_task_acquire (p); -rcu_read_unlock ();return p; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 376/1611 ACPI: IPMI: Fix message kref handling on dead device
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuho Choi <[email protected]>
[ Upstream commit 63320db6a5d84ec3fed8b3d36ba5244d07ddd108 ]
acpi_ipmi_space_handler() takes an extra reference on tx_msg before checking whether the selected IPMI device is dead. The reference belongs to the tx_msg_list entry and is normally dropped by ipmi_cancel_tx_msg() or ipmi_flush_tx_msg() after the message is removed from the list.
On the dead-device path, the message has not been queued yet, but the error path still calls ipmi_msg_release() directly. That bypasses kref_put() and frees tx_msg while the queued-message reference is still recorded in the kref count.
Take the queued-message reference only after the dead-device check succeeds, immediately before adding tx_msg to the list.
--- drivers/acpi/acpi_ipmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/acpi/acpi_ipmi.c +1 -1
@@ -550,7 +550,6 @@ acpi_ipmi_space_handler(u32 function, acpi_physical_address address,return AE_TYPE ; } -acpi_ipmi_msg_get (tx_msg);mutex_lock (&driver_data.ipmi_lock);/* Do not add a tx_msg that can not be flushed. */ if (ipmi_device->dead) {
@@ -558,6 +557,7 @@ acpi_ipmi_space_handler(u32 function, acpi_physical_address address,ipmi_msg_release (tx_msg);return AE_NOT_EXIST ; } +acpi_ipmi_msg_get (tx_msg);spin_lock_irqsave (&ipmi_device->tx_msg_lock, flags);list_add_tail (&tx_msg->head, &ipmi_device->tx_msg_list);spin_unlock_irqrestore (&ipmi_device->tx_msg_lock, flags);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 377/1611 cpufreq: Documentation: fix conservative governor freq_step description
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pengjie Zhang <[email protected]>
[ Upstream commit 03120e1425262c7d11f93362a88e579a1720390b ]
The conservative governor documentation incorrectly states that setting freq_step to 0 will use the default 5% frequency step. In reality, since at least commit 8e677ce83bf4 ("[CPUFREQ] conservative: fixup governor to function more like ondemand logic"), freq_step=0 has always caused the governor to skip frequency updates entirely.
Correct the documentation to reflect the actual behavior: freq_step=0 disables frequency changes by the governor entirely.
--- Documentation/admin-guide/pm/cpufreq.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/admin-guide/pm/cpufreq.rst +2 -2
@@ -586,8 +586,8 @@ This governor exposes the following tunables: 100 (5 by default). This is how much the frequency is allowed to change in one go. Setting - it to 0 will cause the default frequency step (5 percent) to be used - and setting it to 100 effectively causes the governor to periodically + it to 0 disables frequency changes by the governor entirely and setting + it to 100 effectively causes the governor to periodically switch the frequency between the ``scaling_min_freq`` and ``scaling_max_freq`` policy limits.
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 378/1611 thermal: testing: reject missing command arguments
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Samuel Moelius <[email protected]>
[ Upstream commit ef3e98b0aa4b348f44065d7130251273c83bd204 ]
The thermal testing debugfs command parser splits commands at ':' and passes the right-hand side to the command implementation. Commands such as deltz, tzaddtrip, tzreg, and tzunreg require a zone id, but writing one of those command names without ':' leaves the argument pointer NULL.
The command implementations parse the id with sscanf(arg, "%d", ...), so the missing-argument form dereferences a NULL pointer from the debugfs write path.
Reject missing arguments in tt_command_exec() before calling handlers that require an id.
--- drivers/thermal/testing/command.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/thermal/testing/command.c +12 -0
@@ -116,18 +116,30 @@ static int tt_command_exec(int index, const char *arg)break ;case TT_CMD_DELTZ : +if (!arg || !*arg) +return -EINVAL ; + ret =tt_del_tz (arg);break ;case TT_CMD_TZADDTRIP : +if (!arg || !*arg) +return -EINVAL ; + ret =tt_zone_add_trip (arg);break ;case TT_CMD_TZREG : +if (!arg || !*arg) +return -EINVAL ; + ret =tt_zone_reg (arg);break ;case TT_CMD_TZUNREG : +if (!arg || !*arg) +return -EINVAL ; + ret =tt_zone_unreg (arg);break ;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 379/1611 btrfs: dont force DIO writes to be serialized
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mark Harmstone <[email protected]>
[ Upstream commit 14f9161e872072075284b8afa4c3f929e199a0f6 ]
Before btrfs switched to the new mount API in 2023, we were setting SB_NOSEC in btrfs_mount_root(). This flag tells the VFS that the filesystem may have files which don't have security xattrs, enabling it to do some optimizations.
Unfortunately this was missed in the transition, meaning that IS_NOSEC will always return false for a btrfs inode. This means that btrfs_direct_write() calls will always get the inode lock exclusively, meaning that DIO writes to the same file will be serialized.
On my machine, this one-line change results in a ~59% improvement in DIO throughput:
Before patch:
test: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=io_uring, iodepth=64
...
fio-3.39
Starting 32 processes
test: Laying out IO file (1 file / 1024MiB)
Jobs: 32 (f=32): [w(32)][100.0%][w=764MiB/s][w=195k IOPS][eta 00m:00s]
test: (groupid=0, jobs=32): err= 0: pid=586: Wed Apr 22 13:03:04 2026
write: IOPS=202k, BW=787MiB/s (826MB/s)(46.1GiB/60012msec); 0 zone resets
bw ( KiB/s): min=498714, max=1199892, per=100.00%, avg=806659.03, stdev=4229.94, samples=3808
iops : min=124677, max=299971, avg=201661.82, stdev=1057.49, samples=3808
cpu : usr=0.32%, sys=1.27%, ctx=8329204, majf=0, minf=1163
IO depths : 1=0.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=100.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
issued rwts: total=0,12094328,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=64Run status group 0 (all jobs):
WRITE: bw=787MiB/s (826MB/s), 787MiB/s-787MiB/s (826MB/s-826MB/s), io=46.1GiB (49.5GB), run=60012-60012msec
After patch:
test: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=io_uring, iodepth=64
...
fio-3.39
Starting 32 processes
test: Laying out IO file (1 file / 1024MiB)
Jobs: 32 (f=32): [w(32)][100.0%][w=1255MiB/s][w=321k IOPS][eta 00m:00s]
test: (groupid=0, jobs=32): err= 0: pid=572: Wed Apr 22 13:13:46 2026
write: IOPS=320k, BW=1250MiB/s (1311MB/s)(73.3GiB/60003msec); 0 zone resets
bw ( MiB/s): min= 619, max= 2289, per=100.00%, avg=1251.28, stdev= 9.64, samples=3808
iops : min=158538, max=586025, avg=320320.80, stdev=2468.97, samples=3808
cpu : usr=0.35%, sys=11.50%, ctx=1584847, majf=0, minf=1160
IO depths : 1=0.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=100.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
issued rwts: total=0,19203309,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=64Run status group 0 (all jobs):
WRITE: bw=1250MiB/s (1311MB/s), 1250MiB/s-1250MiB/s (1311MB/s-1311MB/s), io=73.3GiB (78.7GB), run=60003-60003msec
The script to reproduce that:
#!/bin/bash
mkfs.btrfs -f /dev/nvme0n1
mount /dev/nvme0n1 /mnt/test
mkdir /mnt/test/nocow
chattr +C /mnt/test/nocow
fio /root/test.fio
# cat /root/test.fio [global] rw=randwrite ioengine=io_uring iodepth=64 size=1g direct=1 startdelay=20 force_async=4 ramp_time=5 runtime=60 group_reporting=1 numjobs=32 time_based disk_util=0 clat_percentiles=0 disable_lat=1 disable_clat=1 disable_slat=1 filename=/mnt/test/nocow/fiofile [test] name=test bs=4k stonewall
This was on a VM with 8 cores and 8GB of RAM, with a real NVMe exposed through PCI passthrough. The figures for XFS and ext4 in comparison are both about ~3GB/s.
--- fs/btrfs/super.c | 1 + 1 file changed, 1 insertion(+)
fs/btrfs/super.c +1 -0
@@ -1874,6 +1874,7 @@ static int btrfs_get_tree_super(struct fs_context *fc) fs_info->fs_devices = fs_devices;mutex_unlock (&uuid_mutex); + fc->sb_flags |=SB_NOSEC ; sb =sget_fc (fc, btrfs_fc_test_super, set_anon_super_fc);if (IS_ERR (sb)) {
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 380/1611 IB/mlx5: Dont take the rereg_mr fallback without a new translation
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Gunthorpe <[email protected]>
[ Upstream commit 55d339d200c908de83a408d023cfb7be779b0dd7 ]
Jumping to mlx5_ib_reg_user_mr() without IB_MR_REREG_TRANS set will use garbage values for start, length, and iova. Recovering the original mr parameters for ODP and DMABUF to properly recreate it is too hard in this flow, so just fail it.
--- drivers/infiniband/hw/mlx5/mr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/infiniband/hw/mlx5/mr.c +1 -1
@@ -1918,7 +1918,7 @@ struct ib_mr *mlx5_ib_rereg_user_mr(struct ib_mr *ib_mr, int flags, u64 start, }/* DM or ODP MR's don't have a normal umem so we can't re-use it */ if (!mr->umem ||is_odp_mr (mr) ||is_dmabuf_mr (mr)) - goto recreate; +return ERR_PTR (-EOPNOTSUPP );/* * Only one active MR can refer to a umem at one time, revoke
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 381/1611 IB/mlx5: Properly support implicit ODP rereg_mr
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Gunthorpe <[email protected]>
[ Upstream commit ee7a8335069150c3f1893a697ab30bbeca00d796 ]
Due to all the child mkeys in the implicit ODP configuration we cannot change anything in place for the parent mkey. Instead the whole thing needs to be rebuilt if any change is requested. If the user does not specify a translation then force the implicit values which will then fall through the logic into mlx5_ib_reg_user_mr() to allocate a completely new MR.
Since implicit children were also touching the mr->pd, this removes another case where the access was racy.
--- drivers/infiniband/hw/mlx5/mr.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
drivers/infiniband/hw/mlx5/mr.c +15 -0
@@ -1904,6 +1904,21 @@ struct ib_mr *mlx5_ib_rereg_user_mr(struct ib_mr *ib_mr, int flags, u64 start,if (!(flags &IB_MR_REREG_PD )) new_pd = ib_mr->pd; +if (mr->is_odp_implicit && !(flags &IB_MR_REREG_TRANS )) { +if (!(new_access_flags &IB_ACCESS_ON_DEMAND )) +return ERR_PTR (-EOPNOTSUPP ); + +/* +* Due to all the child mkeys we cannot actually change an +* implicit MR in place. If the user did not specify a new +* translation then force the fixed implicit MR values. +*/ + start =0 ; + iova =0 ; + length =U64_MAX ; + flags |=IB_MR_REREG_TRANS ; + } +if (!(flags &IB_MR_REREG_TRANS )) {struct ib_umem *umem;
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 382/1611 IB/mlx5: Remove unused mkc bits in mlx5r_umr_update_mr_page_shift()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Gunthorpe <[email protected]>
[ Upstream commit 4910483bd7ee2b40d0cc8ebd537fa33c95562029 ]
The HW only processes mkc fields selected by mkey_mask. pd, qpn and mkey_7_0 are never selected so they can be left as zero.
This removes a racy read of mr->pd.
--- drivers/infiniband/hw/mlx5/umr.c | 16 +++------------- drivers/infiniband/hw/mlx5/umr.h | 3 +-- 2 files changed, 4 insertions(+), 15 deletions(-)
drivers/infiniband/hw/mlx5/umr.c +3 -13
@@ -937,8 +937,7 @@ int mlx5r_umr_update_xlt(struct mlx5_ib_mr *mr, u64 idx, int npages,* pinned and the HW can switch from 4K to huge-page alignment). */ int mlx5r_umr_update_mr_page_shift (struct mlx5_ib_mr *mr, -unsigned int page_shift, -bool dd) +unsigned int page_shift) {struct mlx5_ib_dev *dev =mr_to_mdev (mr);struct mlx5r_umr_wqe wqe = {};
@@ -953,16 +952,8 @@ int mlx5r_umr_update_mr_page_shift(struct mlx5_ib_mr *mr,/* Fill mkey segment with the new page size, keep the rest unchanged */ MLX5_SET (mkc, &wqe.mkey_seg, log_page_size, page_shift); -if (dd) -MLX5_SET (mkc, &wqe.mkey_seg, pd, dev->ddr.pdn); -else -MLX5_SET (mkc, &wqe.mkey_seg, pd,to_mpd (mr->ibmr.pd)->pdn); -MLX5_SET64 (mkc, &wqe.mkey_seg, start_addr, mr->ibmr.iova);MLX5_SET64 (mkc, &wqe.mkey_seg, len, mr->ibmr.length); -MLX5_SET (mkc, &wqe.mkey_seg, qpn,0xffffff ); -MLX5_SET (mkc, &wqe.mkey_seg, mkey_7_0, -mlx5_mkey_variant (mr->mmkey.key)); err =mlx5r_umr_post_send_wait (dev, mr->mmkey.key, &wqe, false);if (!err)
@@ -1049,7 +1040,7 @@ static int _mlx5r_umr_zap_mkey(struct mlx5_ib_mr *mr,* non-present. */ if (*nblocks) { - err =mlx5r_umr_update_mr_page_shift (mr, max_page_shift, dd); + err =mlx5r_umr_update_mr_page_shift (mr, max_page_shift);if (err) { mr->page_shift = old_page_shift;return err;
@@ -1114,8 +1105,7 @@ int mlx5r_umr_dmabuf_update_pgsz(struct mlx5_ib_mr *mr, u32 xlt_flags, goto err; } - err =mlx5r_umr_update_mr_page_shift (mr, mr->page_shift, - mr->data_direct); + err =mlx5r_umr_update_mr_page_shift (mr, mr->page_shift);if (err) goto err; err = _mlx5r_dmabuf_umr_update_pas(mr, xlt_flags, 0, zapped_blocks,
drivers/infiniband/hw/mlx5/umr.h +1 -2
@@ -105,8 +105,7 @@ int mlx5r_umr_update_mr_pas(struct mlx5_ib_mr *mr, unsigned int flags);int mlx5r_umr_update_xlt (struct mlx5_ib_mr *mr,u64 idx,int npages,int page_shift,int flags);int mlx5r_umr_update_mr_page_shift (struct mlx5_ib_mr *mr, -unsigned int page_shift, -bool dd); +unsigned int page_shift);int mlx5r_umr_dmabuf_update_pgsz (struct mlx5_ib_mr *mr,u32 xlt_flags,unsigned int page_shift);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 383/1611 IB/mlx5: Pull the pdn out of the depths of the umr machinery
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Gunthorpe <[email protected]>
[ Upstream commit f387a9f06ea4f05e607a91b161963c0b19436652 ]
Instead of getting the pdn deep inside the umr code, pass it in from the top. to_mpd(mr->ibmr.pd)->pdn is not safe due to the rereg races, so all the call sites need some revision to obtain the pdn in a safe way.
Mark them with mlx5_mr_pdn(); following patches will go through and remove these.
Cases where the XLT flags are known and do not require the PDN can pass 0, such as for mlx5_ib_dmabuf_invalidate_cb().
Also extract the DMABUF data_direct special case from inside the UMR code and into the only place that needs it, pagefault_dmabuf_mr(). The actual mr was created directly without using the UMR flow. Ultimately this will be moved into mlx5_ib_init_dmabuf_mr().
Stable-dep-of: 8e0a02a989c1 ("IB/mlx5: Don't mangle the mr->pd inside the rereg callback")
--- drivers/infiniband/hw/mlx5/mlx5_ib.h | 9 ++++ drivers/infiniband/hw/mlx5/mr.c | 8 +-- drivers/infiniband/hw/mlx5/odp.c | 12 +++-- drivers/infiniband/hw/mlx5/umr.c | 75 ++++++++++++++-------------- drivers/infiniband/hw/mlx5/umr.h | 6 +-- 5 files changed, 64 insertions(+), 46 deletions(-)
drivers/infiniband/hw/mlx5/mlx5_ib.h +9 -0
@@ -331,6 +331,10 @@ struct mlx5_ib_flow_db {#define MLX5_IB_QPT_DCT IB_QPT_RESERVED4#define MLX5_IB_WR_UMR IB_WR_RESERVED1 +/* +* A valid pdn is required when flags include MLX5_IB_UPD_XLT_ENABLE, +* MLX5_IB_UPD_XLT_PD or MLX5_IB_UPD_XLT_ACCESS. +*/ #define MLX5_IB_UPD_XLT_ZAP BIT(0)#define MLX5_IB_UPD_XLT_ENABLE BIT(1)#define MLX5_IB_UPD_XLT_ATOMIC BIT(2)
@@ -1281,6 +1285,11 @@ static inline struct mlx5_ib_pd *to_mpd(struct ib_pd *ibpd) return container_of(ibpd, struct mlx5_ib_pd, ibpd); } +static inline u32 mlx5_mr_pdn (struct mlx5_ib_mr *mr) +{ +return to_mpd (mr->ibmr.pd)->pdn; +} +static inline struct mlx5_ib_srq *to_msrq (struct ib_srq *ibsrq) { return container_of(ibsrq, struct mlx5_ib_srq, ibsrq);
drivers/infiniband/hw/mlx5/mr.c +5 -3
@@ -1505,7 +1505,8 @@ static struct ib_mr *create_real_mr(struct ib_pd *pd, struct ib_umem *umem,* configured properly but left disabled. It is safe to go ahead * and configure it again via UMR while enabling it. */ - err =mlx5r_umr_update_mr_pas (mr,MLX5_IB_UPD_XLT_ENABLE ); + err =mlx5r_umr_update_mr_pas (mr,MLX5_IB_UPD_XLT_ENABLE , +to_mpd (pd)->pdn);if (err) {mlx5_ib_dereg_mr (&mr->ibmr,NULL );return ERR_PTR (err);
@@ -1614,7 +1615,8 @@ static void mlx5_ib_dmabuf_invalidate_cb(struct dma_buf_attachment *attach)if (!umem_dmabuf->sgt || !mr)return ; -mlx5r_umr_update_mr_pas (mr,MLX5_IB_UPD_XLT_ZAP ); +/* MLX5_IB_UPD_XLT_ZAP does not change the pdn */ +mlx5r_umr_update_mr_pas (mr,MLX5_IB_UPD_XLT_ZAP ,0 );ib_umem_dmabuf_unmap_pages (umem_dmabuf); }
@@ -1858,7 +1860,7 @@ static int umr_rereg_pas(struct mlx5_ib_mr *mr, struct ib_pd *pd, mr->ibmr.length = new_umem->length; mr->page_shift =order_base_2 (page_size); mr->umem = new_umem; - err =mlx5r_umr_update_mr_pas (mr, upd_flags); + err =mlx5r_umr_update_mr_pas (mr, upd_flags,mlx5_mr_pdn (mr));if (err) {/* * The MR is revoked at this point so there is no issue to free
drivers/infiniband/hw/mlx5/odp.c +9 -3
@@ -836,12 +836,14 @@ static int pagefault_dmabuf_mr(struct mlx5_ib_mr *mr, size_t bcnt, u32 *bytes_mapped, u32 flags) {struct ib_umem_dmabuf *umem_dmabuf =to_ib_umem_dmabuf (mr->umem); +struct mlx5_ib_dev *dev =mr_to_mdev (mr);int access_mode = mr->data_direct ?MLX5_MKC_ACCESS_MODE_KSM :MLX5_MKC_ACCESS_MODE_MTT ;unsigned int old_page_shift = mr->page_shift;unsigned int page_shift;unsigned long page_size;u32 xlt_flags =0 ; +u32 pdn =0 ;int err;if (flags &MLX5_PF_FLAGS_ENABLE )
@@ -860,8 +862,12 @@ static int pagefault_dmabuf_mr(struct mlx5_ib_mr *mr, size_t bcnt, err = -EINVAL ; }else { page_shift =order_base_2 (page_size); +if (mr->data_direct) + pdn = dev->ddr.pdn; +else + pdn =mlx5_mr_pdn (mr);if (page_shift != mr->page_shift && mr->dmabuf_faulted) { - err =mlx5r_umr_dmabuf_update_pgsz (mr, xlt_flags, + err =mlx5r_umr_dmabuf_update_pgsz (mr, xlt_flags, pdn, page_shift); }else { mr->page_shift = page_shift;
@@ -869,8 +875,8 @@ static int pagefault_dmabuf_mr(struct mlx5_ib_mr *mr, size_t bcnt, err =mlx5r_umr_update_data_direct_ksm_pas ( mr, xlt_flags); else - err =mlx5r_umr_update_mr_pas (mr, - xlt_flags); + err =mlx5r_umr_update_mr_pas (mr, xlt_flags, + pdn); } }dma_resv_unlock (umem_dmabuf->attach->dmabuf->resv);
drivers/infiniband/hw/mlx5/umr.c +38 -37
192 lines not on this page · raw message
drivers/infiniband/hw/mlx5/umr.h +3 -3
@@ -100,13 +100,13 @@ int mlx5r_umr_update_data_direct_ksm_pas_range(struct mlx5_ib_mr *mr, size_t nblocks);int mlx5r_umr_update_data_direct_ksm_pas (struct mlx5_ib_mr *mr,unsigned int flags);int mlx5r_umr_update_mr_pas_range (struct mlx5_ib_mr *mr,unsigned int flags, -size_t start_block,size_t nblocks); -int mlx5r_umr_update_mr_pas (struct mlx5_ib_mr *mr,unsigned int flags); +u32 pdn,size_t start_block,size_t nblocks); +int mlx5r_umr_update_mr_pas (struct mlx5_ib_mr *mr,unsigned int flags,u32 pdn);int mlx5r_umr_update_xlt (struct mlx5_ib_mr *mr,u64 idx,int npages,int page_shift,int flags);int mlx5r_umr_update_mr_page_shift (struct mlx5_ib_mr *mr,unsigned int page_shift); -int mlx5r_umr_dmabuf_update_pgsz (struct mlx5_ib_mr *mr,u32 xlt_flags, +int mlx5r_umr_dmabuf_update_pgsz (struct mlx5_ib_mr *mr,u32 xlt_flags,u32 pdn,unsigned int page_shift);#endif /* _MLX5_IB_UMR_H */
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 384/1611 IB/mlx5: Dont mangle the mr->pd inside the rereg callback
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Gunthorpe <[email protected]>
[ Upstream commit 8e0a02a989c156ce17f06a645d5f075277e06b95 ]
The rereg protocol expects the core code to change mr->pd and synchronize that change with the atomics and syncs. The driver should not touch it.
mlx5 needed to update it in umr_rereg_pas() because mlx5r_umr_update_mr_pas() required the updated mr->pd to build the UMR.
Simply switch mlx5r_umr_update_mr_pas() to use the pdn directly from the new pd and remove the mr->pd update.
--- drivers/infiniband/hw/mlx5/mr.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/infiniband/hw/mlx5/mr.c +2 -4
@@ -1847,10 +1847,8 @@ static int umr_rereg_pas(struct mlx5_ib_mr *mr, struct ib_pd *pd,if (err)return err; -if (flags &IB_MR_REREG_PD ) { - mr->ibmr.pd = pd; +if (flags &IB_MR_REREG_PD ) upd_flags |=MLX5_IB_UPD_XLT_PD ; - }if (flags &IB_MR_REREG_ACCESS ) { mr->access_flags = access_flags; upd_flags |=MLX5_IB_UPD_XLT_ACCESS ;
@@ -1860,7 +1858,7 @@ static int umr_rereg_pas(struct mlx5_ib_mr *mr, struct ib_pd *pd, mr->ibmr.length = new_umem->length; mr->page_shift =order_base_2 (page_size); mr->umem = new_umem; - err =mlx5r_umr_update_mr_pas (mr, upd_flags,mlx5_mr_pdn (mr)); + err =mlx5r_umr_update_mr_pas (mr, upd_flags,to_mpd (pd)->pdn);if (err) {/* * The MR is revoked at this point so there is no issue to free
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 385/1611 spi: ep93xx: fix double-free of zeropage on DMA setup failure
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felix Gu <[email protected]>
[ Upstream commit 7886054b06f762f62054957a8f6de0f14e6b7541 ]
If DMA setup fails after allocating the zeropage, the error path frees the page but leaves espi->zeropage dangling. A subsequent call to ep93xx_spi_release_dma() sees the non-NULL pointer and frees the page again.
Clear the pointer after freeing in the error path of ep93xx_spi_setup_dma().
--- drivers/spi/spi-ep93xx.c | 1 + 1 file changed, 1 insertion(+)
drivers/spi/spi-ep93xx.c +1 -0
@@ -600,6 +600,7 @@ static int ep93xx_spi_setup_dma(struct device *dev, struct ep93xx_spi *espi) espi->dma_rx =NULL ; fail_free_page:free_page ((unsigned long )espi->zeropage); + espi->zeropage =NULL ;return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 386/1611 ASoC: amd: acp-sdw-legacy: Bound DAI link iteration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aaron Ma <[email protected]>
[ Upstream commit d49ecdf327cc91062d2f80996a163cf65fda1e60 ]
create_sdw_dailinks() walks soc_dais until it finds an entry with initialised cleared, but soc_dais is allocated with exactly num_ends entries. If all entries are initialised, the loop reads past the end of the array.
This was reported by KASAN:
BUG: KASAN: slab-out-of-bounds in mc_probe+0x26b3/0x2774 [snd_acp_sdw_legacy_mach] Read of size 1
Pass the allocated entry count to create_sdw_dailinks() and stop before reading past the array.
--- sound/soc/amd/acp/acp-sdw-legacy-mach.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
sound/soc/amd/acp/acp-sdw-legacy-mach.c +4 -3
@@ -287,13 +287,14 @@ static int create_sdw_dailink(struct snd_soc_card *card,static int create_sdw_dailinks (struct snd_soc_card *card,struct snd_soc_dai_link **dai_links,int *be_id, -struct asoc_sdw_dailink *soc_dais, +struct asoc_sdw_dailink *soc_dais,int num_dais,struct snd_soc_codec_conf **codec_conf) {struct device *dev = card->dev;struct asoc_sdw_mc_private *ctx =snd_soc_card_get_drvdata (card);struct amd_mc_ctx *amd_ctx = (struct amd_mc_ctx *)ctx->private;struct snd_soc_dai_link_component *sdw_platform_component; +int i;int ret; sdw_platform_component = devm_kzalloc(dev, sizeof(struct snd_soc_dai_link_component),
@@ -313,7 +314,7 @@ static int create_sdw_dailinks(struct snd_soc_card *card, }/* generate DAI links by each sdw link */ -while (soc_dais->initialised) { +for (i =0 ; i < num_dais && soc_dais->initialised; i++) {int current_be_id =0 ; ret = create_sdw_dailink(card, soc_dais, dai_links,
@@ -438,7 +439,7 @@ static int soc_card_dai_links_create(struct snd_soc_card *card)/* SDW */ if (sdw_be_num) { ret =create_sdw_dailinks (card, &dai_links, &be_id, - soc_dais, &codec_conf); + soc_dais, num_ends, &codec_conf);if (ret)return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 387/1611 ASoC: amd: acp-sdw-sof: Bound DAI link iteration
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aaron Ma <[email protected]>
[ Upstream commit 4d992e63f52d58f52b724606c60ae7b37a1c582f ]
create_sdw_dailinks() walks sof_dais until it finds an entry with initialised cleared, but sof_dais is allocated with exactly num_ends entries. If all entries are initialised, the loop reads past the end of the array.
Pass the allocated entry count to create_sdw_dailinks() and stop before reading past the array.
--- sound/soc/amd/acp/acp-sdw-sof-mach.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
sound/soc/amd/acp/acp-sdw-sof-mach.c +4 -3
@@ -220,13 +220,14 @@ static int create_sdw_dailink(struct snd_soc_card *card,static int create_sdw_dailinks (struct snd_soc_card *card,struct snd_soc_dai_link **dai_links,int *be_id, -struct asoc_sdw_dailink *sof_dais, +struct asoc_sdw_dailink *sof_dais,int num_dais,struct snd_soc_codec_conf **codec_conf) { +int i;int ret;/* generate DAI links by each sdw link */ -while (sof_dais->initialised) { +for (i =0 ; i < num_dais && sof_dais->initialised; i++) {int current_be_id =0 ; ret = create_sdw_dailink(card, sof_dais, dai_links,
@@ -326,7 +327,7 @@ static int sof_card_dai_links_create(struct snd_soc_card *card)/* SDW */ if (sdw_be_num) { ret =create_sdw_dailinks (card, &dai_links, &be_id, - sof_dais, &codec_conf); + sof_dais, num_ends, &codec_conf);if (ret)return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 388/1611 firmware_loader: Fix recursive lock in device_cache_fw_images()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Vyukov <[email protected]>
[ Upstream commit d3ec78f8f8d48a04a9fac38d47275c34645e5103 ]
A recursive locking deadlock can occur in the firmware loader's power management notification handler.
During system suspend or hibernation preparation, fw_pm_notify() calls device_cache_fw_images(). This function acquires fw_lock to set the firmware cache state to FW_LOADER_START_CACHE and then iterates over all devices using dpm_for_each_dev() while still holding the lock.
For each device, dev_cache_fw_image() schedules asynchronous work to cache the firmware. If memory allocation for the async work entry fails (e.g., in out-of-memory conditions), async_schedule_node_domain() falls back to executing the work function synchronously in the current thread.
The synchronous execution path (__async_dev_cache_fw_image() -> cache_firmware() -> request_firmware() -> assign_fw()) attempts to acquire fw_lock again. Since the current thread already holds fw_lock, this results in a recursive locking deadlock.
Fix this by releasing fw_lock immediately after updating the cache state and before calling dpm_for_each_dev(). The lock is only needed to protect the state update. Concurrent firmware requests will correctly see the FW_LOADER_START_CACHE state and use the piggyback mechanism, which is independently protected by its own fwc->name_lock.
--- drivers/base/firmware_loader/main.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/base/firmware_loader/main.c +2 -1
@@ -1512,9 +1512,10 @@ static void device_cache_fw_images(void)mutex_lock (&fw_lock); fwc->state =FW_LOADER_START_CACHE ; -dpm_for_each_dev (NULL , dev_cache_fw_image);mutex_unlock (&fw_lock); +dpm_for_each_dev (NULL , dev_cache_fw_image); +/* wait for completion of caching firmware for all devices */ async_synchronize_full_domain (&fw_cache_domain);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 389/1611 configfs: fix lockless traversals of ->s_children
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
[ Upstream commit 9b9e8bb81c41fd27e7b57a1c936fde140548535f ]
Having the parent directory locked protects entries from removal by another thread, but it does *not* protect cursors from being moved around by lseek() - or freed, for that matter.
--- fs/configfs/dir.c | 54 +++++++++++++++++++++++++++++++++++------------ 1 file changed, 41 insertions(+), 13 deletions(-)
fs/configfs/dir.c +41 -13
@@ -235,15 +235,16 @@ static int configfs_dirent_exists(struct dentry *dentry)const unsigned char *new = dentry->d_name.name;struct configfs_dirent *sd; +spin_lock (&configfs_dirent_lock);list_for_each_entry (sd, &parent_sd->s_children, s_sibling) {if (sd->s_element) { -const unsigned char *existing =configfs_get_name (sd); -if (strcmp (existing, new)) -continue ; -else +if (strcmp (configfs_get_name (sd), new) ==0 ) { +spin_unlock (&configfs_dirent_lock);return -EEXIST ; + } } } +spin_unlock (&configfs_dirent_lock);return 0 ; }
@@ -569,11 +570,28 @@ static void configfs_detach_rollback(struct dentry *dentry)configfs_detach_rollback (sd->s_dentry); } +/* +* Find the next non-cursor. configfs_dirent_lock held by caller. +*/ +static struct configfs_dirent *next_dirent (struct configfs_dirent *parent, +struct configfs_dirent *last) +{ +struct configfs_dirent *s; + + s =list_prepare_entry (last, &parent->s_children, s_sibling); + +list_for_each_entry_continue (s, &parent->s_children, s_sibling) { +if (s->s_element) +return s; + } +return NULL ; +} +static void detach_attrs (struct config_item * item) {struct dentry * dentry =dget (item->ci_dentry); -struct configfs_dirent * parent_sd; -struct configfs_dirent * sd, * tmp; +struct configfs_dirent *parent_sd; +struct configfs_dirent *sd, *next;if (!dentry)return ;
@@ -582,15 +600,19 @@ static void detach_attrs(struct config_item * item) dentry->d_name.name); parent_sd = dentry->d_fsdata; -list_for_each_entry_safe (sd, tmp, &parent_sd->s_children, s_sibling) { -if (!sd->s_element || !(sd->s_type &CONFIGFS_NOT_PINNED )) + +spin_lock (&configfs_dirent_lock); +for (sd =next_dirent (parent_sd,NULL ); sd; sd = next) { + next =next_dirent (parent_sd, sd); +if (!(sd->s_type &CONFIGFS_NOT_PINNED ))continue ; -spin_lock (&configfs_dirent_lock);list_del_init (&sd->s_sibling);spin_unlock (&configfs_dirent_lock);configfs_drop_dentry (sd, dentry);configfs_put (sd); +spin_lock (&configfs_dirent_lock); } +spin_unlock (&configfs_dirent_lock);/** * Drop reference from dget() on entrance.
@@ -649,18 +671,20 @@ static void detach_groups(struct config_group *group)struct dentry * dentry =dget (group->cg_item.ci_dentry);struct dentry *child;struct configfs_dirent *parent_sd; -struct configfs_dirent *sd, *tmp; +struct configfs_dirent *sd, *next;if (!dentry)return ; parent_sd = dentry->d_fsdata; -list_for_each_entry_safe (sd, tmp, &parent_sd->s_children, s_sibling) { -if (!sd->s_element || - !(sd->s_type &CONFIGFS_USET_DEFAULT )) +spin_lock (&configfs_dirent_lock); +for (sd =next_dirent (parent_sd,NULL ); sd; sd = next) { + next =next_dirent (parent_sd, sd); +if (!(sd->s_type &CONFIGFS_USET_DEFAULT ))continue ; child = sd->s_dentry; +spin_unlock (&configfs_dirent_lock);inode_lock (d_inode (child));
@@ -672,7 +696,9 @@ static void detach_groups(struct config_group *group)d_delete (child);dput (child); +spin_lock (&configfs_dirent_lock); } +spin_unlock (&configfs_dirent_lock);/** * Drop reference from dget() on entrance.
@@ -1124,6 +1150,7 @@ configfs_find_subsys_dentry(struct configfs_dirent *root_sd,struct configfs_dirent *p;struct configfs_dirent *ret =NULL ; +spin_lock (&configfs_dirent_lock);list_for_each_entry (p, &root_sd->s_children, s_sibling) {if (p->s_type &CONFIGFS_DIR && p->s_element == subsys_item) {
@@ -1131,6 +1158,7 @@ configfs_find_subsys_dentry(struct configfs_dirent *root_sd,break ; } } +spin_unlock (&configfs_dirent_lock);return ret; }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 390/1611 watchdog: unregister PM notifier on watchdog unregister
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuho Choi <[email protected]>
[ Upstream commit a298c7302ee9584a7a1ac1e8acbede8d98ab51a4 ]
watchdog_register_device() registers wdd->pm_nb when WDOG_NO_PING_ON_SUSPEND is set, but watchdog_unregister_device() does not remove it. This leaves an embedded notifier block on the PM notifier chain after the watchdog device has been unregistered.
A later suspend/resume notification can then call watchdog_pm_notifier() with a stale watchdog_device pointer, or at minimum after wdd->wd_data has been cleared by watchdog_dev_unregister().
Unregister the PM notifier before tearing down the watchdog device.
--- drivers/watchdog/watchdog_core.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/watchdog/watchdog_core.c +3 -0
@@ -390,6 +390,9 @@ static void __watchdog_unregister_device(struct watchdog_device *wdd)if (test_bit (WDOG_STOP_ON_REBOOT , &wdd->status))unregister_reboot_notifier (&wdd->reboot_nb); +if (test_bit (WDOG_NO_PING_ON_SUSPEND , &wdd->status)) +unregister_pm_notifier (&wdd->pm_nb); +watchdog_dev_unregister (wdd);ida_free (&watchdog_ida, wdd->id); }
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 391/1611 pinctrl: qcom: Fix resolving register base address from device node
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sneh Mankad <[email protected]>
[ Upstream commit 4e31ab47997540d0ff4c9de801741bed03c1ab3f ]
Commit 56ffb63749f4 ("pinctrl: qcom: add multi TLMM region option parameter") added reg-names property based register reading. However multiple platforms are not using the reg-names as they have only single TLMM register region.
Commit tried to handle this using the default_region module parameter, however this condition is unreachable as the error return precedes it by just checking if reg-names property exists or not, making it impossible to use tlmm-test for the SoCs (x1e80100) which don't have reg-names property in TLMM device.
Fix this by moving the default_region check at the start of the tlmm_reg_base().
--- drivers/pinctrl/qcom/tlmm-test.c | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-)
drivers/pinctrl/qcom/tlmm-test.c +9 -10
@@ -581,6 +581,9 @@ static int tlmm_reg_base(struct device_node *tlmm, struct resource *res)int ret;int i; +if (!strcmp (tlmm_reg_name,"default_region" )) +return of_address_to_resource (tlmm,0 , res); + count =of_property_count_strings (tlmm,"reg-names" );if (count <=0 ) {pr_err ("failed to find tlmm reg name\n" );
@@ -597,18 +600,14 @@ static int tlmm_reg_base(struct device_node *tlmm, struct resource *res)return -EINVAL ; } -if (!strcmp (tlmm_reg_name,"default_region" )) { - ret =of_address_to_resource (tlmm,0 , res); - }else { -for (i =0 ; i < count; i++) { -if (!strcmp (reg_names[i], tlmm_reg_name)) { - ret =of_address_to_resource (tlmm, i, res); -break ; - } +for (i =0 ; i < count; i++) { +if (!strcmp (reg_names[i], tlmm_reg_name)) { + ret =of_address_to_resource (tlmm, i, res); +break ; } -if (i == count) - ret = -EINVAL ; } +if (i == count) + ret = -EINVAL ;kfree (reg_names);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 392/1611 scsi: target: Fix hexadecimal CHAP_I handling
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Disseldorp <[email protected]>
[ Upstream commit 7e161211f1dd5288b4ea802b30e70ef919ebc3da ]
A mutual CHAP handshake requires target processing of an initiator-sent CHAP_I identifier. The RFC 3720 specification states:
11.1.4. Challenge Handshake Authentication Protocol (CHAP)
...
CHAP_A=<A> CHAP_I=<I> CHAP_C=<C>
...
Where N, (A,A1,A2), I, C, and R are (correspondingly) the Name, Algorithm, Identifier, Challenge, and Response as defined in [RFC1994], N is a text string, A,A1,A2, and I are numbers
CHAP_I parsing currently calls extract_param(), which returns the @identifier string (stripped of any 0b/0B or 0x/0X prefix) and a @type which indicates DECIMAL, HEX, or BASE64 encoding (based on any stripped prefix).
Any HEX encoded CHAP_I string is further processed via:
ret = kstrtoul(&identifier[2], 0, &id);
This is incorrect for two reasons:
* The @identifier string has already been stripped of the 0x/0X prefix, so skipping the first two bytes omits part of the number.
* The kstrtoul() call specifies a base of 0, which will see &identifier[2] parsed as a decimal, unless a '0x' or (octal) '0' is erroneously present at that offset.
Fix this by passing the (zero-offset) identifier string to kstrtoul() along with a base=16 parameter. Also add an explicit error handler for BASE64 encoding.
Hex-encoded CHAP_I handling can be testing using the libiscsi EncodedI test linked below.
--- drivers/target/iscsi/iscsi_target_auth.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/target/iscsi/iscsi_target_auth.c +4 -2
@@ -437,9 +437,11 @@ static int chap_server_compute_hash( }if (type ==HEX ) - ret =kstrtoul (&identifier[2 ],0 , &id); + ret =kstrtoul (identifier,16 , &id); +else if (type ==DECIMAL ) + ret =kstrtoul (identifier,10 , &id);else - ret =kstrtoul (identifier,0 , &id); + ret = -EINVAL ;if (ret <0 ) {pr_err ("kstrtoul() failed for CHAP identifier: %d\n" , ret);
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 393/1611 scsi: target: Remove tcm_loop target reset handling
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mike Christie <[email protected]>
[ Upstream commit 7c08d430835a90414cd962e3a9602e5b002dee3b ]
tcm_loop_target_reset is supposed to handle all the LUNs on a target but it's only doing a TMR_LUN_RESET so only that one LUN is handled. This will cause us to return early while IOs to other LUNs are still hung in lower layers. This just removes the target reset handler for the driver because LIO doesn't support target resets and for the common case where this is run from the scsi-ml error hamdler we have already tried an abort and lun reset so waiting again is most likely useless.
--- drivers/target/loopback/tcm_loop.c | 64 ------------------------------ 1 file changed, 64 deletions(-)
drivers/target/loopback/tcm_loop.c +0 -64
@@ -269,69 +269,6 @@ static int tcm_loop_device_reset(struct scsi_cmnd *sc)return (ret ==TMR_FUNCTION_COMPLETE ) ?SUCCESS :FAILED ; } -static bool tcm_loop_flush_work_iter (struct request *rq,void *data) -{ -struct scsi_cmnd *sc =blk_mq_rq_to_pdu (rq); -struct tcm_loop_cmd *tl_cmd =scsi_cmd_priv (sc); -struct se_cmd *se_cmd = &tl_cmd->tl_se_cmd; - -flush_work (&se_cmd->work); -return true; -} - -static int tcm_loop_target_reset (struct scsi_cmnd *sc) -{ -struct tcm_loop_hba *tl_hba; -struct tcm_loop_tpg *tl_tpg; -struct Scsi_Host *sh = sc->device->host; -int ret; - -/* -* Locate the tcm_loop_hba_t pointer -*/ - tl_hba = *(struct tcm_loop_hba **)shost_priv (sh); -if (!tl_hba) { -pr_err ("Unable to perform device reset without active I_T Nexus\n" ); -return FAILED ; - } -/* -* Locate the tl_tpg pointer from TargetID in sc->device->id -*/ - tl_tpg = &tl_hba->tl_hba_tpgs[sc->device->id]; -if (!tl_tpg) -return FAILED ; - -/* -* Issue a LUN_RESET to drain all commands that the target core -* knows about. This handles commands not yet marked CMD_T_COMPLETE. -*/ - ret =tcm_loop_issue_tmr (tl_tpg, sc->device->lun,0 ,TMR_LUN_RESET ); -if (ret !=TMR_FUNCTION_COMPLETE ) -return FAILED ; - -/* -* Flush any deferred target core completion work that may still be -* queued. Commands that already had CMD_T_COMPLETE set before the TMR -* are skipped by the TMR drain, but their async completion work -* (transport_lun_remove_cmd → percpu_ref_put, release_cmd → scsi_done) -* may still be pending in target_completion_wq. -* -* The SCSI EH will reuse in-flight scsi_cmnd structures for recovery -* commands (e.g. TUR) immediately after this handler returns SUCCESS — -* if deferred work is still pending, the memset in queuecommand would -* zero the se_cmd while the work accesses it, leaking the LUN -* percpu_ref and hanging configfs unlink forever. -* -* Use blk_mq_tagset_busy_iter() to find all started requests and -* flush_work() on each — the same pattern used by mpi3mr, scsi_debug, -* and other SCSI drivers to drain outstanding commands during reset. -*/ -blk_mq_tagset_busy_iter (&sh->tag_set, tcm_loop_flush_work_iter,NULL ); - - tl_tpg->tl_transport_status =TCM_TRANSPORT_ONLINE ; -return SUCCESS ; -} -static const struct scsi_host_template tcm_loop_driver_template = { .show_info = tcm_loop_show_info, .proc_name ="tcm_loopback" ,
@@ -340,7 +277,6 @@ static const struct scsi_host_template tcm_loop_driver_template = { .change_queue_depth = scsi_change_queue_depth, .eh_abort_handler = tcm_loop_abort_task, .eh_device_reset_handler = tcm_loop_device_reset, - .eh_target_reset_handler = tcm_loop_target_reset, .this_id = -1, .sg_tablesize = 256, .max_sectors = 0xFFFF,
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 394/1611 pinctrl: mediatek: mt8516: Fix Schmitt trigger register offset of pins 34-39
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Leonardo Scorcia <[email protected]>
[ Upstream commit 1c3044cab23a056ea28da47da1cdd667a39df0b8 ]
The correct Schmitt trigger register offset for pins 34-39 is 0xA00.
--- drivers/pinctrl/mediatek/pinctrl-mt8516.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/mediatek/pinctrl-mt8516.c +1 -1
@@ -244,7 +244,7 @@ static const struct mtk_pin_ies_smt_set mt8516_smt_set[] = {MTK_PIN_IES_SMT_SPEC (24 ,25 ,0xA00 ,12 ),MTK_PIN_IES_SMT_SPEC (26 ,30 ,0xA00 ,0 ),MTK_PIN_IES_SMT_SPEC (31 ,33 ,0xA00 ,1 ), -MTK_PIN_IES_SMT_SPEC (34 ,39 ,0xA900 ,2 ), +MTK_PIN_IES_SMT_SPEC (34 ,39 ,0xA00 ,2 ),MTK_PIN_IES_SMT_SPEC (40 ,40 ,0xA10 ,11 ),MTK_PIN_IES_SMT_SPEC (41 ,43 ,0xA00 ,10 ), MTK_PIN_IES_SMT_SPEC(44, 47, 0xA00, 11),
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 395/1611 pinctrl: mediatek: mt8167: Fix Schmitt trigger register offset of pins 34-39
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Leonardo Scorcia <[email protected]>
[ Upstream commit 439bc91d20188901dac698bed4921caac76d9074 ]
The correct Schmitt trigger register offset for pins 34-39 is 0xA00. Value was verified with SoC data sheet.
--- drivers/pinctrl/mediatek/pinctrl-mt8167.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/mediatek/pinctrl-mt8167.c +1 -1
@@ -244,7 +244,7 @@ static const struct mtk_pin_ies_smt_set mt8167_smt_set[] = {MTK_PIN_IES_SMT_SPEC (24 ,25 ,0xA00 ,12 ),MTK_PIN_IES_SMT_SPEC (26 ,30 ,0xA00 ,0 ),MTK_PIN_IES_SMT_SPEC (31 ,33 ,0xA00 ,1 ), -MTK_PIN_IES_SMT_SPEC (34 ,39 ,0xA900 ,2 ), +MTK_PIN_IES_SMT_SPEC (34 ,39 ,0xA00 ,2 ),MTK_PIN_IES_SMT_SPEC (40 ,40 ,0xA10 ,11 ),MTK_PIN_IES_SMT_SPEC (41 ,43 ,0xA00 ,10 ), MTK_PIN_IES_SMT_SPEC(44, 47, 0xA00, 11),
Signature · 1 line
2.53.0
Greg Kroah-Hartman
maintainerPATCH 396/1611 vmalloc: fix NULL pointer dereference in is_vm_area_hugepages()
In reply to Greg Kroah-Hartman6.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hui Zhu <[email protected]>
[ Upstream commit c55dd3b46c1208d6d2ea737a8aefef4aa4c70cb8 ]
find_vm_area() can return NULL if the given address is not a valid vmalloc area. Check the return value before dereferencing it to avoid a kernel crash.
--- include/linux/vmalloc.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
include/linux/vmalloc.h +3 -1
@@ -261,7 +261,9 @@ static inline bool is_vm_area_hugepages(const void *addr)* allocated in the vmalloc layer. */ #ifdef CONFIG_HAVE_ARCH_HUGE_VMALLOC -return find_vm_area (addr)->page_order >0 ; +struct vm_struct *area =find_vm_area (addr); + +return area && area->page_order >0 ;#else return false;#endif
Signature · 1 line
2.53.0