From: Sasha Levin Date: Thu, 9 Jun 2022 13:40:32 +0000 (-0400) Subject: Fixes for 5.15 X-Git-Tag: v4.9.318~118 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=84a8102f29e7a78281b3cadc127099728261bdbc;p=thirdparty%2Fkernel%2Fstable-queue.git Fixes for 5.15 Signed-off-by: Sasha Levin --- diff --git a/queue-5.15/afs-fix-infinite-loop-found-by-xfstest-generic-676.patch b/queue-5.15/afs-fix-infinite-loop-found-by-xfstest-generic-676.patch new file mode 100644 index 00000000000..3732dea236a --- /dev/null +++ b/queue-5.15/afs-fix-infinite-loop-found-by-xfstest-generic-676.patch @@ -0,0 +1,65 @@ +From 26dd422410c387f184c464c8e110472834d9e9f9 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 31 May 2022 09:30:40 +0100 +Subject: afs: Fix infinite loop found by xfstest generic/676 + +From: David Howells + +[ Upstream commit 17eabd42560f4636648ad65ba5b20228071e2363 ] + +In AFS, a directory is handled as a file that the client downloads and +parses locally for the purposes of performing lookup and getdents +operations. The in-kernel afs filesystem has a number of functions that +do this. + +A directory file is arranged as a series of 2K blocks divided into +32-byte slots, where a directory entry occupies one or more slots, plus +each block starts with one or more metadata blocks. + +When parsing a block, if the last slots are occupied by a dirent that +occupies more than a single slot and the file position points at a slot +that's not the initial one, the logic in afs_dir_iterate_block() that +skips over it won't advance the file pointer to the end of it. This +will cause an infinite loop in getdents() as it will keep retrying that +block and failing to advance beyond the final entry. + +Fix this by advancing the file pointer if the next entry will be beyond +it when we skip a block. + +This was found by the generic/676 xfstest but can also be triggered with +something like: + + ~/xfstests-dev/src/t_readdir_3 /xfstest.test/z 4000 1 + +Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") +Signed-off-by: David Howells +Reviewed-by: Marc Dionne +Tested-by: Marc Dionne +cc: linux-afs@lists.infradead.org +Link: http://lore.kernel.org/r/165391973497.110268.2939296942213894166.stgit@warthog.procyon.org.uk/ +Signed-off-by: Linus Torvalds +Signed-off-by: Sasha Levin +--- + fs/afs/dir.c | 5 ++++- + 1 file changed, 4 insertions(+), 1 deletion(-) + +diff --git a/fs/afs/dir.c b/fs/afs/dir.c +index 4579bbda4634..948a808a964d 100644 +--- a/fs/afs/dir.c ++++ b/fs/afs/dir.c +@@ -486,8 +486,11 @@ static int afs_dir_iterate_block(struct afs_vnode *dvnode, + } + + /* skip if starts before the current position */ +- if (offset < curr) ++ if (offset < curr) { ++ if (next > curr) ++ ctx->pos = blkoff + next * sizeof(union afs_xdr_dirent); + continue; ++ } + + /* found the next entry */ + if (!dir_emit(ctx, dire->u.name, nlen, +-- +2.35.1 + diff --git a/queue-5.15/arm-dts-aspeed-ast2600-evb-enable-rx-delay-for-mac0-.patch b/queue-5.15/arm-dts-aspeed-ast2600-evb-enable-rx-delay-for-mac0-.patch new file mode 100644 index 00000000000..1f45e8a93f7 --- /dev/null +++ b/queue-5.15/arm-dts-aspeed-ast2600-evb-enable-rx-delay-for-mac0-.patch @@ -0,0 +1,51 @@ +From 5b1e19e29c58ce7d5e2d2892a3c2d261269203aa Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 1 Apr 2022 06:59:06 +0000 +Subject: ARM: dts: aspeed: ast2600-evb: Enable RX delay for MAC0/MAC1 + +From: Howard Chiu + +[ Upstream commit 4d338ee40ba89e508c5d3e1b4af956af7cb5e12e ] + +Since mac0/1 and mac2/3 are physically located on different die, +they have different properties by nature, which is mac0/1 has smaller delay step. + +The property 'phy-mode' on ast2600 mac0 and mac1 is recommended to set to 'rgmii-rxid' +which enables the RX interface delay from the PHY chip. +Refer page 45 of SDK User Guide v08.00 +https://github.com/AspeedTech-BMC/openbmc/releases/download/v08.00/SDK_User_Guide_v08.00.pdf + +Fixes: 2ca5646b5c2f ("ARM: dts: aspeed: Add AST2600 and EVB") +Signed-off-by: Howard Chiu +Link: https://lore.kernel.org/r/SG2PR06MB23152A548AAE81140B57DD69E6E09@SG2PR06MB2315.apcprd06.prod.outlook.com +Signed-off-by: Joel Stanley +Signed-off-by: Sasha Levin +--- + arch/arm/boot/dts/aspeed-ast2600-evb.dts | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/arch/arm/boot/dts/aspeed-ast2600-evb.dts b/arch/arm/boot/dts/aspeed-ast2600-evb.dts +index b7eb552640cb..788448cdd6b3 100644 +--- a/arch/arm/boot/dts/aspeed-ast2600-evb.dts ++++ b/arch/arm/boot/dts/aspeed-ast2600-evb.dts +@@ -103,7 +103,7 @@ + &mac0 { + status = "okay"; + +- phy-mode = "rgmii"; ++ phy-mode = "rgmii-rxid"; + phy-handle = <ðphy0>; + + pinctrl-names = "default"; +@@ -114,7 +114,7 @@ + &mac1 { + status = "okay"; + +- phy-mode = "rgmii"; ++ phy-mode = "rgmii-rxid"; + phy-handle = <ðphy1>; + + pinctrl-names = "default"; +-- +2.35.1 + diff --git a/queue-5.15/arm64-initialize-jump-labels-before-setup_machine_fd.patch b/queue-5.15/arm64-initialize-jump-labels-before-setup_machine_fd.patch new file mode 100644 index 00000000000..76c0ce6741a --- /dev/null +++ b/queue-5.15/arm64-initialize-jump-labels-before-setup_machine_fd.patch @@ -0,0 +1,93 @@ +From 801341d73c47ad13e2b091d2befc813efd2f4e15 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 1 Jun 2022 19:21:09 -0700 +Subject: arm64: Initialize jump labels before setup_machine_fdt() + +From: Stephen Boyd + +[ Upstream commit 73e2d827a501d48dceeb5b9b267a4cd283d6b1ae ] + +A static key warning splat appears during early boot on arm64 systems +that credit randomness from devicetrees that contain an "rng-seed" +property. This is because setup_machine_fdt() is called before +jump_label_init() during setup_arch(). Let's swap the order of these two +calls so that jump labels are initialized before the devicetree is +unflattened and the rng seed is credited. + + static_key_enable_cpuslocked(): static key '0xffffffe51c6fcfc0' used before call to jump_label_init() + WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xb0/0xb8 + Modules linked in: + CPU: 0 PID: 0 Comm: swapper Not tainted 5.18.0+ #224 44b43e377bfc84bc99bb5ab885ff694984ee09ff + pstate: 600001c9 (nZCv dAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) + pc : static_key_enable_cpuslocked+0xb0/0xb8 + lr : static_key_enable_cpuslocked+0xb0/0xb8 + sp : ffffffe51c393cf0 + x29: ffffffe51c393cf0 x28: 000000008185054c x27: 00000000f1042f10 + x26: 0000000000000000 x25: 00000000f10302b2 x24: 0000002513200000 + x23: 0000002513200000 x22: ffffffe51c1c9000 x21: fffffffdfdc00000 + x20: ffffffe51c2f0831 x19: ffffffe51c6fcfc0 x18: 00000000ffff1020 + x17: 00000000e1e2ac90 x16: 00000000000000e0 x15: ffffffe51b710708 + x14: 0000000000000066 x13: 0000000000000018 x12: 0000000000000000 + x11: 0000000000000000 x10: 00000000ffffffff x9 : 0000000000000000 + x8 : 0000000000000000 x7 : 61632065726f6665 x6 : 6220646573752027 + x5 : ffffffe51c641d25 x4 : ffffffe51c13142c x3 : ffff0a00ffffff05 + x2 : 40000000ffffe003 x1 : 00000000000001c0 x0 : 0000000000000065 + Call trace: + static_key_enable_cpuslocked+0xb0/0xb8 + static_key_enable+0x2c/0x40 + crng_set_ready+0x24/0x30 + execute_in_process_context+0x80/0x90 + _credit_init_bits+0x100/0x154 + add_bootloader_randomness+0x64/0x78 + early_init_dt_scan_chosen+0x140/0x184 + early_init_dt_scan_nodes+0x28/0x4c + early_init_dt_scan+0x40/0x44 + setup_machine_fdt+0x7c/0x120 + setup_arch+0x74/0x1d8 + start_kernel+0x84/0x44c + __primary_switched+0xc0/0xc8 + ---[ end trace 0000000000000000 ]--- + random: crng init done + Machine model: Google Lazor (rev1 - 2) with LTE + +Cc: Hsin-Yi Wang +Cc: Douglas Anderson +Cc: Ard Biesheuvel +Cc: Steven Rostedt +Cc: Jason A. Donenfeld +Cc: Dominik Brodowski +Fixes: f5bda35fba61 ("random: use static branch for crng_ready()") +Signed-off-by: Stephen Boyd +Reviewed-by: Jason A. Donenfeld +Link: https://lore.kernel.org/r/20220602022109.780348-1-swboyd@chromium.org +Signed-off-by: Catalin Marinas +Signed-off-by: Sasha Levin +--- + arch/arm64/kernel/setup.c | 7 ++++--- + 1 file changed, 4 insertions(+), 3 deletions(-) + +diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c +index be5f85b0a24d..644b7cd38e3e 100644 +--- a/arch/arm64/kernel/setup.c ++++ b/arch/arm64/kernel/setup.c +@@ -307,13 +307,14 @@ void __init __no_sanitize_address setup_arch(char **cmdline_p) + early_fixmap_init(); + early_ioremap_init(); + +- setup_machine_fdt(__fdt_pointer); +- + /* + * Initialise the static keys early as they may be enabled by the +- * cpufeature code and early parameters. ++ * cpufeature code, early parameters, and DT setup. + */ + jump_label_init(); ++ ++ setup_machine_fdt(__fdt_pointer); ++ + parse_early_param(); + + /* +-- +2.35.1 + diff --git a/queue-5.15/asoc-fsl_sai-fix-fsl_sai_xdr-xfr-definition.patch b/queue-5.15/asoc-fsl_sai-fix-fsl_sai_xdr-xfr-definition.patch new file mode 100644 index 00000000000..1b8d71611b9 --- /dev/null +++ b/queue-5.15/asoc-fsl_sai-fix-fsl_sai_xdr-xfr-definition.patch @@ -0,0 +1,40 @@ +From 871662e34401217a376f5f7b6298f5fa33d698da Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 23 May 2022 13:44:21 +0800 +Subject: ASoC: fsl_sai: Fix FSL_SAI_xDR/xFR definition + +From: Shengjiu Wang + +[ Upstream commit e4dd748dc87cf431af7b3954963be0d9f6150217 ] + +There are multiple xDR and xFR registers, the index is +from 0 to 7. FSL_SAI_xDR and FSL_SAI_xFR is abandoned, +replace them with FSL_SAI_xDR0 and FSL_SAI_xFR0. + +Fixes: 4f7a0728b530 ("ASoC: fsl_sai: Add support for SAI new version") +Signed-off-by: Shengjiu Wang +Link: https://lore.kernel.org/r/1653284661-18964-1-git-send-email-shengjiu.wang@nxp.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + sound/soc/fsl/fsl_sai.h | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/sound/soc/fsl/fsl_sai.h b/sound/soc/fsl/fsl_sai.h +index bc60030967dd..f471467dfb3e 100644 +--- a/sound/soc/fsl/fsl_sai.h ++++ b/sound/soc/fsl/fsl_sai.h +@@ -80,8 +80,8 @@ + #define FSL_SAI_xCR3(tx, ofs) (tx ? FSL_SAI_TCR3(ofs) : FSL_SAI_RCR3(ofs)) + #define FSL_SAI_xCR4(tx, ofs) (tx ? FSL_SAI_TCR4(ofs) : FSL_SAI_RCR4(ofs)) + #define FSL_SAI_xCR5(tx, ofs) (tx ? FSL_SAI_TCR5(ofs) : FSL_SAI_RCR5(ofs)) +-#define FSL_SAI_xDR(tx, ofs) (tx ? FSL_SAI_TDR(ofs) : FSL_SAI_RDR(ofs)) +-#define FSL_SAI_xFR(tx, ofs) (tx ? FSL_SAI_TFR(ofs) : FSL_SAI_RFR(ofs)) ++#define FSL_SAI_xDR0(tx) (tx ? FSL_SAI_TDR0 : FSL_SAI_RDR0) ++#define FSL_SAI_xFR0(tx) (tx ? FSL_SAI_TFR0 : FSL_SAI_RFR0) + #define FSL_SAI_xMR(tx) (tx ? FSL_SAI_TMR : FSL_SAI_RMR) + + /* SAI Transmit/Receive Control Register */ +-- +2.35.1 + diff --git a/queue-5.15/blk-mq-don-t-touch-tagset-in-blk_mq_get_sq_hctx.patch b/queue-5.15/blk-mq-don-t-touch-tagset-in-blk_mq_get_sq_hctx.patch new file mode 100644 index 00000000000..f89045a82e8 --- /dev/null +++ b/queue-5.15/blk-mq-don-t-touch-tagset-in-blk_mq_get_sq_hctx.patch @@ -0,0 +1,58 @@ +From 2db23a1cb9d39f853e5476fee51daeb9661dc4e6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 22 May 2022 20:23:50 +0800 +Subject: blk-mq: don't touch ->tagset in blk_mq_get_sq_hctx + +From: Ming Lei + +[ Upstream commit 5d05426e2d5fd7df8afc866b78c36b37b00188b7 ] + +blk_mq_run_hw_queues() could be run when there isn't queued request and +after queue is cleaned up, at that time tagset is freed, because tagset +lifetime is covered by driver, and often freed after blk_cleanup_queue() +returns. + +So don't touch ->tagset for figuring out current default hctx by the mapping +built in request queue, so use-after-free on tagset can be avoided. Meantime +this way should be fast than retrieving mapping from tagset. + +Cc: "yukuai (C)" +Cc: Jan Kara +Fixes: b6e68ee82585 ("blk-mq: Improve performance of non-mq IO schedulers with multiple HW queues") +Signed-off-by: Ming Lei +Reviewed-by: Jan Kara +Link: https://lore.kernel.org/r/20220522122350.743103-1-ming.lei@redhat.com +Signed-off-by: Jens Axboe +Signed-off-by: Sasha Levin +--- + block/blk-mq.c | 7 +++---- + 1 file changed, 3 insertions(+), 4 deletions(-) + +diff --git a/block/blk-mq.c b/block/blk-mq.c +index 82de39926a9f..b70488e4db94 100644 +--- a/block/blk-mq.c ++++ b/block/blk-mq.c +@@ -1642,8 +1642,7 @@ static bool blk_mq_has_sqsched(struct request_queue *q) + */ + static struct blk_mq_hw_ctx *blk_mq_get_sq_hctx(struct request_queue *q) + { +- struct blk_mq_hw_ctx *hctx; +- ++ struct blk_mq_ctx *ctx = blk_mq_get_ctx(q); + /* + * If the IO scheduler does not respect hardware queues when + * dispatching, we just don't bother with multiple HW queues and +@@ -1651,8 +1650,8 @@ static struct blk_mq_hw_ctx *blk_mq_get_sq_hctx(struct request_queue *q) + * just causes lock contention inside the scheduler and pointless cache + * bouncing. + */ +- hctx = blk_mq_map_queue_type(q, HCTX_TYPE_DEFAULT, +- raw_smp_processor_id()); ++ struct blk_mq_hw_ctx *hctx = blk_mq_map_queue(q, 0, ctx); ++ + if (!blk_mq_hctx_stopped(hctx)) + return hctx; + return NULL; +-- +2.35.1 + diff --git a/queue-5.15/block-make-bioset_exit-fully-resilient-against-being.patch b/queue-5.15/block-make-bioset_exit-fully-resilient-against-being.patch new file mode 100644 index 00000000000..ea282854838 --- /dev/null +++ b/queue-5.15/block-make-bioset_exit-fully-resilient-against-being.patch @@ -0,0 +1,42 @@ +From a699a172d4ccb4061c35011f9dac40c33b3b831a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 29 May 2022 07:13:09 -0600 +Subject: block: make bioset_exit() fully resilient against being called twice + +From: Jens Axboe + +[ Upstream commit 605f7415ecfb426610195dd6c7577b30592b3369 ] + +Most of bioset_exit() is fine being called twice, as it clears the +various allocations etc when they are freed. The exception is +bio_alloc_cache_destroy(), which does not clear ->cache when it has +freed it. + +This isn't necessarily a bug, but can be if buggy users does call the +exit path more then once, or with just a memset() bioset which has +never been initialized. dm appears to be one such user. + +Fixes: be4d234d7aeb ("bio: add allocation cache abstraction") +Link: https://lore.kernel.org/linux-block/YpK7m+14A+pZKs5k@casper.infradead.org/ +Reported-by: Matthew Wilcox +Signed-off-by: Jens Axboe +Signed-off-by: Sasha Levin +--- + block/bio.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/block/bio.c b/block/bio.c +index 9b28381412d2..8381c6690dd6 100644 +--- a/block/bio.c ++++ b/block/bio.c +@@ -665,6 +665,7 @@ static void bio_alloc_cache_destroy(struct bio_set *bs) + bio_alloc_cache_prune(cache, -1U); + } + free_percpu(bs->cache); ++ bs->cache = NULL; + } + + /** +-- +2.35.1 + diff --git a/queue-5.15/block-take-destination-bvec-offsets-into-account-in-.patch b/queue-5.15/block-take-destination-bvec-offsets-into-account-in-.patch new file mode 100644 index 00000000000..3174109714a --- /dev/null +++ b/queue-5.15/block-take-destination-bvec-offsets-into-account-in-.patch @@ -0,0 +1,46 @@ +From 8cc626d12f7e52c893b9a22046af717233b23260 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 24 May 2022 16:39:19 +0200 +Subject: block: take destination bvec offsets into account in + bio_copy_data_iter + +From: Christoph Hellwig + +[ Upstream commit 403d50341cce6b5481a92eb481e6df60b1f49b55 ] + +Appartly bcache can copy into bios that do not just contain fresh +pages but can have offsets into the bio_vecs. Restore support for tht +in bio_copy_data_iter. + +Fixes: f8b679a070c5 ("block: rewrite bio_copy_data_iter to use bvec_kmap_local and memcpy_to_bvec") +Signed-off-by: Christoph Hellwig +Link: https://lore.kernel.org/r/20220524143919.1155501-1-hch@lst.de +Signed-off-by: Jens Axboe +Signed-off-by: Sasha Levin +--- + block/bio.c | 8 +++++--- + 1 file changed, 5 insertions(+), 3 deletions(-) + +diff --git a/block/bio.c b/block/bio.c +index 8906c9856a7d..9b28381412d2 100644 +--- a/block/bio.c ++++ b/block/bio.c +@@ -1289,10 +1289,12 @@ void bio_copy_data_iter(struct bio *dst, struct bvec_iter *dst_iter, + struct bio_vec src_bv = bio_iter_iovec(src, *src_iter); + struct bio_vec dst_bv = bio_iter_iovec(dst, *dst_iter); + unsigned int bytes = min(src_bv.bv_len, dst_bv.bv_len); +- void *src_buf; ++ void *src_buf = bvec_kmap_local(&src_bv); ++ void *dst_buf = bvec_kmap_local(&dst_bv); + +- src_buf = bvec_kmap_local(&src_bv); +- memcpy_to_bvec(&dst_bv, src_buf); ++ memcpy(dst_buf, src_buf, bytes); ++ ++ kunmap_local(dst_buf); + kunmap_local(src_buf); + + bio_advance_iter_single(src, src_iter, bytes); +-- +2.35.1 + diff --git a/queue-5.15/bpf-fix-probe-read-error-in-___bpf_prog_run.patch b/queue-5.15/bpf-fix-probe-read-error-in-___bpf_prog_run.patch new file mode 100644 index 00000000000..686e5cb7fda --- /dev/null +++ b/queue-5.15/bpf-fix-probe-read-error-in-___bpf_prog_run.patch @@ -0,0 +1,95 @@ +From b8599a4e1f00ede188a915c6e969d4d7606ea524 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 24 May 2022 10:12:27 +0800 +Subject: bpf: Fix probe read error in ___bpf_prog_run() + +From: Menglong Dong + +[ Upstream commit caff1fa4118cec4dfd4336521ebd22a6408a1e3e ] + +I think there is something wrong with BPF_PROBE_MEM in ___bpf_prog_run() +in big-endian machine. Let's make a test and see what will happen if we +want to load a 'u16' with BPF_PROBE_MEM. + +Let's make the src value '0x0001', the value of dest register will become +0x0001000000000000, as the value will be loaded to the first 2 byte of +DST with following code: + + bpf_probe_read_kernel(&DST, SIZE, (const void *)(long) (SRC + insn->off)); + +Obviously, the value in DST is not correct. In fact, we can compare +BPF_PROBE_MEM with LDX_MEM_H: + + DST = *(SIZE *)(unsigned long) (SRC + insn->off); + +If the memory load is done by LDX_MEM_H, the value in DST will be 0x1 now. + +And I think this error results in the test case 'test_bpf_sk_storage_map' +failing: + + test_bpf_sk_storage_map:PASS:bpf_iter_bpf_sk_storage_map__open_and_load 0 nsec + test_bpf_sk_storage_map:PASS:socket 0 nsec + test_bpf_sk_storage_map:PASS:map_update 0 nsec + test_bpf_sk_storage_map:PASS:socket 0 nsec + test_bpf_sk_storage_map:PASS:map_update 0 nsec + test_bpf_sk_storage_map:PASS:socket 0 nsec + test_bpf_sk_storage_map:PASS:map_update 0 nsec + test_bpf_sk_storage_map:PASS:attach_iter 0 nsec + test_bpf_sk_storage_map:PASS:create_iter 0 nsec + test_bpf_sk_storage_map:PASS:read 0 nsec + test_bpf_sk_storage_map:FAIL:ipv6_sk_count got 0 expected 3 + $10/26 bpf_iter/bpf_sk_storage_map:FAIL + +The code of the test case is simply, it will load sk->sk_family to the +register with BPF_PROBE_MEM and check if it is AF_INET6. With this patch, +now the test case 'bpf_iter' can pass: + + $10 bpf_iter:OK + +Fixes: 2a02759ef5f8 ("bpf: Add support for BTF pointers to interpreter") +Signed-off-by: Menglong Dong +Signed-off-by: Daniel Borkmann +Reviewed-by: Jiang Biao +Reviewed-by: Hao Peng +Cc: Ilya Leoshkevich +Link: https://lore.kernel.org/bpf/20220524021228.533216-1-imagedong@tencent.com +Signed-off-by: Sasha Levin +--- + kernel/bpf/core.c | 14 +++++--------- + 1 file changed, 5 insertions(+), 9 deletions(-) + +diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c +index 6e3ae90ad107..48eb9c329da6 100644 +--- a/kernel/bpf/core.c ++++ b/kernel/bpf/core.c +@@ -1652,6 +1652,11 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn) + CONT; \ + LDX_MEM_##SIZEOP: \ + DST = *(SIZE *)(unsigned long) (SRC + insn->off); \ ++ CONT; \ ++ LDX_PROBE_MEM_##SIZEOP: \ ++ bpf_probe_read_kernel(&DST, sizeof(SIZE), \ ++ (const void *)(long) (SRC + insn->off)); \ ++ DST = *((SIZE *)&DST); \ + CONT; + + LDST(B, u8) +@@ -1659,15 +1664,6 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn) + LDST(W, u32) + LDST(DW, u64) + #undef LDST +-#define LDX_PROBE(SIZEOP, SIZE) \ +- LDX_PROBE_MEM_##SIZEOP: \ +- bpf_probe_read_kernel(&DST, SIZE, (const void *)(long) (SRC + insn->off)); \ +- CONT; +- LDX_PROBE(B, 1) +- LDX_PROBE(H, 2) +- LDX_PROBE(W, 4) +- LDX_PROBE(DW, 8) +-#undef LDX_PROBE + + #define ATOMIC_ALU_OP(BOP, KOP) \ + case BOP: \ +-- +2.35.1 + diff --git a/queue-5.15/bus-ti-sysc-fix-warnings-for-unbind-for-serial.patch b/queue-5.15/bus-ti-sysc-fix-warnings-for-unbind-for-serial.patch new file mode 100644 index 00000000000..4703e98fbf7 --- /dev/null +++ b/queue-5.15/bus-ti-sysc-fix-warnings-for-unbind-for-serial.patch @@ -0,0 +1,45 @@ +From b2af371cf5dcb3987bd9843f7848813c480052ad Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 12 May 2022 08:30:21 +0300 +Subject: bus: ti-sysc: Fix warnings for unbind for serial + +From: Tony Lindgren + +[ Upstream commit c337125b8834f9719dfda0e40b25eaa266f1b8cf ] + +We can get "failed to disable" clock_unprepare warnings on unbind at least +for the serial console device if the unbind is done before the device has +been idled. + +As some devices are using deferred idle, we must check the status for +pending idle work to idle the device. + +Fixes: 76f0f772e469 ("bus: ti-sysc: Improve handling for no-reset-on-init and no-idle-on-init") +Cc: Romain Naour +Reviewed-by: Romain Naour +Signed-off-by: Tony Lindgren +Link: https://lore.kernel.org/r/20220512053021.61650-1-tony@atomide.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/bus/ti-sysc.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c +index 00d46f3ae22f..e93912e56f28 100644 +--- a/drivers/bus/ti-sysc.c ++++ b/drivers/bus/ti-sysc.c +@@ -3325,7 +3325,9 @@ static int sysc_remove(struct platform_device *pdev) + struct sysc *ddata = platform_get_drvdata(pdev); + int error; + +- cancel_delayed_work_sync(&ddata->idle_work); ++ /* Device can still be enabled, see deferred idle quirk in probe */ ++ if (cancel_delayed_work_sync(&ddata->idle_work)) ++ ti_sysc_idle(&ddata->idle_work.work); + + error = pm_runtime_resume_and_get(ddata->dev); + if (error < 0) { +-- +2.35.1 + diff --git a/queue-5.15/clocksource-drivers-oxnas-rps-fix-irq_of_parse_and_m.patch b/queue-5.15/clocksource-drivers-oxnas-rps-fix-irq_of_parse_and_m.patch new file mode 100644 index 00000000000..9d8086555f2 --- /dev/null +++ b/queue-5.15/clocksource-drivers-oxnas-rps-fix-irq_of_parse_and_m.patch @@ -0,0 +1,38 @@ +From 181ab5e0475354f79816740d4803addd9e851cb1 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 12:41:01 +0200 +Subject: clocksource/drivers/oxnas-rps: Fix irq_of_parse_and_map() return + value + +From: Krzysztof Kozlowski + +[ Upstream commit 9c04a8ff03def4df3f81219ffbe1ec9b44ff5348 ] + +The irq_of_parse_and_map() returns 0 on failure, not a negative ERRNO. + +Fixes: 89355274e1f7 ("clocksource/drivers/oxnas-rps: Add Oxford Semiconductor RPS Dual Timer") +Signed-off-by: Krzysztof Kozlowski +Reviewed-by: Neil Armstrong +Link: https://lore.kernel.org/r/20220422104101.55754-1-krzysztof.kozlowski@linaro.org +Signed-off-by: Daniel Lezcano +Signed-off-by: Sasha Levin +--- + drivers/clocksource/timer-oxnas-rps.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/clocksource/timer-oxnas-rps.c b/drivers/clocksource/timer-oxnas-rps.c +index 56c0cc32d0ac..d514b44e67dd 100644 +--- a/drivers/clocksource/timer-oxnas-rps.c ++++ b/drivers/clocksource/timer-oxnas-rps.c +@@ -236,7 +236,7 @@ static int __init oxnas_rps_timer_init(struct device_node *np) + } + + rps->irq = irq_of_parse_and_map(np, 0); +- if (rps->irq < 0) { ++ if (!rps->irq) { + ret = -EINVAL; + goto err_iomap; + } +-- +2.35.1 + diff --git a/queue-5.15/clocksource-drivers-riscv-events-are-stopped-during-.patch b/queue-5.15/clocksource-drivers-riscv-events-are-stopped-during-.patch new file mode 100644 index 00000000000..6f431d15620 --- /dev/null +++ b/queue-5.15/clocksource-drivers-riscv-events-are-stopped-during-.patch @@ -0,0 +1,40 @@ +From 40aa2e36e52d6f4d9e468a51e11d86632dfd1c27 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 8 May 2022 20:21:21 -0500 +Subject: clocksource/drivers/riscv: Events are stopped during CPU suspend + +From: Samuel Holland + +[ Upstream commit 232ccac1bd9b5bfe73895f527c08623e7fa0752d ] + +Some implementations of the SBI time extension depend on hart-local +state (for example, CSRs) that are lost or hardware that is powered +down when a CPU is suspended. To be safe, the clockevents driver +cannot assume that timer IRQs will be received during CPU suspend. + +Fixes: 62b019436814 ("clocksource: new RISC-V SBI timer driver") +Signed-off-by: Samuel Holland +Reviewed-by: Anup Patel +Link: https://lore.kernel.org/r/20220509012121.40031-1-samuel@sholland.org +Signed-off-by: Daniel Lezcano +Signed-off-by: Sasha Levin +--- + drivers/clocksource/timer-riscv.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/clocksource/timer-riscv.c b/drivers/clocksource/timer-riscv.c +index c51c5ed15aa7..0e7748df4be3 100644 +--- a/drivers/clocksource/timer-riscv.c ++++ b/drivers/clocksource/timer-riscv.c +@@ -32,7 +32,7 @@ static int riscv_clock_next_event(unsigned long delta, + static unsigned int riscv_clock_event_irq; + static DEFINE_PER_CPU(struct clock_event_device, riscv_clock_event) = { + .name = "riscv_timer_clockevent", +- .features = CLOCK_EVT_FEAT_ONESHOT, ++ .features = CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_C3STOP, + .rating = 100, + .set_next_event = riscv_clock_next_event, + }; +-- +2.35.1 + diff --git a/queue-5.15/coresight-cpu-debug-replace-mutex-with-mutex_trylock.patch b/queue-5.15/coresight-cpu-debug-replace-mutex-with-mutex_trylock.patch new file mode 100644 index 00000000000..c2708ccc23a --- /dev/null +++ b/queue-5.15/coresight-cpu-debug-replace-mutex-with-mutex_trylock.patch @@ -0,0 +1,64 @@ +From 2ae7b194feace81c3b9da104daee3dbdadcf02c4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 27 Apr 2022 19:49:03 -0300 +Subject: coresight: cpu-debug: Replace mutex with mutex_trylock on panic + notifier + +From: Guilherme G. Piccoli + +[ Upstream commit 1adff542d67a2ed1120955cb219bfff8a9c53f59 ] + +The panic notifier infrastructure executes registered callbacks when +a panic event happens - such callbacks are executed in atomic context, +with interrupts and preemption disabled in the running CPU and all other +CPUs disabled. That said, mutexes in such context are not a good idea. + +This patch replaces a regular mutex with a mutex_trylock safer approach; +given the nature of the mutex used in the driver, it should be pretty +uncommon being unable to acquire such mutex in the panic path, hence +no functional change should be observed (and if it is, that would be +likely a deadlock with the regular mutex). + +Fixes: 2227b7c74634 ("coresight: add support for CPU debug module") +Cc: Leo Yan +Cc: Mathieu Poirier +Cc: Mike Leach +Cc: Suzuki K Poulose +Signed-off-by: Guilherme G. Piccoli +Reviewed-by: Suzuki K Poulose +Signed-off-by: Suzuki K Poulose +Link: https://lore.kernel.org/r/20220427224924.592546-10-gpiccoli@igalia.com +Signed-off-by: Sasha Levin +--- + drivers/hwtracing/coresight/coresight-cpu-debug.c | 7 ++++--- + 1 file changed, 4 insertions(+), 3 deletions(-) + +diff --git a/drivers/hwtracing/coresight/coresight-cpu-debug.c b/drivers/hwtracing/coresight/coresight-cpu-debug.c +index 00de46565bc4..c60442970c2a 100644 +--- a/drivers/hwtracing/coresight/coresight-cpu-debug.c ++++ b/drivers/hwtracing/coresight/coresight-cpu-debug.c +@@ -380,9 +380,10 @@ static int debug_notifier_call(struct notifier_block *self, + int cpu; + struct debug_drvdata *drvdata; + +- mutex_lock(&debug_lock); ++ /* Bail out if we can't acquire the mutex or the functionality is off */ ++ if (!mutex_trylock(&debug_lock)) ++ return NOTIFY_DONE; + +- /* Bail out if the functionality is disabled */ + if (!debug_enable) + goto skip_dump; + +@@ -401,7 +402,7 @@ static int debug_notifier_call(struct notifier_block *self, + + skip_dump: + mutex_unlock(&debug_lock); +- return 0; ++ return NOTIFY_DONE; + } + + static struct notifier_block debug_notifier = { +-- +2.35.1 + diff --git a/queue-5.15/driver-base-fix-uaf-when-driver_attach-failed.patch b/queue-5.15/driver-base-fix-uaf-when-driver_attach-failed.patch new file mode 100644 index 00000000000..3b1dac6d76f --- /dev/null +++ b/queue-5.15/driver-base-fix-uaf-when-driver_attach-failed.patch @@ -0,0 +1,48 @@ +From d3294a079b7669fd413f1d118a0a319efe4cf519 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 13 May 2022 19:24:44 +0800 +Subject: driver: base: fix UAF when driver_attach failed + +From: Schspa Shi + +[ Upstream commit 310862e574001a97ad02272bac0fd13f75f42a27 ] + +When driver_attach(drv); failed, the driver_private will be freed. +But it has been added to the bus, which caused a UAF. + +To fix it, we need to delete it from the bus when failed. + +Fixes: 190888ac01d0 ("driver core: fix possible missing of device probe") +Signed-off-by: Schspa Shi +Link: https://lore.kernel.org/r/20220513112444.45112-1-schspa@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/base/bus.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/drivers/base/bus.c b/drivers/base/bus.c +index bdc98c5713d5..d171535fc18f 100644 +--- a/drivers/base/bus.c ++++ b/drivers/base/bus.c +@@ -617,7 +617,7 @@ int bus_add_driver(struct device_driver *drv) + if (drv->bus->p->drivers_autoprobe) { + error = driver_attach(drv); + if (error) +- goto out_unregister; ++ goto out_del_list; + } + module_add_driver(drv->owner, drv); + +@@ -644,6 +644,8 @@ int bus_add_driver(struct device_driver *drv) + + return 0; + ++out_del_list: ++ klist_del(&priv->knode_bus); + out_unregister: + kobject_put(&priv->kobj); + /* drv->p is freed in driver_release() */ +-- +2.35.1 + diff --git a/queue-5.15/driver-core-fix-deadlock-in-__device_attach.patch b/queue-5.15/driver-core-fix-deadlock-in-__device_attach.patch new file mode 100644 index 00000000000..0d2af03bca2 --- /dev/null +++ b/queue-5.15/driver-core-fix-deadlock-in-__device_attach.patch @@ -0,0 +1,79 @@ +From cbdb2a218a5eed21c5adacef25440b731f86a979 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 18 May 2022 15:45:16 +0800 +Subject: driver core: fix deadlock in __device_attach + +From: Zhang Wensheng + +[ Upstream commit b232b02bf3c205b13a26dcec08e53baddd8e59ed ] + +In __device_attach function, The lock holding logic is as follows: +... +__device_attach +device_lock(dev) // get lock dev + async_schedule_dev(__device_attach_async_helper, dev); // func + async_schedule_node + async_schedule_node_domain(func) + entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); + /* when fail or work limit, sync to execute func, but + __device_attach_async_helper will get lock dev as + well, which will lead to A-A deadlock. */ + if (!entry || atomic_read(&entry_count) > MAX_WORK) { + func; + else + queue_work_node(node, system_unbound_wq, &entry->work) + device_unlock(dev) + +As shown above, when it is allowed to do async probes, because of +out of memory or work limit, async work is not allowed, to do +sync execute instead. it will lead to A-A deadlock because of +__device_attach_async_helper getting lock dev. + +To fix the deadlock, move the async_schedule_dev outside device_lock, +as we can see, in async_schedule_node_domain, the parameter of +queue_work_node is system_unbound_wq, so it can accept concurrent +operations. which will also not change the code logic, and will +not lead to deadlock. + +Fixes: 765230b5f084 ("driver-core: add asynchronous probing support for drivers") +Signed-off-by: Zhang Wensheng +Link: https://lore.kernel.org/r/20220518074516.1225580-1-zhangwensheng5@huawei.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/base/dd.c | 5 ++++- + 1 file changed, 4 insertions(+), 1 deletion(-) + +diff --git a/drivers/base/dd.c b/drivers/base/dd.c +index 95ae347df137..a480004b9897 100644 +--- a/drivers/base/dd.c ++++ b/drivers/base/dd.c +@@ -944,6 +944,7 @@ static void __device_attach_async_helper(void *_dev, async_cookie_t cookie) + static int __device_attach(struct device *dev, bool allow_async) + { + int ret = 0; ++ bool async = false; + + device_lock(dev); + if (dev->p->dead) { +@@ -982,7 +983,7 @@ static int __device_attach(struct device *dev, bool allow_async) + */ + dev_dbg(dev, "scheduling asynchronous probe\n"); + get_device(dev); +- async_schedule_dev(__device_attach_async_helper, dev); ++ async = true; + } else { + pm_request_idle(dev); + } +@@ -992,6 +993,8 @@ static int __device_attach(struct device *dev, bool allow_async) + } + out_unlock: + device_unlock(dev); ++ if (async) ++ async_schedule_dev(__device_attach_async_helper, dev); + return ret; + } + +-- +2.35.1 + diff --git a/queue-5.15/driver-core-fix-wait_for_device_probe-deferred_probe.patch b/queue-5.15/driver-core-fix-wait_for_device_probe-deferred_probe.patch new file mode 100644 index 00000000000..eb49ca86309 --- /dev/null +++ b/queue-5.15/driver-core-fix-wait_for_device_probe-deferred_probe.patch @@ -0,0 +1,107 @@ +From d2cc539f2ccf7eab621abd38fb1903bb7b4c79c4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 3 Jun 2022 13:31:37 +0200 +Subject: driver core: Fix wait_for_device_probe() & deferred_probe_timeout + interaction + +From: Saravana Kannan + +[ Upstream commit 5ee76c256e928455212ab759c51d198fedbe7523 ] + +Mounting NFS rootfs was timing out when deferred_probe_timeout was +non-zero [1]. This was because ip_auto_config() initcall times out +waiting for the network interfaces to show up when +deferred_probe_timeout was non-zero. While ip_auto_config() calls +wait_for_device_probe() to make sure any currently running deferred +probe work or asynchronous probe finishes, that wasn't sufficient to +account for devices being deferred until deferred_probe_timeout. + +Commit 35a672363ab3 ("driver core: Ensure wait_for_device_probe() waits +until the deferred_probe_timeout fires") tried to fix that by making +sure wait_for_device_probe() waits for deferred_probe_timeout to expire +before returning. + +However, if wait_for_device_probe() is called from the kernel_init() +context: + +- Before deferred_probe_initcall() [2], it causes the boot process to + hang due to a deadlock. + +- After deferred_probe_initcall() [3], it blocks kernel_init() from + continuing till deferred_probe_timeout expires and beats the point of + deferred_probe_timeout that's trying to wait for userspace to load + modules. + +Neither of this is good. So revert the changes to +wait_for_device_probe(). + +[1] - https://lore.kernel.org/lkml/TYAPR01MB45443DF63B9EF29054F7C41FD8C60@TYAPR01MB4544.jpnprd01.prod.outlook.com/ +[2] - https://lore.kernel.org/lkml/YowHNo4sBjr9ijZr@dev-arch.thelio-3990X/ +[3] - https://lore.kernel.org/lkml/Yo3WvGnNk3LvLb7R@linutronix.de/ + +Fixes: 35a672363ab3 ("driver core: Ensure wait_for_device_probe() waits until the deferred_probe_timeout fires") +Cc: John Stultz +Cc: "David S. Miller" +Cc: Alexey Kuznetsov +Cc: Hideaki YOSHIFUJI +Cc: Jakub Kicinski +Cc: Rob Herring +Cc: Geert Uytterhoeven +Cc: Yoshihiro Shimoda +Cc: Robin Murphy +Cc: Andy Shevchenko +Cc: Sudeep Holla +Cc: Andy Shevchenko +Cc: Naresh Kamboju +Cc: Basil Eljuse +Cc: Ferry Toth +Cc: Arnd Bergmann +Cc: Anders Roxell +Cc: linux-pm@vger.kernel.org +Reported-by: Nathan Chancellor +Reported-by: Sebastian Andrzej Siewior +Tested-by: Geert Uytterhoeven +Acked-by: John Stultz +Signed-off-by: Saravana Kannan +Link: https://lore.kernel.org/r/20220526034609.480766-2-saravanak@google.com +Signed-off-by: Greg Kroah-Hartman +Reviewed-by: Rafael J. Wysocki +Signed-off-by: Linus Torvalds +Signed-off-by: Sasha Levin +--- + drivers/base/dd.c | 5 ----- + 1 file changed, 5 deletions(-) + +diff --git a/drivers/base/dd.c b/drivers/base/dd.c +index a480004b9897..76ded601d0c1 100644 +--- a/drivers/base/dd.c ++++ b/drivers/base/dd.c +@@ -257,7 +257,6 @@ DEFINE_SHOW_ATTRIBUTE(deferred_devs); + + int driver_deferred_probe_timeout; + EXPORT_SYMBOL_GPL(driver_deferred_probe_timeout); +-static DECLARE_WAIT_QUEUE_HEAD(probe_timeout_waitqueue); + + static int __init deferred_probe_timeout_setup(char *str) + { +@@ -312,7 +311,6 @@ static void deferred_probe_timeout_work_func(struct work_struct *work) + list_for_each_entry(p, &deferred_probe_pending_list, deferred_probe) + dev_info(p->device, "deferred probe pending\n"); + mutex_unlock(&deferred_probe_mutex); +- wake_up_all(&probe_timeout_waitqueue); + } + static DECLARE_DELAYED_WORK(deferred_probe_timeout_work, deferred_probe_timeout_work_func); + +@@ -719,9 +717,6 @@ int driver_probe_done(void) + */ + void wait_for_device_probe(void) + { +- /* wait for probe timeout */ +- wait_event(probe_timeout_waitqueue, !driver_deferred_probe_timeout); +- + /* wait for the deferred probe workqueue to finish */ + flush_work(&deferred_probe_work); + +-- +2.35.1 + diff --git a/queue-5.15/export-fix-string-handling-of-namespace-in-export_sy.patch b/queue-5.15/export-fix-string-handling-of-namespace-in-export_sy.patch new file mode 100644 index 00000000000..b412ac107f3 --- /dev/null +++ b/queue-5.15/export-fix-string-handling-of-namespace-in-export_sy.patch @@ -0,0 +1,63 @@ +From 198eee9eb5ab58487d8bac101aa3a083facd05c2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 27 Apr 2022 11:04:42 +0200 +Subject: export: fix string handling of namespace in EXPORT_SYMBOL_NS + +From: Greg Kroah-Hartman + +[ Upstream commit d143b9db8069f0e2a0fa34484e806a55a0dd4855 ] + +Commit c3a6cf19e695 ("export: avoid code duplication in +include/linux/export.h") broke the ability for a defined string to be +used as a namespace value. Fix this up by using stringify to properly +encode the namespace name. + +Fixes: c3a6cf19e695 ("export: avoid code duplication in include/linux/export.h") +Cc: Miroslav Benes +Cc: Emil Velikov +Cc: Jessica Yu +Cc: Quentin Perret +Cc: Matthias Maennich +Reviewed-by: Masahiro Yamada +Link: https://lore.kernel.org/r/20220427090442.2105905-1-gregkh@linuxfoundation.org +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + include/linux/export.h | 7 ++++--- + 1 file changed, 4 insertions(+), 3 deletions(-) + +diff --git a/include/linux/export.h b/include/linux/export.h +index 27d848712b90..5910ccb66ca2 100644 +--- a/include/linux/export.h ++++ b/include/linux/export.h +@@ -2,6 +2,8 @@ + #ifndef _LINUX_EXPORT_H + #define _LINUX_EXPORT_H + ++#include ++ + /* + * Export symbols from the kernel to modules. Forked from module.h + * to reduce the amount of pointless cruft we feed to gcc when only +@@ -154,7 +156,6 @@ struct kernel_symbol { + #endif /* CONFIG_MODULES */ + + #ifdef DEFAULT_SYMBOL_NAMESPACE +-#include + #define _EXPORT_SYMBOL(sym, sec) __EXPORT_SYMBOL(sym, sec, __stringify(DEFAULT_SYMBOL_NAMESPACE)) + #else + #define _EXPORT_SYMBOL(sym, sec) __EXPORT_SYMBOL(sym, sec, "") +@@ -162,8 +163,8 @@ struct kernel_symbol { + + #define EXPORT_SYMBOL(sym) _EXPORT_SYMBOL(sym, "") + #define EXPORT_SYMBOL_GPL(sym) _EXPORT_SYMBOL(sym, "_gpl") +-#define EXPORT_SYMBOL_NS(sym, ns) __EXPORT_SYMBOL(sym, "", #ns) +-#define EXPORT_SYMBOL_NS_GPL(sym, ns) __EXPORT_SYMBOL(sym, "_gpl", #ns) ++#define EXPORT_SYMBOL_NS(sym, ns) __EXPORT_SYMBOL(sym, "", __stringify(ns)) ++#define EXPORT_SYMBOL_NS_GPL(sym, ns) __EXPORT_SYMBOL(sym, "_gpl", __stringify(ns)) + + #endif /* !__ASSEMBLY__ */ + +-- +2.35.1 + diff --git a/queue-5.15/extcon-ptn5150-add-queue-work-sync-before-driver-rel.patch b/queue-5.15/extcon-ptn5150-add-queue-work-sync-before-driver-rel.patch new file mode 100644 index 00000000000..66777f5e569 --- /dev/null +++ b/queue-5.15/extcon-ptn5150-add-queue-work-sync-before-driver-rel.patch @@ -0,0 +1,53 @@ +From 48a72de73fe2ea2ee7c8dd62cff168f6bfb01a77 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 19 Apr 2022 20:44:08 +0800 +Subject: extcon: ptn5150: Add queue work sync before driver release + +From: Li Jun + +[ Upstream commit 782cd939cbe0f569197cd1c9b0477ee213167f04 ] + +Add device managed action to sync pending queue work, otherwise +the queued work may run after the work is destroyed. + +Fixes: 4ed754de2d66 ("extcon: Add support for ptn5150 extcon driver") +Reviewed-by: Krzysztof Kozlowski +Signed-off-by: Li Jun +Signed-off-by: Chanwoo Choi +Signed-off-by: Sasha Levin +--- + drivers/extcon/extcon-ptn5150.c | 11 +++++++++++ + 1 file changed, 11 insertions(+) + +diff --git a/drivers/extcon/extcon-ptn5150.c b/drivers/extcon/extcon-ptn5150.c +index 5b9a3cf8df26..2a7874108df8 100644 +--- a/drivers/extcon/extcon-ptn5150.c ++++ b/drivers/extcon/extcon-ptn5150.c +@@ -194,6 +194,13 @@ static int ptn5150_init_dev_type(struct ptn5150_info *info) + return 0; + } + ++static void ptn5150_work_sync_and_put(void *data) ++{ ++ struct ptn5150_info *info = data; ++ ++ cancel_work_sync(&info->irq_work); ++} ++ + static int ptn5150_i2c_probe(struct i2c_client *i2c) + { + struct device *dev = &i2c->dev; +@@ -284,6 +291,10 @@ static int ptn5150_i2c_probe(struct i2c_client *i2c) + if (ret) + return -EINVAL; + ++ ret = devm_add_action_or_reset(dev, ptn5150_work_sync_and_put, info); ++ if (ret) ++ return ret; ++ + /* + * Update current extcon state if for example OTG connection was there + * before the probe +-- +2.35.1 + diff --git a/queue-5.15/firmware-dmi-sysfs-fix-memory-leak-in-dmi_sysfs_regi.patch b/queue-5.15/firmware-dmi-sysfs-fix-memory-leak-in-dmi_sysfs_regi.patch new file mode 100644 index 00000000000..15ab387bf3e --- /dev/null +++ b/queue-5.15/firmware-dmi-sysfs-fix-memory-leak-in-dmi_sysfs_regi.patch @@ -0,0 +1,42 @@ +From 203bb331bffd7ba55d38233bfb0d3f732c14e063 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 11 May 2022 11:14:19 +0400 +Subject: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle + +From: Miaoqian Lin + +[ Upstream commit 660ba678f9998aca6db74f2dd912fa5124f0fa31 ] + +kobject_init_and_add() takes reference even when it fails. +According to the doc of kobject_init_and_add() + + If this function returns an error, kobject_put() must be called to + properly clean up the memory associated with the object. + +Fix this issue by calling kobject_put(). + +Fixes: 948af1f0bbc8 ("firmware: Basic dmi-sysfs support") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220511071421.9769-1-linmq006@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/firmware/dmi-sysfs.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/firmware/dmi-sysfs.c b/drivers/firmware/dmi-sysfs.c +index 8b8127fa8955..4a93fb490cb4 100644 +--- a/drivers/firmware/dmi-sysfs.c ++++ b/drivers/firmware/dmi-sysfs.c +@@ -603,7 +603,7 @@ static void __init dmi_sysfs_register_handle(const struct dmi_header *dh, + "%d-%d", dh->type, entry->instance); + + if (*ret) { +- kfree(entry); ++ kobject_put(&entry->kobj); + return; + } + +-- +2.35.1 + diff --git a/queue-5.15/firmware-stratix10-svc-fix-a-missing-check-on-list-i.patch b/queue-5.15/firmware-stratix10-svc-fix-a-missing-check-on-list-i.patch new file mode 100644 index 00000000000..220f3348426 --- /dev/null +++ b/queue-5.15/firmware-stratix10-svc-fix-a-missing-check-on-list-i.patch @@ -0,0 +1,60 @@ +From 70bbf556b689293ef19beff1618fef30173f6482 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 14 Apr 2022 11:56:09 +0800 +Subject: firmware: stratix10-svc: fix a missing check on list iterator + +From: Xiaomeng Tong + +[ Upstream commit 5a0793ac66ac0e254d292f129a4d6c526f9f2aff ] + +The bug is here: + pmem->vaddr = NULL; + +The list iterator 'pmem' will point to a bogus position containing +HEAD if the list is empty or no element is found. This case must +be checked before any use of the iterator, otherwise it will +lead to a invalid memory access. + +To fix this bug, just gen_pool_free/set NULL/list_del() and return +when found, otherwise list_del HEAD and return; + +Fixes: 7ca5ce896524f ("firmware: add Intel Stratix10 service layer driver") +Signed-off-by: Xiaomeng Tong +Link: https://lore.kernel.org/r/20220414035609.2239-1-xiam0nd.tong@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/firmware/stratix10-svc.c | 12 ++++++------ + 1 file changed, 6 insertions(+), 6 deletions(-) + +diff --git a/drivers/firmware/stratix10-svc.c b/drivers/firmware/stratix10-svc.c +index 53c7e3f8cfde..7dd0ac1a0cfc 100644 +--- a/drivers/firmware/stratix10-svc.c ++++ b/drivers/firmware/stratix10-svc.c +@@ -941,17 +941,17 @@ EXPORT_SYMBOL_GPL(stratix10_svc_allocate_memory); + void stratix10_svc_free_memory(struct stratix10_svc_chan *chan, void *kaddr) + { + struct stratix10_svc_data_mem *pmem; +- size_t size = 0; + + list_for_each_entry(pmem, &svc_data_mem, node) + if (pmem->vaddr == kaddr) { +- size = pmem->size; +- break; ++ gen_pool_free(chan->ctrl->genpool, ++ (unsigned long)kaddr, pmem->size); ++ pmem->vaddr = NULL; ++ list_del(&pmem->node); ++ return; + } + +- gen_pool_free(chan->ctrl->genpool, (unsigned long)kaddr, size); +- pmem->vaddr = NULL; +- list_del(&pmem->node); ++ list_del(&svc_data_mem); + } + EXPORT_SYMBOL_GPL(stratix10_svc_free_memory); + +-- +2.35.1 + diff --git a/queue-5.15/fs-ntfs3-restore-ntfs_xattr_get_acl-and-ntfs_xattr_s.patch b/queue-5.15/fs-ntfs3-restore-ntfs_xattr_get_acl-and-ntfs_xattr_s.patch new file mode 100644 index 00000000000..332253858da --- /dev/null +++ b/queue-5.15/fs-ntfs3-restore-ntfs_xattr_get_acl-and-ntfs_xattr_s.patch @@ -0,0 +1,96 @@ +From 335f7fef8e55984a2ac677d5a9fb8eb45387f768 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Oct 2021 18:15:36 +0300 +Subject: fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions + +From: Konstantin Komarov + +[ Upstream commit 87e21c99bad763524c953ff4d1a61ee19038ddc2 ] + +Apparently we need to maintain these functions with +ntfs_get_acl_ex and ntfs_set_acl_ex. +This commit fixes xfstest generic/099 +Fixes: 95dd8b2c1ed0 ("fs/ntfs3: Remove unnecessary functions") + +Reviewed-by: Kari Argillander +Signed-off-by: Konstantin Komarov +Signed-off-by: Sasha Levin +--- + fs/ntfs3/xattr.c | 61 ++++++++++++++++++++++++++++++++++++++++++++++++ + 1 file changed, 61 insertions(+) + +diff --git a/fs/ntfs3/xattr.c b/fs/ntfs3/xattr.c +index 0968565ff2ca..52ef3a60cde4 100644 +--- a/fs/ntfs3/xattr.c ++++ b/fs/ntfs3/xattr.c +@@ -681,6 +681,67 @@ static int ntfs_xattr_set_acl(struct user_namespace *mnt_userns, + return err; + } + ++static int ntfs_xattr_get_acl(struct user_namespace *mnt_userns, ++ struct inode *inode, int type, void *buffer, ++ size_t size) ++{ ++ struct posix_acl *acl; ++ int err; ++ ++ if (!(inode->i_sb->s_flags & SB_POSIXACL)) { ++ ntfs_inode_warn(inode, "add mount option \"acl\" to use acl"); ++ return -EOPNOTSUPP; ++ } ++ ++ acl = ntfs_get_acl(inode, type, false); ++ if (IS_ERR(acl)) ++ return PTR_ERR(acl); ++ ++ if (!acl) ++ return -ENODATA; ++ ++ err = posix_acl_to_xattr(mnt_userns, acl, buffer, size); ++ posix_acl_release(acl); ++ ++ return err; ++} ++ ++static int ntfs_xattr_set_acl(struct user_namespace *mnt_userns, ++ struct inode *inode, int type, const void *value, ++ size_t size) ++{ ++ struct posix_acl *acl; ++ int err; ++ ++ if (!(inode->i_sb->s_flags & SB_POSIXACL)) { ++ ntfs_inode_warn(inode, "add mount option \"acl\" to use acl"); ++ return -EOPNOTSUPP; ++ } ++ ++ if (!inode_owner_or_capable(mnt_userns, inode)) ++ return -EPERM; ++ ++ if (!value) { ++ acl = NULL; ++ } else { ++ acl = posix_acl_from_xattr(mnt_userns, value, size); ++ if (IS_ERR(acl)) ++ return PTR_ERR(acl); ++ ++ if (acl) { ++ err = posix_acl_valid(mnt_userns, acl); ++ if (err) ++ goto release_and_out; ++ } ++ } ++ ++ err = ntfs_set_acl(mnt_userns, inode, acl, type); ++ ++release_and_out: ++ posix_acl_release(acl); ++ return err; ++} ++ + /* + * ntfs_init_acl - Initialize the ACLs of a new inode. + * +-- +2.35.1 + diff --git a/queue-5.15/gpio-pca953x-use-the-correct-register-address-to-do-.patch b/queue-5.15/gpio-pca953x-use-the-correct-register-address-to-do-.patch new file mode 100644 index 00000000000..43438376cf0 --- /dev/null +++ b/queue-5.15/gpio-pca953x-use-the-correct-register-address-to-do-.patch @@ -0,0 +1,76 @@ +From 747edcd1abff21cc36e93d64ea767ad711ec405c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 30 May 2022 18:48:48 +0800 +Subject: gpio: pca953x: use the correct register address to do regcache sync + +From: Haibo Chen + +[ Upstream commit 43624eda86c98b0de726d0b6f2516ccc3ef7313f ] + +For regcache_sync_region, need to use pca953x_recalc_addr() to get +the real register address. + +Fixes: b76574300504 ("gpio: pca953x: Restore registers after suspend/resume cycle") +Signed-off-by: Haibo Chen +Signed-off-by: Bartosz Golaszewski +Signed-off-by: Sasha Levin +--- + drivers/gpio/gpio-pca953x.c | 19 +++++++++++-------- + 1 file changed, 11 insertions(+), 8 deletions(-) + +diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c +index 8726921a1129..33683295a0bf 100644 +--- a/drivers/gpio/gpio-pca953x.c ++++ b/drivers/gpio/gpio-pca953x.c +@@ -1108,20 +1108,21 @@ static int pca953x_regcache_sync(struct device *dev) + { + struct pca953x_chip *chip = dev_get_drvdata(dev); + int ret; ++ u8 regaddr; + + /* + * The ordering between direction and output is important, + * sync these registers first and only then sync the rest. + */ +- ret = regcache_sync_region(chip->regmap, chip->regs->direction, +- chip->regs->direction + NBANK(chip)); ++ regaddr = pca953x_recalc_addr(chip, chip->regs->direction, 0); ++ ret = regcache_sync_region(chip->regmap, regaddr, regaddr + NBANK(chip)); + if (ret) { + dev_err(dev, "Failed to sync GPIO dir registers: %d\n", ret); + return ret; + } + +- ret = regcache_sync_region(chip->regmap, chip->regs->output, +- chip->regs->output + NBANK(chip)); ++ regaddr = pca953x_recalc_addr(chip, chip->regs->output, 0); ++ ret = regcache_sync_region(chip->regmap, regaddr, regaddr + NBANK(chip)); + if (ret) { + dev_err(dev, "Failed to sync GPIO out registers: %d\n", ret); + return ret; +@@ -1129,16 +1130,18 @@ static int pca953x_regcache_sync(struct device *dev) + + #ifdef CONFIG_GPIO_PCA953X_IRQ + if (chip->driver_data & PCA_PCAL) { +- ret = regcache_sync_region(chip->regmap, PCAL953X_IN_LATCH, +- PCAL953X_IN_LATCH + NBANK(chip)); ++ regaddr = pca953x_recalc_addr(chip, PCAL953X_IN_LATCH, 0); ++ ret = regcache_sync_region(chip->regmap, regaddr, ++ regaddr + NBANK(chip)); + if (ret) { + dev_err(dev, "Failed to sync INT latch registers: %d\n", + ret); + return ret; + } + +- ret = regcache_sync_region(chip->regmap, PCAL953X_INT_MASK, +- PCAL953X_INT_MASK + NBANK(chip)); ++ regaddr = pca953x_recalc_addr(chip, PCAL953X_INT_MASK, 0); ++ ret = regcache_sync_region(chip->regmap, regaddr, ++ regaddr + NBANK(chip)); + if (ret) { + dev_err(dev, "Failed to sync INT mask registers: %d\n", + ret); +-- +2.35.1 + diff --git a/queue-5.15/iio-adc-ad7124-remove-shift-from-scan_type.patch b/queue-5.15/iio-adc-ad7124-remove-shift-from-scan_type.patch new file mode 100644 index 00000000000..4fd87c01d74 --- /dev/null +++ b/queue-5.15/iio-adc-ad7124-remove-shift-from-scan_type.patch @@ -0,0 +1,36 @@ +From 93b2576dc481c6c3bafc48fe35a317a190327ac0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 22 Mar 2022 12:50:24 +0200 +Subject: iio: adc: ad7124: Remove shift from scan_type + +From: Alexandru Tachici + +[ Upstream commit fe78ccf79b0e29fd6d8dc2e2c3b0dbeda4ce3ad8 ] + +The 24 bits data is stored in 32 bits in BE. There +is no need to shift it. This confuses user-space apps. + +Fixes: b3af341bbd966 ("iio: adc: Add ad7124 support") +Signed-off-by: Alexandru Tachici +Link: https://lore.kernel.org/r/20220322105029.86389-2-alexandru.tachici@analog.com +Signed-off-by: Jonathan Cameron +Signed-off-by: Sasha Levin +--- + drivers/iio/adc/ad7124.c | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/drivers/iio/adc/ad7124.c b/drivers/iio/adc/ad7124.c +index 18c154afbd7a..101f2da2811b 100644 +--- a/drivers/iio/adc/ad7124.c ++++ b/drivers/iio/adc/ad7124.c +@@ -188,7 +188,6 @@ static const struct iio_chan_spec ad7124_channel_template = { + .sign = 'u', + .realbits = 24, + .storagebits = 32, +- .shift = 8, + .endianness = IIO_BE, + }, + }; +-- +2.35.1 + diff --git a/queue-5.15/iio-adc-sc27xx-fine-tune-the-scale-calibration-value.patch b/queue-5.15/iio-adc-sc27xx-fine-tune-the-scale-calibration-value.patch new file mode 100644 index 00000000000..d53d111bf42 --- /dev/null +++ b/queue-5.15/iio-adc-sc27xx-fine-tune-the-scale-calibration-value.patch @@ -0,0 +1,64 @@ +From af7051a74799546319e4fcf82ad88a6d0913ec6b Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 19 Apr 2022 22:24:54 +0800 +Subject: iio: adc: sc27xx: Fine tune the scale calibration values + +From: Cixi Geng + +[ Upstream commit 5a7a184b11c6910f47600ff5cbbee34168f701a8 ] + +Small adjustment the scale calibration value for the sc2731, +use new name sc2731_[big|small]_scale_graph_calib, and remove +the origin [big|small]_scale_graph_calib struct for unused. + +Fixes: 8ba0dbfd07a35 (iio: adc: sc27xx: Add ADC scale calibration) +Signed-off-by: Cixi Geng +Link: https://lore.kernel.org/r/20220419142458.884933-4-gengcixi@gmail.com +Signed-off-by: Jonathan Cameron +Signed-off-by: Sasha Levin +--- + drivers/iio/adc/sc27xx_adc.c | 16 ++++++++-------- + 1 file changed, 8 insertions(+), 8 deletions(-) + +diff --git a/drivers/iio/adc/sc27xx_adc.c b/drivers/iio/adc/sc27xx_adc.c +index aee076c8e2b1..cfe003cc4f0b 100644 +--- a/drivers/iio/adc/sc27xx_adc.c ++++ b/drivers/iio/adc/sc27xx_adc.c +@@ -103,14 +103,14 @@ static struct sc27xx_adc_linear_graph small_scale_graph = { + 100, 341, + }; + +-static const struct sc27xx_adc_linear_graph big_scale_graph_calib = { +- 4200, 856, +- 3600, 733, ++static const struct sc27xx_adc_linear_graph sc2731_big_scale_graph_calib = { ++ 4200, 850, ++ 3600, 728, + }; + +-static const struct sc27xx_adc_linear_graph small_scale_graph_calib = { +- 1000, 833, +- 100, 80, ++static const struct sc27xx_adc_linear_graph sc2731_small_scale_graph_calib = { ++ 1000, 838, ++ 100, 84, + }; + + static int sc27xx_adc_get_calib_data(u32 calib_data, int calib_adc) +@@ -130,11 +130,11 @@ static int sc27xx_adc_scale_calibration(struct sc27xx_adc_data *data, + size_t len; + + if (big_scale) { +- calib_graph = &big_scale_graph_calib; ++ calib_graph = &sc2731_big_scale_graph_calib; + graph = &big_scale_graph; + cell_name = "big_scale_calib"; + } else { +- calib_graph = &small_scale_graph_calib; ++ calib_graph = &sc2731_small_scale_graph_calib; + graph = &small_scale_graph; + cell_name = "small_scale_calib"; + } +-- +2.35.1 + diff --git a/queue-5.15/iio-adc-sc27xx-fix-read-big-scale-voltage-not-right.patch b/queue-5.15/iio-adc-sc27xx-fix-read-big-scale-voltage-not-right.patch new file mode 100644 index 00000000000..92b42329178 --- /dev/null +++ b/queue-5.15/iio-adc-sc27xx-fix-read-big-scale-voltage-not-right.patch @@ -0,0 +1,40 @@ +From 28ac2045bc39d87d61a281911f14b62243b589e5 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 19 Apr 2022 22:24:53 +0800 +Subject: iio: adc: sc27xx: fix read big scale voltage not right + +From: Cixi Geng + +[ Upstream commit ad930a75613282400179361e220e58b87386b8c7 ] + +Fix wrong configuration value of SC27XX_ADC_SCALE_MASK and +SC27XX_ADC_SCALE_SHIFT by spec documetation. + +Fixes: 5df362a6cf49c (iio: adc: Add Spreadtrum SC27XX PMICs ADC support) +Signed-off-by: Cixi Geng +Reviewed-by: Baolin Wang +Link: https://lore.kernel.org/r/20220419142458.884933-3-gengcixi@gmail.com +Signed-off-by: Jonathan Cameron +Signed-off-by: Sasha Levin +--- + drivers/iio/adc/sc27xx_adc.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/drivers/iio/adc/sc27xx_adc.c b/drivers/iio/adc/sc27xx_adc.c +index 00098caf6d9e..aee076c8e2b1 100644 +--- a/drivers/iio/adc/sc27xx_adc.c ++++ b/drivers/iio/adc/sc27xx_adc.c +@@ -36,8 +36,8 @@ + + /* Bits and mask definition for SC27XX_ADC_CH_CFG register */ + #define SC27XX_ADC_CHN_ID_MASK GENMASK(4, 0) +-#define SC27XX_ADC_SCALE_MASK GENMASK(10, 8) +-#define SC27XX_ADC_SCALE_SHIFT 8 ++#define SC27XX_ADC_SCALE_MASK GENMASK(10, 9) ++#define SC27XX_ADC_SCALE_SHIFT 9 + + /* Bits definitions for SC27XX_ADC_INT_EN registers */ + #define SC27XX_ADC_IRQ_EN BIT(0) +-- +2.35.1 + diff --git a/queue-5.15/iio-adc-stmpe-adc-fix-wait_for_completion_timeout-re.patch b/queue-5.15/iio-adc-stmpe-adc-fix-wait_for_completion_timeout-re.patch new file mode 100644 index 00000000000..3ad7224ed5a --- /dev/null +++ b/queue-5.15/iio-adc-stmpe-adc-fix-wait_for_completion_timeout-re.patch @@ -0,0 +1,68 @@ +From 74e7cc461c0ddbc4d467976cd17a4639b8c1e4cb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 06:51:45 +0000 +Subject: iio: adc: stmpe-adc: Fix wait_for_completion_timeout return value + check + +From: Miaoqian Lin + +[ Upstream commit d345b23200bcdbd2bd3582213d738c258b77718f ] + +wait_for_completion_timeout() returns unsigned long not long. +it returns 0 if timed out, and positive if completed. +The check for <= 0 is ambiguous and should be == 0 here +indicating timeout which is the only error case + +Fixes: e813dde6f833 ("iio: stmpe-adc: Use wait_for_completion_timeout") +Signed-off-by: Miaoqian Lin +Reviewed-by: Philippe Schenker +Link: https://lore.kernel.org/r/20220412065150.14486-1-linmq006@gmail.com +Signed-off-by: Jonathan Cameron +Signed-off-by: Sasha Levin +--- + drivers/iio/adc/stmpe-adc.c | 8 ++++---- + 1 file changed, 4 insertions(+), 4 deletions(-) + +diff --git a/drivers/iio/adc/stmpe-adc.c b/drivers/iio/adc/stmpe-adc.c +index fba659bfdb40..64305d9fa560 100644 +--- a/drivers/iio/adc/stmpe-adc.c ++++ b/drivers/iio/adc/stmpe-adc.c +@@ -61,7 +61,7 @@ struct stmpe_adc { + static int stmpe_read_voltage(struct stmpe_adc *info, + struct iio_chan_spec const *chan, int *val) + { +- long ret; ++ unsigned long ret; + + mutex_lock(&info->lock); + +@@ -79,7 +79,7 @@ static int stmpe_read_voltage(struct stmpe_adc *info, + + ret = wait_for_completion_timeout(&info->completion, STMPE_ADC_TIMEOUT); + +- if (ret <= 0) { ++ if (ret == 0) { + stmpe_reg_write(info->stmpe, STMPE_REG_ADC_INT_STA, + STMPE_ADC_CH(info->channel)); + mutex_unlock(&info->lock); +@@ -96,7 +96,7 @@ static int stmpe_read_voltage(struct stmpe_adc *info, + static int stmpe_read_temp(struct stmpe_adc *info, + struct iio_chan_spec const *chan, int *val) + { +- long ret; ++ unsigned long ret; + + mutex_lock(&info->lock); + +@@ -114,7 +114,7 @@ static int stmpe_read_temp(struct stmpe_adc *info, + + ret = wait_for_completion_timeout(&info->completion, STMPE_ADC_TIMEOUT); + +- if (ret <= 0) { ++ if (ret == 0) { + mutex_unlock(&info->lock); + return -ETIMEDOUT; + } +-- +2.35.1 + diff --git a/queue-5.15/iio-proximity-vl53l0x-fix-return-value-check-of-wait.patch b/queue-5.15/iio-proximity-vl53l0x-fix-return-value-check-of-wait.patch new file mode 100644 index 00000000000..8de12329115 --- /dev/null +++ b/queue-5.15/iio-proximity-vl53l0x-fix-return-value-check-of-wait.patch @@ -0,0 +1,52 @@ +From 549f9beb10de99b5846dcb8d039bab6593c1d691 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 06:42:09 +0000 +Subject: iio: proximity: vl53l0x: Fix return value check of + wait_for_completion_timeout + +From: Miaoqian Lin + +[ Upstream commit 50f2959113cb6756ffd73c4fedc712cf2661f711 ] + +wait_for_completion_timeout() returns unsigned long not int. +It returns 0 if timed out, and positive if completed. +The check for <= 0 is ambiguous and should be == 0 here +indicating timeout which is the only error case. + +Fixes: 3cef2e31b54b ("iio: proximity: vl53l0x: Add IRQ support") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220412064210.10734-1-linmq006@gmail.com +Signed-off-by: Jonathan Cameron +Signed-off-by: Sasha Levin +--- + drivers/iio/proximity/vl53l0x-i2c.c | 7 +++---- + 1 file changed, 3 insertions(+), 4 deletions(-) + +diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c +index cf38144b6f95..13a87d3e3544 100644 +--- a/drivers/iio/proximity/vl53l0x-i2c.c ++++ b/drivers/iio/proximity/vl53l0x-i2c.c +@@ -104,6 +104,7 @@ static int vl53l0x_read_proximity(struct vl53l0x_data *data, + u16 tries = 20; + u8 buffer[12]; + int ret; ++ unsigned long time_left; + + ret = i2c_smbus_write_byte_data(client, VL_REG_SYSRANGE_START, 1); + if (ret < 0) +@@ -112,10 +113,8 @@ static int vl53l0x_read_proximity(struct vl53l0x_data *data, + if (data->client->irq) { + reinit_completion(&data->completion); + +- ret = wait_for_completion_timeout(&data->completion, HZ/10); +- if (ret < 0) +- return ret; +- else if (ret == 0) ++ time_left = wait_for_completion_timeout(&data->completion, HZ/10); ++ if (time_left == 0) + return -ETIMEDOUT; + + vl53l0x_clear_irq(data); +-- +2.35.1 + diff --git a/queue-5.15/jffs2-fix-memory-leak-in-jffs2_do_fill_super.patch b/queue-5.15/jffs2-fix-memory-leak-in-jffs2_do_fill_super.patch new file mode 100644 index 00000000000..0474ae48e80 --- /dev/null +++ b/queue-5.15/jffs2-fix-memory-leak-in-jffs2_do_fill_super.patch @@ -0,0 +1,68 @@ +From 455ecd1558632ebc55b98d2abe87e2dd42bb2e1f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 17:38:16 +0800 +Subject: jffs2: fix memory leak in jffs2_do_fill_super + +From: Baokun Li + +[ Upstream commit c14adb1cf70a984ed081c67e9d27bc3caad9537c ] + +If jffs2_iget() or d_make_root() in jffs2_do_fill_super() returns +an error, we can observe the following kmemleak report: + +-------------------------------------------- +unreferenced object 0xffff888105a65340 (size 64): + comm "mount", pid 710, jiffies 4302851558 (age 58.239s) + hex dump (first 32 bytes): + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ + backtrace: + [] kmem_cache_alloc_trace+0x475/0x8a0 + [] jffs2_sum_init+0x96/0x1a0 + [] jffs2_do_mount_fs+0x745/0x2120 + [] jffs2_do_fill_super+0x35c/0x810 + [] jffs2_fill_super+0x2b9/0x3b0 + [...] +unreferenced object 0xffff8881bd7f0000 (size 65536): + comm "mount", pid 710, jiffies 4302851558 (age 58.239s) + hex dump (first 32 bytes): + bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb ................ + bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb ................ + backtrace: + [] kmalloc_order+0xda/0x110 + [] kmalloc_order_trace+0x21/0x130 + [] __kmalloc+0x711/0x8a0 + [] jffs2_sum_init+0xd9/0x1a0 + [] jffs2_do_mount_fs+0x745/0x2120 + [] jffs2_do_fill_super+0x35c/0x810 + [] jffs2_fill_super+0x2b9/0x3b0 + [...] +-------------------------------------------- + +This is because the resources allocated in jffs2_sum_init() are not +released. Call jffs2_sum_exit() to release these resources to solve +the problem. + +Fixes: e631ddba5887 ("[JFFS2] Add erase block summary support (mount time improvement)") +Signed-off-by: Baokun Li +Signed-off-by: Richard Weinberger +Signed-off-by: Sasha Levin +--- + fs/jffs2/fs.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/fs/jffs2/fs.c b/fs/jffs2/fs.c +index 71f03a5d36ed..f83a468b6488 100644 +--- a/fs/jffs2/fs.c ++++ b/fs/jffs2/fs.c +@@ -604,6 +604,7 @@ int jffs2_do_fill_super(struct super_block *sb, struct fs_context *fc) + jffs2_free_raw_node_refs(c); + kvfree(c->blocks); + jffs2_clear_xattr_subsystem(c); ++ jffs2_sum_exit(c); + out_inohash: + kfree(c->inocache_list); + out_wbuf: +-- +2.35.1 + diff --git a/queue-5.15/ksmbd-fix-reference-count-leak-in-smb_check_perm_dac.patch b/queue-5.15/ksmbd-fix-reference-count-leak-in-smb_check_perm_dac.patch new file mode 100644 index 00000000000..2d9d70355e9 --- /dev/null +++ b/queue-5.15/ksmbd-fix-reference-count-leak-in-smb_check_perm_dac.patch @@ -0,0 +1,43 @@ +From 5241acb604cef37bed84caa5a7de38889b6d684e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 29 Apr 2022 16:11:22 +0800 +Subject: ksmbd: fix reference count leak in smb_check_perm_dacl() + +From: Xin Xiong + +[ Upstream commit d21a580dafc69aa04f46e6099616146a536b0724 ] + +The issue happens in a specific path in smb_check_perm_dacl(). When +"id" and "uid" have the same value, the function simply jumps out of +the loop without decrementing the reference count of the object +"posix_acls", which is increased by get_acl() earlier. This may +result in memory leaks. + +Fix it by decreasing the reference count of "posix_acls" before +jumping to label "check_access_bits". + +Fixes: 777cad1604d6 ("ksmbd: remove select FS_POSIX_ACL in Kconfig") +Signed-off-by: Xin Xiong +Signed-off-by: Xin Tan +Acked-by: Namjae Jeon +Signed-off-by: Steve French +Signed-off-by: Sasha Levin +--- + fs/ksmbd/smbacl.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/fs/ksmbd/smbacl.c b/fs/ksmbd/smbacl.c +index bd792db32623..7e57ffdb4ce3 100644 +--- a/fs/ksmbd/smbacl.c ++++ b/fs/ksmbd/smbacl.c +@@ -1274,6 +1274,7 @@ int smb_check_perm_dacl(struct ksmbd_conn *conn, struct path *path, + if (!access_bits) + access_bits = + SET_MINIMUM_RIGHTS; ++ posix_acl_release(posix_acls); + goto check_access_bits; + } + } +-- +2.35.1 + diff --git a/queue-5.15/lkdtm-bugs-check-for-the-null-pointer-after-calling-.patch b/queue-5.15/lkdtm-bugs-check-for-the-null-pointer-after-calling-.patch new file mode 100644 index 00000000000..09ba7b36a97 --- /dev/null +++ b/queue-5.15/lkdtm-bugs-check-for-the-null-pointer-after-calling-.patch @@ -0,0 +1,47 @@ +From 16c5bf2ebb89e7adfbe394f645f7e561f8323607 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 20 Jan 2022 17:29:36 +0800 +Subject: lkdtm/bugs: Check for the NULL pointer after calling kmalloc + +From: Jiasheng Jiang + +[ Upstream commit 4a9800c81d2f34afb66b4b42e0330ae8298019a2 ] + +As the possible failure of the kmalloc(), the not_checked and checked +could be NULL pointer. +Therefore, it should be better to check it in order to avoid the +dereference of the NULL pointer. +Also, we need to kfree the 'not_checked' and 'checked' to avoid +the memory leak if fails. +And since it is just a test, it may directly return without error +number. + +Fixes: ae2e1aad3e48 ("drivers/misc/lkdtm/bugs.c: add arithmetic overflow and array bounds checks") +Signed-off-by: Jiasheng Jiang +Acked-by: Dan Carpenter +Signed-off-by: Kees Cook +Link: https://lore.kernel.org/r/20220120092936.1874264-1-jiasheng@iscas.ac.cn +Signed-off-by: Sasha Levin +--- + drivers/misc/lkdtm/bugs.c | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/drivers/misc/lkdtm/bugs.c b/drivers/misc/lkdtm/bugs.c +index 4282b625200f..072e3b742edf 100644 +--- a/drivers/misc/lkdtm/bugs.c ++++ b/drivers/misc/lkdtm/bugs.c +@@ -248,6 +248,11 @@ void lkdtm_ARRAY_BOUNDS(void) + + not_checked = kmalloc(sizeof(*not_checked) * 2, GFP_KERNEL); + checked = kmalloc(sizeof(*checked) * 2, GFP_KERNEL); ++ if (!not_checked || !checked) { ++ kfree(not_checked); ++ kfree(checked); ++ return; ++ } + + pr_info("Array access within bounds ...\n"); + /* For both, touch all bytes in the actual member size. */ +-- +2.35.1 + diff --git a/queue-5.15/lkdtm-bugs-don-t-expect-thread-termination-without-c.patch b/queue-5.15/lkdtm-bugs-don-t-expect-thread-termination-without-c.patch new file mode 100644 index 00000000000..542ffdaac23 --- /dev/null +++ b/queue-5.15/lkdtm-bugs-don-t-expect-thread-termination-without-c.patch @@ -0,0 +1,100 @@ +From dfc686914f909f88c98af9f3ad5b57c550773344 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 11 Apr 2022 21:13:39 +0200 +Subject: lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP + +From: Christophe Leroy + +[ Upstream commit 8bfdbddd68249e0d8598777cca8249619ee51df0 ] + +When you don't select CONFIG_UBSAN_TRAP, you get: + + # echo ARRAY_BOUNDS > /sys/kernel/debug/provoke-crash/DIRECT +[ 102.265827] ================================================================================ +[ 102.278433] UBSAN: array-index-out-of-bounds in drivers/misc/lkdtm/bugs.c:342:16 +[ 102.287207] index 8 is out of range for type 'char [8]' +[ 102.298722] ================================================================================ +[ 102.313712] lkdtm: FAIL: survived array bounds overflow! +[ 102.318770] lkdtm: Unexpected! This kernel (5.16.0-rc1-s3k-dev-01884-g720dcf79314a ppc) was built with CONFIG_UBSAN_BOUNDS=y + +It is not correct because when CONFIG_UBSAN_TRAP is not selected +you can't expect array bounds overflow to kill the thread. + +Modify the logic so that when the kernel is built with +CONFIG_UBSAN_BOUNDS but without CONFIG_UBSAN_TRAP, you get a warning +about CONFIG_UBSAN_TRAP not been selected instead. + +This also require a fix of pr_expected_config(), otherwise the +following error is encountered. + + CC drivers/misc/lkdtm/bugs.o +drivers/misc/lkdtm/bugs.c: In function 'lkdtm_ARRAY_BOUNDS': +drivers/misc/lkdtm/bugs.c:351:2: error: 'else' without a previous 'if' + 351 | else + | ^~~~ + +Fixes: c75be56e35b2 ("lkdtm/bugs: Add ARRAY_BOUNDS to selftests") +Signed-off-by: Christophe Leroy +Signed-off-by: Kees Cook +Link: https://lore.kernel.org/r/363b58690e907c677252467a94fe49444c80ea76.1649704381.git.christophe.leroy@csgroup.eu +Signed-off-by: Sasha Levin +--- + drivers/misc/lkdtm/bugs.c | 5 ++++- + drivers/misc/lkdtm/lkdtm.h | 8 ++++---- + 2 files changed, 8 insertions(+), 5 deletions(-) + +diff --git a/drivers/misc/lkdtm/bugs.c b/drivers/misc/lkdtm/bugs.c +index 072e3b742edf..fac4a811b97b 100644 +--- a/drivers/misc/lkdtm/bugs.c ++++ b/drivers/misc/lkdtm/bugs.c +@@ -272,7 +272,10 @@ void lkdtm_ARRAY_BOUNDS(void) + kfree(not_checked); + kfree(checked); + pr_err("FAIL: survived array bounds overflow!\n"); +- pr_expected_config(CONFIG_UBSAN_BOUNDS); ++ if (IS_ENABLED(CONFIG_UBSAN_BOUNDS)) ++ pr_expected_config(CONFIG_UBSAN_TRAP); ++ else ++ pr_expected_config(CONFIG_UBSAN_BOUNDS); + } + + void lkdtm_CORRUPT_LIST_ADD(void) +diff --git a/drivers/misc/lkdtm/lkdtm.h b/drivers/misc/lkdtm/lkdtm.h +index c212a253edde..ef9a24aabfc3 100644 +--- a/drivers/misc/lkdtm/lkdtm.h ++++ b/drivers/misc/lkdtm/lkdtm.h +@@ -9,19 +9,19 @@ + extern char *lkdtm_kernel_info; + + #define pr_expected_config(kconfig) \ +-{ \ ++do { \ + if (IS_ENABLED(kconfig)) \ + pr_err("Unexpected! This %s was built with " #kconfig "=y\n", \ + lkdtm_kernel_info); \ + else \ + pr_warn("This is probably expected, since this %s was built *without* " #kconfig "=y\n", \ + lkdtm_kernel_info); \ +-} ++} while (0) + + #ifndef MODULE + int lkdtm_check_bool_cmdline(const char *param); + #define pr_expected_config_param(kconfig, param) \ +-{ \ ++do { \ + if (IS_ENABLED(kconfig)) { \ + switch (lkdtm_check_bool_cmdline(param)) { \ + case 0: \ +@@ -52,7 +52,7 @@ int lkdtm_check_bool_cmdline(const char *param); + break; \ + } \ + } \ +-} ++} while (0) + #else + #define pr_expected_config_param(kconfig, param) pr_expected_config(kconfig) + #endif +-- +2.35.1 + diff --git a/queue-5.15/misc-fastrpc-fix-an-incorrect-null-check-on-list-ite.patch b/queue-5.15/misc-fastrpc-fix-an-incorrect-null-check-on-list-ite.patch new file mode 100644 index 00000000000..b2e125ccd37 --- /dev/null +++ b/queue-5.15/misc-fastrpc-fix-an-incorrect-null-check-on-list-ite.patch @@ -0,0 +1,60 @@ +From 4c2b5f78f27c3e9faf8b7b974c3aaed844c19456 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 27 Mar 2022 14:22:02 +0800 +Subject: misc: fastrpc: fix an incorrect NULL check on list iterator + +From: Xiaomeng Tong + +[ Upstream commit 5ac11fe03a0a83042d1a040dbce4fa2fb5521e23 ] + +The bug is here: + if (!buf) { + +The list iterator value 'buf' will *always* be set and non-NULL +by list_for_each_entry(), so it is incorrect to assume that the +iterator value will be NULL if the list is empty (in this case, the +check 'if (!buf) {' will always be false and never exit expectly). + +To fix the bug, use a new variable 'iter' as the list iterator, +while use the original variable 'buf' as a dedicated pointer to +point to the found element. + +Fixes: 2419e55e532de ("misc: fastrpc: add mmap/unmap support") +Signed-off-by: Xiaomeng Tong +Link: https://lore.kernel.org/r/20220327062202.5720-1-xiam0nd.tong@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/misc/fastrpc.c | 9 +++++---- + 1 file changed, 5 insertions(+), 4 deletions(-) + +diff --git a/drivers/misc/fastrpc.c b/drivers/misc/fastrpc.c +index 86d8fb8c0148..c7134d2cf69a 100644 +--- a/drivers/misc/fastrpc.c ++++ b/drivers/misc/fastrpc.c +@@ -1351,17 +1351,18 @@ static int fastrpc_req_munmap_impl(struct fastrpc_user *fl, + struct fastrpc_req_munmap *req) + { + struct fastrpc_invoke_args args[1] = { [0] = { 0 } }; +- struct fastrpc_buf *buf, *b; ++ struct fastrpc_buf *buf = NULL, *iter, *b; + struct fastrpc_munmap_req_msg req_msg; + struct device *dev = fl->sctx->dev; + int err; + u32 sc; + + spin_lock(&fl->lock); +- list_for_each_entry_safe(buf, b, &fl->mmaps, node) { +- if ((buf->raddr == req->vaddrout) && (buf->size == req->size)) ++ list_for_each_entry_safe(iter, b, &fl->mmaps, node) { ++ if ((iter->raddr == req->vaddrout) && (iter->size == req->size)) { ++ buf = iter; + break; +- buf = NULL; ++ } + } + spin_unlock(&fl->lock); + +-- +2.35.1 + diff --git a/queue-5.15/misc-pvpanic-convert-regular-spinlock-into-trylock-o.patch b/queue-5.15/misc-pvpanic-convert-regular-spinlock-into-trylock-o.patch new file mode 100644 index 00000000000..04664d3a017 --- /dev/null +++ b/queue-5.15/misc-pvpanic-convert-regular-spinlock-into-trylock-o.patch @@ -0,0 +1,71 @@ +From 2d3dd77beac17d54dd28a510721d0d0dc3d462fb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 27 Apr 2022 19:48:59 -0300 +Subject: misc/pvpanic: Convert regular spinlock into trylock on panic path + +From: Guilherme G. Piccoli + +[ Upstream commit e918c10265ef2bc82ce8a6fed6d8123d09ec1db3 ] + +The pvpanic driver relies on panic notifiers to execute a callback +on panic event. Such function is executed in atomic context - the +panic function disables local IRQs, preemption and all other CPUs +that aren't running the panic code. + +With that said, it's dangerous to use regular spinlocks in such path, +as introduced by commit b3c0f8774668 ("misc/pvpanic: probe multiple instances"). +This patch fixes that by replacing regular spinlocks with the trylock +safer approach. + +It also fixes an old comment (about a long gone framebuffer code) and +the notifier priority - we should execute hypervisor notifiers early, +deferring this way the panic action to the hypervisor, as expected by +the users that are setting up pvpanic. + +Fixes: b3c0f8774668 ("misc/pvpanic: probe multiple instances") +Cc: Christophe JAILLET +Cc: Mihai Carabas +Cc: Shile Zhang +Cc: Wang ShaoBo +Cc: zhenwei pi +Signed-off-by: Guilherme G. Piccoli +Link: https://lore.kernel.org/r/20220427224924.592546-6-gpiccoli@igalia.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/misc/pvpanic/pvpanic.c | 10 ++++++++-- + 1 file changed, 8 insertions(+), 2 deletions(-) + +diff --git a/drivers/misc/pvpanic/pvpanic.c b/drivers/misc/pvpanic/pvpanic.c +index 700d7d02c800..b9e6400a574b 100644 +--- a/drivers/misc/pvpanic/pvpanic.c ++++ b/drivers/misc/pvpanic/pvpanic.c +@@ -34,7 +34,9 @@ pvpanic_send_event(unsigned int event) + { + struct pvpanic_instance *pi_cur; + +- spin_lock(&pvpanic_lock); ++ if (!spin_trylock(&pvpanic_lock)) ++ return; ++ + list_for_each_entry(pi_cur, &pvpanic_list, list) { + if (event & pi_cur->capability & pi_cur->events) + iowrite8(event, pi_cur->base); +@@ -56,9 +58,13 @@ pvpanic_panic_notify(struct notifier_block *nb, unsigned long code, + return NOTIFY_DONE; + } + ++/* ++ * Call our notifier very early on panic, deferring the ++ * action taken to the hypervisor. ++ */ + static struct notifier_block pvpanic_panic_nb = { + .notifier_call = pvpanic_panic_notify, +- .priority = 1, /* let this called before broken drm_fb_helper() */ ++ .priority = INT_MAX, + }; + + static void pvpanic_remove(void *param) +-- +2.35.1 + diff --git a/queue-5.15/modpost-fix-removing-numeric-suffixes.patch b/queue-5.15/modpost-fix-removing-numeric-suffixes.patch new file mode 100644 index 00000000000..014411076f8 --- /dev/null +++ b/queue-5.15/modpost-fix-removing-numeric-suffixes.patch @@ -0,0 +1,58 @@ +From 7f86a91445e190c529e6c83f3a9451bef769ee08 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 24 May 2022 17:27:18 +0200 +Subject: modpost: fix removing numeric suffixes + +From: Alexander Lobakin + +[ Upstream commit b5beffa20d83c4e15306c991ffd00de0d8628338 ] + +With the `-z unique-symbol` linker flag or any similar mechanism, +it is possible to trigger the following: + +ERROR: modpost: "param_set_uint.0" [vmlinux] is a static EXPORT_SYMBOL + +The reason is that for now the condition from remove_dot(): + +if (m && (s[n + m] == '.' || s[n + m] == 0)) + +which was designed to test if it's a dot or a '\0' after the suffix +is never satisfied. +This is due to that `s[n + m]` always points to the last digit of a +numeric suffix, not on the symbol next to it (from a custom debug +print added to modpost): + +param_set_uint.0, s[n + m] is '0', s[n + m + 1] is '\0' + +So it's off-by-one and was like that since 2014. + +Fix this for the sake of any potential upcoming features, but don't +bother stable-backporting, as it's well hidden -- apart from that +LD flag, it can be triggered only with GCC LTO which never landed +upstream. + +Fixes: fcd38ed0ff26 ("scripts: modpost: fix compilation warning") +Signed-off-by: Alexander Lobakin +Reviewed-by: Petr Mladek +Signed-off-by: Masahiro Yamada +Signed-off-by: Sasha Levin +--- + scripts/mod/modpost.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c +index ca491aa2b376..7a5bddb8913e 100644 +--- a/scripts/mod/modpost.c ++++ b/scripts/mod/modpost.c +@@ -1971,7 +1971,7 @@ static char *remove_dot(char *s) + + if (n && s[n]) { + size_t m = strspn(s + n + 1, "0123456789"); +- if (m && (s[n + m] == '.' || s[n + m] == 0)) ++ if (m && (s[n + m + 1] == '.' || s[n + m + 1] == 0)) + s[n] = 0; + + /* strip trailing .lto */ +-- +2.35.1 + diff --git a/queue-5.15/net-dsa-mv88e6xxx-fix-refcount-leak-in-mv88e6xxx_mdi.patch b/queue-5.15/net-dsa-mv88e6xxx-fix-refcount-leak-in-mv88e6xxx_mdi.patch new file mode 100644 index 00000000000..18a9b237dd2 --- /dev/null +++ b/queue-5.15/net-dsa-mv88e6xxx-fix-refcount-leak-in-mv88e6xxx_mdi.patch @@ -0,0 +1,44 @@ +From 0c1e0c3d7b857075a25e58e18028dcb3a1a75485 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 26 May 2022 18:52:08 +0400 +Subject: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Miaoqian Lin + +[ Upstream commit 02ded5a173619b11728b8bf75a3fd995a2c1ff28 ] + +of_get_child_by_name() returns a node pointer with refcount +incremented, we should use of_node_put() on it when done. + +mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register(). +We don't need the device node after it. + +Add missing of_node_put() to avoid refcount leak. + +Fixes: a3c53be55c95 ("net: dsa: mv88e6xxx: Support multiple MDIO busses") +Signed-off-by: Miaoqian Lin +Reviewed-by: Marek Behún +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/dsa/mv88e6xxx/chip.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c +index 0830d7bb7a00..f9efd0c8bab8 100644 +--- a/drivers/net/dsa/mv88e6xxx/chip.c ++++ b/drivers/net/dsa/mv88e6xxx/chip.c +@@ -3492,6 +3492,7 @@ static int mv88e6xxx_mdios_register(struct mv88e6xxx_chip *chip, + */ + child = of_get_child_by_name(np, "mdio"); + err = mv88e6xxx_mdio_register(chip, child, false); ++ of_node_put(child); + if (err) + return err; + +-- +2.35.1 + diff --git a/queue-5.15/net-ethernet-mtk_eth_soc-out-of-bounds-read-in-mtk_h.patch b/queue-5.15/net-ethernet-mtk_eth_soc-out-of-bounds-read-in-mtk_h.patch new file mode 100644 index 00000000000..609719fb6c8 --- /dev/null +++ b/queue-5.15/net-ethernet-mtk_eth_soc-out-of-bounds-read-in-mtk_h.patch @@ -0,0 +1,38 @@ +From c8c20cc17322296204cf599d77ee004638b4ec97 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 26 May 2022 11:02:42 +0300 +Subject: net: ethernet: mtk_eth_soc: out of bounds read in + mtk_hwlro_get_fdir_entry() + +From: Dan Carpenter + +[ Upstream commit e7e7104e2d5ddf3806a28695670f21bef471f1e1 ] + +The "fsp->location" variable comes from user via ethtool_get_rxnfc(). +Check that it is valid to prevent an out of bounds read. + +Fixes: 7aab747e5563 ("net: ethernet: mediatek: add ethtool functions to configure RX flows of HW LRO") +Signed-off-by: Dan Carpenter +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/mediatek/mtk_eth_soc.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/drivers/net/ethernet/mediatek/mtk_eth_soc.c b/drivers/net/ethernet/mediatek/mtk_eth_soc.c +index ee1fd472e925..d2d7160b789c 100644 +--- a/drivers/net/ethernet/mediatek/mtk_eth_soc.c ++++ b/drivers/net/ethernet/mediatek/mtk_eth_soc.c +@@ -1991,6 +1991,9 @@ static int mtk_hwlro_get_fdir_entry(struct net_device *dev, + struct ethtool_rx_flow_spec *fsp = + (struct ethtool_rx_flow_spec *)&cmd->fs; + ++ if (fsp->location >= ARRAY_SIZE(mac->hwlro_ip)) ++ return -EINVAL; ++ + /* only tcp dst ipv4 is meaningful, others are meaningless */ + fsp->flow_type = TCP_V4_FLOW; + fsp->h_u.tcp_ip4_spec.ip4dst = ntohl(mac->hwlro_ip[fsp->location]); +-- +2.35.1 + diff --git a/queue-5.15/net-ethernet-ti-am65-cpsw-nuss-fix-some-refcount-lea.patch b/queue-5.15/net-ethernet-ti-am65-cpsw-nuss-fix-some-refcount-lea.patch new file mode 100644 index 00000000000..0a2bbda14ec --- /dev/null +++ b/queue-5.15/net-ethernet-ti-am65-cpsw-nuss-fix-some-refcount-lea.patch @@ -0,0 +1,50 @@ +From 4b44a3c28792618d02bd28933dac8e3fac0fa2cb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 26 May 2022 12:52:08 +0400 +Subject: net: ethernet: ti: am65-cpsw-nuss: Fix some refcount leaks + +From: Miaoqian Lin + +[ Upstream commit 5dd89d2fc438457811cbbec07999ce0d80051ff5 ] + +of_get_child_by_name() returns a node pointer with refcount +incremented, we should use of_node_put() on it when not need anymore. +am65_cpsw_init_cpts() and am65_cpsw_nuss_probe() don't release +the refcount in error case. +Add missing of_node_put() to avoid refcount leak. + +Fixes: b1f66a5bee07 ("net: ethernet: ti: am65-cpsw-nuss: enable packet timestamping support") +Fixes: 93a76530316a ("net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver") +Signed-off-by: Miaoqian Lin +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/ti/am65-cpsw-nuss.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/ti/am65-cpsw-nuss.c b/drivers/net/ethernet/ti/am65-cpsw-nuss.c +index 130346f74ee8..ea9d073e87fa 100644 +--- a/drivers/net/ethernet/ti/am65-cpsw-nuss.c ++++ b/drivers/net/ethernet/ti/am65-cpsw-nuss.c +@@ -1802,6 +1802,7 @@ static int am65_cpsw_init_cpts(struct am65_cpsw_common *common) + if (IS_ERR(cpts)) { + int ret = PTR_ERR(cpts); + ++ of_node_put(node); + if (ret == -EOPNOTSUPP) { + dev_info(dev, "cpts disabled\n"); + return 0; +@@ -2668,9 +2669,9 @@ static int am65_cpsw_nuss_probe(struct platform_device *pdev) + if (!node) + return -ENOENT; + common->port_num = of_get_child_count(node); ++ of_node_put(node); + if (common->port_num < 1 || common->port_num > AM65_CPSW_MAX_PORTS) + return -ENOENT; +- of_node_put(node); + + common->rx_flow_id_base = -1; + init_completion(&common->tdown_complete); +-- +2.35.1 + diff --git a/queue-5.15/net-mlx5-correct-ece-offset-in-query-qp-output.patch b/queue-5.15/net-mlx5-correct-ece-offset-in-query-qp-output.patch new file mode 100644 index 00000000000..afe2f54bb07 --- /dev/null +++ b/queue-5.15/net-mlx5-correct-ece-offset-in-query-qp-output.patch @@ -0,0 +1,41 @@ +From 183dad0af5117d4fe4dc0f0166f84d8ffc704bef Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 26 Apr 2022 21:28:14 +0800 +Subject: net/mlx5: correct ECE offset in query qp output + +From: Changcheng Liu + +[ Upstream commit 3fc2a9e89b3508a5cc0c324f26d7b4740ba8c456 ] + +ECE field should be after opt_param_mask in query qp output. + +Fixes: 6b646a7e4af6 ("net/mlx5: Add ability to read and write ECE options") +Signed-off-by: Changcheng Liu +Signed-off-by: Saeed Mahameed +Signed-off-by: Sasha Levin +--- + include/linux/mlx5/mlx5_ifc.h | 5 ++--- + 1 file changed, 2 insertions(+), 3 deletions(-) + +diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h +index fdf4589ab4d4..cd9d1c95129e 100644 +--- a/include/linux/mlx5/mlx5_ifc.h ++++ b/include/linux/mlx5/mlx5_ifc.h +@@ -5028,12 +5028,11 @@ struct mlx5_ifc_query_qp_out_bits { + + u8 syndrome[0x20]; + +- u8 reserved_at_40[0x20]; +- u8 ece[0x20]; ++ u8 reserved_at_40[0x40]; + + u8 opt_param_mask[0x20]; + +- u8 reserved_at_a0[0x20]; ++ u8 ece[0x20]; + + struct mlx5_ifc_qpc_bits qpc; + +-- +2.35.1 + diff --git a/queue-5.15/net-mlx5-ct-fix-header-rewrite-re-use-for-tupels.patch b/queue-5.15/net-mlx5-ct-fix-header-rewrite-re-use-for-tupels.patch new file mode 100644 index 00000000000..3c875d09328 --- /dev/null +++ b/queue-5.15/net-mlx5-ct-fix-header-rewrite-re-use-for-tupels.patch @@ -0,0 +1,81 @@ +From 35b84fd529c1a6a73575624e14f91fc3557d483c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 23 May 2022 19:12:21 +0300 +Subject: net/mlx5: CT: Fix header-rewrite re-use for tupels + +From: Paul Blakey + +[ Upstream commit 1f2856cde64baa78475e6d3c601fb7b7f693a161 ] + +Tuple entries that don't have nat configured for them +which are added to the ct nat table will always create +a new modify header, as we don't check for possible +re-use on them. The same for tuples that have nat configured +for them but are added to ct table. + +Fix the above by only avoiding wasteful re-use lookup +for actually natted entries in ct nat table. + +Fixes: 7fac5c2eced3 ("net/mlx5: CT: Avoid reusing modify header context for natted entries") +Signed-off-by: Paul Blakey +Reviewed-by: Ariel Levkovich +Signed-off-by: Saeed Mahameed +Signed-off-by: Sasha Levin +--- + .../ethernet/mellanox/mlx5/core/en/tc_ct.c | 19 +++++++++++-------- + 1 file changed, 11 insertions(+), 8 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c b/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c +index d4b7b4d73b08..94200f2dd92b 100644 +--- a/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c ++++ b/drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c +@@ -650,7 +650,7 @@ mlx5_tc_ct_entry_create_mod_hdr(struct mlx5_tc_ct_priv *ct_priv, + struct mlx5_flow_attr *attr, + struct flow_rule *flow_rule, + struct mlx5e_mod_hdr_handle **mh, +- u8 zone_restore_id, bool nat) ++ u8 zone_restore_id, bool nat_table, bool has_nat) + { + struct mlx5e_tc_mod_hdr_acts mod_acts = {}; + struct flow_action_entry *meta; +@@ -665,11 +665,12 @@ mlx5_tc_ct_entry_create_mod_hdr(struct mlx5_tc_ct_priv *ct_priv, + &attr->ct_attr.ct_labels_id); + if (err) + return -EOPNOTSUPP; +- if (nat) { +- err = mlx5_tc_ct_entry_create_nat(ct_priv, flow_rule, +- &mod_acts); +- if (err) +- goto err_mapping; ++ if (nat_table) { ++ if (has_nat) { ++ err = mlx5_tc_ct_entry_create_nat(ct_priv, flow_rule, &mod_acts); ++ if (err) ++ goto err_mapping; ++ } + + ct_state |= MLX5_CT_STATE_NAT_BIT; + } +@@ -684,7 +685,7 @@ mlx5_tc_ct_entry_create_mod_hdr(struct mlx5_tc_ct_priv *ct_priv, + if (err) + goto err_mapping; + +- if (nat) { ++ if (nat_table && has_nat) { + attr->modify_hdr = mlx5_modify_header_alloc(ct_priv->dev, ct_priv->ns_type, + mod_acts.num_actions, + mod_acts.actions); +@@ -752,7 +753,9 @@ mlx5_tc_ct_entry_add_rule(struct mlx5_tc_ct_priv *ct_priv, + + err = mlx5_tc_ct_entry_create_mod_hdr(ct_priv, attr, flow_rule, + &zone_rule->mh, +- zone_restore_id, nat); ++ zone_restore_id, ++ nat, ++ mlx5_tc_ct_entry_has_nat(entry)); + if (err) { + ct_dbg("Failed to create ct entry mod hdr"); + goto err_mod_hdr; +-- +2.35.1 + diff --git a/queue-5.15/net-mlx5-don-t-use-already-freed-action-pointer.patch b/queue-5.15/net-mlx5-don-t-use-already-freed-action-pointer.patch new file mode 100644 index 00000000000..d2647ab2db8 --- /dev/null +++ b/queue-5.15/net-mlx5-don-t-use-already-freed-action-pointer.patch @@ -0,0 +1,50 @@ +From c729d56117eddb8627d180c68102d4378760fa02 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 24 May 2022 15:59:27 +0300 +Subject: net/mlx5: Don't use already freed action pointer + +From: Leon Romanovsky + +[ Upstream commit 80b2bd737d0e833e6a2b77e482e5a714a79c86a4 ] + +The call to mlx5dr_action_destroy() releases "action" memory. That +pointer is set to miss_action later and generates the following smatch +error: + + drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c:53 set_miss_action() + warn: 'action' was already freed. + +Make sure that the pointer is always valid by setting NULL after destroy. + +Fixes: 6a48faeeca10 ("net/mlx5: Add direct rule fs_cmd implementation") +Reported-by: Dan Carpenter +Signed-off-by: Leon Romanovsky +Signed-off-by: Saeed Mahameed +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c | 9 ++++----- + 1 file changed, 4 insertions(+), 5 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c b/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c +index ae4597118f8b..0553ee1fe80a 100644 +--- a/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c ++++ b/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c +@@ -43,11 +43,10 @@ static int set_miss_action(struct mlx5_flow_root_namespace *ns, + err = mlx5dr_table_set_miss_action(ft->fs_dr_table.dr_table, action); + if (err && action) { + err = mlx5dr_action_destroy(action); +- if (err) { +- action = NULL; +- mlx5_core_err(ns->dev, "Failed to destroy action (%d)\n", +- err); +- } ++ if (err) ++ mlx5_core_err(ns->dev, ++ "Failed to destroy action (%d)\n", err); ++ action = NULL; + } + ft->fs_dr_table.miss_action = action; + if (old_miss_action) { +-- +2.35.1 + diff --git a/queue-5.15/net-mlx5e-tc-nic-mode-fix-tc-chains-miss-table.patch b/queue-5.15/net-mlx5e-tc-nic-mode-fix-tc-chains-miss-table.patch new file mode 100644 index 00000000000..06617523b1d --- /dev/null +++ b/queue-5.15/net-mlx5e-tc-nic-mode-fix-tc-chains-miss-table.patch @@ -0,0 +1,151 @@ +From 98ee174b6c981dbd2fe3df989b938228d57f9979 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 2 May 2022 10:51:30 +0300 +Subject: net/mlx5e: TC NIC mode, fix tc chains miss table + +From: Maor Dickman + +[ Upstream commit 66cb64e292d21588bdb831f08a7ec0ff04d6380d ] + +The cited commit changed promisc table to be created on demand with the +highest priority in the NIC table replacing the vlan table, this caused +tc NIC tables miss flow to skip the prmoisc table because it use vlan +table as miss table. + +OVS offload in NIC mode use promisc by default so any unicast packet +which will be handled by tc NIC tables miss flow will skip the promisc +rule and will be dropped. + +Fix this by adding new empty table in new tc level with low priority and +point the nic tc chain miss to it, the new table is managed so it will +point to vlan table if promisc is disabled and to promisc table if enabled. + +Fixes: 1c46d7409f30 ("net/mlx5e: Optimize promiscuous mode") +Signed-off-by: Maor Dickman +Reviewed-by: Paul Blakey +Reviewed-by: Ariel Levkovich +Signed-off-by: Saeed Mahameed +Signed-off-by: Sasha Levin +--- + .../net/ethernet/mellanox/mlx5/core/en/fs.h | 2 + + .../net/ethernet/mellanox/mlx5/core/en_tc.c | 38 ++++++++++++++++++- + .../net/ethernet/mellanox/mlx5/core/fs_core.c | 2 +- + 3 files changed, 39 insertions(+), 3 deletions(-) + +diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/fs.h b/drivers/net/ethernet/mellanox/mlx5/core/en/fs.h +index a88a1a48229f..d634c034a419 100644 +--- a/drivers/net/ethernet/mellanox/mlx5/core/en/fs.h ++++ b/drivers/net/ethernet/mellanox/mlx5/core/en/fs.h +@@ -12,6 +12,7 @@ struct mlx5e_post_act; + enum { + MLX5E_TC_FT_LEVEL = 0, + MLX5E_TC_TTC_FT_LEVEL, ++ MLX5E_TC_MISS_LEVEL, + }; + + struct mlx5e_tc_table { +@@ -20,6 +21,7 @@ struct mlx5e_tc_table { + */ + struct mutex t_lock; + struct mlx5_flow_table *t; ++ struct mlx5_flow_table *miss_t; + struct mlx5_fs_chains *chains; + struct mlx5e_post_act *post_act; + +diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c +index 60a4ac0ca76d..3aa8d0b83d10 100644 +--- a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c ++++ b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c +@@ -4993,6 +4993,33 @@ static int mlx5e_tc_nic_get_ft_size(struct mlx5_core_dev *dev) + return tc_tbl_size; + } + ++static int mlx5e_tc_nic_create_miss_table(struct mlx5e_priv *priv) ++{ ++ struct mlx5_flow_table **ft = &priv->fs.tc.miss_t; ++ struct mlx5_flow_table_attr ft_attr = {}; ++ struct mlx5_flow_namespace *ns; ++ int err = 0; ++ ++ ft_attr.max_fte = 1; ++ ft_attr.autogroup.max_num_groups = 1; ++ ft_attr.level = MLX5E_TC_MISS_LEVEL; ++ ft_attr.prio = 0; ++ ns = mlx5_get_flow_namespace(priv->mdev, MLX5_FLOW_NAMESPACE_KERNEL); ++ ++ *ft = mlx5_create_auto_grouped_flow_table(ns, &ft_attr); ++ if (IS_ERR(*ft)) { ++ err = PTR_ERR(*ft); ++ netdev_err(priv->netdev, "failed to create tc nic miss table err=%d\n", err); ++ } ++ ++ return err; ++} ++ ++static void mlx5e_tc_nic_destroy_miss_table(struct mlx5e_priv *priv) ++{ ++ mlx5_destroy_flow_table(priv->fs.tc.miss_t); ++} ++ + int mlx5e_tc_nic_init(struct mlx5e_priv *priv) + { + struct mlx5e_tc_table *tc = &priv->fs.tc; +@@ -5025,19 +5052,23 @@ int mlx5e_tc_nic_init(struct mlx5e_priv *priv) + } + tc->mapping = chains_mapping; + ++ err = mlx5e_tc_nic_create_miss_table(priv); ++ if (err) ++ goto err_chains; ++ + if (MLX5_CAP_FLOWTABLE_NIC_RX(priv->mdev, ignore_flow_level)) + attr.flags = MLX5_CHAINS_AND_PRIOS_SUPPORTED | + MLX5_CHAINS_IGNORE_FLOW_LEVEL_SUPPORTED; + attr.ns = MLX5_FLOW_NAMESPACE_KERNEL; + attr.max_ft_sz = mlx5e_tc_nic_get_ft_size(dev); + attr.max_grp_num = MLX5E_TC_TABLE_NUM_GROUPS; +- attr.default_ft = mlx5e_vlan_get_flowtable(priv->fs.vlan); ++ attr.default_ft = priv->fs.tc.miss_t; + attr.mapping = chains_mapping; + + tc->chains = mlx5_chains_create(dev, &attr); + if (IS_ERR(tc->chains)) { + err = PTR_ERR(tc->chains); +- goto err_chains; ++ goto err_miss; + } + + tc->post_act = mlx5e_tc_post_act_init(priv, tc->chains, MLX5_FLOW_NAMESPACE_KERNEL); +@@ -5060,6 +5091,8 @@ int mlx5e_tc_nic_init(struct mlx5e_priv *priv) + mlx5_tc_ct_clean(tc->ct); + mlx5e_tc_post_act_destroy(tc->post_act); + mlx5_chains_destroy(tc->chains); ++err_miss: ++ mlx5e_tc_nic_destroy_miss_table(priv); + err_chains: + mapping_destroy(chains_mapping); + err_mapping: +@@ -5100,6 +5133,7 @@ void mlx5e_tc_nic_cleanup(struct mlx5e_priv *priv) + mlx5e_tc_post_act_destroy(tc->post_act); + mapping_destroy(tc->mapping); + mlx5_chains_destroy(tc->chains); ++ mlx5e_tc_nic_destroy_miss_table(priv); + } + + int mlx5e_tc_esw_init(struct rhashtable *tc_ht) +diff --git a/drivers/net/ethernet/mellanox/mlx5/core/fs_core.c b/drivers/net/ethernet/mellanox/mlx5/core/fs_core.c +index a197dd7ca73b..379130ed300c 100644 +--- a/drivers/net/ethernet/mellanox/mlx5/core/fs_core.c ++++ b/drivers/net/ethernet/mellanox/mlx5/core/fs_core.c +@@ -113,7 +113,7 @@ + #define KERNEL_MIN_LEVEL (KERNEL_NIC_PRIO_NUM_LEVELS + 1) + + #define KERNEL_NIC_TC_NUM_PRIOS 1 +-#define KERNEL_NIC_TC_NUM_LEVELS 2 ++#define KERNEL_NIC_TC_NUM_LEVELS 3 + + #define ANCHOR_NUM_LEVELS 1 + #define ANCHOR_NUM_PRIOS 1 +-- +2.35.1 + diff --git a/queue-5.15/net-mlx5e-update-netdev-features-after-changing-xdp-.patch b/queue-5.15/net-mlx5e-update-netdev-features-after-changing-xdp-.patch new file mode 100644 index 00000000000..a220d5e6cbf --- /dev/null +++ b/queue-5.15/net-mlx5e-update-netdev-features-after-changing-xdp-.patch @@ -0,0 +1,44 @@ +From 4d583b1f69be334c1ef804289da37f3829ea4dc3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 23 May 2022 15:39:13 +0300 +Subject: net/mlx5e: Update netdev features after changing XDP state + +From: Maxim Mikityanskiy + +[ Upstream commit f6279f113ad593971999c877eb69dc3d36a75894 ] + +Some features (LRO, HW GRO) conflict with XDP. If there is an attempt to +enable such features while XDP is active, they will be set to `off +[requested on]`. In order to activate these features after XDP is turned +off, the driver needs to call netdev_update_features(). This commit adds +this missing call after XDP state changes. + +Fixes: cf6e34c8c22f ("net/mlx5e: Properly block LRO when XDP is enabled") +Fixes: b0617e7b3500 ("net/mlx5e: Properly block HW GRO when XDP is enabled") +Signed-off-by: Maxim Mikityanskiy +Reviewed-by: Tariq Toukan +Signed-off-by: Saeed Mahameed +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +index 7efb898e9f96..e00648094fc2 100644 +--- a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c ++++ b/drivers/net/ethernet/mellanox/mlx5/core/en_main.c +@@ -4181,6 +4181,11 @@ static int mlx5e_xdp_set(struct net_device *netdev, struct bpf_prog *prog) + + unlock: + mutex_unlock(&priv->state_lock); ++ ++ /* Need to fix some features. */ ++ if (!err) ++ netdev_update_features(netdev); ++ + return err; + } + +-- +2.35.1 + diff --git a/queue-5.15/net-sched-add-barrier-to-fix-packet-stuck-problem-fo.patch b/queue-5.15/net-sched-add-barrier-to-fix-packet-stuck-problem-fo.patch new file mode 100644 index 00000000000..26453f3188f --- /dev/null +++ b/queue-5.15/net-sched-add-barrier-to-fix-packet-stuck-problem-fo.patch @@ -0,0 +1,71 @@ +From 814b681e7b33506aaba0681d7e4aa5da7979ae1c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 28 May 2022 18:16:28 +0800 +Subject: net: sched: add barrier to fix packet stuck problem for lockless + qdisc + +From: Guoju Fang + +[ Upstream commit 2e8728c955ce0624b958eee6e030a37aca3a5d86 ] + +In qdisc_run_end(), the spin_unlock() only has store-release semantic, +which guarantees all earlier memory access are visible before it. But +the subsequent test_bit() has no barrier semantics so may be reordered +ahead of the spin_unlock(). The store-load reordering may cause a packet +stuck problem. + +The concurrent operations can be described as below, + CPU 0 | CPU 1 + qdisc_run_end() | qdisc_run_begin() + . | . + ----> /* may be reorderd here */ | . +| . | . +| spin_unlock() | set_bit() +| . | smp_mb__after_atomic() + ---- test_bit() | spin_trylock() + . | . + +Consider the following sequence of events: + CPU 0 reorder test_bit() ahead and see MISSED = 0 + CPU 1 calls set_bit() + CPU 1 calls spin_trylock() and return fail + CPU 0 executes spin_unlock() + +At the end of the sequence, CPU 0 calls spin_unlock() and does nothing +because it see MISSED = 0. The skb on CPU 1 has beed enqueued but no one +take it, until the next cpu pushing to the qdisc (if ever ...) will +notice and dequeue it. + +This patch fix this by adding one explicit barrier. As spin_unlock() and +test_bit() ordering is a store-load ordering, a full memory barrier +smp_mb() is needed here. + +Fixes: a90c57f2cedd ("net: sched: fix packet stuck problem for lockless qdisc") +Signed-off-by: Guoju Fang +Link: https://lore.kernel.org/r/20220528101628.120193-1-gjfang@linux.alibaba.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Sasha Levin +--- + include/net/sch_generic.h | 6 ++++++ + 1 file changed, 6 insertions(+) + +diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h +index 9e9ff13adda8..1958d1260fe9 100644 +--- a/include/net/sch_generic.h ++++ b/include/net/sch_generic.h +@@ -202,6 +202,12 @@ static inline void qdisc_run_end(struct Qdisc *qdisc) + if (qdisc->flags & TCQ_F_NOLOCK) { + spin_unlock(&qdisc->seqlock); + ++ /* spin_unlock() only has store-release semantic. The unlock ++ * and test_bit() ordering is a store-load ordering, so a full ++ * memory barrier is needed here. ++ */ ++ smp_mb(); ++ + if (unlikely(test_bit(__QDISC_STATE_MISSED, + &qdisc->state))) + __netif_schedule(qdisc); +-- +2.35.1 + diff --git a/queue-5.15/net-sched-fixed-barrier-to-prevent-skbuff-sticking-i.patch b/queue-5.15/net-sched-fixed-barrier-to-prevent-skbuff-sticking-i.patch new file mode 100644 index 00000000000..7f9b98e9bab --- /dev/null +++ b/queue-5.15/net-sched-fixed-barrier-to-prevent-skbuff-sticking-i.patch @@ -0,0 +1,140 @@ +From 6492734b4dc34de1003d78653c82d054364de9fc Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 25 May 2022 17:17:46 -0700 +Subject: net: sched: fixed barrier to prevent skbuff sticking in qdisc backlog + +From: Vincent Ray + +[ Upstream commit a54ce3703613e41fe1d98060b62ec09a3984dc28 ] + +In qdisc_run_begin(), smp_mb__before_atomic() used before test_bit() +does not provide any ordering guarantee as test_bit() is not an atomic +operation. This, added to the fact that the spin_trylock() call at +the beginning of qdisc_run_begin() does not guarantee acquire +semantics if it does not grab the lock, makes it possible for the +following statement : + +if (test_bit(__QDISC_STATE_MISSED, &qdisc->state)) + +to be executed before an enqueue operation called before +qdisc_run_begin(). + +As a result the following race can happen : + + CPU 1 CPU 2 + + qdisc_run_begin() qdisc_run_begin() /* true */ + set(MISSED) . + /* returns false */ . + . /* sees MISSED = 1 */ + . /* so qdisc not empty */ + . __qdisc_run() + . . + . pfifo_fast_dequeue() + ----> /* may be done here */ . +| . clear(MISSED) +| . . +| . smp_mb __after_atomic(); +| . . +| . /* recheck the queue */ +| . /* nothing => exit */ +| enqueue(skb1) +| . +| qdisc_run_begin() +| . +| spin_trylock() /* fail */ +| . +| smp_mb__before_atomic() /* not enough */ +| . + ---- if (test_bit(MISSED)) + return false; /* exit */ + +In the above scenario, CPU 1 and CPU 2 both try to grab the +qdisc->seqlock at the same time. Only CPU 2 succeeds and enters the +bypass code path, where it emits its skb then calls __qdisc_run(). + +CPU1 fails, sets MISSED and goes down the traditionnal enqueue() + +dequeue() code path. But when executing qdisc_run_begin() for the +second time, after enqueuing its skbuff, it sees the MISSED bit still +set (by itself) and consequently chooses to exit early without setting +it again nor trying to grab the spinlock again. + +Meanwhile CPU2 has seen MISSED = 1, cleared it, checked the queue +and found it empty, so it returned. + +At the end of the sequence, we end up with skb1 enqueued in the +backlog, both CPUs out of __dev_xmit_skb(), the MISSED bit not set, +and no __netif_schedule() called made. skb1 will now linger in the +qdisc until somebody later performs a full __qdisc_run(). Associated +to the bypass capacity of the qdisc, and the ability of the TCP layer +to avoid resending packets which it knows are still in the qdisc, this +can lead to serious traffic "holes" in a TCP connection. + +We fix this by replacing the smp_mb__before_atomic() / test_bit() / +set_bit() / smp_mb__after_atomic() sequence inside qdisc_run_begin() +by a single test_and_set_bit() call, which is more concise and +enforces the needed memory barriers. + +Fixes: 89837eb4b246 ("net: sched: add barrier to ensure correct ordering for lockless qdisc") +Signed-off-by: Vincent Ray +Signed-off-by: Eric Dumazet +Link: https://lore.kernel.org/r/20220526001746.2437669-1-eric.dumazet@gmail.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Sasha Levin +--- + include/net/sch_generic.h | 36 ++++++++---------------------------- + 1 file changed, 8 insertions(+), 28 deletions(-) + +diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h +index 4121ffd0faf8..9e9ff13adda8 100644 +--- a/include/net/sch_generic.h ++++ b/include/net/sch_generic.h +@@ -173,37 +173,17 @@ static inline bool qdisc_run_begin(struct Qdisc *qdisc) + if (spin_trylock(&qdisc->seqlock)) + return true; + +- /* Paired with smp_mb__after_atomic() to make sure +- * STATE_MISSED checking is synchronized with clearing +- * in pfifo_fast_dequeue(). ++ /* No need to insist if the MISSED flag was already set. ++ * Note that test_and_set_bit() also gives us memory ordering ++ * guarantees wrt potential earlier enqueue() and below ++ * spin_trylock(), both of which are necessary to prevent races + */ +- smp_mb__before_atomic(); +- +- /* If the MISSED flag is set, it means other thread has +- * set the MISSED flag before second spin_trylock(), so +- * we can return false here to avoid multi cpus doing +- * the set_bit() and second spin_trylock() concurrently. +- */ +- if (test_bit(__QDISC_STATE_MISSED, &qdisc->state)) ++ if (test_and_set_bit(__QDISC_STATE_MISSED, &qdisc->state)) + return false; + +- /* Set the MISSED flag before the second spin_trylock(), +- * if the second spin_trylock() return false, it means +- * other cpu holding the lock will do dequeuing for us +- * or it will see the MISSED flag set after releasing +- * lock and reschedule the net_tx_action() to do the +- * dequeuing. +- */ +- set_bit(__QDISC_STATE_MISSED, &qdisc->state); +- +- /* spin_trylock() only has load-acquire semantic, so use +- * smp_mb__after_atomic() to ensure STATE_MISSED is set +- * before doing the second spin_trylock(). +- */ +- smp_mb__after_atomic(); +- +- /* Retry again in case other CPU may not see the new flag +- * after it releases the lock at the end of qdisc_run_end(). ++ /* Try to take the lock again to make sure that we will either ++ * grab it or the CPU that still has it will see MISSED set ++ * when testing it in qdisc_run_end() + */ + return spin_trylock(&qdisc->seqlock); + } else if (qdisc_is_running(qdisc)) { +-- +2.35.1 + diff --git a/queue-5.15/net-smc-fixes-for-converting-from-struct-smc_cdc_tx_.patch b/queue-5.15/net-smc-fixes-for-converting-from-struct-smc_cdc_tx_.patch new file mode 100644 index 00000000000..501e0c3eabb --- /dev/null +++ b/queue-5.15/net-smc-fixes-for-converting-from-struct-smc_cdc_tx_.patch @@ -0,0 +1,37 @@ +From b00f576bbe6e4d4053fe0479bdab78da35773fb2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 28 May 2022 14:54:57 +0800 +Subject: net/smc: fixes for converting from "struct smc_cdc_tx_pend **" to + "struct smc_wr_tx_pend_priv *" + +From: Guangguan Wang + +[ Upstream commit e225c9a5a74b12e9ef8516f30a3db2c7eb866ee1 ] + +"struct smc_cdc_tx_pend **" can not directly convert +to "struct smc_wr_tx_pend_priv *". + +Fixes: 2bced6aefa3d ("net/smc: put slot when connection is killed") +Signed-off-by: Guangguan Wang +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/smc/smc_cdc.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/net/smc/smc_cdc.c b/net/smc/smc_cdc.c +index 84c8a4374fdd..5d180d24cbf1 100644 +--- a/net/smc/smc_cdc.c ++++ b/net/smc/smc_cdc.c +@@ -72,7 +72,7 @@ int smc_cdc_get_free_slot(struct smc_connection *conn, + /* abnormal termination */ + if (!rc) + smc_wr_tx_put_slot(link, +- (struct smc_wr_tx_pend_priv *)pend); ++ (struct smc_wr_tx_pend_priv *)(*pend)); + rc = -EPIPE; + } + return rc; +-- +2.35.1 + diff --git a/queue-5.15/nfp-only-report-pause-frame-configuration-for-physic.patch b/queue-5.15/nfp-only-report-pause-frame-configuration-for-physic.patch new file mode 100644 index 00000000000..220ee3d9061 --- /dev/null +++ b/queue-5.15/nfp-only-report-pause-frame-configuration-for-physic.patch @@ -0,0 +1,46 @@ +From 69981f5f7101af7fd18e1841620456482ebb7a36 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 27 May 2022 20:24:24 +0200 +Subject: nfp: only report pause frame configuration for physical device + +From: Yu Xiao + +[ Upstream commit 0649e4d63420ebc8cbebef3e9d39e12ffc5eb9fa ] + +Only report pause frame configuration for physical device. Logical +port of both PCI PF and PCI VF do not support it. + +Fixes: 9fdc5d85a8fe ("nfp: update ethtool reporting of pauseframe control") +Signed-off-by: Yu Xiao +Signed-off-by: Simon Horman +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c b/drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c +index be1a358baadb..8b614b0201e7 100644 +--- a/drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c ++++ b/drivers/net/ethernet/netronome/nfp/nfp_net_ethtool.c +@@ -286,8 +286,6 @@ nfp_net_get_link_ksettings(struct net_device *netdev, + + /* Init to unknowns */ + ethtool_link_ksettings_add_link_mode(cmd, supported, FIBRE); +- ethtool_link_ksettings_add_link_mode(cmd, supported, Pause); +- ethtool_link_ksettings_add_link_mode(cmd, advertising, Pause); + cmd->base.port = PORT_OTHER; + cmd->base.speed = SPEED_UNKNOWN; + cmd->base.duplex = DUPLEX_UNKNOWN; +@@ -295,6 +293,8 @@ nfp_net_get_link_ksettings(struct net_device *netdev, + port = nfp_port_from_netdev(netdev); + eth_port = nfp_port_get_eth_port(port); + if (eth_port) { ++ ethtool_link_ksettings_add_link_mode(cmd, supported, Pause); ++ ethtool_link_ksettings_add_link_mode(cmd, advertising, Pause); + cmd->base.autoneg = eth_port->aneg != NFP_ANEG_DISABLED ? + AUTONEG_ENABLE : AUTONEG_DISABLE; + nfp_net_set_fec_link_mode(eth_port, cmd); +-- +2.35.1 + diff --git a/queue-5.15/octeontx2-af-fix-error-code-in-is_valid_offset.patch b/queue-5.15/octeontx2-af-fix-error-code-in-is_valid_offset.patch new file mode 100644 index 00000000000..17a022b7d25 --- /dev/null +++ b/queue-5.15/octeontx2-af-fix-error-code-in-is_valid_offset.patch @@ -0,0 +1,37 @@ +From 550393b7841f692e693c906aa6637e53f26c0c15 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 31 May 2022 10:28:45 +0300 +Subject: octeontx2-af: fix error code in is_valid_offset() + +From: Dan Carpenter + +[ Upstream commit f3d671c711097a133bc36bd2bde52f1fcca783a6 ] + +The is_valid_offset() function returns success/true if the call to +validate_and_get_cpt_blkaddr() fails. + +Fixes: ecad2ce8c48f ("octeontx2-af: cn10k: Add mailbox to configure reassembly timeout") +Signed-off-by: Dan Carpenter +Link: https://lore.kernel.org/r/YpXDrTPb8qV01JSP@kili +Signed-off-by: Paolo Abeni +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/marvell/octeontx2/af/rvu_cpt.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_cpt.c b/drivers/net/ethernet/marvell/octeontx2/af/rvu_cpt.c +index 1f90a7403392..4895faa667b5 100644 +--- a/drivers/net/ethernet/marvell/octeontx2/af/rvu_cpt.c ++++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu_cpt.c +@@ -206,7 +206,7 @@ static bool is_valid_offset(struct rvu *rvu, struct cpt_rd_wr_reg_msg *req) + + blkaddr = validate_and_get_cpt_blkaddr(req->blkaddr); + if (blkaddr < 0) +- return blkaddr; ++ return false; + + /* Registers that can be accessed from PF/VF */ + if ((offset & 0xFF000) == CPT_AF_LFX_CTL(0) || +-- +2.35.1 + diff --git a/queue-5.15/pcmcia-db1xxx_ss-restrict-to-mips_db1xxx-boards.patch b/queue-5.15/pcmcia-db1xxx_ss-restrict-to-mips_db1xxx-boards.patch new file mode 100644 index 00000000000..79c34a00a06 --- /dev/null +++ b/queue-5.15/pcmcia-db1xxx_ss-restrict-to-mips_db1xxx-boards.patch @@ -0,0 +1,48 @@ +From 77163968a95478027c06f601a88c482127720e0f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 23 Jan 2022 09:40:31 -0800 +Subject: pcmcia: db1xxx_ss: restrict to MIPS_DB1XXX boards + +From: Randy Dunlap + +[ Upstream commit 3928cf08334ed895a31458cbebd8d4ec6d84c080 ] + +When the MIPS_ALCHEMY board selection is MIPS_XXS1500 instead of +MIPS_DB1XXX, the PCMCIA driver 'db1xxx_ss' has build errors due +to missing DB1XXX symbols. The PCMCIA driver should be restricted +to MIPS_DB1XXX instead of MIPS_ALCHEMY to fix this build error. + +ERROR: modpost: "bcsr_read" [drivers/pcmcia/db1xxx_ss.ko] undefined! +ERROR: modpost: "bcsr_mod" [drivers/pcmcia/db1xxx_ss.ko] undefined! + +Fixes: 42a4f17dc356 ("MIPS: Alchemy: remove SOC_AU1X00 in favor of MIPS_ALCHEMY") +Signed-off-by: Randy Dunlap +Reported-by: kernel test robot +Cc: Arnd Bergmann +Cc: Daniel Vetter +Cc: Kees Cook +Cc: Thomas Bogendoerfer +Cc: linux-mips@vger.kernel.org +Acked-by: Manuel Lauss +Signed-off-by: Dominik Brodowski +Signed-off-by: Sasha Levin +--- + drivers/pcmcia/Kconfig | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/pcmcia/Kconfig b/drivers/pcmcia/Kconfig +index d13b8d1a780a..4868ec03e32f 100644 +--- a/drivers/pcmcia/Kconfig ++++ b/drivers/pcmcia/Kconfig +@@ -151,7 +151,7 @@ config TCIC + + config PCMCIA_ALCHEMY_DEVBOARD + tristate "Alchemy Db/Pb1xxx PCMCIA socket services" +- depends on MIPS_ALCHEMY && PCMCIA ++ depends on MIPS_DB1XXX && PCMCIA + help + Enable this driver of you want PCMCIA support on your Alchemy + Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300 +-- +2.35.1 + diff --git a/queue-5.15/perf-c2c-fix-sorting-in-percent_rmt_hitm_cmp.patch b/queue-5.15/perf-c2c-fix-sorting-in-percent_rmt_hitm_cmp.patch new file mode 100644 index 00000000000..fe9d96c2f3e --- /dev/null +++ b/queue-5.15/perf-c2c-fix-sorting-in-percent_rmt_hitm_cmp.patch @@ -0,0 +1,49 @@ +From 5ba5be163ffffb0862a10cd4e9251426e40e3ec2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 30 May 2022 16:42:53 +0800 +Subject: perf c2c: Fix sorting in percent_rmt_hitm_cmp() + +From: Leo Yan + +[ Upstream commit b24192a17337abbf3f44aaa75e15df14a2d0016e ] + +The function percent_rmt_hitm_cmp() wrongly uses local HITMs for +sorting remote HITMs. + +Since this function is to sort cache lines for remote HITMs, this patch +changes to use 'rmt_hitm' field for correct sorting. + +Fixes: 9cb3500afc0980c5 ("perf c2c report: Add hitm/store percent related sort keys") +Signed-off-by: Leo Yan +Acked-by: Namhyung Kim +Cc: Alexander Shishkin +Cc: Ingo Molnar +Cc: Jiri Olsa +Cc: Joe Mario +Cc: Mark Rutland +Cc: Peter Zijlstra +Link: https://lore.kernel.org/r/20220530084253.750190-1-leo.yan@linaro.org +Signed-off-by: Arnaldo Carvalho de Melo +Signed-off-by: Sasha Levin +--- + tools/perf/builtin-c2c.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/tools/perf/builtin-c2c.c b/tools/perf/builtin-c2c.c +index 1fb0c507a551..e6f900c3accb 100644 +--- a/tools/perf/builtin-c2c.c ++++ b/tools/perf/builtin-c2c.c +@@ -924,8 +924,8 @@ percent_rmt_hitm_cmp(struct perf_hpp_fmt *fmt __maybe_unused, + double per_left; + double per_right; + +- per_left = PERCENT(left, lcl_hitm); +- per_right = PERCENT(right, lcl_hitm); ++ per_left = PERCENT(left, rmt_hitm); ++ per_right = PERCENT(right, rmt_hitm); + + return per_left - per_right; + } +-- +2.35.1 + diff --git a/queue-5.15/phy-qcom-qmp-fix-pipe-clock-imbalance-on-power-on-fa.patch b/queue-5.15/phy-qcom-qmp-fix-pipe-clock-imbalance-on-power-on-fa.patch new file mode 100644 index 00000000000..d8152571adc --- /dev/null +++ b/queue-5.15/phy-qcom-qmp-fix-pipe-clock-imbalance-on-power-on-fa.patch @@ -0,0 +1,40 @@ +From 8df5737e3327541abd54f1109b6266764627450c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 2 May 2022 15:31:29 +0200 +Subject: phy: qcom-qmp: fix pipe-clock imbalance on power-on failure + +From: Johan Hovold + +[ Upstream commit 5e73b2d9867998278479ccc065a8a8227a5513ef ] + +Make sure to disable the pipe clock also if ufs-reset deassertion fails +during power on. + +Note that the ufs-reset is asserted in qcom_qmp_phy_com_exit(). + +Fixes: c9b589791fc1 ("phy: qcom: Utilize UFS reset controller") +Cc: Evan Green +Signed-off-by: Johan Hovold +Link: https://lore.kernel.org/r/20220502133130.4125-2-johan+linaro@kernel.org +Signed-off-by: Vinod Koul +Signed-off-by: Sasha Levin +--- + drivers/phy/qualcomm/phy-qcom-qmp.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c b/drivers/phy/qualcomm/phy-qcom-qmp.c +index 9bb19c4bfe79..ed69d455ac0e 100644 +--- a/drivers/phy/qualcomm/phy-qcom-qmp.c ++++ b/drivers/phy/qualcomm/phy-qcom-qmp.c +@@ -4802,7 +4802,7 @@ static int qcom_qmp_phy_power_on(struct phy *phy) + + ret = reset_control_deassert(qmp->ufs_reset); + if (ret) +- goto err_lane_rst; ++ goto err_pcs_ready; + + qcom_qmp_phy_configure(pcs_misc, cfg->regs, cfg->pcs_misc_tbl, + cfg->pcs_misc_tbl_num); +-- +2.35.1 + diff --git a/queue-5.15/platform-finally-disallow-irq0-in-platform_get_irq-a.patch b/queue-5.15/platform-finally-disallow-irq0-in-platform_get_irq-a.patch new file mode 100644 index 00000000000..ca2d0ad18d4 --- /dev/null +++ b/queue-5.15/platform-finally-disallow-irq0-in-platform_get_irq-a.patch @@ -0,0 +1,55 @@ +From 94ed149cab47d752cadb9fb64792f90b39da8af3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 11 Mar 2022 22:35:29 +0300 +Subject: platform: finally disallow IRQ0 in platform_get_irq() and its ilk + +From: Sergey Shtylyov + +[ Upstream commit ce753ad1549cbe9ccaea4c06a1f5fa47432c8289 ] + +The commit a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is +invalid") only calls WARN() when IRQ0 is about to be returned, however +using IRQ0 is considered invalid (according to Linus) outside the arch/ +code where it's used by the i8253 drivers. Many driver subsystems treat +0 specially (e.g. as an indication of the polling mode by libata), so +the users of platform_get_irq[_byname]() in them would have to filter +out IRQ0 explicitly and this (quite obviously) doesn't scale... +Let's finally get this straight and return -EINVAL instead of IRQ0! + +Fixes: a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is invalid") +Acked-by: Marc Zyngier +Signed-off-by: Sergey Shtylyov +Link: https://lore.kernel.org/r/025679e1-1f0a-ae4b-4369-01164f691511@omp.ru +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/base/platform.c | 6 ++++-- + 1 file changed, 4 insertions(+), 2 deletions(-) + +diff --git a/drivers/base/platform.c b/drivers/base/platform.c +index 652531f67135..dd208430aadc 100644 +--- a/drivers/base/platform.c ++++ b/drivers/base/platform.c +@@ -231,7 +231,8 @@ int platform_get_irq_optional(struct platform_device *dev, unsigned int num) + out_not_found: + ret = -ENXIO; + out: +- WARN(ret == 0, "0 is an invalid IRQ number\n"); ++ if (WARN(!ret, "0 is an invalid IRQ number\n")) ++ return -EINVAL; + return ret; + } + EXPORT_SYMBOL_GPL(platform_get_irq_optional); +@@ -445,7 +446,8 @@ static int __platform_get_irq_byname(struct platform_device *dev, + + r = platform_get_resource_byname(dev, IORESOURCE_IRQ, name); + if (r) { +- WARN(r->start == 0, "0 is an invalid IRQ number\n"); ++ if (WARN(!r->start, "0 is an invalid IRQ number\n")) ++ return -EINVAL; + return r->start; + } + +-- +2.35.1 + diff --git a/queue-5.15/power-supply-axp288_fuel_gauge-drop-bios-version-che.patch b/queue-5.15/power-supply-axp288_fuel_gauge-drop-bios-version-che.patch new file mode 100644 index 00000000000..257d517827d --- /dev/null +++ b/queue-5.15/power-supply-axp288_fuel_gauge-drop-bios-version-che.patch @@ -0,0 +1,39 @@ +From ba4badf6d9cc13a2c0337c42205ad25a6de88050 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 2 May 2022 13:12:35 +0200 +Subject: power: supply: axp288_fuel_gauge: Drop BIOS version check from "T3 + MRD" DMI quirk + +From: Hans de Goede + +[ Upstream commit f61509a6f0b70f5bedea34efaf8065621689bd7a ] + +Some "T3 MRD" mini-PCs / HDMI-sticks without a battery use a different +value then "5.11" for their DMI BIOS version field. + +Drop the BIOS version check so that the no-battery "T3 MRD" DMI quirk +applies to these too. + +Fixes: 3a06b912a5ce ("power: supply: axp288_fuel_gauge: Make "T3 MRD" no_battery_list DMI entry more generic") +Signed-off-by: Hans de Goede +Signed-off-by: Sebastian Reichel +Signed-off-by: Sasha Levin +--- + drivers/power/supply/axp288_fuel_gauge.c | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/drivers/power/supply/axp288_fuel_gauge.c b/drivers/power/supply/axp288_fuel_gauge.c +index c1da217fdb0e..97e8663c08df 100644 +--- a/drivers/power/supply/axp288_fuel_gauge.c ++++ b/drivers/power/supply/axp288_fuel_gauge.c +@@ -605,7 +605,6 @@ static const struct dmi_system_id axp288_no_battery_list[] = { + DMI_MATCH(DMI_BOARD_NAME, "T3 MRD"), + DMI_MATCH(DMI_CHASSIS_TYPE, "3"), + DMI_MATCH(DMI_BIOS_VENDOR, "American Megatrends Inc."), +- DMI_MATCH(DMI_BIOS_VERSION, "5.11"), + }, + }, + {} +-- +2.35.1 + diff --git a/queue-5.15/pvpanic-fix-typos-in-the-comments.patch b/queue-5.15/pvpanic-fix-typos-in-the-comments.patch new file mode 100644 index 00000000000..5ee8639e21c --- /dev/null +++ b/queue-5.15/pvpanic-fix-typos-in-the-comments.patch @@ -0,0 +1,50 @@ +From 3c5fb09787b08bfbfcc5fbe94424e91197856799 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 29 Aug 2021 15:43:53 +0300 +Subject: pvpanic: Fix typos in the comments + +From: Andy Shevchenko + +[ Upstream commit cc5b392d0f94f27743583140d819fa35a46899db ] + +Fix a few spelling typos in the comments. + +Reviewed-by: Mihai Carabas +Signed-off-by: Andy Shevchenko +Link: https://lore.kernel.org/r/20210829124354.81653-2-andriy.shevchenko@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/misc/pvpanic/pvpanic-mmio.c | 2 +- + drivers/misc/pvpanic/pvpanic.c | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/drivers/misc/pvpanic/pvpanic-mmio.c b/drivers/misc/pvpanic/pvpanic-mmio.c +index be4016084979..61dbff5f0065 100644 +--- a/drivers/misc/pvpanic/pvpanic-mmio.c ++++ b/drivers/misc/pvpanic/pvpanic-mmio.c +@@ -100,7 +100,7 @@ static int pvpanic_mmio_probe(struct platform_device *pdev) + pi->base = base; + pi->capability = PVPANIC_PANICKED | PVPANIC_CRASH_LOADED; + +- /* initlize capability by RDPT */ ++ /* initialize capability by RDPT */ + pi->capability &= ioread8(base); + pi->events = pi->capability; + +diff --git a/drivers/misc/pvpanic/pvpanic.c b/drivers/misc/pvpanic/pvpanic.c +index bb7aa6368538..700d7d02c800 100644 +--- a/drivers/misc/pvpanic/pvpanic.c ++++ b/drivers/misc/pvpanic/pvpanic.c +@@ -58,7 +58,7 @@ pvpanic_panic_notify(struct notifier_block *nb, unsigned long code, + + static struct notifier_block pvpanic_panic_nb = { + .notifier_call = pvpanic_panic_notify, +- .priority = 1, /* let this called before broken drm_fb_helper */ ++ .priority = 1, /* let this called before broken drm_fb_helper() */ + }; + + static void pvpanic_remove(void *param) +-- +2.35.1 + diff --git a/queue-5.15/pwm-lp3943-fix-duty-calculation-in-case-period-was-c.patch b/queue-5.15/pwm-lp3943-fix-duty-calculation-in-case-period-was-c.patch new file mode 100644 index 00000000000..07ece723de5 --- /dev/null +++ b/queue-5.15/pwm-lp3943-fix-duty-calculation-in-case-period-was-c.patch @@ -0,0 +1,40 @@ +From 720e34ddc287cd38a92d7fda731c6a1a77d0a2e3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 8 Apr 2022 17:22:38 +0200 +Subject: pwm: lp3943: Fix duty calculation in case period was clamped +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Uwe Kleine-König + +[ Upstream commit 5e3b07ca5cc78cd4a987e78446849e41288d87cb ] + +The hardware only supports periods <= 1.6 ms and if a bigger period is +requested it is clamped to 1.6 ms. In this case duty_cycle might be bigger +than 1.6 ms and then the duty cycle register is written with a value +bigger than LP3943_MAX_DUTY. So clamp duty_cycle accordingly. + +Fixes: af66b3c0934e ("pwm: Add LP3943 PWM driver") +Signed-off-by: Uwe Kleine-König +Signed-off-by: Thierry Reding +Signed-off-by: Sasha Levin +--- + drivers/pwm/pwm-lp3943.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/pwm/pwm-lp3943.c b/drivers/pwm/pwm-lp3943.c +index ea17d446a627..2bd04ecb508c 100644 +--- a/drivers/pwm/pwm-lp3943.c ++++ b/drivers/pwm/pwm-lp3943.c +@@ -125,6 +125,7 @@ static int lp3943_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm, + if (err) + return err; + ++ duty_ns = min(duty_ns, period_ns); + val = (u8)(duty_ns * LP3943_MAX_DUTY / period_ns); + + return lp3943_write_byte(lp3943, reg_duty, val); +-- +2.35.1 + diff --git a/queue-5.15/pwm-raspberrypi-poe-fix-endianness-in-firmware-struc.patch b/queue-5.15/pwm-raspberrypi-poe-fix-endianness-in-firmware-struc.patch new file mode 100644 index 00000000000..b76a59a89ce --- /dev/null +++ b/queue-5.15/pwm-raspberrypi-poe-fix-endianness-in-firmware-struc.patch @@ -0,0 +1,46 @@ +From e6e4dfc83f92afac9e5392943c01a9efcffc8f13 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 8 Apr 2022 17:38:46 +0200 +Subject: pwm: raspberrypi-poe: Fix endianness in firmware struct +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Uwe Kleine-König + +[ Upstream commit 09f688f0718f57f9cf68ee1aa94490f641e759ba ] + +The reg member of struct raspberrypi_pwm_prop is a little endian 32 bit +quantity. Explicitly convert the (native endian) value to little endian +on assignment as is already done in raspberrypi_pwm_set_property(). + +This fixes the following sparse warning: + + drivers/pwm/pwm-raspberrypi-poe.c:69:24: warning: incorrect type in initializer (different base types) + drivers/pwm/pwm-raspberrypi-poe.c:69:24: expected restricted __le32 [usertype] reg + drivers/pwm/pwm-raspberrypi-poe.c:69:24: got unsigned int [usertype] reg + +Fixes: 79caa362eab6 ("pwm: Add Raspberry Pi Firmware based PWM bus") +Signed-off-by: Uwe Kleine-König +Signed-off-by: Thierry Reding +Signed-off-by: Sasha Levin +--- + drivers/pwm/pwm-raspberrypi-poe.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/pwm/pwm-raspberrypi-poe.c b/drivers/pwm/pwm-raspberrypi-poe.c +index 579a15240e0a..c877de37734d 100644 +--- a/drivers/pwm/pwm-raspberrypi-poe.c ++++ b/drivers/pwm/pwm-raspberrypi-poe.c +@@ -66,7 +66,7 @@ static int raspberrypi_pwm_get_property(struct rpi_firmware *firmware, + u32 reg, u32 *val) + { + struct raspberrypi_pwm_prop msg = { +- .reg = reg ++ .reg = cpu_to_le32(reg), + }; + int ret; + +-- +2.35.1 + diff --git a/queue-5.15/regulator-mt6315-regulator-fix-invalid-allowed-mode.patch b/queue-5.15/regulator-mt6315-regulator-fix-invalid-allowed-mode.patch new file mode 100644 index 00000000000..b82ac2d329e --- /dev/null +++ b/queue-5.15/regulator-mt6315-regulator-fix-invalid-allowed-mode.patch @@ -0,0 +1,53 @@ +From 11e27b4b37fb25f8ddca043a7f4316fed0760b72 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 29 May 2022 17:46:13 +0200 +Subject: regulator: mt6315-regulator: fix invalid allowed mode + +From: Fabien Parent + +[ Upstream commit 28cbc2d4c54c09a427b18a1604740efb6b2cc2d6 ] + +In the binding example, the regulator mode 4 is shown as a valid mode, +but the driver actually only support mode 0 to 2: + +This generates an error in dmesg when copy/pasting the binding example: +[ 0.306080] vbuck1: invalid regulator-allowed-modes element 4 +[ 0.307290] vbuck2: invalid regulator-allowed-modes element 4 + +This commit fixes this error by removing the invalid mode from the +examples. + +Fixes: 977fb5b58469 ("regulator: document binding for MT6315 regulator") +Signed-off-by: Fabien Parent +Link: https://lore.kernel.org/r/20220529154613.337559-1-fparent@baylibre.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + .../devicetree/bindings/regulator/mt6315-regulator.yaml | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml b/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml +index 5d2d989de893..37402c370fbb 100644 +--- a/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml ++++ b/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml +@@ -55,7 +55,7 @@ examples: + regulator-min-microvolt = <300000>; + regulator-max-microvolt = <1193750>; + regulator-enable-ramp-delay = <256>; +- regulator-allowed-modes = <0 1 2 4>; ++ regulator-allowed-modes = <0 1 2>; + }; + + vbuck3 { +@@ -63,7 +63,7 @@ examples: + regulator-min-microvolt = <300000>; + regulator-max-microvolt = <1193750>; + regulator-enable-ramp-delay = <256>; +- regulator-allowed-modes = <0 1 2 4>; ++ regulator-allowed-modes = <0 1 2>; + }; + }; + }; +-- +2.35.1 + diff --git a/queue-5.15/remoteproc-imx_rproc-ignore-create-mem-entry-for-res.patch b/queue-5.15/remoteproc-imx_rproc-ignore-create-mem-entry-for-res.patch new file mode 100644 index 00000000000..182f5cfaa6a --- /dev/null +++ b/queue-5.15/remoteproc-imx_rproc-ignore-create-mem-entry-for-res.patch @@ -0,0 +1,39 @@ +From 50b23e67da216607e7517f1ffeeb319fb3b33ac2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 15 Apr 2022 10:57:37 +0800 +Subject: remoteproc: imx_rproc: Ignore create mem entry for resource table + +From: Peng Fan + +[ Upstream commit 58b7c856519fe946620ee68dd0c37bd3c695484a ] + +Resource table is used by Linux to get information published by +remote processor. It should be not be used for memory allocation, so +not create rproc mem entry. + +Fixes: b29b4249f8f0 ("remoteproc: imx_rproc: add i.MX specific parse fw hook") +Signed-off-by: Peng Fan +Link: https://lore.kernel.org/r/20220415025737.1561976-1-peng.fan@oss.nxp.com +Signed-off-by: Mathieu Poirier +Signed-off-by: Sasha Levin +--- + drivers/remoteproc/imx_rproc.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c +index 05c39e1c56b4..59eae605ad59 100644 +--- a/drivers/remoteproc/imx_rproc.c ++++ b/drivers/remoteproc/imx_rproc.c +@@ -447,6 +447,9 @@ static int imx_rproc_prepare(struct rproc *rproc) + if (!strcmp(it.node->name, "vdev0buffer")) + continue; + ++ if (!strcmp(it.node->name, "rsc-table")) ++ continue; ++ + rmem = of_reserved_mem_lookup(it.node); + if (!rmem) { + dev_err(priv->dev, "unable to acquire memory-region\n"); +-- +2.35.1 + diff --git a/queue-5.15/riscv-read-only-pages-should-not-be-writable.patch b/queue-5.15/riscv-read-only-pages-should-not-be-writable.patch new file mode 100644 index 00000000000..c1fc3f74480 --- /dev/null +++ b/queue-5.15/riscv-read-only-pages-should-not-be-writable.patch @@ -0,0 +1,39 @@ +From 1468f8e976f0aecec56fdf4deb38609f44591417 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 28 May 2022 03:41:32 +0200 +Subject: riscv: read-only pages should not be writable + +From: Heinrich Schuchardt + +[ Upstream commit 630f972d76d6460235e84e1aa034ee06f9c8c3a9 ] + +If EFI pages are marked as read-only, +we should remove the _PAGE_WRITE flag. + +The current code overwrites an unused value. + +Fixes: b91540d52a08b ("RISC-V: Add EFI runtime services") +Signed-off-by: Heinrich Schuchardt +Link: https://lore.kernel.org/r/20220528014132.91052-1-heinrich.schuchardt@canonical.com +Signed-off-by: Ard Biesheuvel +Signed-off-by: Sasha Levin +--- + arch/riscv/kernel/efi.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/riscv/kernel/efi.c b/arch/riscv/kernel/efi.c +index 024159298231..1aa540350abd 100644 +--- a/arch/riscv/kernel/efi.c ++++ b/arch/riscv/kernel/efi.c +@@ -65,7 +65,7 @@ static int __init set_permissions(pte_t *ptep, unsigned long addr, void *data) + + if (md->attribute & EFI_MEMORY_RO) { + val = pte_val(pte) & ~_PAGE_WRITE; +- val = pte_val(pte) | _PAGE_READ; ++ val |= _PAGE_READ; + pte = __pte(val); + } + if (md->attribute & EFI_MEMORY_XP) { +-- +2.35.1 + diff --git a/queue-5.15/rpmsg-qcom_smd-fix-irq_of_parse_and_map-return-value.patch b/queue-5.15/rpmsg-qcom_smd-fix-irq_of_parse_and_map-return-value.patch new file mode 100644 index 00000000000..fc2d9acb5c1 --- /dev/null +++ b/queue-5.15/rpmsg-qcom_smd-fix-irq_of_parse_and_map-return-value.patch @@ -0,0 +1,36 @@ +From 7b4ed1cda04530dd26de5c8600e5fb04e867879b Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 12:53:26 +0200 +Subject: rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value + +From: Krzysztof Kozlowski + +[ Upstream commit 1a358d35066487d228a68303d808bc4721c6b1b9 ] + +The irq_of_parse_and_map() returns 0 on failure, not a negative ERRNO. + +Fixes: 53e2822e56c7 ("rpmsg: Introduce Qualcomm SMD backend") +Signed-off-by: Krzysztof Kozlowski +Signed-off-by: Bjorn Andersson +Link: https://lore.kernel.org/r/20220422105326.78713-1-krzysztof.kozlowski@linaro.org +Signed-off-by: Sasha Levin +--- + drivers/rpmsg/qcom_smd.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/rpmsg/qcom_smd.c b/drivers/rpmsg/qcom_smd.c +index 8da1b5cb31b3..775a7e44ac68 100644 +--- a/drivers/rpmsg/qcom_smd.c ++++ b/drivers/rpmsg/qcom_smd.c +@@ -1404,7 +1404,7 @@ static int qcom_smd_parse_edge(struct device *dev, + edge->name = node->name; + + irq = irq_of_parse_and_map(node, 0); +- if (irq < 0) { ++ if (!irq) { + dev_err(dev, "required smd interrupt missing\n"); + ret = irq; + goto put_node; +-- +2.35.1 + diff --git a/queue-5.15/rpmsg-qcom_smd-fix-returning-0-if-irq_of_parse_and_m.patch b/queue-5.15/rpmsg-qcom_smd-fix-returning-0-if-irq_of_parse_and_m.patch new file mode 100644 index 00000000000..b26a4fa58c5 --- /dev/null +++ b/queue-5.15/rpmsg-qcom_smd-fix-returning-0-if-irq_of_parse_and_m.patch @@ -0,0 +1,37 @@ +From 32c18a8ef53df6c9017f533b6347399999a7938d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 23 Apr 2022 11:39:32 +0200 +Subject: rpmsg: qcom_smd: Fix returning 0 if irq_of_parse_and_map() fails + +From: Krzysztof Kozlowski + +[ Upstream commit 59d6f72f6f9c92fec8757d9e29527da828e9281f ] + +irq_of_parse_and_map() returns 0 on failure, so this should not be +passed further as error return code. + +Fixes: 1a358d350664 ("rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value") +Signed-off-by: Krzysztof Kozlowski +Signed-off-by: Bjorn Andersson +Link: https://lore.kernel.org/r/20220423093932.32136-1-krzysztof.kozlowski@linaro.org +Signed-off-by: Sasha Levin +--- + drivers/rpmsg/qcom_smd.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/rpmsg/qcom_smd.c b/drivers/rpmsg/qcom_smd.c +index 775a7e44ac68..370688e8646b 100644 +--- a/drivers/rpmsg/qcom_smd.c ++++ b/drivers/rpmsg/qcom_smd.c +@@ -1406,7 +1406,7 @@ static int qcom_smd_parse_edge(struct device *dev, + irq = irq_of_parse_and_map(node, 0); + if (!irq) { + dev_err(dev, "required smd interrupt missing\n"); +- ret = irq; ++ ret = -EINVAL; + goto put_node; + } + +-- +2.35.1 + diff --git a/queue-5.15/rpmsg-virtio-fix-possible-double-free-in-rpmsg_probe.patch b/queue-5.15/rpmsg-virtio-fix-possible-double-free-in-rpmsg_probe.patch new file mode 100644 index 00000000000..7ee80606198 --- /dev/null +++ b/queue-5.15/rpmsg-virtio-fix-possible-double-free-in-rpmsg_probe.patch @@ -0,0 +1,50 @@ +From 8e24d338803e4ab1d62d738f918c8dcaf081a31a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 26 Apr 2022 14:05:34 +0800 +Subject: rpmsg: virtio: Fix possible double free in rpmsg_probe() + +From: Hangyu Hua + +[ Upstream commit c2eecefec5df1306eafce28ccdf1ca159a552ecc ] + +vch will be free in virtio_rpmsg_release_device() when +rpmsg_ns_register_device() fails. There is no need to call kfree() again. + +Fix this by changing error path from free_vch to free_ctrldev. + +Fixes: c486682ae1e2 ("rpmsg: virtio: Register the rpmsg_char device") +Signed-off-by: Hangyu Hua +Tested-by: Arnaud Pouliquen +Link: https://lore.kernel.org/r/20220426060536.15594-2-hbh25y@gmail.com +Signed-off-by: Mathieu Poirier +Signed-off-by: Sasha Levin +--- + drivers/rpmsg/virtio_rpmsg_bus.c | 5 ++--- + 1 file changed, 2 insertions(+), 3 deletions(-) + +diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c +index 8e49a3bacfc7..834a0811e371 100644 +--- a/drivers/rpmsg/virtio_rpmsg_bus.c ++++ b/drivers/rpmsg/virtio_rpmsg_bus.c +@@ -964,7 +964,8 @@ static int rpmsg_probe(struct virtio_device *vdev) + + err = rpmsg_ns_register_device(rpdev_ns); + if (err) +- goto free_vch; ++ /* vch will be free in virtio_rpmsg_release_device() */ ++ goto free_ctrldev; + } + + /* +@@ -988,8 +989,6 @@ static int rpmsg_probe(struct virtio_device *vdev) + + return 0; + +-free_vch: +- kfree(vch); + free_ctrldev: + rpmsg_virtio_del_ctrl_dev(rpdev_ctrl); + free_coherent: +-- +2.35.1 + diff --git a/queue-5.15/rpmsg-virtio-fix-possible-double-free-in-rpmsg_virti.patch b/queue-5.15/rpmsg-virtio-fix-possible-double-free-in-rpmsg_virti.patch new file mode 100644 index 00000000000..a9d34e55929 --- /dev/null +++ b/queue-5.15/rpmsg-virtio-fix-possible-double-free-in-rpmsg_virti.patch @@ -0,0 +1,40 @@ +From 57948ff24acfa97456a14926e9b5031ecc372fe4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 26 Apr 2022 14:05:35 +0800 +Subject: rpmsg: virtio: Fix possible double free in + rpmsg_virtio_add_ctrl_dev() + +From: Hangyu Hua + +[ Upstream commit 1680939e9ecf7764fba8689cfb3429c2fe2bb23c ] + +vch will be free in virtio_rpmsg_release_device() when +rpmsg_ctrldev_register_device() fails. There is no need to call +kfree() again. + +Fixes: c486682ae1e2 ("rpmsg: virtio: Register the rpmsg_char device") +Signed-off-by: Hangyu Hua +Tested-by: Arnaud Pouliquen +Link: https://lore.kernel.org/r/20220426060536.15594-3-hbh25y@gmail.com +Signed-off-by: Mathieu Poirier +Signed-off-by: Sasha Levin +--- + drivers/rpmsg/virtio_rpmsg_bus.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c +index 834a0811e371..3a62e6197151 100644 +--- a/drivers/rpmsg/virtio_rpmsg_bus.c ++++ b/drivers/rpmsg/virtio_rpmsg_bus.c +@@ -842,7 +842,7 @@ static struct rpmsg_device *rpmsg_virtio_add_ctrl_dev(struct virtio_device *vdev + + err = rpmsg_chrdev_register_device(rpdev_ctrl); + if (err) { +- kfree(vch); ++ /* vch will be free in virtio_rpmsg_release_device() */ + return ERR_PTR(err); + } + +-- +2.35.1 + diff --git a/queue-5.15/rpmsg-virtio-fix-the-unregistration-of-the-device-rp.patch b/queue-5.15/rpmsg-virtio-fix-the-unregistration-of-the-device-rp.patch new file mode 100644 index 00000000000..90c3934c06b --- /dev/null +++ b/queue-5.15/rpmsg-virtio-fix-the-unregistration-of-the-device-rp.patch @@ -0,0 +1,40 @@ +From 1d3e9f5617c053c0920bac01ad2fb4dd7bf5280f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 26 Apr 2022 14:05:36 +0800 +Subject: rpmsg: virtio: Fix the unregistration of the device rpmsg_ctrl + +From: Arnaud Pouliquen + +[ Upstream commit df191796985922488e4e6b64f7bd79c3934412f2 ] + +Unregister the rpmsg_ctrl device instead of just freeing the +the virtio_rpmsg_channel structure. +This will properly unregister the device and call +virtio_rpmsg_release_device() that frees the structure. + +Fixes: c486682ae1e2 ("rpmsg: virtio: Register the rpmsg_char device") +Signed-off-by: Arnaud Pouliquen +Reviewed-by: Hangyu Hua +Link: https://lore.kernel.org/r/20220426060536.15594-4-hbh25y@gmail.com +Signed-off-by: Mathieu Poirier +Signed-off-by: Sasha Levin +--- + drivers/rpmsg/virtio_rpmsg_bus.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c +index 3a62e6197151..b03e7404212f 100644 +--- a/drivers/rpmsg/virtio_rpmsg_bus.c ++++ b/drivers/rpmsg/virtio_rpmsg_bus.c +@@ -853,7 +853,7 @@ static void rpmsg_virtio_del_ctrl_dev(struct rpmsg_device *rpdev_ctrl) + { + if (!rpdev_ctrl) + return; +- kfree(to_virtio_rpmsg_channel(rpdev_ctrl)); ++ device_unregister(&rpdev_ctrl->dev); + } + + static int rpmsg_probe(struct virtio_device *vdev) +-- +2.35.1 + diff --git a/queue-5.15/rtc-ftrtc010-fix-error-handling-in-ftrtc010_rtc_prob.patch b/queue-5.15/rtc-ftrtc010-fix-error-handling-in-ftrtc010_rtc_prob.patch new file mode 100644 index 00000000000..01c4608104b --- /dev/null +++ b/queue-5.15/rtc-ftrtc010-fix-error-handling-in-ftrtc010_rtc_prob.patch @@ -0,0 +1,94 @@ +From ee88b6ca6a935a66e511ac806caaeb3a8f75f7ba Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 3 Apr 2022 05:49:12 +0000 +Subject: rtc: ftrtc010: Fix error handling in ftrtc010_rtc_probe + +From: Miaoqian Lin + +[ Upstream commit b520cbe5be37b1b9b401c0b6ecbdae32575273db ] + +In the error handling path, the clk_prepare_enable() function +call should be balanced by a corresponding 'clk_disable_unprepare()' +call , as already done in the remove function. + +clk_disable_unprepare calls clk_disable() and clk_unprepare(). +They will use IS_ERR_OR_NULL to check the argument. + +Fixes: ac05fba39cc5 ("rtc: gemini: Add optional clock handling") +Signed-off-by: Miaoqian Lin +Reviewed-by: Linus Walleij +Signed-off-by: Alexandre Belloni +Link: https://lore.kernel.org/r/20220403054912.31739-1-linmq006@gmail.com +Signed-off-by: Sasha Levin +--- + drivers/rtc/rtc-ftrtc010.c | 34 ++++++++++++++++++++++++---------- + 1 file changed, 24 insertions(+), 10 deletions(-) + +diff --git a/drivers/rtc/rtc-ftrtc010.c b/drivers/rtc/rtc-ftrtc010.c +index 53bb08fe1cd4..25c6e7d9570f 100644 +--- a/drivers/rtc/rtc-ftrtc010.c ++++ b/drivers/rtc/rtc-ftrtc010.c +@@ -137,26 +137,34 @@ static int ftrtc010_rtc_probe(struct platform_device *pdev) + ret = clk_prepare_enable(rtc->extclk); + if (ret) { + dev_err(dev, "failed to enable EXTCLK\n"); +- return ret; ++ goto err_disable_pclk; + } + } + + rtc->rtc_irq = platform_get_irq(pdev, 0); +- if (rtc->rtc_irq < 0) +- return rtc->rtc_irq; ++ if (rtc->rtc_irq < 0) { ++ ret = rtc->rtc_irq; ++ goto err_disable_extclk; ++ } + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); +- if (!res) +- return -ENODEV; ++ if (!res) { ++ ret = -ENODEV; ++ goto err_disable_extclk; ++ } + + rtc->rtc_base = devm_ioremap(dev, res->start, + resource_size(res)); +- if (!rtc->rtc_base) +- return -ENOMEM; ++ if (!rtc->rtc_base) { ++ ret = -ENOMEM; ++ goto err_disable_extclk; ++ } + + rtc->rtc_dev = devm_rtc_allocate_device(dev); +- if (IS_ERR(rtc->rtc_dev)) +- return PTR_ERR(rtc->rtc_dev); ++ if (IS_ERR(rtc->rtc_dev)) { ++ ret = PTR_ERR(rtc->rtc_dev); ++ goto err_disable_extclk; ++ } + + rtc->rtc_dev->ops = &ftrtc010_rtc_ops; + +@@ -172,9 +180,15 @@ static int ftrtc010_rtc_probe(struct platform_device *pdev) + ret = devm_request_irq(dev, rtc->rtc_irq, ftrtc010_rtc_interrupt, + IRQF_SHARED, pdev->name, dev); + if (unlikely(ret)) +- return ret; ++ goto err_disable_extclk; + + return devm_rtc_register_device(rtc->rtc_dev); ++ ++err_disable_extclk: ++ clk_disable_unprepare(rtc->extclk); ++err_disable_pclk: ++ clk_disable_unprepare(rtc->pclk); ++ return ret; + } + + static int ftrtc010_rtc_remove(struct platform_device *pdev) +-- +2.35.1 + diff --git a/queue-5.15/rtc-ftrtc010-use-platform_get_irq-to-get-the-interru.patch b/queue-5.15/rtc-ftrtc010-use-platform_get_irq-to-get-the-interru.patch new file mode 100644 index 00000000000..879847feecc --- /dev/null +++ b/queue-5.15/rtc-ftrtc010-use-platform_get_irq-to-get-the-interru.patch @@ -0,0 +1,49 @@ +From ab05a06e2d870d365730c2dad474a50d06276fe4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 20 Dec 2021 01:15:24 +0000 +Subject: rtc: ftrtc010: Use platform_get_irq() to get the interrupt + +From: Lad Prabhakar + +[ Upstream commit 05020a733b02cf7a474305e620fb306cd3abfe84 ] + +platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static +allocation of IRQ resources in DT core code, this causes an issue +when using hierarchical interrupt domains using "interrupts" property +in the node as this bypasses the hierarchical setup and messes up the +irq chaining. + +In preparation for removal of static setup of IRQ resource from DT core +code use platform_get_irq(). + +Signed-off-by: Lad Prabhakar +Reviewed-by: Linus Walleij +Signed-off-by: Alexandre Belloni +Link: https://lore.kernel.org/r/20211220011524.17206-1-prabhakar.mahadev-lad.rj@bp.renesas.com +Signed-off-by: Sasha Levin +--- + drivers/rtc/rtc-ftrtc010.c | 8 +++----- + 1 file changed, 3 insertions(+), 5 deletions(-) + +diff --git a/drivers/rtc/rtc-ftrtc010.c b/drivers/rtc/rtc-ftrtc010.c +index ad3add5db4c8..53bb08fe1cd4 100644 +--- a/drivers/rtc/rtc-ftrtc010.c ++++ b/drivers/rtc/rtc-ftrtc010.c +@@ -141,11 +141,9 @@ static int ftrtc010_rtc_probe(struct platform_device *pdev) + } + } + +- res = platform_get_resource(pdev, IORESOURCE_IRQ, 0); +- if (!res) +- return -ENODEV; +- +- rtc->rtc_irq = res->start; ++ rtc->rtc_irq = platform_get_irq(pdev, 0); ++ if (rtc->rtc_irq < 0) ++ return rtc->rtc_irq; + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); + if (!res) +-- +2.35.1 + diff --git a/queue-5.15/rtc-mt6397-check-return-value-after-calling-platform.patch b/queue-5.15/rtc-mt6397-check-return-value-after-calling-platform.patch new file mode 100644 index 00000000000..61a216c352d --- /dev/null +++ b/queue-5.15/rtc-mt6397-check-return-value-after-calling-platform.patch @@ -0,0 +1,38 @@ +From af576b20f1e8da9ce56a45be762f4ae7467209f3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 5 May 2022 20:50:43 +0800 +Subject: rtc: mt6397: check return value after calling platform_get_resource() + +From: Yang Yingliang + +[ Upstream commit d3b43eb505bffb8e4cdf6800c15660c001553fe6 ] + +It will cause null-ptr-deref if platform_get_resource() returns NULL, +we need check the return value. + +Fixes: fc2979118f3f ("rtc: mediatek: Add MT6397 RTC driver") +Signed-off-by: Yang Yingliang +Reviewed-by: AngeloGioacchino Del Regno +Signed-off-by: Alexandre Belloni +Link: https://lore.kernel.org/r/20220505125043.1594771-1-yangyingliang@huawei.com +Signed-off-by: Sasha Levin +--- + drivers/rtc/rtc-mt6397.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/rtc/rtc-mt6397.c b/drivers/rtc/rtc-mt6397.c +index 80dc479a6ff0..1d297af80f87 100644 +--- a/drivers/rtc/rtc-mt6397.c ++++ b/drivers/rtc/rtc-mt6397.c +@@ -269,6 +269,8 @@ static int mtk_rtc_probe(struct platform_device *pdev) + return -ENOMEM; + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); ++ if (!res) ++ return -EINVAL; + rtc->addr_base = res->start; + + rtc->data = of_device_get_match_data(&pdev->dev); +-- +2.35.1 + diff --git a/queue-5.15/s390-crypto-fix-scatterwalk_unmap-callers-in-aes-gcm.patch b/queue-5.15/s390-crypto-fix-scatterwalk_unmap-callers-in-aes-gcm.patch new file mode 100644 index 00000000000..57c329619ca --- /dev/null +++ b/queue-5.15/s390-crypto-fix-scatterwalk_unmap-callers-in-aes-gcm.patch @@ -0,0 +1,52 @@ +From d34c52afdf7ac2dba04cb75432dc770d3f0e0e0d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 17 May 2022 16:30:47 +0200 +Subject: s390/crypto: fix scatterwalk_unmap() callers in AES-GCM + +From: Jann Horn + +[ Upstream commit bd52cd5e23f134019b23f0c389db0f9a436e4576 ] + +The argument of scatterwalk_unmap() is supposed to be the void* that was +returned by the previous scatterwalk_map() call. +The s390 AES-GCM implementation was instead passing the pointer to the +struct scatter_walk. + +This doesn't actually break anything because scatterwalk_unmap() only uses +its argument under CONFIG_HIGHMEM and ARCH_HAS_FLUSH_ON_KUNMAP. + +Fixes: bf7fa038707c ("s390/crypto: add s390 platform specific aes gcm support.") +Signed-off-by: Jann Horn +Acked-by: Harald Freudenberger +Link: https://lore.kernel.org/r/20220517143047.3054498-1-jannh@google.com +Signed-off-by: Heiko Carstens +Signed-off-by: Sasha Levin +--- + arch/s390/crypto/aes_s390.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/arch/s390/crypto/aes_s390.c b/arch/s390/crypto/aes_s390.c +index 54c7536f2482..1023e9d43d44 100644 +--- a/arch/s390/crypto/aes_s390.c ++++ b/arch/s390/crypto/aes_s390.c +@@ -701,7 +701,7 @@ static inline void _gcm_sg_unmap_and_advance(struct gcm_sg_walk *gw, + unsigned int nbytes) + { + gw->walk_bytes_remain -= nbytes; +- scatterwalk_unmap(&gw->walk); ++ scatterwalk_unmap(gw->walk_ptr); + scatterwalk_advance(&gw->walk, nbytes); + scatterwalk_done(&gw->walk, 0, gw->walk_bytes_remain); + gw->walk_ptr = NULL; +@@ -776,7 +776,7 @@ static int gcm_out_walk_go(struct gcm_sg_walk *gw, unsigned int minbytesneeded) + goto out; + } + +- scatterwalk_unmap(&gw->walk); ++ scatterwalk_unmap(gw->walk_ptr); + gw->walk_ptr = NULL; + + gw->ptr = gw->buf; +-- +2.35.1 + diff --git a/queue-5.15/s390-mcck-isolate-sie-instruction-when-setting-cif_m.patch b/queue-5.15/s390-mcck-isolate-sie-instruction-when-setting-cif_m.patch new file mode 100644 index 00000000000..76026dad7cf --- /dev/null +++ b/queue-5.15/s390-mcck-isolate-sie-instruction-when-setting-cif_m.patch @@ -0,0 +1,57 @@ +From a7ee291ae3c523ac2f8897f110dea833ccf08df4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 23 May 2022 12:38:14 +0200 +Subject: s390/mcck: isolate SIE instruction when setting CIF_MCCK_GUEST flag + +From: Alexander Gordeev + +[ Upstream commit 29ccaa4b35ea874ddd50518e5c2c746b9238a792 ] + +Commit d768bd892fc8 ("s390: add options to change branch prediction +behaviour for the kernel") introduced .Lsie_exit label - supposedly +to fence off SIE instruction. However, the corresponding address +range length .Lsie_crit_mcck_length was not updated, which led to +BPON code potentionally marked with CIF_MCCK_GUEST flag. + +Both .Lsie_exit and .Lsie_crit_mcck_length were removed with commit +0b0ed657fe00 ("s390: remove critical section cleanup from entry.S"), +but the issue persisted - currently BPOFF and BPENTER macros might +get wrongly considered by the machine check handler as a guest. + +Fixes: d768bd892fc8 ("s390: add options to change branch prediction behaviour for the kernel") +Reviewed-by: Sven Schnelle +Reviewed-by: Christian Borntraeger +Signed-off-by: Alexander Gordeev +Signed-off-by: Heiko Carstens +Signed-off-by: Sasha Levin +--- + arch/s390/kernel/entry.S | 6 +++++- + 1 file changed, 5 insertions(+), 1 deletion(-) + +diff --git a/arch/s390/kernel/entry.S b/arch/s390/kernel/entry.S +index 4c9b967290ae..d530eb4dc413 100644 +--- a/arch/s390/kernel/entry.S ++++ b/arch/s390/kernel/entry.S +@@ -248,6 +248,10 @@ ENTRY(sie64a) + BPEXIT __SF_SIE_FLAGS(%r15),(_TIF_ISOLATE_BP|_TIF_ISOLATE_BP_GUEST) + .Lsie_entry: + sie 0(%r14) ++# Let the next instruction be NOP to avoid triggering a machine check ++# and handling it in a guest as result of the instruction execution. ++ nopr 7 ++.Lsie_leave: + BPOFF + BPENTER __SF_SIE_FLAGS(%r15),(_TIF_ISOLATE_BP|_TIF_ISOLATE_BP_GUEST) + .Lsie_skip: +@@ -536,7 +540,7 @@ ENTRY(mcck_int_handler) + jno .Lmcck_panic + #if IS_ENABLED(CONFIG_KVM) + OUTSIDE %r9,.Lsie_gmap,.Lsie_done,6f +- OUTSIDE %r9,.Lsie_entry,.Lsie_skip,4f ++ OUTSIDE %r9,.Lsie_entry,.Lsie_leave,4f + oi __LC_CPU_FLAGS+7, _CIF_MCCK_GUEST + j 5f + 4: CHKSTG .Lmcck_panic +-- +2.35.1 + diff --git a/queue-5.15/scsi-sd-fix-potential-null-pointer-dereference.patch b/queue-5.15/scsi-sd-fix-potential-null-pointer-dereference.patch new file mode 100644 index 00000000000..344fc650735 --- /dev/null +++ b/queue-5.15/scsi-sd-fix-potential-null-pointer-dereference.patch @@ -0,0 +1,47 @@ +From 5233dec21d8f0e9481a280a30ad3391107c891b8 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 1 Jun 2022 15:25:43 +0900 +Subject: scsi: sd: Fix potential NULL pointer dereference + +From: Damien Le Moal + +[ Upstream commit 05fbde3a77a4f1d62e4c4428f384288c1f1a0be5 ] + +If sd_probe() sees an early error before sdkp->device is initialized, +sd_zbc_release_disk() is called. This causes a NULL pointer dereference +when sd_is_zoned() is called inside that function. Avoid this by removing +the call to sd_zbc_release_disk() in sd_probe() error path. + +This change is safe and does not result in zone information memory leakage +because the zone information for a zoned disk is allocated only when +sd_revalidate_disk() is called, at which point sdkp->disk_dev is fully set, +resulting in sd_disk_release() being called when needed to cleanup a disk +zone information using sd_zbc_release_disk(). + +Link: https://lore.kernel.org/r/20220601062544.905141-2-damien.lemoal@opensource.wdc.com +Fixes: 89d947561077 ("sd: Implement support for ZBC devices") +Reported-by: Dongliang Mu +Suggested-by: Christoph Hellwig +Reviewed-by: Christoph Hellwig +Signed-off-by: Damien Le Moal +Signed-off-by: Martin K. Petersen +Signed-off-by: Sasha Levin +--- + drivers/scsi/sd.c | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c +index a713babaee0f..de6640ad1943 100644 +--- a/drivers/scsi/sd.c ++++ b/drivers/scsi/sd.c +@@ -3480,7 +3480,6 @@ static int sd_probe(struct device *dev) + out_put: + put_disk(gd); + out_free: +- sd_zbc_release_disk(sdkp); + kfree(sdkp); + out: + scsi_autopm_put_device(sdp); +-- +2.35.1 + diff --git a/queue-5.15/selftests-bpf-fix-selftest-after-random-urandom_read.patch b/queue-5.15/selftests-bpf-fix-selftest-after-random-urandom_read.patch new file mode 100644 index 00000000000..5843e0ebeb9 --- /dev/null +++ b/queue-5.15/selftests-bpf-fix-selftest-after-random-urandom_read.patch @@ -0,0 +1,53 @@ +From d77386e4a246eac55091d81be254838e1554ba1f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 25 Mar 2022 15:56:43 -0700 +Subject: selftests/bpf: fix selftest after random: Urandom_read tracepoint + removal + +From: Andrii Nakryiko + +[ Upstream commit 99dea2c664d7bc7e4f6f6947182d0d365165a998 ] + +14c174633f34 ("random: remove unused tracepoints") removed all the +tracepoints from drivers/char/random.c, one of which, +random:urandom_read, was used by stacktrace_build_id selftest to trigger +stack trace capture. + +Fix breakage by switching to kprobing urandom_read() function. + +Suggested-by: Yonghong Song +Signed-off-by: Andrii Nakryiko +Signed-off-by: Alexei Starovoitov +Acked-by: Yonghong Song +Link: https://lore.kernel.org/bpf/20220325225643.2606-1-andrii@kernel.org +Signed-off-by: Sasha Levin +--- + .../selftests/bpf/progs/test_stacktrace_build_id.c | 12 ++---------- + 1 file changed, 2 insertions(+), 10 deletions(-) + +diff --git a/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c b/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c +index 0cf0134631b4..08aee18d9ded 100644 +--- a/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c ++++ b/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c +@@ -39,16 +39,8 @@ struct { + __type(value, stack_trace_t); + } stack_amap SEC(".maps"); + +-/* taken from /sys/kernel/debug/tracing/events/random/urandom_read/format */ +-struct random_urandom_args { +- unsigned long long pad; +- int got_bits; +- int pool_left; +- int input_left; +-}; +- +-SEC("tracepoint/random/urandom_read") +-int oncpu(struct random_urandom_args *args) ++SEC("kprobe/urandom_read") ++int oncpu(struct pt_regs *args) + { + __u32 max_len = sizeof(struct bpf_stack_build_id) + * PERF_MAX_STACK_DEPTH; +-- +2.35.1 + diff --git a/queue-5.15/selftests-bpf-fix-stacktrace_build_id-with-missing-k.patch b/queue-5.15/selftests-bpf-fix-stacktrace_build_id-with-missing-k.patch new file mode 100644 index 00000000000..f278f9c58a8 --- /dev/null +++ b/queue-5.15/selftests-bpf-fix-stacktrace_build_id-with-missing-k.patch @@ -0,0 +1,51 @@ +From 8a82a77b6166a6ce3266c032eac3032e46a7cbbd Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 26 May 2022 12:16:08 -0700 +Subject: selftests/bpf: fix stacktrace_build_id with missing + kprobe/urandom_read + +From: Song Liu + +[ Upstream commit 59ed76fe2f981bccde37bdddb465f260a96a2404 ] + +Kernel function urandom_read is replaced with urandom_read_iter. +Therefore, kprobe on urandom_read is not working any more: + +[root@eth50-1 bpf]# ./test_progs -n 161 +test_stacktrace_build_id:PASS:skel_open_and_load 0 nsec +libbpf: kprobe perf_event_open() failed: No such file or directory +libbpf: prog 'oncpu': failed to create kprobe 'urandom_read+0x0' \ + perf event: No such file or directory +libbpf: prog 'oncpu': failed to auto-attach: -2 +test_stacktrace_build_id:FAIL:attach_tp err -2 +161 stacktrace_build_id:FAIL + +Fix this by replacing urandom_read with urandom_read_iter in the test. + +Fixes: 1b388e7765f2 ("random: convert to using fops->read_iter()") +Reported-by: Mykola Lysenko +Signed-off-by: Song Liu +Acked-by: David Vernet +Link: https://lore.kernel.org/r/20220526191608.2364049-1-song@kernel.org +Signed-off-by: Alexei Starovoitov +Signed-off-by: Sasha Levin +--- + tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c b/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c +index 08aee18d9ded..58fbe22a3bf8 100644 +--- a/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c ++++ b/tools/testing/selftests/bpf/progs/test_stacktrace_build_id.c +@@ -39,7 +39,7 @@ struct { + __type(value, stack_trace_t); + } stack_amap SEC(".maps"); + +-SEC("kprobe/urandom_read") ++SEC("kprobe/urandom_read_iter") + int oncpu(struct pt_regs *args) + { + __u32 max_len = sizeof(struct bpf_stack_build_id) +-- +2.35.1 + diff --git a/queue-5.15/serial-8250_aspeed_vuart-fix-potential-null-derefere.patch b/queue-5.15/serial-8250_aspeed_vuart-fix-potential-null-derefere.patch new file mode 100644 index 00000000000..d83b8cdb0ad --- /dev/null +++ b/queue-5.15/serial-8250_aspeed_vuart-fix-potential-null-derefere.patch @@ -0,0 +1,38 @@ +From 0f23cd394ba1a238e47aee89f9c45e5f5d960e9a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 4 Apr 2022 14:38:40 +0000 +Subject: serial: 8250_aspeed_vuart: Fix potential NULL dereference in + aspeed_vuart_probe + +From: Miaoqian Lin + +[ Upstream commit 0e0fd55719fa081de6f9e5d9e6cef48efb04d34a ] + +platform_get_resource() may fail and return NULL, so we should +better check it's return value to avoid a NULL pointer dereference. + +Fixes: 54da3e381c2b ("serial: 8250_aspeed_vuart: use UPF_IOREMAP to set up register mapping") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220404143842.16960-1-linmq006@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/8250/8250_aspeed_vuart.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/tty/serial/8250/8250_aspeed_vuart.c b/drivers/tty/serial/8250/8250_aspeed_vuart.c +index c2cecc6f47db..179bb1375636 100644 +--- a/drivers/tty/serial/8250/8250_aspeed_vuart.c ++++ b/drivers/tty/serial/8250/8250_aspeed_vuart.c +@@ -429,6 +429,8 @@ static int aspeed_vuart_probe(struct platform_device *pdev) + timer_setup(&vuart->unthrottle_timer, aspeed_vuart_unthrottle_exp, 0); + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); ++ if (!res) ++ return -EINVAL; + + memset(&port, 0, sizeof(port)); + port.port.private_data = vuart; +-- +2.35.1 + diff --git a/queue-5.15/serial-8250_fintek-check-ser_rs485_rts_-only-with-rs.patch b/queue-5.15/serial-8250_fintek-check-ser_rs485_rts_-only-with-rs.patch new file mode 100644 index 00000000000..77ec1c8c378 --- /dev/null +++ b/queue-5.15/serial-8250_fintek-check-ser_rs485_rts_-only-with-rs.patch @@ -0,0 +1,61 @@ +From c99a630075d1267c8f3443e3bfc92eeec4c3bb92 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 13 May 2022 16:46:43 +0300 +Subject: serial: 8250_fintek: Check SER_RS485_RTS_* only with RS485 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit af0179270977508df6986b51242825d7edd59caf ] + +SER_RS485_RTS_ON_SEND and SER_RS485_RTS_AFTER_SEND relate to behavior +within RS485 operation. The driver checks if they have the same value +which is not possible to realize with the hardware. The check is taken +regardless of SER_RS485_ENABLED flag and -EINVAL is returned when the +check fails, which creates problems. + +This check makes it unnecessarily complicated to turn RS485 mode off as +simple zeroed serial_rs485 struct will trigger that equal values check. +In addition, the driver itself memsets its rs485 structure to zero when +RS485 is disabled but if userspace would try to make an TIOCSRS485 +ioctl() call with the very same struct, it would end up failing with +-EINVAL which doesn't make much sense. + +Resolve the problem by moving the check inside SER_RS485_ENABLED block. + +Fixes: 7ecc77011c6f ("serial: 8250_fintek: Return -EINVAL on invalid configuration") +Cc: Ricardo Ribalda Delgado +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/035c738-8ea5-8b17-b1d7-84a7b3aeaa51@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/8250/8250_fintek.c | 8 ++++---- + 1 file changed, 4 insertions(+), 4 deletions(-) + +diff --git a/drivers/tty/serial/8250/8250_fintek.c b/drivers/tty/serial/8250/8250_fintek.c +index 251f0018ae8c..dba5950b8d0e 100644 +--- a/drivers/tty/serial/8250/8250_fintek.c ++++ b/drivers/tty/serial/8250/8250_fintek.c +@@ -200,12 +200,12 @@ static int fintek_8250_rs485_config(struct uart_port *port, + if (!pdata) + return -EINVAL; + +- /* Hardware do not support same RTS level on send and receive */ +- if (!(rs485->flags & SER_RS485_RTS_ON_SEND) == +- !(rs485->flags & SER_RS485_RTS_AFTER_SEND)) +- return -EINVAL; + + if (rs485->flags & SER_RS485_ENABLED) { ++ /* Hardware do not support same RTS level on send and receive */ ++ if (!(rs485->flags & SER_RS485_RTS_ON_SEND) == ++ !(rs485->flags & SER_RS485_RTS_AFTER_SEND)) ++ return -EINVAL; + memset(rs485->padding, 0, sizeof(rs485->padding)); + config |= RS485_URA; + } else { +-- +2.35.1 + diff --git a/queue-5.15/serial-cpm_uart-fix-build-error-without-config_seria.patch b/queue-5.15/serial-cpm_uart-fix-build-error-without-config_seria.patch new file mode 100644 index 00000000000..5cc10c08f3e --- /dev/null +++ b/queue-5.15/serial-cpm_uart-fix-build-error-without-config_seria.patch @@ -0,0 +1,45 @@ +From 4ab78b63715d53efa5d8c583319513be507c4be6 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 18 May 2022 21:54:52 +0800 +Subject: serial: cpm_uart: Fix build error without CONFIG_SERIAL_CPM_CONSOLE +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: YueHaibing + +[ Upstream commit 0258502f11a4f6036b5f8b34b09027c8a92def3a ] + +drivers/tty/serial/cpm_uart/cpm_uart_core.c: In function ‘cpm_uart_init_port’: +drivers/tty/serial/cpm_uart/cpm_uart_core.c:1251:7: error: ‘udbg_port’ undeclared (first use in this function); did you mean ‘uart_port’? + if (!udbg_port) + ^~~~~~~~~ + uart_port + +commit d142585bceb3 leave this corner, wrap it with #ifdef block + +Fixes: d142585bceb3 ("serial: cpm_uart: Protect udbg definitions by CONFIG_SERIAL_CPM_CONSOLE") +Signed-off-by: YueHaibing +Link: https://lore.kernel.org/r/20220518135452.39480-1-yuehaibing@huawei.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/cpm_uart/cpm_uart_core.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/tty/serial/cpm_uart/cpm_uart_core.c b/drivers/tty/serial/cpm_uart/cpm_uart_core.c +index d6d3db9c3b1f..db07d6a5d764 100644 +--- a/drivers/tty/serial/cpm_uart/cpm_uart_core.c ++++ b/drivers/tty/serial/cpm_uart/cpm_uart_core.c +@@ -1247,7 +1247,7 @@ static int cpm_uart_init_port(struct device_node *np, + } + + #ifdef CONFIG_PPC_EARLY_DEBUG_CPM +-#ifdef CONFIG_CONSOLE_POLL ++#if defined(CONFIG_CONSOLE_POLL) && defined(CONFIG_SERIAL_CPM_CONSOLE) + if (!udbg_port) + #endif + udbg_putc = NULL; +-- +2.35.1 + diff --git a/queue-5.15/serial-digicolor-usart-don-t-allow-cs5-6.patch b/queue-5.15/serial-digicolor-usart-don-t-allow-cs5-6.patch new file mode 100644 index 00000000000..f86a0f3073c --- /dev/null +++ b/queue-5.15/serial-digicolor-usart-don-t-allow-cs5-6.patch @@ -0,0 +1,46 @@ +From 2d257aba715b6783b4b5447a2fef0bfec9eca147 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:01 +0300 +Subject: serial: digicolor-usart: Don't allow CS5-6 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit fd63031b8c0763addcecdefe0e0c59d49646204e ] + +Only CS7 and CS8 seem supported but CSIZE is not sanitized to CS8 in +the default: block. + +Set CSIZE correctly so that userspace knows the effective value. +Incorrect CSIZE also results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Fixes: 5930cb3511df (serial: driver for Conexant Digicolor USART) +Acked-by: Baruch Siach +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-3-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/digicolor-usart.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/tty/serial/digicolor-usart.c b/drivers/tty/serial/digicolor-usart.c +index c7f81aa1ce91..5fea9bf86e85 100644 +--- a/drivers/tty/serial/digicolor-usart.c ++++ b/drivers/tty/serial/digicolor-usart.c +@@ -309,6 +309,8 @@ static void digicolor_uart_set_termios(struct uart_port *port, + case CS8: + default: + config |= UA_CONFIG_CHAR_LEN; ++ termios->c_cflag &= ~CSIZE; ++ termios->c_cflag |= CS8; + break; + } + +-- +2.35.1 + diff --git a/queue-5.15/serial-meson-acquire-port-lock-in-startup.patch b/queue-5.15/serial-meson-acquire-port-lock-in-startup.patch new file mode 100644 index 00000000000..73027d491eb --- /dev/null +++ b/queue-5.15/serial-meson-acquire-port-lock-in-startup.patch @@ -0,0 +1,98 @@ +From 00f10d9dda52f2cf4c2a795b0a330c0594ce3ca0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 8 May 2022 12:41:47 +0206 +Subject: serial: meson: acquire port->lock in startup() + +From: John Ogness + +[ Upstream commit 589f892ac8ef244e47c5a00ffd8605daa1eaef8e ] + +The uart_ops startup() callback is called without interrupts +disabled and without port->lock locked, relatively late during the +boot process (from the call path of console_on_rootfs()). If the +device is a console, it was already previously registered and could +be actively printing messages. + +Since the startup() callback is reading/writing registers used by +the console write() callback (AML_UART_CONTROL), its access must +be synchronized using the port->lock. Currently it is not. + +The startup() callback is the only function that explicitly enables +interrupts. Without the synchronization, it is possible that +interrupts become accidentally permanently disabled. + +CPU0 CPU1 +meson_serial_console_write meson_uart_startup +-------------------------- ------------------ +spin_lock(port->lock) +val = readl(AML_UART_CONTROL) +uart_console_write() + writel(INT_EN, AML_UART_CONTROL) +writel(val, AML_UART_CONTROL) +spin_unlock(port->lock) + +Add port->lock synchronization to meson_uart_startup() to avoid +racing with meson_serial_console_write(). + +Also add detailed comments to meson_uart_reset() explaining why it +is *not* using port->lock synchronization. + +Link: https://lore.kernel.org/lkml/2a82eae7-a256-f70c-fd82-4e510750906e@samsung.com +Fixes: ff7693d079e5 ("ARM: meson: serial: add MesonX SoC on-chip uart driver") +Reported-by: Marek Szyprowski +Tested-by: Marek Szyprowski +Reviewed-by: Petr Mladek +Reviewed-by: Jiri Slaby +Acked-by: Neil Armstrong +Signed-off-by: John Ogness +Link: https://lore.kernel.org/r/20220508103547.626355-1-john.ogness@linutronix.de +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/meson_uart.c | 13 +++++++++++++ + 1 file changed, 13 insertions(+) + +diff --git a/drivers/tty/serial/meson_uart.c b/drivers/tty/serial/meson_uart.c +index efee3935917f..62e6c1af1344 100644 +--- a/drivers/tty/serial/meson_uart.c ++++ b/drivers/tty/serial/meson_uart.c +@@ -253,6 +253,14 @@ static const char *meson_uart_type(struct uart_port *port) + return (port->type == PORT_MESON) ? "meson_uart" : NULL; + } + ++/* ++ * This function is called only from probe() using a temporary io mapping ++ * in order to perform a reset before setting up the device. Since the ++ * temporarily mapped region was successfully requested, there can be no ++ * console on this port at this time. Hence it is not necessary for this ++ * function to acquire the port->lock. (Since there is no console on this ++ * port at this time, the port->lock is not initialized yet.) ++ */ + static void meson_uart_reset(struct uart_port *port) + { + u32 val; +@@ -267,9 +275,12 @@ static void meson_uart_reset(struct uart_port *port) + + static int meson_uart_startup(struct uart_port *port) + { ++ unsigned long flags; + u32 val; + int ret = 0; + ++ spin_lock_irqsave(&port->lock, flags); ++ + val = readl(port->membase + AML_UART_CONTROL); + val |= AML_UART_CLEAR_ERR; + writel(val, port->membase + AML_UART_CONTROL); +@@ -285,6 +296,8 @@ static int meson_uart_startup(struct uart_port *port) + val = (AML_UART_RECV_IRQ(1) | AML_UART_XMIT_IRQ(port->fifosize / 2)); + writel(val, port->membase + AML_UART_MISC); + ++ spin_unlock_irqrestore(&port->lock, flags); ++ + ret = request_irq(port->irq, meson_uart_interrupt, 0, + port->name, port); + +-- +2.35.1 + diff --git a/queue-5.15/serial-rda-uart-don-t-allow-cs5-6.patch b/queue-5.15/serial-rda-uart-don-t-allow-cs5-6.patch new file mode 100644 index 00000000000..977ea970f40 --- /dev/null +++ b/queue-5.15/serial-rda-uart-don-t-allow-cs5-6.patch @@ -0,0 +1,46 @@ +From 89aceaba652a706eabc55aeb7c2d2f3f320986eb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:02 +0300 +Subject: serial: rda-uart: Don't allow CS5-6 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit 098333a9c7d12bb3ce44c82f08b4d810c44d31b0 ] + +Only CS7 and CS8 are supported but CSIZE is not sanitized after +fallthrough from CS5 or CS6 to CS7. + +Set CSIZE correctly so that userspace knows the effective value. +Incorrect CSIZE also results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Fixes: c10b13325ced (tty: serial: Add RDA8810PL UART driver) +Cc: Manivannan Sadhasivam +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-4-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/rda-uart.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/tty/serial/rda-uart.c b/drivers/tty/serial/rda-uart.c +index d550d8fa2fab..a8fe1c3ebcd9 100644 +--- a/drivers/tty/serial/rda-uart.c ++++ b/drivers/tty/serial/rda-uart.c +@@ -262,6 +262,8 @@ static void rda_uart_set_termios(struct uart_port *port, + fallthrough; + case CS7: + ctrl &= ~RDA_UART_DBITS_8; ++ termios->c_cflag &= ~CSIZE; ++ termios->c_cflag |= CS7; + break; + default: + ctrl |= RDA_UART_DBITS_8; +-- +2.35.1 + diff --git a/queue-5.15/serial-sh-sci-don-t-allow-cs5-6.patch b/queue-5.15/serial-sh-sci-don-t-allow-cs5-6.patch new file mode 100644 index 00000000000..f74e2952554 --- /dev/null +++ b/queue-5.15/serial-sh-sci-don-t-allow-cs5-6.patch @@ -0,0 +1,50 @@ +From 08b3e9394302d1c1f7f4976ce2cdea0d77a7b19f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:04 +0300 +Subject: serial: sh-sci: Don't allow CS5-6 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit 9b87162de8be26bf3156460b37deee6399fd0fcb ] + +Only CS7 and CS8 seem supported but CSIZE is not sanitized from +CS5 or CS6 to CS8. + +Set CSIZE correctly so that userspace knows the effective value. +Incorrect CSIZE also results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Fixes: 1da177e4c3f4 (Linux-2.6.12-rc2) +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-6-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/sh-sci.c | 6 +++++- + 1 file changed, 5 insertions(+), 1 deletion(-) + +diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c +index 89ee43061d3a..c5c0f39cb1c7 100644 +--- a/drivers/tty/serial/sh-sci.c ++++ b/drivers/tty/serial/sh-sci.c +@@ -2390,8 +2390,12 @@ static void sci_set_termios(struct uart_port *port, struct ktermios *termios, + int best_clk = -1; + unsigned long flags; + +- if ((termios->c_cflag & CSIZE) == CS7) ++ if ((termios->c_cflag & CSIZE) == CS7) { + smr_val |= SCSMR_CHR; ++ } else { ++ termios->c_cflag &= ~CSIZE; ++ termios->c_cflag |= CS8; ++ } + if (termios->c_cflag & PARENB) + smr_val |= SCSMR_PE; + if (termios->c_cflag & PARODD) +-- +2.35.1 + diff --git a/queue-5.15/serial-sifive-report-actual-baud-base-rather-than-fi.patch b/queue-5.15/serial-sifive-report-actual-baud-base-rather-than-fi.patch new file mode 100644 index 00000000000..9af648ef649 --- /dev/null +++ b/queue-5.15/serial-sifive-report-actual-baud-base-rather-than-fi.patch @@ -0,0 +1,66 @@ +From f22d0e6d13fbca4f082ea306a8cfa473cfa2b952 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 29 Apr 2022 21:40:18 +0100 +Subject: serial: sifive: Report actual baud base rather than fixed 115200 + +From: Maciej W. Rozycki + +[ Upstream commit 0a7ff843d507ce2cca2c3b7e169ee56e28133530 ] + +The base baud value reported is supposed to be the highest baud rate +that can be set for a serial port. The SiFive FU740-C000 SOC's on-chip +UART supports baud rates of up to 1/16 of the input clock rate, which is +the bus clock `tlclk'[1], often at 130MHz in the case of the HiFive +Unmatched board. + +However the sifive UART driver reports a fixed value of 115200 instead: + +10010000.serial: ttySIF0 at MMIO 0x10010000 (irq = 1, base_baud = 115200) is a SiFive UART v0 +10011000.serial: ttySIF1 at MMIO 0x10011000 (irq = 2, base_baud = 115200) is a SiFive UART v0 + +even though we already support setting higher baud rates, e.g.: + +$ tty +/dev/ttySIF1 +$ stty speed +230400 + +The baud base value is computed by the serial core by dividing the UART +clock recorded in `struct uart_port' by 16, which is also the minimum +value of the clock divider supported, so correct the baud base value +reported by setting the UART clock recorded to the input clock rate +rather than 115200: + +10010000.serial: ttySIF0 at MMIO 0x10010000 (irq = 1, base_baud = 8125000) is a SiFive UART v0 +10011000.serial: ttySIF1 at MMIO 0x10011000 (irq = 2, base_baud = 8125000) is a SiFive UART v0 + +References: + +[1] "SiFive FU740-C000 Manual", v1p3, SiFive, Inc., August 13, 2021, + Section 16.9 "Baud Rate Divisor Register (div)", pp.143-144 + +Signed-off-by: Maciej W. Rozycki +Fixes: 1f1496a923b6 ("riscv: Fix sifive serial driver") +Link: https://lore.kernel.org/r/alpine.DEB.2.21.2204291656280.9383@angie.orcam.me.uk +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/sifive.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/tty/serial/sifive.c b/drivers/tty/serial/sifive.c +index 0ac0371f943b..a579d46ed78c 100644 +--- a/drivers/tty/serial/sifive.c ++++ b/drivers/tty/serial/sifive.c +@@ -998,7 +998,7 @@ static int sifive_serial_probe(struct platform_device *pdev) + /* Set up clock divider */ + ssp->clkin_rate = clk_get_rate(ssp->clk); + ssp->baud_rate = SIFIVE_DEFAULT_BAUD_RATE; +- ssp->port.uartclk = ssp->baud_rate * 16; ++ ssp->port.uartclk = ssp->clkin_rate; + __ssp_update_div(ssp); + + platform_set_drvdata(pdev, ssp); +-- +2.35.1 + diff --git a/queue-5.15/serial-sifive-sanitize-csize-and-c_iflag.patch b/queue-5.15/serial-sifive-sanitize-csize-and-c_iflag.patch new file mode 100644 index 00000000000..951c7db7c80 --- /dev/null +++ b/queue-5.15/serial-sifive-sanitize-csize-and-c_iflag.patch @@ -0,0 +1,58 @@ +From 016e4aa6a4fea8e729f84e63994cb921c8062380 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:05 +0300 +Subject: serial: sifive: Sanitize CSIZE and c_iflag +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit c069d2756c01ed36121fae6a42c14fdf1325c71d ] + +Only CS8 is supported but CSIZE was not sanitized to CS8. + +Set CSIZE correctly so that userspace knows the effective value. +Incorrect CSIZE also results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Similarly, INPCK, PARMRK, and BRKINT are reported textually unsupported +but were not cleared in termios c_iflag which is the machine-readable +format. + +Fixes: 45c054d0815b (tty: serial: add driver for the SiFive UART) +Cc: Paul Walmsley +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-7-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/sifive.c | 6 +++++- + 1 file changed, 5 insertions(+), 1 deletion(-) + +diff --git a/drivers/tty/serial/sifive.c b/drivers/tty/serial/sifive.c +index a579d46ed78c..4b0fa91e9f9a 100644 +--- a/drivers/tty/serial/sifive.c ++++ b/drivers/tty/serial/sifive.c +@@ -666,12 +666,16 @@ static void sifive_serial_set_termios(struct uart_port *port, + int rate; + char nstop; + +- if ((termios->c_cflag & CSIZE) != CS8) ++ if ((termios->c_cflag & CSIZE) != CS8) { + dev_err_once(ssp->port.dev, "only 8-bit words supported\n"); ++ termios->c_cflag &= ~CSIZE; ++ termios->c_cflag |= CS8; ++ } + if (termios->c_iflag & (INPCK | PARMRK)) + dev_err_once(ssp->port.dev, "parity checking not supported\n"); + if (termios->c_iflag & BRKINT) + dev_err_once(ssp->port.dev, "BREAK detection not supported\n"); ++ termios->c_iflag &= ~(INPCK|PARMRK|BRKINT); + + /* Set number of stop bits */ + nstop = (termios->c_cflag & CSTOPB) ? 2 : 1; +-- +2.35.1 + diff --git a/queue-5.15/serial-st-asc-sanitize-csize-and-correct-parenb-for-.patch b/queue-5.15/serial-st-asc-sanitize-csize-and-correct-parenb-for-.patch new file mode 100644 index 00000000000..a9e862fb3e9 --- /dev/null +++ b/queue-5.15/serial-st-asc-sanitize-csize-and-correct-parenb-for-.patch @@ -0,0 +1,52 @@ +From 230d4fa447d98b55bfe128a0b039722a7d1c9dff Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:06 +0300 +Subject: serial: st-asc: Sanitize CSIZE and correct PARENB for CS7 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit 52bb1cb7118564166b04d52387bd8403632f5190 ] + +Only CS7 and CS8 seem supported but CSIZE is not sanitized from CS5 or +CS6 to CS8. In addition, ASC_CTL_MODE_7BIT_PAR suggests that CS7 has +to have parity, thus add PARENB. + +Incorrect CSIZE results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Fixes: c4b058560762 (serial:st-asc: Add ST ASC driver.) +Cc: Srinivas Kandagatla +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-8-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/st-asc.c | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/drivers/tty/serial/st-asc.c b/drivers/tty/serial/st-asc.c +index 87e480cc8206..5a45633aaea8 100644 +--- a/drivers/tty/serial/st-asc.c ++++ b/drivers/tty/serial/st-asc.c +@@ -535,10 +535,14 @@ static void asc_set_termios(struct uart_port *port, struct ktermios *termios, + /* set character length */ + if ((cflag & CSIZE) == CS7) { + ctrl_val |= ASC_CTL_MODE_7BIT_PAR; ++ cflag |= PARENB; + } else { + ctrl_val |= (cflag & PARENB) ? ASC_CTL_MODE_8BIT_PAR : + ASC_CTL_MODE_8BIT; ++ cflag &= ~CSIZE; ++ cflag |= CS8; + } ++ termios->c_cflag = cflag; + + /* set stop bit */ + ctrl_val |= (cflag & CSTOPB) ? ASC_CTL_STOP_2BIT : ASC_CTL_STOP_1BIT; +-- +2.35.1 + diff --git a/queue-5.15/serial-stm32-usart-correct-csize-bits-and-parity.patch b/queue-5.15/serial-stm32-usart-correct-csize-bits-and-parity.patch new file mode 100644 index 00000000000..a04831a6c14 --- /dev/null +++ b/queue-5.15/serial-stm32-usart-correct-csize-bits-and-parity.patch @@ -0,0 +1,64 @@ +From b7751ad2c0185fa0c6de643582f233f6d46e35b0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:07 +0300 +Subject: serial: stm32-usart: Correct CSIZE, bits, and parity +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit 1deeda8d2877c18bc2b9eeee10dd6d2628852848 ] + +Add CSIZE sanitization for unsupported CSIZE configurations. In +addition, if parity is asked for but CSx was unsupported, the sensible +result is CS8+parity which requires setting USART_CR1_M0 like with 9 +bits. + +Incorrect CSIZE results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Fixes: c8a9d043947b (serial: stm32: fix word length configuration) +Cc: Erwan Le Ray +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-9-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/stm32-usart.c | 15 ++++++++++++--- + 1 file changed, 12 insertions(+), 3 deletions(-) + +diff --git a/drivers/tty/serial/stm32-usart.c b/drivers/tty/serial/stm32-usart.c +index 810a1b0b6520..10e9f983de62 100644 +--- a/drivers/tty/serial/stm32-usart.c ++++ b/drivers/tty/serial/stm32-usart.c +@@ -807,13 +807,22 @@ static void stm32_usart_set_termios(struct uart_port *port, + * CS8 or (CS7 + parity), 8 bits word aka [M1:M0] = 0b00 + * M0 and M1 already cleared by cr1 initialization. + */ +- if (bits == 9) ++ if (bits == 9) { + cr1 |= USART_CR1_M0; +- else if ((bits == 7) && cfg->has_7bits_data) ++ } else if ((bits == 7) && cfg->has_7bits_data) { + cr1 |= USART_CR1_M1; +- else if (bits != 8) ++ } else if (bits != 8) { + dev_dbg(port->dev, "Unsupported data bits config: %u bits\n" + , bits); ++ cflag &= ~CSIZE; ++ cflag |= CS8; ++ termios->c_cflag = cflag; ++ bits = 8; ++ if (cflag & PARENB) { ++ bits++; ++ cr1 |= USART_CR1_M0; ++ } ++ } + + if (ofs->rtor != UNDEF_REG && (stm32_port->rx_ch || + (stm32_port->fifoen && +-- +2.35.1 + diff --git a/queue-5.15/serial-txx9-don-t-allow-cs5-6.patch b/queue-5.15/serial-txx9-don-t-allow-cs5-6.patch new file mode 100644 index 00000000000..5f0994bb708 --- /dev/null +++ b/queue-5.15/serial-txx9-don-t-allow-cs5-6.patch @@ -0,0 +1,45 @@ +From 16616b76aa6c1f6a51160b1c1aaeaacdd9f3afda Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 19 May 2022 11:18:03 +0300 +Subject: serial: txx9: Don't allow CS5-6 +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Ilpo Järvinen + +[ Upstream commit 79ac88655dc0551e3571ad16bdabdbe65d61553e ] + +Only CS7 and CS8 are supported but CSIZE is not sanitized with +CS5 or CS6 to CS8. + +Set CSIZE correctly so that userspace knows the effective value. +Incorrect CSIZE also results in miscalculation of the frame bits in +tty_get_char_size() or in its predecessor where the roughly the same +code is directly within uart_update_timeout(). + +Fixes: 1da177e4c3f4 (Linux-2.6.12-rc2) +Signed-off-by: Ilpo Järvinen +Link: https://lore.kernel.org/r/20220519081808.3776-5-ilpo.jarvinen@linux.intel.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/serial_txx9.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/tty/serial/serial_txx9.c b/drivers/tty/serial/serial_txx9.c +index aaca4fe38486..1f8362d5e3b9 100644 +--- a/drivers/tty/serial/serial_txx9.c ++++ b/drivers/tty/serial/serial_txx9.c +@@ -644,6 +644,8 @@ serial_txx9_set_termios(struct uart_port *port, struct ktermios *termios, + case CS6: /* not supported */ + case CS8: + cval |= TXX9_SILCR_UMODE_8BIT; ++ termios->c_cflag &= ~CSIZE; ++ termios->c_cflag |= CS8; + break; + } + +-- +2.35.1 + diff --git a/queue-5.15/series b/queue-5.15/series new file mode 100644 index 00000000000..3b3bd601eb4 --- /dev/null +++ b/queue-5.15/series @@ -0,0 +1,112 @@ +fs-ntfs3-restore-ntfs_xattr_get_acl-and-ntfs_xattr_s.patch +pcmcia-db1xxx_ss-restrict-to-mips_db1xxx-boards.patch +staging-greybus-codecs-fix-type-confusion-of-list-it.patch +iio-adc-ad7124-remove-shift-from-scan_type.patch +lkdtm-bugs-check-for-the-null-pointer-after-calling-.patch +lkdtm-bugs-don-t-expect-thread-termination-without-c.patch +tty-goldfish-use-tty_port_destroy-to-destroy-port.patch +tty-serial-owl-fix-missing-clk_disable_unprepare-in-.patch +tty-n_tty-restore-eof-push-handling-behavior.patch +serial-8250_aspeed_vuart-fix-potential-null-derefere.patch +tty-serial-fsl_lpuart-fix-potential-bug-when-using-b.patch +remoteproc-imx_rproc-ignore-create-mem-entry-for-res.patch +usb-usbip-fix-a-refcount-leak-in-stub_probe.patch +usb-usbip-add-missing-device-lock-on-tweak-configura.patch +usb-storage-karma-fix-rio_karma_init-return.patch +usb-musb-fix-missing-of_node_put-in-omap2430_probe.patch +staging-fieldbus-fix-the-error-handling-path-in-anyb.patch +pwm-lp3943-fix-duty-calculation-in-case-period-was-c.patch +pwm-raspberrypi-poe-fix-endianness-in-firmware-struc.patch +rpmsg-qcom_smd-fix-irq_of_parse_and_map-return-value.patch +usb-dwc3-gadget-replace-list_for_each_entry_safe-if-.patch +usb-dwc3-pci-fix-pm_runtime_get_sync-error-checking.patch +misc-fastrpc-fix-an-incorrect-null-check-on-list-ite.patch +firmware-stratix10-svc-fix-a-missing-check-on-list-i.patch +usb-typec-mux-check-dev_set_name-return-value.patch +rpmsg-virtio-fix-possible-double-free-in-rpmsg_probe.patch +rpmsg-virtio-fix-possible-double-free-in-rpmsg_virti.patch +rpmsg-virtio-fix-the-unregistration-of-the-device-rp.patch +platform-finally-disallow-irq0-in-platform_get_irq-a.patch +iio-adc-stmpe-adc-fix-wait_for_completion_timeout-re.patch +iio-proximity-vl53l0x-fix-return-value-check-of-wait.patch +iio-adc-sc27xx-fix-read-big-scale-voltage-not-right.patch +iio-adc-sc27xx-fine-tune-the-scale-calibration-value.patch +rpmsg-qcom_smd-fix-returning-0-if-irq_of_parse_and_m.patch +pvpanic-fix-typos-in-the-comments.patch +misc-pvpanic-convert-regular-spinlock-into-trylock-o.patch +phy-qcom-qmp-fix-pipe-clock-imbalance-on-power-on-fa.patch +power-supply-axp288_fuel_gauge-drop-bios-version-che.patch +serial-sifive-report-actual-baud-base-rather-than-fi.patch +export-fix-string-handling-of-namespace-in-export_sy.patch +soundwire-intel-prevent-pm_runtime-resume-prior-to-s.patch +coresight-cpu-debug-replace-mutex-with-mutex_trylock.patch +ksmbd-fix-reference-count-leak-in-smb_check_perm_dac.patch +extcon-ptn5150-add-queue-work-sync-before-driver-rel.patch +soc-rockchip-fix-refcount-leak-in-rockchip_grf_init.patch +clocksource-drivers-riscv-events-are-stopped-during-.patch +arm-dts-aspeed-ast2600-evb-enable-rx-delay-for-mac0-.patch +rtc-mt6397-check-return-value-after-calling-platform.patch +rtc-ftrtc010-use-platform_get_irq-to-get-the-interru.patch +rtc-ftrtc010-fix-error-handling-in-ftrtc010_rtc_prob.patch +staging-r8188eu-add-check-for-kzalloc.patch +tty-n_gsm-don-t-ignore-write-return-value-in-gsmld_o.patch +tty-n_gsm-fix-packet-data-hex-dump-output.patch +serial-meson-acquire-port-lock-in-startup.patch +serial-8250_fintek-check-ser_rs485_rts_-only-with-rs.patch +serial-cpm_uart-fix-build-error-without-config_seria.patch +serial-digicolor-usart-don-t-allow-cs5-6.patch +serial-rda-uart-don-t-allow-cs5-6.patch +serial-txx9-don-t-allow-cs5-6.patch +serial-sh-sci-don-t-allow-cs5-6.patch +serial-sifive-sanitize-csize-and-c_iflag.patch +serial-st-asc-sanitize-csize-and-correct-parenb-for-.patch +serial-stm32-usart-correct-csize-bits-and-parity.patch +firmware-dmi-sysfs-fix-memory-leak-in-dmi_sysfs_regi.patch +bus-ti-sysc-fix-warnings-for-unbind-for-serial.patch +driver-base-fix-uaf-when-driver_attach-failed.patch +driver-core-fix-deadlock-in-__device_attach.patch +watchdog-rti-wdt-fix-pm_runtime_get_sync-error-check.patch +watchdog-ts4800_wdt-fix-refcount-leak-in-ts4800_wdt_.patch +blk-mq-don-t-touch-tagset-in-blk_mq_get_sq_hctx.patch +asoc-fsl_sai-fix-fsl_sai_xdr-xfr-definition.patch +clocksource-drivers-oxnas-rps-fix-irq_of_parse_and_m.patch +s390-crypto-fix-scatterwalk_unmap-callers-in-aes-gcm.patch +net-sched-fixed-barrier-to-prevent-skbuff-sticking-i.patch +net-ethernet-mtk_eth_soc-out-of-bounds-read-in-mtk_h.patch +net-ethernet-ti-am65-cpsw-nuss-fix-some-refcount-lea.patch +net-dsa-mv88e6xxx-fix-refcount-leak-in-mv88e6xxx_mdi.patch +modpost-fix-removing-numeric-suffixes.patch +jffs2-fix-memory-leak-in-jffs2_do_fill_super.patch +ubi-fastmap-fix-high-cpu-usage-of-ubi_bgt-by-making-.patch +ubi-ubi_create_volume-fix-use-after-free-when-volume.patch +selftests-bpf-fix-selftest-after-random-urandom_read.patch +selftests-bpf-fix-stacktrace_build_id-with-missing-k.patch +bpf-fix-probe-read-error-in-___bpf_prog_run.patch +block-take-destination-bvec-offsets-into-account-in-.patch +riscv-read-only-pages-should-not-be-writable.patch +net-smc-fixes-for-converting-from-struct-smc_cdc_tx_.patch +tcp-add-accessors-to-read-set-tp-snd_cwnd.patch +nfp-only-report-pause-frame-configuration-for-physic.patch +sfc-fix-considering-that-all-channels-have-tx-queues.patch +sfc-fix-wrong-tx-channel-offset-with-efx_separate_tx.patch +block-make-bioset_exit-fully-resilient-against-being.patch +vdpa-fix-error-logic-in-vdpa_nl_cmd_dev_get_doit.patch +virtio-pci-fix-an-error-handling-path-in-vp_modern_p.patch +net-mlx5-don-t-use-already-freed-action-pointer.patch +net-mlx5e-tc-nic-mode-fix-tc-chains-miss-table.patch +net-mlx5-ct-fix-header-rewrite-re-use-for-tupels.patch +net-mlx5-correct-ece-offset-in-query-qp-output.patch +net-mlx5e-update-netdev-features-after-changing-xdp-.patch +net-sched-add-barrier-to-fix-packet-stuck-problem-fo.patch +tcp-tcp_rtx_synack-can-be-called-from-process-contex.patch +vdpa-ifcvf-set-pci-driver-data-in-probe.patch +octeontx2-af-fix-error-code-in-is_valid_offset.patch +s390-mcck-isolate-sie-instruction-when-setting-cif_m.patch +regulator-mt6315-regulator-fix-invalid-allowed-mode.patch +gpio-pca953x-use-the-correct-register-address-to-do-.patch +afs-fix-infinite-loop-found-by-xfstest-generic-676.patch +scsi-sd-fix-potential-null-pointer-dereference.patch +tipc-check-attribute-length-for-bearer-name.patch +arm64-initialize-jump-labels-before-setup_machine_fd.patch +driver-core-fix-wait_for_device_probe-deferred_probe.patch +perf-c2c-fix-sorting-in-percent_rmt_hitm_cmp.patch diff --git a/queue-5.15/sfc-fix-considering-that-all-channels-have-tx-queues.patch b/queue-5.15/sfc-fix-considering-that-all-channels-have-tx-queues.patch new file mode 100644 index 00000000000..6aa165f6740 --- /dev/null +++ b/queue-5.15/sfc-fix-considering-that-all-channels-have-tx-queues.patch @@ -0,0 +1,68 @@ +From 5237fe111b5f5c055f315b01869fc1b6a5767bc4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 27 May 2022 10:05:28 +0200 +Subject: sfc: fix considering that all channels have TX queues +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Martin Habets + +[ Upstream commit 2e102b53f8a778f872dc137f4c7ac548705817aa ] + +Normally, all channels have RX and TX queues, but this is not true if +modparam efx_separate_tx_channels=1 is used. In that cases, some +channels only have RX queues and others only TX queues (or more +preciselly, they have them allocated, but not initialized). + +Fix efx_channel_has_tx_queues to return the correct value for this case +too. + +Messages shown at probe time before the fix: + sfc 0000:03:00.0 ens6f0np0: MC command 0x82 inlen 544 failed rc=-22 (raw=0) arg=0 + ------------[ cut here ]------------ + netdevice: ens6f0np0: failed to initialise TXQ -1 + WARNING: CPU: 1 PID: 626 at drivers/net/ethernet/sfc/ef10.c:2393 efx_ef10_tx_init+0x201/0x300 [sfc] + [...] stripped + RIP: 0010:efx_ef10_tx_init+0x201/0x300 [sfc] + [...] stripped + Call Trace: + efx_init_tx_queue+0xaa/0xf0 [sfc] + efx_start_channels+0x49/0x120 [sfc] + efx_start_all+0x1f8/0x430 [sfc] + efx_net_open+0x5a/0xe0 [sfc] + __dev_open+0xd0/0x190 + __dev_change_flags+0x1b3/0x220 + dev_change_flags+0x21/0x60 + [...] stripped + +Messages shown at remove time before the fix: + sfc 0000:03:00.0 ens6f0np0: failed to flush 10 queues + sfc 0000:03:00.0 ens6f0np0: failed to flush queues + +Fixes: 8700aff08984 ("sfc: fix channel allocation with brute force") +Reported-by: Tianhao Zhao +Signed-off-by: Martin Habets +Tested-by: Íñigo Huguet +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/sfc/net_driver.h | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/ethernet/sfc/net_driver.h b/drivers/net/ethernet/sfc/net_driver.h +index f6981810039d..bf097264d8fb 100644 +--- a/drivers/net/ethernet/sfc/net_driver.h ++++ b/drivers/net/ethernet/sfc/net_driver.h +@@ -1533,7 +1533,7 @@ static inline bool efx_channel_is_xdp_tx(struct efx_channel *channel) + + static inline bool efx_channel_has_tx_queues(struct efx_channel *channel) + { +- return true; ++ return channel && channel->channel >= channel->efx->tx_channel_offset; + } + + static inline unsigned int efx_channel_num_tx_queues(struct efx_channel *channel) +-- +2.35.1 + diff --git a/queue-5.15/sfc-fix-wrong-tx-channel-offset-with-efx_separate_tx.patch b/queue-5.15/sfc-fix-wrong-tx-channel-offset-with-efx_separate_tx.patch new file mode 100644 index 00000000000..edcb52a0bbb --- /dev/null +++ b/queue-5.15/sfc-fix-wrong-tx-channel-offset-with-efx_separate_tx.patch @@ -0,0 +1,70 @@ +From d25c9cff707b5f7f62356c5ed67dc5dc3f602401 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 27 May 2022 10:05:29 +0200 +Subject: sfc: fix wrong tx channel offset with efx_separate_tx_channels +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Íñigo Huguet + +[ Upstream commit c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 ] + +tx_channel_offset is calculated in efx_allocate_msix_channels, but it is +also calculated again in efx_set_channels because it was originally done +there, and when efx_allocate_msix_channels was introduced it was +forgotten to be removed from efx_set_channels. + +Moreover, the old calculation is wrong when using +efx_separate_tx_channels because now we can have XDP channels after the +TX channels, so n_channels - n_tx_channels doesn't point to the first TX +channel. + +Remove the old calculation from efx_set_channels, and add the +initialization of this variable if MSI or legacy interrupts are used, +next to the initialization of the rest of the related variables, where +it was missing. + +Fixes: 3990a8fffbda ("sfc: allocate channels for XDP tx queues") +Reported-by: Tianhao Zhao +Signed-off-by: Íñigo Huguet +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/sfc/efx_channels.c | 6 ++---- + 1 file changed, 2 insertions(+), 4 deletions(-) + +diff --git a/drivers/net/ethernet/sfc/efx_channels.c b/drivers/net/ethernet/sfc/efx_channels.c +index d5f2ccd3bca4..b1657e03a74f 100644 +--- a/drivers/net/ethernet/sfc/efx_channels.c ++++ b/drivers/net/ethernet/sfc/efx_channels.c +@@ -308,6 +308,7 @@ int efx_probe_interrupts(struct efx_nic *efx) + efx->n_channels = 1; + efx->n_rx_channels = 1; + efx->n_tx_channels = 1; ++ efx->tx_channel_offset = 0; + efx->n_xdp_channels = 0; + efx->xdp_channel_offset = efx->n_channels; + rc = pci_enable_msi(efx->pci_dev); +@@ -328,6 +329,7 @@ int efx_probe_interrupts(struct efx_nic *efx) + efx->n_channels = 1 + (efx_separate_tx_channels ? 1 : 0); + efx->n_rx_channels = 1; + efx->n_tx_channels = 1; ++ efx->tx_channel_offset = 1; + efx->n_xdp_channels = 0; + efx->xdp_channel_offset = efx->n_channels; + efx->legacy_irq = efx->pci_dev->irq; +@@ -956,10 +958,6 @@ int efx_set_channels(struct efx_nic *efx) + struct efx_channel *channel; + int rc; + +- efx->tx_channel_offset = +- efx_separate_tx_channels ? +- efx->n_channels - efx->n_tx_channels : 0; +- + if (efx->xdp_tx_queue_count) { + EFX_WARN_ON_PARANOID(efx->xdp_tx_queues); + +-- +2.35.1 + diff --git a/queue-5.15/soc-rockchip-fix-refcount-leak-in-rockchip_grf_init.patch b/queue-5.15/soc-rockchip-fix-refcount-leak-in-rockchip_grf_init.patch new file mode 100644 index 00000000000..6a00be60916 --- /dev/null +++ b/queue-5.15/soc-rockchip-fix-refcount-leak-in-rockchip_grf_init.patch @@ -0,0 +1,44 @@ +From b57e15ea35380f10bac9feccff84c73038cbc30e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 16 May 2022 11:20:10 +0400 +Subject: soc: rockchip: Fix refcount leak in rockchip_grf_init + +From: Miaoqian Lin + +[ Upstream commit 9b59588d8be91c96bfb0371e912ceb4f16315dbf ] + +of_find_matching_node_and_match returns a node pointer with refcount +incremented, we should use of_node_put() on it when done. +Add missing of_node_put() to avoid refcount leak. + +Fixes: 4c58063d4258 ("soc: rockchip: add driver handling grf setup") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220516072013.19731-1-linmq006@gmail.com +Signed-off-by: Heiko Stuebner +Signed-off-by: Sasha Levin +--- + drivers/soc/rockchip/grf.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/soc/rockchip/grf.c b/drivers/soc/rockchip/grf.c +index 494cf2b5bf7b..343ff61ccccb 100644 +--- a/drivers/soc/rockchip/grf.c ++++ b/drivers/soc/rockchip/grf.c +@@ -148,12 +148,14 @@ static int __init rockchip_grf_init(void) + return -ENODEV; + if (!match || !match->data) { + pr_err("%s: missing grf data\n", __func__); ++ of_node_put(np); + return -EINVAL; + } + + grf_info = match->data; + + grf = syscon_node_to_regmap(np); ++ of_node_put(np); + if (IS_ERR(grf)) { + pr_err("%s: could not get grf syscon\n", __func__); + return PTR_ERR(grf); +-- +2.35.1 + diff --git a/queue-5.15/soundwire-intel-prevent-pm_runtime-resume-prior-to-s.patch b/queue-5.15/soundwire-intel-prevent-pm_runtime-resume-prior-to-s.patch new file mode 100644 index 00000000000..124e07d350a --- /dev/null +++ b/queue-5.15/soundwire-intel-prevent-pm_runtime-resume-prior-to-s.patch @@ -0,0 +1,58 @@ +From d5ba7bd51ca01b6c17420121b52671f21d236789 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 20 Apr 2022 10:32:39 +0800 +Subject: soundwire: intel: prevent pm_runtime resume prior to system suspend + +From: Pierre-Louis Bossart + +[ Upstream commit 6d9f2dadba698114fed97b224578c5338a36b0d9 ] + +commit e38f9ff63e6d ("ACPI: scan: Do not add device IDs from _CID if _HID is not valid") +exposes a race condition on a TGL RVP device leading to a timeout. + +The detailed analysis shows the RT711 codec driver scheduling a jack +detection workqueue while attaching during a spurious pm_runtime +resume, and the work function happens to be scheduled after the +manager device is suspended. + +The direct link between this ACPI patch and a spurious pm_runtime +resume is not obvious; the most likely explanation is that a change in +the ACPI device linked list management modifies the order in which the +pm_runtime device status is checked and exposes a race condition that +was probably present for a very long time, but was not identified. + +We already have a check in the .prepare stage, where we will resume to +full power from specific clock-stop modes. In all other cases, we +don't need to resume to full power by default. Adding the +SMART_SUSPEND flag prevents the spurious resume from happening. + +BugLink: https://github.com/thesofproject/linux/issues/3459 +Fixes: 029bfd1cd53cd ("soundwire: intel: conditionally exit clock stop mode on system suspend") +Signed-off-by: Pierre-Louis Bossart +Reviewed-by: Ranjani Sridharan +Reviewed-by: Rander Wang +Signed-off-by: Bard Liao +Link: https://lore.kernel.org/r/20220420023241.14335-2-yung-chuan.liao@linux.intel.com +Signed-off-by: Vinod Koul +Signed-off-by: Sasha Levin +--- + drivers/soundwire/intel.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c +index f72d36654ac2..38e7f1a2bb97 100644 +--- a/drivers/soundwire/intel.c ++++ b/drivers/soundwire/intel.c +@@ -1298,6 +1298,9 @@ static int intel_link_probe(struct auxiliary_device *auxdev, + /* use generic bandwidth allocation algorithm */ + sdw->cdns.bus.compute_params = sdw_compute_params; + ++ /* avoid resuming from pm_runtime suspend if it's not required */ ++ dev_pm_set_driver_flags(dev, DPM_FLAG_SMART_SUSPEND); ++ + ret = sdw_bus_master_add(bus, dev, dev->fwnode); + if (ret) { + dev_err(dev, "sdw_bus_master_add fail: %d\n", ret); +-- +2.35.1 + diff --git a/queue-5.15/staging-fieldbus-fix-the-error-handling-path-in-anyb.patch b/queue-5.15/staging-fieldbus-fix-the-error-handling-path-in-anyb.patch new file mode 100644 index 00000000000..026a6274ff3 --- /dev/null +++ b/queue-5.15/staging-fieldbus-fix-the-error-handling-path-in-anyb.patch @@ -0,0 +1,39 @@ +From 1ecd8a51620ac8cda65bab25c141657560eb9f73 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 08:48:18 +0200 +Subject: staging: fieldbus: Fix the error handling path in + anybuss_host_common_probe() + +From: Christophe JAILLET + +[ Upstream commit 7079b3483a17be2cfba64cbd4feb1b7ae07f1ea7 ] + +If device_register() fails, device_unregister() should not be called +because it will free some resources that are not allocated. +put_device() should be used instead. + +Fixes: 308ee87a2f1e ("staging: fieldbus: anybus-s: support HMS Anybus-S bus") +Signed-off-by: Christophe JAILLET +Link: https://lore.kernel.org/r/5401a519608d6e1a4e7435c20f4f20b0c5c36c23.1650610082.git.christophe.jaillet@wanadoo.fr +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/staging/fieldbus/anybuss/host.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/staging/fieldbus/anybuss/host.c b/drivers/staging/fieldbus/anybuss/host.c +index 8a75f6642c78..0c41d1e0204f 100644 +--- a/drivers/staging/fieldbus/anybuss/host.c ++++ b/drivers/staging/fieldbus/anybuss/host.c +@@ -1384,7 +1384,7 @@ anybuss_host_common_probe(struct device *dev, + goto err_device; + return cd; + err_device: +- device_unregister(&cd->client->dev); ++ put_device(&cd->client->dev); + err_kthread: + kthread_stop(cd->qthread); + err_reset: +-- +2.35.1 + diff --git a/queue-5.15/staging-greybus-codecs-fix-type-confusion-of-list-it.patch b/queue-5.15/staging-greybus-codecs-fix-type-confusion-of-list-it.patch new file mode 100644 index 00000000000..394b93d4ecc --- /dev/null +++ b/queue-5.15/staging-greybus-codecs-fix-type-confusion-of-list-it.patch @@ -0,0 +1,44 @@ +From 0c223b9c7a4c9d60cfaa2673abcaa70efd57a78a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 21 Mar 2022 13:36:26 +0100 +Subject: staging: greybus: codecs: fix type confusion of list iterator + variable + +From: Jakob Koschel + +[ Upstream commit 84ef256550196bc06e6849a34224c998b45bd557 ] + +If the list does not exit early then data == NULL and 'module' does not +point to a valid list element. +Using 'module' in such a case is not valid and was therefore removed. + +Fixes: 6dd67645f22c ("greybus: audio: Use single codec driver registration") +Reviewed-by: Dan Carpenter +Reviewed-by: Vaibhav Agarwal +Reviewed-by: Mark Greer +Signed-off-by: Jakob Koschel +Link: https://lore.kernel.org/r/20220321123626.3068639-1-jakobkoschel@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/staging/greybus/audio_codec.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/drivers/staging/greybus/audio_codec.c b/drivers/staging/greybus/audio_codec.c +index b589cf6b1d03..e19b91e7a72e 100644 +--- a/drivers/staging/greybus/audio_codec.c ++++ b/drivers/staging/greybus/audio_codec.c +@@ -599,8 +599,8 @@ static int gbcodec_mute_stream(struct snd_soc_dai *dai, int mute, int stream) + break; + } + if (!data) { +- dev_err(dai->dev, "%s:%s DATA connection missing\n", +- dai->name, module->name); ++ dev_err(dai->dev, "%s DATA connection missing\n", ++ dai->name); + mutex_unlock(&codec->lock); + return -ENODEV; + } +-- +2.35.1 + diff --git a/queue-5.15/staging-r8188eu-add-check-for-kzalloc.patch b/queue-5.15/staging-r8188eu-add-check-for-kzalloc.patch new file mode 100644 index 00000000000..e635a48fa62 --- /dev/null +++ b/queue-5.15/staging-r8188eu-add-check-for-kzalloc.patch @@ -0,0 +1,87 @@ +From 6093b220651703a9a8373dc7eebf2a1c040532cc Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 18 May 2022 15:59:57 +0800 +Subject: staging: r8188eu: add check for kzalloc + +From: Jiasheng Jiang + +[ Upstream commit f94b47c6bde624d6c07f43054087607c52054a95 ] + +As kzalloc() may return null pointer, it should be better to +check the return value and return error if fails in order +to avoid dereference of null pointer. +Moreover, the return value of rtw_alloc_hwxmits() should also +be dealt with. + +Fixes: 15865124feed ("staging: r8188eu: introduce new core dir for RTL8188eu driver") +Reviewed-by: Dan Carpenter +Signed-off-by: Jiasheng Jiang +Link: https://lore.kernel.org/r/20220518075957.514603-1-jiasheng@iscas.ac.cn +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/staging/r8188eu/core/rtw_xmit.c | 13 +++++++++++-- + drivers/staging/r8188eu/include/rtw_xmit.h | 2 +- + 2 files changed, 12 insertions(+), 3 deletions(-) + +diff --git a/drivers/staging/r8188eu/core/rtw_xmit.c b/drivers/staging/r8188eu/core/rtw_xmit.c +index 46fe62c7c32c..0ee4f88a60d4 100644 +--- a/drivers/staging/r8188eu/core/rtw_xmit.c ++++ b/drivers/staging/r8188eu/core/rtw_xmit.c +@@ -179,7 +179,12 @@ s32 _rtw_init_xmit_priv(struct xmit_priv *pxmitpriv, struct adapter *padapter) + + pxmitpriv->free_xmit_extbuf_cnt = num_xmit_extbuf; + +- rtw_alloc_hwxmits(padapter); ++ res = rtw_alloc_hwxmits(padapter); ++ if (res) { ++ res = _FAIL; ++ goto exit; ++ } ++ + rtw_init_hwxmits(pxmitpriv->hwxmits, pxmitpriv->hwxmit_entry); + + for (i = 0; i < 4; i++) +@@ -1516,7 +1521,7 @@ s32 rtw_xmit_classifier(struct adapter *padapter, struct xmit_frame *pxmitframe) + return res; + } + +-void rtw_alloc_hwxmits(struct adapter *padapter) ++int rtw_alloc_hwxmits(struct adapter *padapter) + { + struct hw_xmit *hwxmits; + struct xmit_priv *pxmitpriv = &padapter->xmitpriv; +@@ -1524,6 +1529,8 @@ void rtw_alloc_hwxmits(struct adapter *padapter) + pxmitpriv->hwxmit_entry = HWXMIT_ENTRY; + + pxmitpriv->hwxmits = kzalloc(sizeof(struct hw_xmit) * pxmitpriv->hwxmit_entry, GFP_KERNEL); ++ if (!pxmitpriv->hwxmits) ++ return -ENOMEM; + + hwxmits = pxmitpriv->hwxmits; + +@@ -1540,6 +1547,8 @@ void rtw_alloc_hwxmits(struct adapter *padapter) + hwxmits[3] .sta_queue = &pxmitpriv->bk_pending; + } else { + } ++ ++ return 0; + } + + void rtw_free_hwxmits(struct adapter *padapter) +diff --git a/drivers/staging/r8188eu/include/rtw_xmit.h b/drivers/staging/r8188eu/include/rtw_xmit.h +index 5f6e2402e5c4..762a2fa3bd17 100644 +--- a/drivers/staging/r8188eu/include/rtw_xmit.h ++++ b/drivers/staging/r8188eu/include/rtw_xmit.h +@@ -345,7 +345,7 @@ s32 rtw_txframes_sta_ac_pending(struct adapter *padapter, + void rtw_init_hwxmits(struct hw_xmit *phwxmit, int entry); + s32 _rtw_init_xmit_priv(struct xmit_priv *pxmitpriv, struct adapter *padapter); + void _rtw_free_xmit_priv(struct xmit_priv *pxmitpriv); +-void rtw_alloc_hwxmits(struct adapter *padapter); ++int rtw_alloc_hwxmits(struct adapter *padapter); + void rtw_free_hwxmits(struct adapter *padapter); + s32 rtw_xmit(struct adapter *padapter, struct sk_buff **pkt); + +-- +2.35.1 + diff --git a/queue-5.15/tcp-add-accessors-to-read-set-tp-snd_cwnd.patch b/queue-5.15/tcp-add-accessors-to-read-set-tp-snd_cwnd.patch new file mode 100644 index 00000000000..70336a647c0 --- /dev/null +++ b/queue-5.15/tcp-add-accessors-to-read-set-tp-snd_cwnd.patch @@ -0,0 +1,1447 @@ +From d3c67b41ff9f45ca652fde3bdfd05be1b2af3dcd Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 5 Apr 2022 16:35:38 -0700 +Subject: tcp: add accessors to read/set tp->snd_cwnd + +From: Eric Dumazet + +[ Upstream commit 40570375356c874b1578e05c1dcc3ff7c1322dbe ] + +We had various bugs over the years with code +breaking the assumption that tp->snd_cwnd is greater +than zero. + +Lately, syzbot reported the WARN_ON_ONCE(!tp->prior_cwnd) added +in commit 8b8a321ff72c ("tcp: fix zero cwnd in tcp_cwnd_reduction") +can trigger, and without a repro we would have to spend +considerable time finding the bug. + +Instead of complaining too late, we want to catch where +and when tp->snd_cwnd is set to an illegal value. + +Signed-off-by: Eric Dumazet +Suggested-by: Yuchung Cheng +Cc: Neal Cardwell +Acked-by: Yuchung Cheng +Link: https://lore.kernel.org/r/20220405233538.947344-1-eric.dumazet@gmail.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Sasha Levin +--- + include/net/tcp.h | 19 +++++++++++++++---- + include/trace/events/tcp.h | 2 +- + net/core/filter.c | 2 +- + net/ipv4/tcp.c | 8 ++++---- + net/ipv4/tcp_bbr.c | 20 ++++++++++---------- + net/ipv4/tcp_bic.c | 14 +++++++------- + net/ipv4/tcp_cdg.c | 30 +++++++++++++++--------------- + net/ipv4/tcp_cong.c | 18 +++++++++--------- + net/ipv4/tcp_cubic.c | 22 +++++++++++----------- + net/ipv4/tcp_dctcp.c | 11 ++++++----- + net/ipv4/tcp_highspeed.c | 18 +++++++++--------- + net/ipv4/tcp_htcp.c | 10 +++++----- + net/ipv4/tcp_hybla.c | 18 +++++++++--------- + net/ipv4/tcp_illinois.c | 12 +++++++----- + net/ipv4/tcp_input.c | 36 ++++++++++++++++++------------------ + net/ipv4/tcp_ipv4.c | 2 +- + net/ipv4/tcp_lp.c | 6 +++--- + net/ipv4/tcp_metrics.c | 12 ++++++------ + net/ipv4/tcp_nv.c | 24 ++++++++++++------------ + net/ipv4/tcp_output.c | 30 +++++++++++++++--------------- + net/ipv4/tcp_rate.c | 2 +- + net/ipv4/tcp_scalable.c | 4 ++-- + net/ipv4/tcp_vegas.c | 21 +++++++++++---------- + net/ipv4/tcp_veno.c | 24 ++++++++++++------------ + net/ipv4/tcp_westwood.c | 3 ++- + net/ipv4/tcp_yeah.c | 30 +++++++++++++++--------------- + net/ipv6/tcp_ipv6.c | 2 +- + 27 files changed, 208 insertions(+), 192 deletions(-) + +diff --git a/include/net/tcp.h b/include/net/tcp.h +index 91ac329ca578..3b97db2d438f 100644 +--- a/include/net/tcp.h ++++ b/include/net/tcp.h +@@ -1199,9 +1199,20 @@ static inline unsigned int tcp_packets_in_flight(const struct tcp_sock *tp) + + #define TCP_INFINITE_SSTHRESH 0x7fffffff + ++static inline u32 tcp_snd_cwnd(const struct tcp_sock *tp) ++{ ++ return tp->snd_cwnd; ++} ++ ++static inline void tcp_snd_cwnd_set(struct tcp_sock *tp, u32 val) ++{ ++ WARN_ON_ONCE((int)val <= 0); ++ tp->snd_cwnd = val; ++} ++ + static inline bool tcp_in_slow_start(const struct tcp_sock *tp) + { +- return tp->snd_cwnd < tp->snd_ssthresh; ++ return tcp_snd_cwnd(tp) < tp->snd_ssthresh; + } + + static inline bool tcp_in_initial_slowstart(const struct tcp_sock *tp) +@@ -1227,8 +1238,8 @@ static inline __u32 tcp_current_ssthresh(const struct sock *sk) + return tp->snd_ssthresh; + else + return max(tp->snd_ssthresh, +- ((tp->snd_cwnd >> 1) + +- (tp->snd_cwnd >> 2))); ++ ((tcp_snd_cwnd(tp) >> 1) + ++ (tcp_snd_cwnd(tp) >> 2))); + } + + /* Use define here intentionally to get WARN_ON location shown at the caller */ +@@ -1270,7 +1281,7 @@ static inline bool tcp_is_cwnd_limited(const struct sock *sk) + + /* If in slow start, ensure cwnd grows to twice what was ACKed. */ + if (tcp_in_slow_start(tp)) +- return tp->snd_cwnd < 2 * tp->max_packets_out; ++ return tcp_snd_cwnd(tp) < 2 * tp->max_packets_out; + + return tp->is_cwnd_limited; + } +diff --git a/include/trace/events/tcp.h b/include/trace/events/tcp.h +index 521059d8dc0a..edcd6369de10 100644 +--- a/include/trace/events/tcp.h ++++ b/include/trace/events/tcp.h +@@ -279,7 +279,7 @@ TRACE_EVENT(tcp_probe, + __entry->data_len = skb->len - __tcp_hdrlen(th); + __entry->snd_nxt = tp->snd_nxt; + __entry->snd_una = tp->snd_una; +- __entry->snd_cwnd = tp->snd_cwnd; ++ __entry->snd_cwnd = tcp_snd_cwnd(tp); + __entry->snd_wnd = tp->snd_wnd; + __entry->rcv_wnd = tp->rcv_wnd; + __entry->ssthresh = tcp_current_ssthresh(sk); +diff --git a/net/core/filter.c b/net/core/filter.c +index 707e2e48d769..0816468c545c 100644 +--- a/net/core/filter.c ++++ b/net/core/filter.c +@@ -4885,7 +4885,7 @@ static int _bpf_setsockopt(struct sock *sk, int level, int optname, + if (val <= 0 || tp->data_segs_out > tp->syn_data) + ret = -EINVAL; + else +- tp->snd_cwnd = val; ++ tcp_snd_cwnd_set(tp, val); + break; + case TCP_BPF_SNDCWND_CLAMP: + if (val <= 0) { +diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c +index ef68d55e0944..f79b5a98888c 100644 +--- a/net/ipv4/tcp.c ++++ b/net/ipv4/tcp.c +@@ -435,7 +435,7 @@ void tcp_init_sock(struct sock *sk) + * algorithms that we must have the following bandaid to talk + * efficiently to them. -DaveM + */ +- tp->snd_cwnd = TCP_INIT_CWND; ++ tcp_snd_cwnd_set(tp, TCP_INIT_CWND); + + /* There's a bubble in the pipe until at least the first ACK. */ + tp->app_limited = ~0U; +@@ -3021,7 +3021,7 @@ int tcp_disconnect(struct sock *sk, int flags) + icsk->icsk_rto_min = TCP_RTO_MIN; + icsk->icsk_delack_max = TCP_DELACK_MAX; + tp->snd_ssthresh = TCP_INFINITE_SSTHRESH; +- tp->snd_cwnd = TCP_INIT_CWND; ++ tcp_snd_cwnd_set(tp, TCP_INIT_CWND); + tp->snd_cwnd_cnt = 0; + tp->window_clamp = 0; + tp->delivered = 0; +@@ -3732,7 +3732,7 @@ void tcp_get_info(struct sock *sk, struct tcp_info *info) + info->tcpi_max_pacing_rate = rate64; + + info->tcpi_reordering = tp->reordering; +- info->tcpi_snd_cwnd = tp->snd_cwnd; ++ info->tcpi_snd_cwnd = tcp_snd_cwnd(tp); + + if (info->tcpi_state == TCP_LISTEN) { + /* listeners aliased fields : +@@ -3901,7 +3901,7 @@ struct sk_buff *tcp_get_timestamping_opt_stats(const struct sock *sk, + rate64 = tcp_compute_delivery_rate(tp); + nla_put_u64_64bit(stats, TCP_NLA_DELIVERY_RATE, rate64, TCP_NLA_PAD); + +- nla_put_u32(stats, TCP_NLA_SND_CWND, tp->snd_cwnd); ++ nla_put_u32(stats, TCP_NLA_SND_CWND, tcp_snd_cwnd(tp)); + nla_put_u32(stats, TCP_NLA_REORDERING, tp->reordering); + nla_put_u32(stats, TCP_NLA_MIN_RTT, tcp_min_rtt(tp)); + +diff --git a/net/ipv4/tcp_bbr.c b/net/ipv4/tcp_bbr.c +index 6274462b86b4..c5ee83654db1 100644 +--- a/net/ipv4/tcp_bbr.c ++++ b/net/ipv4/tcp_bbr.c +@@ -274,7 +274,7 @@ static void bbr_init_pacing_rate_from_rtt(struct sock *sk) + } else { /* no RTT sample yet */ + rtt_us = USEC_PER_MSEC; /* use nominal default RTT */ + } +- bw = (u64)tp->snd_cwnd * BW_UNIT; ++ bw = (u64)tcp_snd_cwnd(tp) * BW_UNIT; + do_div(bw, rtt_us); + sk->sk_pacing_rate = bbr_bw_to_pacing_rate(sk, bw, bbr_high_gain); + } +@@ -321,9 +321,9 @@ static void bbr_save_cwnd(struct sock *sk) + struct bbr *bbr = inet_csk_ca(sk); + + if (bbr->prev_ca_state < TCP_CA_Recovery && bbr->mode != BBR_PROBE_RTT) +- bbr->prior_cwnd = tp->snd_cwnd; /* this cwnd is good enough */ ++ bbr->prior_cwnd = tcp_snd_cwnd(tp); /* this cwnd is good enough */ + else /* loss recovery or BBR_PROBE_RTT have temporarily cut cwnd */ +- bbr->prior_cwnd = max(bbr->prior_cwnd, tp->snd_cwnd); ++ bbr->prior_cwnd = max(bbr->prior_cwnd, tcp_snd_cwnd(tp)); + } + + static void bbr_cwnd_event(struct sock *sk, enum tcp_ca_event event) +@@ -480,7 +480,7 @@ static bool bbr_set_cwnd_to_recover_or_restore( + struct tcp_sock *tp = tcp_sk(sk); + struct bbr *bbr = inet_csk_ca(sk); + u8 prev_state = bbr->prev_ca_state, state = inet_csk(sk)->icsk_ca_state; +- u32 cwnd = tp->snd_cwnd; ++ u32 cwnd = tcp_snd_cwnd(tp); + + /* An ACK for P pkts should release at most 2*P packets. We do this + * in two steps. First, here we deduct the number of lost packets. +@@ -518,7 +518,7 @@ static void bbr_set_cwnd(struct sock *sk, const struct rate_sample *rs, + { + struct tcp_sock *tp = tcp_sk(sk); + struct bbr *bbr = inet_csk_ca(sk); +- u32 cwnd = tp->snd_cwnd, target_cwnd = 0; ++ u32 cwnd = tcp_snd_cwnd(tp), target_cwnd = 0; + + if (!acked) + goto done; /* no packet fully ACKed; just apply caps */ +@@ -542,9 +542,9 @@ static void bbr_set_cwnd(struct sock *sk, const struct rate_sample *rs, + cwnd = max(cwnd, bbr_cwnd_min_target); + + done: +- tp->snd_cwnd = min(cwnd, tp->snd_cwnd_clamp); /* apply global cap */ ++ tcp_snd_cwnd_set(tp, min(cwnd, tp->snd_cwnd_clamp)); /* apply global cap */ + if (bbr->mode == BBR_PROBE_RTT) /* drain queue, refresh min_rtt */ +- tp->snd_cwnd = min(tp->snd_cwnd, bbr_cwnd_min_target); ++ tcp_snd_cwnd_set(tp, min(tcp_snd_cwnd(tp), bbr_cwnd_min_target)); + } + + /* End cycle phase if it's time and/or we hit the phase's in-flight target. */ +@@ -854,7 +854,7 @@ static void bbr_update_ack_aggregation(struct sock *sk, + bbr->ack_epoch_acked = min_t(u32, 0xFFFFF, + bbr->ack_epoch_acked + rs->acked_sacked); + extra_acked = bbr->ack_epoch_acked - expected_acked; +- extra_acked = min(extra_acked, tp->snd_cwnd); ++ extra_acked = min(extra_acked, tcp_snd_cwnd(tp)); + if (extra_acked > bbr->extra_acked[bbr->extra_acked_win_idx]) + bbr->extra_acked[bbr->extra_acked_win_idx] = extra_acked; + } +@@ -912,7 +912,7 @@ static void bbr_check_probe_rtt_done(struct sock *sk) + return; + + bbr->min_rtt_stamp = tcp_jiffies32; /* wait a while until PROBE_RTT */ +- tp->snd_cwnd = max(tp->snd_cwnd, bbr->prior_cwnd); ++ tcp_snd_cwnd_set(tp, max(tcp_snd_cwnd(tp), bbr->prior_cwnd)); + bbr_reset_mode(sk); + } + +@@ -1091,7 +1091,7 @@ static u32 bbr_undo_cwnd(struct sock *sk) + bbr->full_bw = 0; /* spurious slow-down; reset full pipe detection */ + bbr->full_bw_cnt = 0; + bbr_reset_lt_bw_sampling(sk); +- return tcp_sk(sk)->snd_cwnd; ++ return tcp_snd_cwnd(tcp_sk(sk)); + } + + /* Entering loss recovery, so save cwnd for when we exit or undo recovery. */ +diff --git a/net/ipv4/tcp_bic.c b/net/ipv4/tcp_bic.c +index f5f588b1f6e9..58358bf92e1b 100644 +--- a/net/ipv4/tcp_bic.c ++++ b/net/ipv4/tcp_bic.c +@@ -150,7 +150,7 @@ static void bictcp_cong_avoid(struct sock *sk, u32 ack, u32 acked) + if (!acked) + return; + } +- bictcp_update(ca, tp->snd_cwnd); ++ bictcp_update(ca, tcp_snd_cwnd(tp)); + tcp_cong_avoid_ai(tp, ca->cnt, acked); + } + +@@ -166,16 +166,16 @@ static u32 bictcp_recalc_ssthresh(struct sock *sk) + ca->epoch_start = 0; /* end of epoch */ + + /* Wmax and fast convergence */ +- if (tp->snd_cwnd < ca->last_max_cwnd && fast_convergence) +- ca->last_max_cwnd = (tp->snd_cwnd * (BICTCP_BETA_SCALE + beta)) ++ if (tcp_snd_cwnd(tp) < ca->last_max_cwnd && fast_convergence) ++ ca->last_max_cwnd = (tcp_snd_cwnd(tp) * (BICTCP_BETA_SCALE + beta)) + / (2 * BICTCP_BETA_SCALE); + else +- ca->last_max_cwnd = tp->snd_cwnd; ++ ca->last_max_cwnd = tcp_snd_cwnd(tp); + +- if (tp->snd_cwnd <= low_window) +- return max(tp->snd_cwnd >> 1U, 2U); ++ if (tcp_snd_cwnd(tp) <= low_window) ++ return max(tcp_snd_cwnd(tp) >> 1U, 2U); + else +- return max((tp->snd_cwnd * beta) / BICTCP_BETA_SCALE, 2U); ++ return max((tcp_snd_cwnd(tp) * beta) / BICTCP_BETA_SCALE, 2U); + } + + static void bictcp_state(struct sock *sk, u8 new_state) +diff --git a/net/ipv4/tcp_cdg.c b/net/ipv4/tcp_cdg.c +index 709d23801823..ddc7ba0554bd 100644 +--- a/net/ipv4/tcp_cdg.c ++++ b/net/ipv4/tcp_cdg.c +@@ -161,8 +161,8 @@ static void tcp_cdg_hystart_update(struct sock *sk) + LINUX_MIB_TCPHYSTARTTRAINDETECT); + NET_ADD_STATS(sock_net(sk), + LINUX_MIB_TCPHYSTARTTRAINCWND, +- tp->snd_cwnd); +- tp->snd_ssthresh = tp->snd_cwnd; ++ tcp_snd_cwnd(tp)); ++ tp->snd_ssthresh = tcp_snd_cwnd(tp); + return; + } + } +@@ -180,8 +180,8 @@ static void tcp_cdg_hystart_update(struct sock *sk) + LINUX_MIB_TCPHYSTARTDELAYDETECT); + NET_ADD_STATS(sock_net(sk), + LINUX_MIB_TCPHYSTARTDELAYCWND, +- tp->snd_cwnd); +- tp->snd_ssthresh = tp->snd_cwnd; ++ tcp_snd_cwnd(tp)); ++ tp->snd_ssthresh = tcp_snd_cwnd(tp); + } + } + } +@@ -252,7 +252,7 @@ static bool tcp_cdg_backoff(struct sock *sk, u32 grad) + return false; + } + +- ca->shadow_wnd = max(ca->shadow_wnd, tp->snd_cwnd); ++ ca->shadow_wnd = max(ca->shadow_wnd, tcp_snd_cwnd(tp)); + ca->state = CDG_BACKOFF; + tcp_enter_cwr(sk); + return true; +@@ -285,14 +285,14 @@ static void tcp_cdg_cong_avoid(struct sock *sk, u32 ack, u32 acked) + } + + if (!tcp_is_cwnd_limited(sk)) { +- ca->shadow_wnd = min(ca->shadow_wnd, tp->snd_cwnd); ++ ca->shadow_wnd = min(ca->shadow_wnd, tcp_snd_cwnd(tp)); + return; + } + +- prior_snd_cwnd = tp->snd_cwnd; ++ prior_snd_cwnd = tcp_snd_cwnd(tp); + tcp_reno_cong_avoid(sk, ack, acked); + +- incr = tp->snd_cwnd - prior_snd_cwnd; ++ incr = tcp_snd_cwnd(tp) - prior_snd_cwnd; + ca->shadow_wnd = max(ca->shadow_wnd, ca->shadow_wnd + incr); + } + +@@ -331,15 +331,15 @@ static u32 tcp_cdg_ssthresh(struct sock *sk) + struct tcp_sock *tp = tcp_sk(sk); + + if (ca->state == CDG_BACKOFF) +- return max(2U, (tp->snd_cwnd * min(1024U, backoff_beta)) >> 10); ++ return max(2U, (tcp_snd_cwnd(tp) * min(1024U, backoff_beta)) >> 10); + + if (ca->state == CDG_NONFULL && use_tolerance) +- return tp->snd_cwnd; ++ return tcp_snd_cwnd(tp); + +- ca->shadow_wnd = min(ca->shadow_wnd >> 1, tp->snd_cwnd); ++ ca->shadow_wnd = min(ca->shadow_wnd >> 1, tcp_snd_cwnd(tp)); + if (use_shadow) +- return max3(2U, ca->shadow_wnd, tp->snd_cwnd >> 1); +- return max(2U, tp->snd_cwnd >> 1); ++ return max3(2U, ca->shadow_wnd, tcp_snd_cwnd(tp) >> 1); ++ return max(2U, tcp_snd_cwnd(tp) >> 1); + } + + static void tcp_cdg_cwnd_event(struct sock *sk, const enum tcp_ca_event ev) +@@ -357,7 +357,7 @@ static void tcp_cdg_cwnd_event(struct sock *sk, const enum tcp_ca_event ev) + + ca->gradients = gradients; + ca->rtt_seq = tp->snd_nxt; +- ca->shadow_wnd = tp->snd_cwnd; ++ ca->shadow_wnd = tcp_snd_cwnd(tp); + break; + case CA_EVENT_COMPLETE_CWR: + ca->state = CDG_UNKNOWN; +@@ -380,7 +380,7 @@ static void tcp_cdg_init(struct sock *sk) + ca->gradients = kcalloc(window, sizeof(ca->gradients[0]), + GFP_NOWAIT | __GFP_NOWARN); + ca->rtt_seq = tp->snd_nxt; +- ca->shadow_wnd = tp->snd_cwnd; ++ ca->shadow_wnd = tcp_snd_cwnd(tp); + } + + static void tcp_cdg_release(struct sock *sk) +diff --git a/net/ipv4/tcp_cong.c b/net/ipv4/tcp_cong.c +index db5831e6c136..f43db30a7195 100644 +--- a/net/ipv4/tcp_cong.c ++++ b/net/ipv4/tcp_cong.c +@@ -395,10 +395,10 @@ int tcp_set_congestion_control(struct sock *sk, const char *name, bool load, + */ + u32 tcp_slow_start(struct tcp_sock *tp, u32 acked) + { +- u32 cwnd = min(tp->snd_cwnd + acked, tp->snd_ssthresh); ++ u32 cwnd = min(tcp_snd_cwnd(tp) + acked, tp->snd_ssthresh); + +- acked -= cwnd - tp->snd_cwnd; +- tp->snd_cwnd = min(cwnd, tp->snd_cwnd_clamp); ++ acked -= cwnd - tcp_snd_cwnd(tp); ++ tcp_snd_cwnd_set(tp, min(cwnd, tp->snd_cwnd_clamp)); + + return acked; + } +@@ -412,7 +412,7 @@ void tcp_cong_avoid_ai(struct tcp_sock *tp, u32 w, u32 acked) + /* If credits accumulated at a higher w, apply them gently now. */ + if (tp->snd_cwnd_cnt >= w) { + tp->snd_cwnd_cnt = 0; +- tp->snd_cwnd++; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + } + + tp->snd_cwnd_cnt += acked; +@@ -420,9 +420,9 @@ void tcp_cong_avoid_ai(struct tcp_sock *tp, u32 w, u32 acked) + u32 delta = tp->snd_cwnd_cnt / w; + + tp->snd_cwnd_cnt -= delta * w; +- tp->snd_cwnd += delta; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + delta); + } +- tp->snd_cwnd = min(tp->snd_cwnd, tp->snd_cwnd_clamp); ++ tcp_snd_cwnd_set(tp, min(tcp_snd_cwnd(tp), tp->snd_cwnd_clamp)); + } + EXPORT_SYMBOL_GPL(tcp_cong_avoid_ai); + +@@ -447,7 +447,7 @@ void tcp_reno_cong_avoid(struct sock *sk, u32 ack, u32 acked) + return; + } + /* In dangerous area, increase slowly. */ +- tcp_cong_avoid_ai(tp, tp->snd_cwnd, acked); ++ tcp_cong_avoid_ai(tp, tcp_snd_cwnd(tp), acked); + } + EXPORT_SYMBOL_GPL(tcp_reno_cong_avoid); + +@@ -456,7 +456,7 @@ u32 tcp_reno_ssthresh(struct sock *sk) + { + const struct tcp_sock *tp = tcp_sk(sk); + +- return max(tp->snd_cwnd >> 1U, 2U); ++ return max(tcp_snd_cwnd(tp) >> 1U, 2U); + } + EXPORT_SYMBOL_GPL(tcp_reno_ssthresh); + +@@ -464,7 +464,7 @@ u32 tcp_reno_undo_cwnd(struct sock *sk) + { + const struct tcp_sock *tp = tcp_sk(sk); + +- return max(tp->snd_cwnd, tp->prior_cwnd); ++ return max(tcp_snd_cwnd(tp), tp->prior_cwnd); + } + EXPORT_SYMBOL_GPL(tcp_reno_undo_cwnd); + +diff --git a/net/ipv4/tcp_cubic.c b/net/ipv4/tcp_cubic.c +index 8d2d4d652f6d..af4fc067f2a1 100644 +--- a/net/ipv4/tcp_cubic.c ++++ b/net/ipv4/tcp_cubic.c +@@ -332,7 +332,7 @@ static void cubictcp_cong_avoid(struct sock *sk, u32 ack, u32 acked) + if (!acked) + return; + } +- bictcp_update(ca, tp->snd_cwnd, acked); ++ bictcp_update(ca, tcp_snd_cwnd(tp), acked); + tcp_cong_avoid_ai(tp, ca->cnt, acked); + } + +@@ -344,13 +344,13 @@ static u32 cubictcp_recalc_ssthresh(struct sock *sk) + ca->epoch_start = 0; /* end of epoch */ + + /* Wmax and fast convergence */ +- if (tp->snd_cwnd < ca->last_max_cwnd && fast_convergence) +- ca->last_max_cwnd = (tp->snd_cwnd * (BICTCP_BETA_SCALE + beta)) ++ if (tcp_snd_cwnd(tp) < ca->last_max_cwnd && fast_convergence) ++ ca->last_max_cwnd = (tcp_snd_cwnd(tp) * (BICTCP_BETA_SCALE + beta)) + / (2 * BICTCP_BETA_SCALE); + else +- ca->last_max_cwnd = tp->snd_cwnd; ++ ca->last_max_cwnd = tcp_snd_cwnd(tp); + +- return max((tp->snd_cwnd * beta) / BICTCP_BETA_SCALE, 2U); ++ return max((tcp_snd_cwnd(tp) * beta) / BICTCP_BETA_SCALE, 2U); + } + + static void cubictcp_state(struct sock *sk, u8 new_state) +@@ -411,13 +411,13 @@ static void hystart_update(struct sock *sk, u32 delay) + ca->found = 1; + pr_debug("hystart_ack_train (%u > %u) delay_min %u (+ ack_delay %u) cwnd %u\n", + now - ca->round_start, threshold, +- ca->delay_min, hystart_ack_delay(sk), tp->snd_cwnd); ++ ca->delay_min, hystart_ack_delay(sk), tcp_snd_cwnd(tp)); + NET_INC_STATS(sock_net(sk), + LINUX_MIB_TCPHYSTARTTRAINDETECT); + NET_ADD_STATS(sock_net(sk), + LINUX_MIB_TCPHYSTARTTRAINCWND, +- tp->snd_cwnd); +- tp->snd_ssthresh = tp->snd_cwnd; ++ tcp_snd_cwnd(tp)); ++ tp->snd_ssthresh = tcp_snd_cwnd(tp); + } + } + } +@@ -436,8 +436,8 @@ static void hystart_update(struct sock *sk, u32 delay) + LINUX_MIB_TCPHYSTARTDELAYDETECT); + NET_ADD_STATS(sock_net(sk), + LINUX_MIB_TCPHYSTARTDELAYCWND, +- tp->snd_cwnd); +- tp->snd_ssthresh = tp->snd_cwnd; ++ tcp_snd_cwnd(tp)); ++ tp->snd_ssthresh = tcp_snd_cwnd(tp); + } + } + } +@@ -467,7 +467,7 @@ static void cubictcp_acked(struct sock *sk, const struct ack_sample *sample) + + /* hystart triggers when cwnd is larger than some threshold */ + if (!ca->found && tcp_in_slow_start(tp) && hystart && +- tp->snd_cwnd >= hystart_low_window) ++ tcp_snd_cwnd(tp) >= hystart_low_window) + hystart_update(sk, delay); + } + +diff --git a/net/ipv4/tcp_dctcp.c b/net/ipv4/tcp_dctcp.c +index 79f705450c16..43bcefbaefbb 100644 +--- a/net/ipv4/tcp_dctcp.c ++++ b/net/ipv4/tcp_dctcp.c +@@ -104,8 +104,8 @@ static u32 dctcp_ssthresh(struct sock *sk) + struct dctcp *ca = inet_csk_ca(sk); + struct tcp_sock *tp = tcp_sk(sk); + +- ca->loss_cwnd = tp->snd_cwnd; +- return max(tp->snd_cwnd - ((tp->snd_cwnd * ca->dctcp_alpha) >> 11U), 2U); ++ ca->loss_cwnd = tcp_snd_cwnd(tp); ++ return max(tcp_snd_cwnd(tp) - ((tcp_snd_cwnd(tp) * ca->dctcp_alpha) >> 11U), 2U); + } + + static void dctcp_update_alpha(struct sock *sk, u32 flags) +@@ -146,8 +146,8 @@ static void dctcp_react_to_loss(struct sock *sk) + struct dctcp *ca = inet_csk_ca(sk); + struct tcp_sock *tp = tcp_sk(sk); + +- ca->loss_cwnd = tp->snd_cwnd; +- tp->snd_ssthresh = max(tp->snd_cwnd >> 1U, 2U); ++ ca->loss_cwnd = tcp_snd_cwnd(tp); ++ tp->snd_ssthresh = max(tcp_snd_cwnd(tp) >> 1U, 2U); + } + + static void dctcp_state(struct sock *sk, u8 new_state) +@@ -209,8 +209,9 @@ static size_t dctcp_get_info(struct sock *sk, u32 ext, int *attr, + static u32 dctcp_cwnd_undo(struct sock *sk) + { + const struct dctcp *ca = inet_csk_ca(sk); ++ struct tcp_sock *tp = tcp_sk(sk); + +- return max(tcp_sk(sk)->snd_cwnd, ca->loss_cwnd); ++ return max(tcp_snd_cwnd(tp), ca->loss_cwnd); + } + + static struct tcp_congestion_ops dctcp __read_mostly = { +diff --git a/net/ipv4/tcp_highspeed.c b/net/ipv4/tcp_highspeed.c +index 349069d6cd0a..c6de5ce79ad3 100644 +--- a/net/ipv4/tcp_highspeed.c ++++ b/net/ipv4/tcp_highspeed.c +@@ -127,22 +127,22 @@ static void hstcp_cong_avoid(struct sock *sk, u32 ack, u32 acked) + * snd_cwnd <= + * hstcp_aimd_vals[ca->ai].cwnd + */ +- if (tp->snd_cwnd > hstcp_aimd_vals[ca->ai].cwnd) { +- while (tp->snd_cwnd > hstcp_aimd_vals[ca->ai].cwnd && ++ if (tcp_snd_cwnd(tp) > hstcp_aimd_vals[ca->ai].cwnd) { ++ while (tcp_snd_cwnd(tp) > hstcp_aimd_vals[ca->ai].cwnd && + ca->ai < HSTCP_AIMD_MAX - 1) + ca->ai++; +- } else if (ca->ai && tp->snd_cwnd <= hstcp_aimd_vals[ca->ai-1].cwnd) { +- while (ca->ai && tp->snd_cwnd <= hstcp_aimd_vals[ca->ai-1].cwnd) ++ } else if (ca->ai && tcp_snd_cwnd(tp) <= hstcp_aimd_vals[ca->ai-1].cwnd) { ++ while (ca->ai && tcp_snd_cwnd(tp) <= hstcp_aimd_vals[ca->ai-1].cwnd) + ca->ai--; + } + + /* Do additive increase */ +- if (tp->snd_cwnd < tp->snd_cwnd_clamp) { ++ if (tcp_snd_cwnd(tp) < tp->snd_cwnd_clamp) { + /* cwnd = cwnd + a(w) / cwnd */ + tp->snd_cwnd_cnt += ca->ai + 1; +- if (tp->snd_cwnd_cnt >= tp->snd_cwnd) { +- tp->snd_cwnd_cnt -= tp->snd_cwnd; +- tp->snd_cwnd++; ++ if (tp->snd_cwnd_cnt >= tcp_snd_cwnd(tp)) { ++ tp->snd_cwnd_cnt -= tcp_snd_cwnd(tp); ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + } + } + } +@@ -154,7 +154,7 @@ static u32 hstcp_ssthresh(struct sock *sk) + struct hstcp *ca = inet_csk_ca(sk); + + /* Do multiplicative decrease */ +- return max(tp->snd_cwnd - ((tp->snd_cwnd * hstcp_aimd_vals[ca->ai].md) >> 8), 2U); ++ return max(tcp_snd_cwnd(tp) - ((tcp_snd_cwnd(tp) * hstcp_aimd_vals[ca->ai].md) >> 8), 2U); + } + + static struct tcp_congestion_ops tcp_highspeed __read_mostly = { +diff --git a/net/ipv4/tcp_htcp.c b/net/ipv4/tcp_htcp.c +index 55adcfcf96fe..52b1f2665dfa 100644 +--- a/net/ipv4/tcp_htcp.c ++++ b/net/ipv4/tcp_htcp.c +@@ -124,7 +124,7 @@ static void measure_achieved_throughput(struct sock *sk, + + ca->packetcount += sample->pkts_acked; + +- if (ca->packetcount >= tp->snd_cwnd - (ca->alpha >> 7 ? : 1) && ++ if (ca->packetcount >= tcp_snd_cwnd(tp) - (ca->alpha >> 7 ? : 1) && + now - ca->lasttime >= ca->minRTT && + ca->minRTT > 0) { + __u32 cur_Bi = ca->packetcount * HZ / (now - ca->lasttime); +@@ -225,7 +225,7 @@ static u32 htcp_recalc_ssthresh(struct sock *sk) + const struct htcp *ca = inet_csk_ca(sk); + + htcp_param_update(sk); +- return max((tp->snd_cwnd * ca->beta) >> 7, 2U); ++ return max((tcp_snd_cwnd(tp) * ca->beta) >> 7, 2U); + } + + static void htcp_cong_avoid(struct sock *sk, u32 ack, u32 acked) +@@ -242,9 +242,9 @@ static void htcp_cong_avoid(struct sock *sk, u32 ack, u32 acked) + /* In dangerous area, increase slowly. + * In theory this is tp->snd_cwnd += alpha / tp->snd_cwnd + */ +- if ((tp->snd_cwnd_cnt * ca->alpha)>>7 >= tp->snd_cwnd) { +- if (tp->snd_cwnd < tp->snd_cwnd_clamp) +- tp->snd_cwnd++; ++ if ((tp->snd_cwnd_cnt * ca->alpha)>>7 >= tcp_snd_cwnd(tp)) { ++ if (tcp_snd_cwnd(tp) < tp->snd_cwnd_clamp) ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + tp->snd_cwnd_cnt = 0; + htcp_alpha_update(ca); + } else +diff --git a/net/ipv4/tcp_hybla.c b/net/ipv4/tcp_hybla.c +index be39327e04e6..abd7d91807e5 100644 +--- a/net/ipv4/tcp_hybla.c ++++ b/net/ipv4/tcp_hybla.c +@@ -54,7 +54,7 @@ static void hybla_init(struct sock *sk) + ca->rho2_7ls = 0; + ca->snd_cwnd_cents = 0; + ca->hybla_en = true; +- tp->snd_cwnd = 2; ++ tcp_snd_cwnd_set(tp, 2); + tp->snd_cwnd_clamp = 65535; + + /* 1st Rho measurement based on initial srtt */ +@@ -62,7 +62,7 @@ static void hybla_init(struct sock *sk) + + /* set minimum rtt as this is the 1st ever seen */ + ca->minrtt_us = tp->srtt_us; +- tp->snd_cwnd = ca->rho; ++ tcp_snd_cwnd_set(tp, ca->rho); + } + + static void hybla_state(struct sock *sk, u8 ca_state) +@@ -137,31 +137,31 @@ static void hybla_cong_avoid(struct sock *sk, u32 ack, u32 acked) + * as long as increment is estimated as (rho<<7)/window + * it already is <<7 and we can easily count its fractions. + */ +- increment = ca->rho2_7ls / tp->snd_cwnd; ++ increment = ca->rho2_7ls / tcp_snd_cwnd(tp); + if (increment < 128) + tp->snd_cwnd_cnt++; + } + + odd = increment % 128; +- tp->snd_cwnd += increment >> 7; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + (increment >> 7)); + ca->snd_cwnd_cents += odd; + + /* check when fractions goes >=128 and increase cwnd by 1. */ + while (ca->snd_cwnd_cents >= 128) { +- tp->snd_cwnd++; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + ca->snd_cwnd_cents -= 128; + tp->snd_cwnd_cnt = 0; + } + /* check when cwnd has not been incremented for a while */ +- if (increment == 0 && odd == 0 && tp->snd_cwnd_cnt >= tp->snd_cwnd) { +- tp->snd_cwnd++; ++ if (increment == 0 && odd == 0 && tp->snd_cwnd_cnt >= tcp_snd_cwnd(tp)) { ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + tp->snd_cwnd_cnt = 0; + } + /* clamp down slowstart cwnd to ssthresh value. */ + if (is_slowstart) +- tp->snd_cwnd = min(tp->snd_cwnd, tp->snd_ssthresh); ++ tcp_snd_cwnd_set(tp, min(tcp_snd_cwnd(tp), tp->snd_ssthresh)); + +- tp->snd_cwnd = min_t(u32, tp->snd_cwnd, tp->snd_cwnd_clamp); ++ tcp_snd_cwnd_set(tp, min(tcp_snd_cwnd(tp), tp->snd_cwnd_clamp)); + } + + static struct tcp_congestion_ops tcp_hybla __read_mostly = { +diff --git a/net/ipv4/tcp_illinois.c b/net/ipv4/tcp_illinois.c +index 00e54873213e..c0c81a2c77fa 100644 +--- a/net/ipv4/tcp_illinois.c ++++ b/net/ipv4/tcp_illinois.c +@@ -224,7 +224,7 @@ static void update_params(struct sock *sk) + struct tcp_sock *tp = tcp_sk(sk); + struct illinois *ca = inet_csk_ca(sk); + +- if (tp->snd_cwnd < win_thresh) { ++ if (tcp_snd_cwnd(tp) < win_thresh) { + ca->alpha = ALPHA_BASE; + ca->beta = BETA_BASE; + } else if (ca->cnt_rtt > 0) { +@@ -284,9 +284,9 @@ static void tcp_illinois_cong_avoid(struct sock *sk, u32 ack, u32 acked) + * tp->snd_cwnd += alpha/tp->snd_cwnd + */ + delta = (tp->snd_cwnd_cnt * ca->alpha) >> ALPHA_SHIFT; +- if (delta >= tp->snd_cwnd) { +- tp->snd_cwnd = min(tp->snd_cwnd + delta / tp->snd_cwnd, +- (u32)tp->snd_cwnd_clamp); ++ if (delta >= tcp_snd_cwnd(tp)) { ++ tcp_snd_cwnd_set(tp, min(tcp_snd_cwnd(tp) + delta / tcp_snd_cwnd(tp), ++ (u32)tp->snd_cwnd_clamp)); + tp->snd_cwnd_cnt = 0; + } + } +@@ -296,9 +296,11 @@ static u32 tcp_illinois_ssthresh(struct sock *sk) + { + struct tcp_sock *tp = tcp_sk(sk); + struct illinois *ca = inet_csk_ca(sk); ++ u32 decr; + + /* Multiplicative decrease */ +- return max(tp->snd_cwnd - ((tp->snd_cwnd * ca->beta) >> BETA_SHIFT), 2U); ++ decr = (tcp_snd_cwnd(tp) * ca->beta) >> BETA_SHIFT; ++ return max(tcp_snd_cwnd(tp) - decr, 2U); + } + + /* Extract info for Tcp socket info provided via netlink. */ +diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c +index dfd32cd3b95e..4e87614313c0 100644 +--- a/net/ipv4/tcp_input.c ++++ b/net/ipv4/tcp_input.c +@@ -414,7 +414,7 @@ static void tcp_sndbuf_expand(struct sock *sk) + per_mss = roundup_pow_of_two(per_mss) + + SKB_DATA_ALIGN(sizeof(struct sk_buff)); + +- nr_segs = max_t(u32, TCP_INIT_CWND, tp->snd_cwnd); ++ nr_segs = max_t(u32, TCP_INIT_CWND, tcp_snd_cwnd(tp)); + nr_segs = max_t(u32, nr_segs, tp->reordering + 1); + + /* Fast Recovery (RFC 5681 3.2) : +@@ -901,12 +901,12 @@ static void tcp_update_pacing_rate(struct sock *sk) + * If snd_cwnd >= (tp->snd_ssthresh / 2), we are approaching + * end of slow start and should slow down. + */ +- if (tp->snd_cwnd < tp->snd_ssthresh / 2) ++ if (tcp_snd_cwnd(tp) < tp->snd_ssthresh / 2) + rate *= sock_net(sk)->ipv4.sysctl_tcp_pacing_ss_ratio; + else + rate *= sock_net(sk)->ipv4.sysctl_tcp_pacing_ca_ratio; + +- rate *= max(tp->snd_cwnd, tp->packets_out); ++ rate *= max(tcp_snd_cwnd(tp), tp->packets_out); + + if (likely(tp->srtt_us)) + do_div(rate, tp->srtt_us); +@@ -2139,12 +2139,12 @@ void tcp_enter_loss(struct sock *sk) + !after(tp->high_seq, tp->snd_una) || + (icsk->icsk_ca_state == TCP_CA_Loss && !icsk->icsk_retransmits)) { + tp->prior_ssthresh = tcp_current_ssthresh(sk); +- tp->prior_cwnd = tp->snd_cwnd; ++ tp->prior_cwnd = tcp_snd_cwnd(tp); + tp->snd_ssthresh = icsk->icsk_ca_ops->ssthresh(sk); + tcp_ca_event(sk, CA_EVENT_LOSS); + tcp_init_undo(tp); + } +- tp->snd_cwnd = tcp_packets_in_flight(tp) + 1; ++ tcp_snd_cwnd_set(tp, tcp_packets_in_flight(tp) + 1); + tp->snd_cwnd_cnt = 0; + tp->snd_cwnd_stamp = tcp_jiffies32; + +@@ -2450,7 +2450,7 @@ static void DBGUNDO(struct sock *sk, const char *msg) + pr_debug("Undo %s %pI4/%u c%u l%u ss%u/%u p%u\n", + msg, + &inet->inet_daddr, ntohs(inet->inet_dport), +- tp->snd_cwnd, tcp_left_out(tp), ++ tcp_snd_cwnd(tp), tcp_left_out(tp), + tp->snd_ssthresh, tp->prior_ssthresh, + tp->packets_out); + } +@@ -2459,7 +2459,7 @@ static void DBGUNDO(struct sock *sk, const char *msg) + pr_debug("Undo %s %pI6/%u c%u l%u ss%u/%u p%u\n", + msg, + &sk->sk_v6_daddr, ntohs(inet->inet_dport), +- tp->snd_cwnd, tcp_left_out(tp), ++ tcp_snd_cwnd(tp), tcp_left_out(tp), + tp->snd_ssthresh, tp->prior_ssthresh, + tp->packets_out); + } +@@ -2484,7 +2484,7 @@ static void tcp_undo_cwnd_reduction(struct sock *sk, bool unmark_loss) + if (tp->prior_ssthresh) { + const struct inet_connection_sock *icsk = inet_csk(sk); + +- tp->snd_cwnd = icsk->icsk_ca_ops->undo_cwnd(sk); ++ tcp_snd_cwnd_set(tp, icsk->icsk_ca_ops->undo_cwnd(sk)); + + if (tp->prior_ssthresh > tp->snd_ssthresh) { + tp->snd_ssthresh = tp->prior_ssthresh; +@@ -2591,7 +2591,7 @@ static void tcp_init_cwnd_reduction(struct sock *sk) + tp->high_seq = tp->snd_nxt; + tp->tlp_high_seq = 0; + tp->snd_cwnd_cnt = 0; +- tp->prior_cwnd = tp->snd_cwnd; ++ tp->prior_cwnd = tcp_snd_cwnd(tp); + tp->prr_delivered = 0; + tp->prr_out = 0; + tp->snd_ssthresh = inet_csk(sk)->icsk_ca_ops->ssthresh(sk); +@@ -2621,7 +2621,7 @@ void tcp_cwnd_reduction(struct sock *sk, int newly_acked_sacked, int newly_lost, + } + /* Force a fast retransmit upon entering fast recovery */ + sndcnt = max(sndcnt, (tp->prr_out ? 0 : 1)); +- tp->snd_cwnd = tcp_packets_in_flight(tp) + sndcnt; ++ tcp_snd_cwnd_set(tp, tcp_packets_in_flight(tp) + sndcnt); + } + + static inline void tcp_end_cwnd_reduction(struct sock *sk) +@@ -2634,7 +2634,7 @@ static inline void tcp_end_cwnd_reduction(struct sock *sk) + /* Reset cwnd to ssthresh in CWR or Recovery (unless it's undone) */ + if (tp->snd_ssthresh < TCP_INFINITE_SSTHRESH && + (inet_csk(sk)->icsk_ca_state == TCP_CA_CWR || tp->undo_marker)) { +- tp->snd_cwnd = tp->snd_ssthresh; ++ tcp_snd_cwnd_set(tp, tp->snd_ssthresh); + tp->snd_cwnd_stamp = tcp_jiffies32; + } + tcp_ca_event(sk, CA_EVENT_COMPLETE_CWR); +@@ -2701,9 +2701,9 @@ static void tcp_mtup_probe_success(struct sock *sk) + + /* FIXME: breaks with very large cwnd */ + tp->prior_ssthresh = tcp_current_ssthresh(sk); +- tp->snd_cwnd = tp->snd_cwnd * +- tcp_mss_to_mtu(sk, tp->mss_cache) / +- icsk->icsk_mtup.probe_size; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) * ++ tcp_mss_to_mtu(sk, tp->mss_cache) / ++ icsk->icsk_mtup.probe_size); + tp->snd_cwnd_cnt = 0; + tp->snd_cwnd_stamp = tcp_jiffies32; + tp->snd_ssthresh = tcp_current_ssthresh(sk); +@@ -3026,7 +3026,7 @@ static void tcp_fastretrans_alert(struct sock *sk, const u32 prior_snd_una, + tp->snd_una == tp->mtu_probe.probe_seq_start) { + tcp_mtup_probe_failed(sk); + /* Restores the reduction we did in tcp_mtup_probe() */ +- tp->snd_cwnd++; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + tcp_simple_retransmit(sk); + return; + } +@@ -5403,7 +5403,7 @@ static bool tcp_should_expand_sndbuf(const struct sock *sk) + return false; + + /* If we filled the congestion window, do not expand. */ +- if (tcp_packets_in_flight(tp) >= tp->snd_cwnd) ++ if (tcp_packets_in_flight(tp) >= tcp_snd_cwnd(tp)) + return false; + + return true; +@@ -5970,9 +5970,9 @@ void tcp_init_transfer(struct sock *sk, int bpf_op, struct sk_buff *skb) + * retransmission has occurred. + */ + if (tp->total_retrans > 1 && tp->undo_marker) +- tp->snd_cwnd = 1; ++ tcp_snd_cwnd_set(tp, 1); + else +- tp->snd_cwnd = tcp_init_cwnd(tp, __sk_dst_get(sk)); ++ tcp_snd_cwnd_set(tp, tcp_init_cwnd(tp, __sk_dst_get(sk))); + tp->snd_cwnd_stamp = tcp_jiffies32; + + bpf_skops_established(sk, bpf_op, skb); +diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c +index 0fe9461647da..a189625098ba 100644 +--- a/net/ipv4/tcp_ipv4.c ++++ b/net/ipv4/tcp_ipv4.c +@@ -2656,7 +2656,7 @@ static void get_tcp4_sock(struct sock *sk, struct seq_file *f, int i) + jiffies_to_clock_t(icsk->icsk_rto), + jiffies_to_clock_t(icsk->icsk_ack.ato), + (icsk->icsk_ack.quick << 1) | inet_csk_in_pingpong_mode(sk), +- tp->snd_cwnd, ++ tcp_snd_cwnd(tp), + state == TCP_LISTEN ? + fastopenq->max_qlen : + (tcp_in_initial_slowstart(tp) ? -1 : tp->snd_ssthresh)); +diff --git a/net/ipv4/tcp_lp.c b/net/ipv4/tcp_lp.c +index 82b36ec3f2f8..ae36780977d2 100644 +--- a/net/ipv4/tcp_lp.c ++++ b/net/ipv4/tcp_lp.c +@@ -297,7 +297,7 @@ static void tcp_lp_pkts_acked(struct sock *sk, const struct ack_sample *sample) + lp->flag &= ~LP_WITHIN_THR; + + pr_debug("TCP-LP: %05o|%5u|%5u|%15u|%15u|%15u\n", lp->flag, +- tp->snd_cwnd, lp->remote_hz, lp->owd_min, lp->owd_max, ++ tcp_snd_cwnd(tp), lp->remote_hz, lp->owd_min, lp->owd_max, + lp->sowd >> 3); + + if (lp->flag & LP_WITHIN_THR) +@@ -313,12 +313,12 @@ static void tcp_lp_pkts_acked(struct sock *sk, const struct ack_sample *sample) + /* happened within inference + * drop snd_cwnd into 1 */ + if (lp->flag & LP_WITHIN_INF) +- tp->snd_cwnd = 1U; ++ tcp_snd_cwnd_set(tp, 1U); + + /* happened after inference + * cut snd_cwnd into half */ + else +- tp->snd_cwnd = max(tp->snd_cwnd >> 1U, 1U); ++ tcp_snd_cwnd_set(tp, max(tcp_snd_cwnd(tp) >> 1U, 1U)); + + /* record this drop time */ + lp->last_drop = now; +diff --git a/net/ipv4/tcp_metrics.c b/net/ipv4/tcp_metrics.c +index 0588b004ddac..7029b0e98edb 100644 +--- a/net/ipv4/tcp_metrics.c ++++ b/net/ipv4/tcp_metrics.c +@@ -388,15 +388,15 @@ void tcp_update_metrics(struct sock *sk) + if (!net->ipv4.sysctl_tcp_no_ssthresh_metrics_save && + !tcp_metric_locked(tm, TCP_METRIC_SSTHRESH)) { + val = tcp_metric_get(tm, TCP_METRIC_SSTHRESH); +- if (val && (tp->snd_cwnd >> 1) > val) ++ if (val && (tcp_snd_cwnd(tp) >> 1) > val) + tcp_metric_set(tm, TCP_METRIC_SSTHRESH, +- tp->snd_cwnd >> 1); ++ tcp_snd_cwnd(tp) >> 1); + } + if (!tcp_metric_locked(tm, TCP_METRIC_CWND)) { + val = tcp_metric_get(tm, TCP_METRIC_CWND); +- if (tp->snd_cwnd > val) ++ if (tcp_snd_cwnd(tp) > val) + tcp_metric_set(tm, TCP_METRIC_CWND, +- tp->snd_cwnd); ++ tcp_snd_cwnd(tp)); + } + } else if (!tcp_in_slow_start(tp) && + icsk->icsk_ca_state == TCP_CA_Open) { +@@ -404,10 +404,10 @@ void tcp_update_metrics(struct sock *sk) + if (!net->ipv4.sysctl_tcp_no_ssthresh_metrics_save && + !tcp_metric_locked(tm, TCP_METRIC_SSTHRESH)) + tcp_metric_set(tm, TCP_METRIC_SSTHRESH, +- max(tp->snd_cwnd >> 1, tp->snd_ssthresh)); ++ max(tcp_snd_cwnd(tp) >> 1, tp->snd_ssthresh)); + if (!tcp_metric_locked(tm, TCP_METRIC_CWND)) { + val = tcp_metric_get(tm, TCP_METRIC_CWND); +- tcp_metric_set(tm, TCP_METRIC_CWND, (val + tp->snd_cwnd) >> 1); ++ tcp_metric_set(tm, TCP_METRIC_CWND, (val + tcp_snd_cwnd(tp)) >> 1); + } + } else { + /* Else slow start did not finish, cwnd is non-sense, +diff --git a/net/ipv4/tcp_nv.c b/net/ipv4/tcp_nv.c +index 95db7a11ba2a..63024ec17b20 100644 +--- a/net/ipv4/tcp_nv.c ++++ b/net/ipv4/tcp_nv.c +@@ -198,10 +198,10 @@ static void tcpnv_cong_avoid(struct sock *sk, u32 ack, u32 acked) + } + + if (ca->cwnd_growth_factor < 0) { +- cnt = tp->snd_cwnd << -ca->cwnd_growth_factor; ++ cnt = tcp_snd_cwnd(tp) << -ca->cwnd_growth_factor; + tcp_cong_avoid_ai(tp, cnt, acked); + } else { +- cnt = max(4U, tp->snd_cwnd >> ca->cwnd_growth_factor); ++ cnt = max(4U, tcp_snd_cwnd(tp) >> ca->cwnd_growth_factor); + tcp_cong_avoid_ai(tp, cnt, acked); + } + } +@@ -210,7 +210,7 @@ static u32 tcpnv_recalc_ssthresh(struct sock *sk) + { + const struct tcp_sock *tp = tcp_sk(sk); + +- return max((tp->snd_cwnd * nv_loss_dec_factor) >> 10, 2U); ++ return max((tcp_snd_cwnd(tp) * nv_loss_dec_factor) >> 10, 2U); + } + + static void tcpnv_state(struct sock *sk, u8 new_state) +@@ -258,7 +258,7 @@ static void tcpnv_acked(struct sock *sk, const struct ack_sample *sample) + return; + + /* Stop cwnd growth if we were in catch up mode */ +- if (ca->nv_catchup && tp->snd_cwnd >= nv_min_cwnd) { ++ if (ca->nv_catchup && tcp_snd_cwnd(tp) >= nv_min_cwnd) { + ca->nv_catchup = 0; + ca->nv_allow_cwnd_growth = 0; + } +@@ -372,7 +372,7 @@ static void tcpnv_acked(struct sock *sk, const struct ack_sample *sample) + * if cwnd < max_win, grow cwnd + * else leave the same + */ +- if (tp->snd_cwnd > max_win) { ++ if (tcp_snd_cwnd(tp) > max_win) { + /* there is congestion, check that it is ok + * to make a CA decision + * 1. We should have at least nv_dec_eval_min_calls +@@ -399,20 +399,20 @@ static void tcpnv_acked(struct sock *sk, const struct ack_sample *sample) + ca->nv_allow_cwnd_growth = 0; + tp->snd_ssthresh = + (nv_ssthresh_factor * max_win) >> 3; +- if (tp->snd_cwnd - max_win > 2) { ++ if (tcp_snd_cwnd(tp) - max_win > 2) { + /* gap > 2, we do exponential cwnd decrease */ + int dec; + +- dec = max(2U, ((tp->snd_cwnd - max_win) * ++ dec = max(2U, ((tcp_snd_cwnd(tp) - max_win) * + nv_cong_dec_mult) >> 7); +- tp->snd_cwnd -= dec; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) - dec); + } else if (nv_cong_dec_mult > 0) { +- tp->snd_cwnd = max_win; ++ tcp_snd_cwnd_set(tp, max_win); + } + if (ca->cwnd_growth_factor > 0) + ca->cwnd_growth_factor = 0; + ca->nv_no_cong_cnt = 0; +- } else if (tp->snd_cwnd <= max_win - nv_pad_buffer) { ++ } else if (tcp_snd_cwnd(tp) <= max_win - nv_pad_buffer) { + /* There is no congestion, grow cwnd if allowed*/ + if (ca->nv_eval_call_cnt < nv_inc_eval_min_calls) + return; +@@ -445,8 +445,8 @@ static void tcpnv_acked(struct sock *sk, const struct ack_sample *sample) + * (it wasn't before, if it is now is because nv + * decreased it). + */ +- if (tp->snd_cwnd < nv_min_cwnd) +- tp->snd_cwnd = nv_min_cwnd; ++ if (tcp_snd_cwnd(tp) < nv_min_cwnd) ++ tcp_snd_cwnd_set(tp, nv_min_cwnd); + } + } + +diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c +index df413282fa2e..ed7125a47ce0 100644 +--- a/net/ipv4/tcp_output.c ++++ b/net/ipv4/tcp_output.c +@@ -143,7 +143,7 @@ void tcp_cwnd_restart(struct sock *sk, s32 delta) + { + struct tcp_sock *tp = tcp_sk(sk); + u32 restart_cwnd = tcp_init_cwnd(tp, __sk_dst_get(sk)); +- u32 cwnd = tp->snd_cwnd; ++ u32 cwnd = tcp_snd_cwnd(tp); + + tcp_ca_event(sk, CA_EVENT_CWND_RESTART); + +@@ -152,7 +152,7 @@ void tcp_cwnd_restart(struct sock *sk, s32 delta) + + while ((delta -= inet_csk(sk)->icsk_rto) > 0 && cwnd > restart_cwnd) + cwnd >>= 1; +- tp->snd_cwnd = max(cwnd, restart_cwnd); ++ tcp_snd_cwnd_set(tp, max(cwnd, restart_cwnd)); + tp->snd_cwnd_stamp = tcp_jiffies32; + tp->snd_cwnd_used = 0; + } +@@ -1015,7 +1015,7 @@ static void tcp_tsq_write(struct sock *sk) + struct tcp_sock *tp = tcp_sk(sk); + + if (tp->lost_out > tp->retrans_out && +- tp->snd_cwnd > tcp_packets_in_flight(tp)) { ++ tcp_snd_cwnd(tp) > tcp_packets_in_flight(tp)) { + tcp_mstamp_refresh(tp); + tcp_xmit_retransmit_queue(sk); + } +@@ -1866,9 +1866,9 @@ static void tcp_cwnd_application_limited(struct sock *sk) + /* Limited by application or receiver window. */ + u32 init_win = tcp_init_cwnd(tp, __sk_dst_get(sk)); + u32 win_used = max(tp->snd_cwnd_used, init_win); +- if (win_used < tp->snd_cwnd) { ++ if (win_used < tcp_snd_cwnd(tp)) { + tp->snd_ssthresh = tcp_current_ssthresh(sk); +- tp->snd_cwnd = (tp->snd_cwnd + win_used) >> 1; ++ tcp_snd_cwnd_set(tp, (tcp_snd_cwnd(tp) + win_used) >> 1); + } + tp->snd_cwnd_used = 0; + } +@@ -2040,7 +2040,7 @@ static inline unsigned int tcp_cwnd_test(const struct tcp_sock *tp, + return 1; + + in_flight = tcp_packets_in_flight(tp); +- cwnd = tp->snd_cwnd; ++ cwnd = tcp_snd_cwnd(tp); + if (in_flight >= cwnd) + return 0; + +@@ -2197,12 +2197,12 @@ static bool tcp_tso_should_defer(struct sock *sk, struct sk_buff *skb, + in_flight = tcp_packets_in_flight(tp); + + BUG_ON(tcp_skb_pcount(skb) <= 1); +- BUG_ON(tp->snd_cwnd <= in_flight); ++ BUG_ON(tcp_snd_cwnd(tp) <= in_flight); + + send_win = tcp_wnd_end(tp) - TCP_SKB_CB(skb)->seq; + + /* From in_flight test above, we know that cwnd > in_flight. */ +- cong_win = (tp->snd_cwnd - in_flight) * tp->mss_cache; ++ cong_win = (tcp_snd_cwnd(tp) - in_flight) * tp->mss_cache; + + limit = min(send_win, cong_win); + +@@ -2216,7 +2216,7 @@ static bool tcp_tso_should_defer(struct sock *sk, struct sk_buff *skb, + + win_divisor = READ_ONCE(sock_net(sk)->ipv4.sysctl_tcp_tso_win_divisor); + if (win_divisor) { +- u32 chunk = min(tp->snd_wnd, tp->snd_cwnd * tp->mss_cache); ++ u32 chunk = min(tp->snd_wnd, tcp_snd_cwnd(tp) * tp->mss_cache); + + /* If at least some fraction of a window is available, + * just use it. +@@ -2344,7 +2344,7 @@ static int tcp_mtu_probe(struct sock *sk) + if (likely(!icsk->icsk_mtup.enabled || + icsk->icsk_mtup.probe_size || + inet_csk(sk)->icsk_ca_state != TCP_CA_Open || +- tp->snd_cwnd < 11 || ++ tcp_snd_cwnd(tp) < 11 || + tp->rx_opt.num_sacks || tp->rx_opt.dsack)) + return -1; + +@@ -2380,7 +2380,7 @@ static int tcp_mtu_probe(struct sock *sk) + return 0; + + /* Do we need to wait to drain cwnd? With none in flight, don't stall */ +- if (tcp_packets_in_flight(tp) + 2 > tp->snd_cwnd) { ++ if (tcp_packets_in_flight(tp) + 2 > tcp_snd_cwnd(tp)) { + if (!tcp_packets_in_flight(tp)) + return -1; + else +@@ -2452,7 +2452,7 @@ static int tcp_mtu_probe(struct sock *sk) + if (!tcp_transmit_skb(sk, nskb, 1, GFP_ATOMIC)) { + /* Decrement cwnd here because we are sending + * effectively two packets. */ +- tp->snd_cwnd--; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) - 1); + tcp_event_new_data_sent(sk, nskb); + + icsk->icsk_mtup.probe_size = tcp_mss_to_mtu(sk, nskb->len); +@@ -2709,7 +2709,7 @@ static bool tcp_write_xmit(struct sock *sk, unsigned int mss_now, int nonagle, + else + tcp_chrono_stop(sk, TCP_CHRONO_RWND_LIMITED); + +- is_cwnd_limited |= (tcp_packets_in_flight(tp) >= tp->snd_cwnd); ++ is_cwnd_limited |= (tcp_packets_in_flight(tp) >= tcp_snd_cwnd(tp)); + if (likely(sent_pkts || is_cwnd_limited)) + tcp_cwnd_validate(sk, is_cwnd_limited); + +@@ -2819,7 +2819,7 @@ void tcp_send_loss_probe(struct sock *sk) + if (unlikely(!skb)) { + WARN_ONCE(tp->packets_out, + "invalid inflight: %u state %u cwnd %u mss %d\n", +- tp->packets_out, sk->sk_state, tp->snd_cwnd, mss); ++ tp->packets_out, sk->sk_state, tcp_snd_cwnd(tp), mss); + inet_csk(sk)->icsk_pending = 0; + return; + } +@@ -3308,7 +3308,7 @@ void tcp_xmit_retransmit_queue(struct sock *sk) + if (!hole) + tp->retransmit_skb_hint = skb; + +- segs = tp->snd_cwnd - tcp_packets_in_flight(tp); ++ segs = tcp_snd_cwnd(tp) - tcp_packets_in_flight(tp); + if (segs <= 0) + break; + sacked = TCP_SKB_CB(skb)->sacked; +diff --git a/net/ipv4/tcp_rate.c b/net/ipv4/tcp_rate.c +index 6ab197928abb..042e27f54116 100644 +--- a/net/ipv4/tcp_rate.c ++++ b/net/ipv4/tcp_rate.c +@@ -194,7 +194,7 @@ void tcp_rate_check_app_limited(struct sock *sk) + /* Nothing in sending host's qdisc queues or NIC tx queue. */ + sk_wmem_alloc_get(sk) < SKB_TRUESIZE(1) && + /* We are not limited by CWND. */ +- tcp_packets_in_flight(tp) < tp->snd_cwnd && ++ tcp_packets_in_flight(tp) < tcp_snd_cwnd(tp) && + /* All lost packets have been retransmitted. */ + tp->lost_out <= tp->retrans_out) + tp->app_limited = +diff --git a/net/ipv4/tcp_scalable.c b/net/ipv4/tcp_scalable.c +index 5842081bc8a2..862b96248a92 100644 +--- a/net/ipv4/tcp_scalable.c ++++ b/net/ipv4/tcp_scalable.c +@@ -27,7 +27,7 @@ static void tcp_scalable_cong_avoid(struct sock *sk, u32 ack, u32 acked) + if (!acked) + return; + } +- tcp_cong_avoid_ai(tp, min(tp->snd_cwnd, TCP_SCALABLE_AI_CNT), ++ tcp_cong_avoid_ai(tp, min(tcp_snd_cwnd(tp), TCP_SCALABLE_AI_CNT), + acked); + } + +@@ -35,7 +35,7 @@ static u32 tcp_scalable_ssthresh(struct sock *sk) + { + const struct tcp_sock *tp = tcp_sk(sk); + +- return max(tp->snd_cwnd - (tp->snd_cwnd>>TCP_SCALABLE_MD_SCALE), 2U); ++ return max(tcp_snd_cwnd(tp) - (tcp_snd_cwnd(tp)>>TCP_SCALABLE_MD_SCALE), 2U); + } + + static struct tcp_congestion_ops tcp_scalable __read_mostly = { +diff --git a/net/ipv4/tcp_vegas.c b/net/ipv4/tcp_vegas.c +index c8003c8aad2c..786848ad37ea 100644 +--- a/net/ipv4/tcp_vegas.c ++++ b/net/ipv4/tcp_vegas.c +@@ -159,7 +159,7 @@ EXPORT_SYMBOL_GPL(tcp_vegas_cwnd_event); + + static inline u32 tcp_vegas_ssthresh(struct tcp_sock *tp) + { +- return min(tp->snd_ssthresh, tp->snd_cwnd); ++ return min(tp->snd_ssthresh, tcp_snd_cwnd(tp)); + } + + static void tcp_vegas_cong_avoid(struct sock *sk, u32 ack, u32 acked) +@@ -217,14 +217,14 @@ static void tcp_vegas_cong_avoid(struct sock *sk, u32 ack, u32 acked) + * This is: + * (actual rate in segments) * baseRTT + */ +- target_cwnd = (u64)tp->snd_cwnd * vegas->baseRTT; ++ target_cwnd = (u64)tcp_snd_cwnd(tp) * vegas->baseRTT; + do_div(target_cwnd, rtt); + + /* Calculate the difference between the window we had, + * and the window we would like to have. This quantity + * is the "Diff" from the Arizona Vegas papers. + */ +- diff = tp->snd_cwnd * (rtt-vegas->baseRTT) / vegas->baseRTT; ++ diff = tcp_snd_cwnd(tp) * (rtt-vegas->baseRTT) / vegas->baseRTT; + + if (diff > gamma && tcp_in_slow_start(tp)) { + /* Going too fast. Time to slow down +@@ -238,7 +238,8 @@ static void tcp_vegas_cong_avoid(struct sock *sk, u32 ack, u32 acked) + * truncation robs us of full link + * utilization. + */ +- tp->snd_cwnd = min(tp->snd_cwnd, (u32)target_cwnd+1); ++ tcp_snd_cwnd_set(tp, min(tcp_snd_cwnd(tp), ++ (u32)target_cwnd + 1)); + tp->snd_ssthresh = tcp_vegas_ssthresh(tp); + + } else if (tcp_in_slow_start(tp)) { +@@ -254,14 +255,14 @@ static void tcp_vegas_cong_avoid(struct sock *sk, u32 ack, u32 acked) + /* The old window was too fast, so + * we slow down. + */ +- tp->snd_cwnd--; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) - 1); + tp->snd_ssthresh + = tcp_vegas_ssthresh(tp); + } else if (diff < alpha) { + /* We don't have enough extra packets + * in the network, so speed up. + */ +- tp->snd_cwnd++; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + } else { + /* Sending just as fast as we + * should be. +@@ -269,10 +270,10 @@ static void tcp_vegas_cong_avoid(struct sock *sk, u32 ack, u32 acked) + } + } + +- if (tp->snd_cwnd < 2) +- tp->snd_cwnd = 2; +- else if (tp->snd_cwnd > tp->snd_cwnd_clamp) +- tp->snd_cwnd = tp->snd_cwnd_clamp; ++ if (tcp_snd_cwnd(tp) < 2) ++ tcp_snd_cwnd_set(tp, 2); ++ else if (tcp_snd_cwnd(tp) > tp->snd_cwnd_clamp) ++ tcp_snd_cwnd_set(tp, tp->snd_cwnd_clamp); + + tp->snd_ssthresh = tcp_current_ssthresh(sk); + } +diff --git a/net/ipv4/tcp_veno.c b/net/ipv4/tcp_veno.c +index cd50a61c9976..366ff6f214b2 100644 +--- a/net/ipv4/tcp_veno.c ++++ b/net/ipv4/tcp_veno.c +@@ -146,11 +146,11 @@ static void tcp_veno_cong_avoid(struct sock *sk, u32 ack, u32 acked) + + rtt = veno->minrtt; + +- target_cwnd = (u64)tp->snd_cwnd * veno->basertt; ++ target_cwnd = (u64)tcp_snd_cwnd(tp) * veno->basertt; + target_cwnd <<= V_PARAM_SHIFT; + do_div(target_cwnd, rtt); + +- veno->diff = (tp->snd_cwnd << V_PARAM_SHIFT) - target_cwnd; ++ veno->diff = (tcp_snd_cwnd(tp) << V_PARAM_SHIFT) - target_cwnd; + + if (tcp_in_slow_start(tp)) { + /* Slow start. */ +@@ -164,15 +164,15 @@ static void tcp_veno_cong_avoid(struct sock *sk, u32 ack, u32 acked) + /* In the "non-congestive state", increase cwnd + * every rtt. + */ +- tcp_cong_avoid_ai(tp, tp->snd_cwnd, acked); ++ tcp_cong_avoid_ai(tp, tcp_snd_cwnd(tp), acked); + } else { + /* In the "congestive state", increase cwnd + * every other rtt. + */ +- if (tp->snd_cwnd_cnt >= tp->snd_cwnd) { ++ if (tp->snd_cwnd_cnt >= tcp_snd_cwnd(tp)) { + if (veno->inc && +- tp->snd_cwnd < tp->snd_cwnd_clamp) { +- tp->snd_cwnd++; ++ tcp_snd_cwnd(tp) < tp->snd_cwnd_clamp) { ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) + 1); + veno->inc = 0; + } else + veno->inc = 1; +@@ -181,10 +181,10 @@ static void tcp_veno_cong_avoid(struct sock *sk, u32 ack, u32 acked) + tp->snd_cwnd_cnt += acked; + } + done: +- if (tp->snd_cwnd < 2) +- tp->snd_cwnd = 2; +- else if (tp->snd_cwnd > tp->snd_cwnd_clamp) +- tp->snd_cwnd = tp->snd_cwnd_clamp; ++ if (tcp_snd_cwnd(tp) < 2) ++ tcp_snd_cwnd_set(tp, 2); ++ else if (tcp_snd_cwnd(tp) > tp->snd_cwnd_clamp) ++ tcp_snd_cwnd_set(tp, tp->snd_cwnd_clamp); + } + /* Wipe the slate clean for the next rtt. */ + /* veno->cntrtt = 0; */ +@@ -199,10 +199,10 @@ static u32 tcp_veno_ssthresh(struct sock *sk) + + if (veno->diff < beta) + /* in "non-congestive state", cut cwnd by 1/5 */ +- return max(tp->snd_cwnd * 4 / 5, 2U); ++ return max(tcp_snd_cwnd(tp) * 4 / 5, 2U); + else + /* in "congestive state", cut cwnd by 1/2 */ +- return max(tp->snd_cwnd >> 1U, 2U); ++ return max(tcp_snd_cwnd(tp) >> 1U, 2U); + } + + static struct tcp_congestion_ops tcp_veno __read_mostly = { +diff --git a/net/ipv4/tcp_westwood.c b/net/ipv4/tcp_westwood.c +index b2e05c4cea00..c6e97141eef2 100644 +--- a/net/ipv4/tcp_westwood.c ++++ b/net/ipv4/tcp_westwood.c +@@ -244,7 +244,8 @@ static void tcp_westwood_event(struct sock *sk, enum tcp_ca_event event) + + switch (event) { + case CA_EVENT_COMPLETE_CWR: +- tp->snd_cwnd = tp->snd_ssthresh = tcp_westwood_bw_rttmin(sk); ++ tp->snd_ssthresh = tcp_westwood_bw_rttmin(sk); ++ tcp_snd_cwnd_set(tp, tp->snd_ssthresh); + break; + case CA_EVENT_LOSS: + tp->snd_ssthresh = tcp_westwood_bw_rttmin(sk); +diff --git a/net/ipv4/tcp_yeah.c b/net/ipv4/tcp_yeah.c +index 07c4c93b9fdb..18b07ff5d20e 100644 +--- a/net/ipv4/tcp_yeah.c ++++ b/net/ipv4/tcp_yeah.c +@@ -71,11 +71,11 @@ static void tcp_yeah_cong_avoid(struct sock *sk, u32 ack, u32 acked) + + if (!yeah->doing_reno_now) { + /* Scalable */ +- tcp_cong_avoid_ai(tp, min(tp->snd_cwnd, TCP_SCALABLE_AI_CNT), ++ tcp_cong_avoid_ai(tp, min(tcp_snd_cwnd(tp), TCP_SCALABLE_AI_CNT), + acked); + } else { + /* Reno */ +- tcp_cong_avoid_ai(tp, tp->snd_cwnd, acked); ++ tcp_cong_avoid_ai(tp, tcp_snd_cwnd(tp), acked); + } + + /* The key players are v_vegas.beg_snd_una and v_beg_snd_nxt. +@@ -130,7 +130,7 @@ static void tcp_yeah_cong_avoid(struct sock *sk, u32 ack, u32 acked) + /* Compute excess number of packets above bandwidth + * Avoid doing full 64 bit divide. + */ +- bw = tp->snd_cwnd; ++ bw = tcp_snd_cwnd(tp); + bw *= rtt - yeah->vegas.baseRTT; + do_div(bw, rtt); + queue = bw; +@@ -138,20 +138,20 @@ static void tcp_yeah_cong_avoid(struct sock *sk, u32 ack, u32 acked) + if (queue > TCP_YEAH_ALPHA || + rtt - yeah->vegas.baseRTT > (yeah->vegas.baseRTT / TCP_YEAH_PHY)) { + if (queue > TCP_YEAH_ALPHA && +- tp->snd_cwnd > yeah->reno_count) { ++ tcp_snd_cwnd(tp) > yeah->reno_count) { + u32 reduction = min(queue / TCP_YEAH_GAMMA , +- tp->snd_cwnd >> TCP_YEAH_EPSILON); ++ tcp_snd_cwnd(tp) >> TCP_YEAH_EPSILON); + +- tp->snd_cwnd -= reduction; ++ tcp_snd_cwnd_set(tp, tcp_snd_cwnd(tp) - reduction); + +- tp->snd_cwnd = max(tp->snd_cwnd, +- yeah->reno_count); ++ tcp_snd_cwnd_set(tp, max(tcp_snd_cwnd(tp), ++ yeah->reno_count)); + +- tp->snd_ssthresh = tp->snd_cwnd; ++ tp->snd_ssthresh = tcp_snd_cwnd(tp); + } + + if (yeah->reno_count <= 2) +- yeah->reno_count = max(tp->snd_cwnd>>1, 2U); ++ yeah->reno_count = max(tcp_snd_cwnd(tp)>>1, 2U); + else + yeah->reno_count++; + +@@ -176,7 +176,7 @@ static void tcp_yeah_cong_avoid(struct sock *sk, u32 ack, u32 acked) + */ + yeah->vegas.beg_snd_una = yeah->vegas.beg_snd_nxt; + yeah->vegas.beg_snd_nxt = tp->snd_nxt; +- yeah->vegas.beg_snd_cwnd = tp->snd_cwnd; ++ yeah->vegas.beg_snd_cwnd = tcp_snd_cwnd(tp); + + /* Wipe the slate clean for the next RTT. */ + yeah->vegas.cntRTT = 0; +@@ -193,16 +193,16 @@ static u32 tcp_yeah_ssthresh(struct sock *sk) + if (yeah->doing_reno_now < TCP_YEAH_RHO) { + reduction = yeah->lastQ; + +- reduction = min(reduction, max(tp->snd_cwnd>>1, 2U)); ++ reduction = min(reduction, max(tcp_snd_cwnd(tp)>>1, 2U)); + +- reduction = max(reduction, tp->snd_cwnd >> TCP_YEAH_DELTA); ++ reduction = max(reduction, tcp_snd_cwnd(tp) >> TCP_YEAH_DELTA); + } else +- reduction = max(tp->snd_cwnd>>1, 2U); ++ reduction = max(tcp_snd_cwnd(tp)>>1, 2U); + + yeah->fast_count = 0; + yeah->reno_count = max(yeah->reno_count>>1, 2U); + +- return max_t(int, tp->snd_cwnd - reduction, 2); ++ return max_t(int, tcp_snd_cwnd(tp) - reduction, 2); + } + + static struct tcp_congestion_ops tcp_yeah __read_mostly = { +diff --git a/net/ipv6/tcp_ipv6.c b/net/ipv6/tcp_ipv6.c +index 8eedf59e9cf2..beaa0c2ada23 100644 +--- a/net/ipv6/tcp_ipv6.c ++++ b/net/ipv6/tcp_ipv6.c +@@ -2075,7 +2075,7 @@ static void get_tcp6_sock(struct seq_file *seq, struct sock *sp, int i) + jiffies_to_clock_t(icsk->icsk_rto), + jiffies_to_clock_t(icsk->icsk_ack.ato), + (icsk->icsk_ack.quick << 1) | inet_csk_in_pingpong_mode(sp), +- tp->snd_cwnd, ++ tcp_snd_cwnd(tp), + state == TCP_LISTEN ? + fastopenq->max_qlen : + (tcp_in_initial_slowstart(tp) ? -1 : tp->snd_ssthresh) +-- +2.35.1 + diff --git a/queue-5.15/tcp-tcp_rtx_synack-can-be-called-from-process-contex.patch b/queue-5.15/tcp-tcp_rtx_synack-can-be-called-from-process-contex.patch new file mode 100644 index 00000000000..5705864a543 --- /dev/null +++ b/queue-5.15/tcp-tcp_rtx_synack-can-be-called-from-process-contex.patch @@ -0,0 +1,92 @@ +From 9067d66365e78a5ff70c9d9215169431424412ab Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 30 May 2022 14:37:13 -0700 +Subject: tcp: tcp_rtx_synack() can be called from process context + +From: Eric Dumazet + +[ Upstream commit 0a375c822497ed6ad6b5da0792a12a6f1af10c0b ] + +Laurent reported the enclosed report [1] + +This bug triggers with following coditions: + +0) Kernel built with CONFIG_DEBUG_PREEMPT=y + +1) A new passive FastOpen TCP socket is created. + This FO socket waits for an ACK coming from client to be a complete + ESTABLISHED one. +2) A socket operation on this socket goes through lock_sock() + release_sock() dance. +3) While the socket is owned by the user in step 2), + a retransmit of the SYN is received and stored in socket backlog. +4) At release_sock() time, the socket backlog is processed while + in process context. +5) A SYNACK packet is cooked in response of the SYN retransmit. +6) -> tcp_rtx_synack() is called in process context. + +Before blamed commit, tcp_rtx_synack() was always called from BH handler, +from a timer handler. + +Fix this by using TCP_INC_STATS() & NET_INC_STATS() +which do not assume caller is in non preemptible context. + +[1] +BUG: using __this_cpu_add() in preemptible [00000000] code: epollpep/2180 +caller is tcp_rtx_synack.part.0+0x36/0xc0 +CPU: 10 PID: 2180 Comm: epollpep Tainted: G OE 5.16.0-0.bpo.4-amd64 #1 Debian 5.16.12-1~bpo11+1 +Hardware name: Supermicro SYS-5039MC-H8TRF/X11SCD-F, BIOS 1.7 11/23/2021 +Call Trace: + + dump_stack_lvl+0x48/0x5e + check_preemption_disabled+0xde/0xe0 + tcp_rtx_synack.part.0+0x36/0xc0 + tcp_rtx_synack+0x8d/0xa0 + ? kmem_cache_alloc+0x2e0/0x3e0 + ? apparmor_file_alloc_security+0x3b/0x1f0 + inet_rtx_syn_ack+0x16/0x30 + tcp_check_req+0x367/0x610 + tcp_rcv_state_process+0x91/0xf60 + ? get_nohz_timer_target+0x18/0x1a0 + ? lock_timer_base+0x61/0x80 + ? preempt_count_add+0x68/0xa0 + tcp_v4_do_rcv+0xbd/0x270 + __release_sock+0x6d/0xb0 + release_sock+0x2b/0x90 + sock_setsockopt+0x138/0x1140 + ? __sys_getsockname+0x7e/0xc0 + ? aa_sk_perm+0x3e/0x1a0 + __sys_setsockopt+0x198/0x1e0 + __x64_sys_setsockopt+0x21/0x30 + do_syscall_64+0x38/0xc0 + entry_SYSCALL_64_after_hwframe+0x44/0xae + +Fixes: 168a8f58059a ("tcp: TCP Fast Open Server - main code path") +Signed-off-by: Eric Dumazet +Reported-by: Laurent Fasnacht +Acked-by: Neal Cardwell +Link: https://lore.kernel.org/r/20220530213713.601888-1-eric.dumazet@gmail.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Sasha Levin +--- + net/ipv4/tcp_output.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c +index ed7125a47ce0..dc3b4668fcde 100644 +--- a/net/ipv4/tcp_output.c ++++ b/net/ipv4/tcp_output.c +@@ -4116,8 +4116,8 @@ int tcp_rtx_synack(const struct sock *sk, struct request_sock *req) + res = af_ops->send_synack(sk, NULL, &fl, req, NULL, TCP_SYNACK_NORMAL, + NULL); + if (!res) { +- __TCP_INC_STATS(sock_net(sk), TCP_MIB_RETRANSSEGS); +- __NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPSYNRETRANS); ++ TCP_INC_STATS(sock_net(sk), TCP_MIB_RETRANSSEGS); ++ NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPSYNRETRANS); + if (unlikely(tcp_passive_fastopen(sk))) + tcp_sk(sk)->total_retrans++; + trace_tcp_retransmit_synack(sk, req); +-- +2.35.1 + diff --git a/queue-5.15/tipc-check-attribute-length-for-bearer-name.patch b/queue-5.15/tipc-check-attribute-length-for-bearer-name.patch new file mode 100644 index 00000000000..4e831bdcc80 --- /dev/null +++ b/queue-5.15/tipc-check-attribute-length-for-bearer-name.patch @@ -0,0 +1,58 @@ +From bfd64e77a0c1516b93cce7894a3405f38879293f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 2 Jun 2022 13:30:53 +0700 +Subject: tipc: check attribute length for bearer name + +From: Hoang Le + +[ Upstream commit 7f36f798f89bf32c0164049cb0e3fd1af613d0bb ] + +syzbot reported uninit-value: +===================================================== +BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:644 [inline] +BUG: KMSAN: uninit-value in string+0x4f9/0x6f0 lib/vsprintf.c:725 + string_nocheck lib/vsprintf.c:644 [inline] + string+0x4f9/0x6f0 lib/vsprintf.c:725 + vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806 + vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158 + vprintk_emit+0x28b/0xab0 kernel/printk/printk.c:2256 + vprintk_default+0x86/0xa0 kernel/printk/printk.c:2283 + vprintk+0x15f/0x180 kernel/printk/printk_safe.c:50 + _printk+0x18d/0x1cf kernel/printk/printk.c:2293 + tipc_enable_bearer net/tipc/bearer.c:371 [inline] + __tipc_nl_bearer_enable+0x2022/0x22a0 net/tipc/bearer.c:1033 + tipc_nl_bearer_enable+0x6c/0xb0 net/tipc/bearer.c:1042 + genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline] + +- Do sanity check the attribute length for TIPC_NLA_BEARER_NAME. +- Do not use 'illegal name' in printing message. + +Reported-by: syzbot+e820fdc8ce362f2dea51@syzkaller.appspotmail.com +Fixes: cb30a63384bc ("tipc: refactor function tipc_enable_bearer()") +Acked-by: Jon Maloy +Signed-off-by: Hoang Le +Link: https://lore.kernel.org/r/20220602063053.5892-1-hoang.h.le@dektech.com.au +Signed-off-by: Jakub Kicinski +Signed-off-by: Sasha Levin +--- + net/tipc/bearer.c | 3 +-- + 1 file changed, 1 insertion(+), 2 deletions(-) + +diff --git a/net/tipc/bearer.c b/net/tipc/bearer.c +index 36b466cfd9e1..b0ad61b4b101 100644 +--- a/net/tipc/bearer.c ++++ b/net/tipc/bearer.c +@@ -259,9 +259,8 @@ static int tipc_enable_bearer(struct net *net, const char *name, + u32 i; + + if (!bearer_name_validate(name, &b_names)) { +- errstr = "illegal name"; + NL_SET_ERR_MSG(extack, "Illegal name"); +- goto rejected; ++ return res; + } + + if (prio > TIPC_MAX_LINK_PRI && prio != TIPC_MEDIA_LINK_PRI) { +-- +2.35.1 + diff --git a/queue-5.15/tty-goldfish-use-tty_port_destroy-to-destroy-port.patch b/queue-5.15/tty-goldfish-use-tty_port_destroy-to-destroy-port.patch new file mode 100644 index 00000000000..8d5e29e7d40 --- /dev/null +++ b/queue-5.15/tty-goldfish-use-tty_port_destroy-to-destroy-port.patch @@ -0,0 +1,48 @@ +From 5440f337b921d9e807a557d28ce70857ff59e0f5 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 28 Mar 2022 19:58:44 +0800 +Subject: tty: goldfish: Use tty_port_destroy() to destroy port + +From: Wang Weiyang + +[ Upstream commit 507b05063d1b7a1fcb9f7d7c47586fc4f3508f98 ] + +In goldfish_tty_probe(), the port initialized through tty_port_init() +should be destroyed in error paths.In goldfish_tty_remove(), qtty->port +also should be destroyed or else might leak resources. + +Fix the above by calling tty_port_destroy(). + +Fixes: 666b7793d4bf ("goldfish: tty driver") +Reviewed-by: Jiri Slaby +Signed-off-by: Wang Weiyang +Link: https://lore.kernel.org/r/20220328115844.86032-1-wangweiyang2@huawei.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/goldfish.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/tty/goldfish.c b/drivers/tty/goldfish.c +index 876ff5445c52..0dc9a6a36ce0 100644 +--- a/drivers/tty/goldfish.c ++++ b/drivers/tty/goldfish.c +@@ -407,6 +407,7 @@ static int goldfish_tty_probe(struct platform_device *pdev) + err_tty_register_device_failed: + free_irq(irq, qtty); + err_dec_line_count: ++ tty_port_destroy(&qtty->port); + goldfish_tty_current_line_count--; + if (goldfish_tty_current_line_count == 0) + goldfish_tty_delete_driver(); +@@ -428,6 +429,7 @@ static int goldfish_tty_remove(struct platform_device *pdev) + iounmap(qtty->base); + qtty->base = NULL; + free_irq(qtty->irq, pdev); ++ tty_port_destroy(&qtty->port); + goldfish_tty_current_line_count--; + if (goldfish_tty_current_line_count == 0) + goldfish_tty_delete_driver(); +-- +2.35.1 + diff --git a/queue-5.15/tty-n_gsm-don-t-ignore-write-return-value-in-gsmld_o.patch b/queue-5.15/tty-n_gsm-don-t-ignore-write-return-value-in-gsmld_o.patch new file mode 100644 index 00000000000..656e209b3b9 --- /dev/null +++ b/queue-5.15/tty-n_gsm-don-t-ignore-write-return-value-in-gsmld_o.patch @@ -0,0 +1,47 @@ +From 4536ca648192ce2fb1ea3f590f4b1ba6f6be36b9 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 30 Sep 2021 09:06:24 +0300 +Subject: tty: n_gsm: Don't ignore write return value in gsmld_output() + +From: Tony Lindgren + +[ Upstream commit 9136c68346d096697935b9840782f7051d5796c5 ] + +We currently have gsmld_output() ignore the return value from device +write. This means we will lose packets if device write returns 0 or +an error. + +Signed-off-by: Tony Lindgren +Link: https://lore.kernel.org/r/20210930060624.46523-1-tony@atomide.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/n_gsm.c | 5 ++--- + 1 file changed, 2 insertions(+), 3 deletions(-) + +diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c +index 1767503de744..0722860b6f54 100644 +--- a/drivers/tty/n_gsm.c ++++ b/drivers/tty/n_gsm.c +@@ -692,7 +692,7 @@ static void gsm_data_kick(struct gsm_mux *gsm, struct gsm_dlci *dlci) + print_hex_dump_bytes("gsm_data_kick: ", + DUMP_PREFIX_OFFSET, + gsm->txframe, len); +- if (gsmld_output(gsm, gsm->txframe, len) < 0) ++ if (gsmld_output(gsm, gsm->txframe, len) <= 0) + break; + /* FIXME: Can eliminate one SOF in many more cases */ + gsm->tx_bytes -= msg->len; +@@ -2373,8 +2373,7 @@ static int gsmld_output(struct gsm_mux *gsm, u8 *data, int len) + if (debug & 4) + print_hex_dump_bytes("gsmld_output: ", DUMP_PREFIX_OFFSET, + data, len); +- gsm->tty->ops->write(gsm->tty, data, len); +- return len; ++ return gsm->tty->ops->write(gsm->tty, data, len); + } + + /** +-- +2.35.1 + diff --git a/queue-5.15/tty-n_gsm-fix-packet-data-hex-dump-output.patch b/queue-5.15/tty-n_gsm-fix-packet-data-hex-dump-output.patch new file mode 100644 index 00000000000..add4d468913 --- /dev/null +++ b/queue-5.15/tty-n_gsm-fix-packet-data-hex-dump-output.patch @@ -0,0 +1,102 @@ +From da9f8c61cf9c8105ded2b5ec50901c4a5c2ab3ac Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 12 May 2022 16:15:06 +0300 +Subject: tty: n_gsm: Fix packet data hex dump output + +From: Tony Lindgren + +[ Upstream commit 925ea0fa5277c1e6bb9e51955ef34eea9736c3d7 ] + +The module param debug for n_gsm uses KERN_INFO level, but the hexdump +now uses KERN_DEBUG level. This started after commit 091cb0994edd +("lib/hexdump: make print_hex_dump_bytes() a nop on !DEBUG builds"). +We now use dynamic_hex_dump() unless DEBUG is set. + +This causes no packets to be seen with modprobe n_gsm debug=0x1f unlike +earlier. Let's fix this by adding gsm_hex_dump_bytes() that calls +print_hex_dump() with KERN_INFO to match what n_gsm is doing with the +other debug related output. + +Fixes: 091cb0994edd ("lib/hexdump: make print_hex_dump_bytes() a nop on !DEBUG builds") +Cc: Stephen Boyd +Signed-off-by: Tony Lindgren +Link: https://lore.kernel.org/r/20220512131506.1216-1-tony@atomide.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/n_gsm.c | 31 +++++++++++++++++++++++-------- + 1 file changed, 23 insertions(+), 8 deletions(-) + +diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c +index 0722860b6f54..a246f429ffb7 100644 +--- a/drivers/tty/n_gsm.c ++++ b/drivers/tty/n_gsm.c +@@ -443,6 +443,25 @@ static u8 gsm_encode_modem(const struct gsm_dlci *dlci) + return modembits; + } + ++static void gsm_hex_dump_bytes(const char *fname, const u8 *data, ++ unsigned long len) ++{ ++ char *prefix; ++ ++ if (!fname) { ++ print_hex_dump(KERN_INFO, "", DUMP_PREFIX_NONE, 16, 1, data, len, ++ true); ++ return; ++ } ++ ++ prefix = kasprintf(GFP_KERNEL, "%s: ", fname); ++ if (!prefix) ++ return; ++ print_hex_dump(KERN_INFO, prefix, DUMP_PREFIX_OFFSET, 16, 1, data, len, ++ true); ++ kfree(prefix); ++} ++ + /** + * gsm_print_packet - display a frame for debug + * @hdr: header to print before decode +@@ -507,7 +526,7 @@ static void gsm_print_packet(const char *hdr, int addr, int cr, + else + pr_cont("(F)"); + +- print_hex_dump_bytes("", DUMP_PREFIX_NONE, data, dlen); ++ gsm_hex_dump_bytes(NULL, data, dlen); + } + + +@@ -689,9 +708,7 @@ static void gsm_data_kick(struct gsm_mux *gsm, struct gsm_dlci *dlci) + } + + if (debug & 4) +- print_hex_dump_bytes("gsm_data_kick: ", +- DUMP_PREFIX_OFFSET, +- gsm->txframe, len); ++ gsm_hex_dump_bytes(__func__, gsm->txframe, len); + if (gsmld_output(gsm, gsm->txframe, len) <= 0) + break; + /* FIXME: Can eliminate one SOF in many more cases */ +@@ -2371,8 +2388,7 @@ static int gsmld_output(struct gsm_mux *gsm, u8 *data, int len) + return -ENOSPC; + } + if (debug & 4) +- print_hex_dump_bytes("gsmld_output: ", DUMP_PREFIX_OFFSET, +- data, len); ++ gsm_hex_dump_bytes(__func__, data, len); + return gsm->tty->ops->write(gsm->tty, data, len); + } + +@@ -2448,8 +2464,7 @@ static void gsmld_receive_buf(struct tty_struct *tty, const unsigned char *cp, + char flags = TTY_NORMAL; + + if (debug & 4) +- print_hex_dump_bytes("gsmld_receive: ", DUMP_PREFIX_OFFSET, +- cp, count); ++ gsm_hex_dump_bytes(__func__, cp, count); + + for (; count; count--, cp++) { + if (fp) +-- +2.35.1 + diff --git a/queue-5.15/tty-n_tty-restore-eof-push-handling-behavior.patch b/queue-5.15/tty-n_tty-restore-eof-push-handling-behavior.patch new file mode 100644 index 00000000000..c1adba47670 --- /dev/null +++ b/queue-5.15/tty-n_tty-restore-eof-push-handling-behavior.patch @@ -0,0 +1,123 @@ +From fc90286649a0eb05417635cf37b582b3c7e79f55 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 30 Mar 2022 01:58:10 +0200 +Subject: tty: n_tty: Restore EOF push handling behavior + +From: Daniel Gibson + +[ Upstream commit 65a8b287023da68c4550deab5c764e6891cf1caf ] + +TTYs in ICANON mode have a special case that allows "pushing" a line +without a regular EOL character (like newline), by using EOF (the EOT +character - ASCII 0x4) as a pseudo-EOL. It is silently discarded, so +the reader of the PTS will receive the line *without* EOF or any other +terminating character. + +This special case has an edge case: What happens if the readers buffer +is the same size as the line (without EOF)? Will they be able to tell +if the whole line is received, i.e. if the next read() will return more +of the same line or the next line? + +There are two possibilities, that both have (dis)advantages: + +1. The next read() returns 0. FreeBSD (13.0) and OSX (10.11) do this. + Advantage: The reader can interpret this as "the line is over". + Disadvantage: read() returning 0 means EOF, the reader could also + interpret it as "there's no more data" and stop reading or even + close the PT. + +2. The next read() returns the next line, the EOF is silently discarded. + Solaris (or at least OpenIndiana 2021.10) does this, Linux has done + do this since commit 40d5e0905a03 ("n_tty: Fix EOF push handling"); + this behavior was recently broken by commit 359303076163 ("tty: + n_tty: do not look ahead for EOL character past the end of the buffer"). + Advantage: read() won't return 0 (EOF), reader less likely to be + confused (and things like `while(read(..)>0)` don't break) + Disadvantage: The reader can't really know if the read() continues + the last line (that filled the whole read buffer) or starts a + new line. + +As both options are defensible (and are used by other Unix-likes), it's +best to stick to the "old" behavior since "n_tty: Fix EOF push handling" +of 2013, i.e. silently discard that EOF. + +This patch - that I actually got from Linus for testing and only +modified slightly - restores that behavior by skipping an EOF +character if it's the next character after reading is done. + +Based on a patch from Linus Torvalds. + +Link: https://bugzilla.kernel.org/show_bug.cgi?id=215611 +Fixes: 359303076163 ("tty: n_tty: do not look ahead for EOL character past the end of the buffer") +Cc: Peter Hurley +Cc: Greg Kroah-Hartman +Cc: Jiri Slaby +Reviewed-and-tested-by: Daniel Gibson +Acked-by: Linus Torvalds +Signed-off-by: Daniel Gibson +Link: https://lore.kernel.org/r/20220329235810.452513-2-daniel@gibson.sh +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/n_tty.c | 38 +++++++++++++++++++++++++++++++++++++- + 1 file changed, 37 insertions(+), 1 deletion(-) + +diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c +index de5b45de5040..891036bd9f89 100644 +--- a/drivers/tty/n_tty.c ++++ b/drivers/tty/n_tty.c +@@ -2012,6 +2012,35 @@ static bool canon_copy_from_read_buf(struct tty_struct *tty, + return ldata->read_tail != canon_head; + } + ++/* ++ * If we finished a read at the exact location of an ++ * EOF (special EOL character that's a __DISABLED_CHAR) ++ * in the stream, silently eat the EOF. ++ */ ++static void canon_skip_eof(struct tty_struct *tty) ++{ ++ struct n_tty_data *ldata = tty->disc_data; ++ size_t tail, canon_head; ++ ++ canon_head = smp_load_acquire(&ldata->canon_head); ++ tail = ldata->read_tail; ++ ++ // No data? ++ if (tail == canon_head) ++ return; ++ ++ // See if the tail position is EOF in the circular buffer ++ tail &= (N_TTY_BUF_SIZE - 1); ++ if (!test_bit(tail, ldata->read_flags)) ++ return; ++ if (read_buf(ldata, tail) != __DISABLED_CHAR) ++ return; ++ ++ // Clear the EOL bit, skip the EOF char. ++ clear_bit(tail, ldata->read_flags); ++ smp_store_release(&ldata->read_tail, ldata->read_tail + 1); ++} ++ + /** + * job_control - check job control + * @tty: tty +@@ -2081,7 +2110,14 @@ static ssize_t n_tty_read(struct tty_struct *tty, struct file *file, + */ + if (*cookie) { + if (ldata->icanon && !L_EXTPROC(tty)) { +- if (canon_copy_from_read_buf(tty, &kb, &nr)) ++ /* ++ * If we have filled the user buffer, see ++ * if we should skip an EOF character before ++ * releasing the lock and returning done. ++ */ ++ if (!nr) ++ canon_skip_eof(tty); ++ else if (canon_copy_from_read_buf(tty, &kb, &nr)) + return kb - kbuf; + } else { + if (copy_from_read_buf(tty, &kb, &nr)) +-- +2.35.1 + diff --git a/queue-5.15/tty-serial-fsl_lpuart-fix-potential-bug-when-using-b.patch b/queue-5.15/tty-serial-fsl_lpuart-fix-potential-bug-when-using-b.patch new file mode 100644 index 00000000000..11b3703064c --- /dev/null +++ b/queue-5.15/tty-serial-fsl_lpuart-fix-potential-bug-when-using-b.patch @@ -0,0 +1,118 @@ +From f1e33f21406a26c0dad77ade085d184e1eaa8622 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 21 Mar 2022 19:22:11 +0800 +Subject: tty: serial: fsl_lpuart: fix potential bug when using both + of_alias_get_id and ida_simple_get + +From: Sherry Sun + +[ Upstream commit f398e0aa325c61fa20903833a5b534ecb8e6e418 ] + +Now fsl_lpuart driver use both of_alias_get_id() and ida_simple_get() in +.probe(), which has the potential bug. For example, when remove the +lpuart7 alias in dts, of_alias_get_id() will return error, then call +ida_simple_get() to allocate the id 0 for lpuart7, this may confilct +with the lpuart4 which has alias 0. + + aliases { + ... + serial0 = &lpuart4; + serial1 = &lpuart5; + serial2 = &lpuart6; + serial3 = &lpuart7; + } + +So remove the ida_simple_get() in .probe(), return an error directly +when calling of_alias_get_id() fails, which is consistent with other +uart drivers behavior. + +Fixes: 3bc3206e1c0f ("serial: fsl_lpuart: Remove the alias node dependence") +Signed-off-by: Sherry Sun +Link: https://lore.kernel.org/r/20220321112211.8895-1-sherry.sun@nxp.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/fsl_lpuart.c | 24 ++++-------------------- + 1 file changed, 4 insertions(+), 20 deletions(-) + +diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c +index 33e5eba6ff04..481107fdd69b 100644 +--- a/drivers/tty/serial/fsl_lpuart.c ++++ b/drivers/tty/serial/fsl_lpuart.c +@@ -239,8 +239,6 @@ + /* IMX lpuart has four extra unused regs located at the beginning */ + #define IMX_REG_OFF 0x10 + +-static DEFINE_IDA(fsl_lpuart_ida); +- + enum lpuart_type { + VF610_LPUART, + LS1021A_LPUART, +@@ -275,7 +273,6 @@ struct lpuart_port { + int rx_dma_rng_buf_len; + unsigned int dma_tx_nents; + wait_queue_head_t dma_wait; +- bool id_allocated; + }; + + struct lpuart_soc_data { +@@ -2703,23 +2700,18 @@ static int lpuart_probe(struct platform_device *pdev) + + ret = of_alias_get_id(np, "serial"); + if (ret < 0) { +- ret = ida_simple_get(&fsl_lpuart_ida, 0, UART_NR, GFP_KERNEL); +- if (ret < 0) { +- dev_err(&pdev->dev, "port line is full, add device failed\n"); +- return ret; +- } +- sport->id_allocated = true; ++ dev_err(&pdev->dev, "failed to get alias id, errno %d\n", ret); ++ return ret; + } + if (ret >= ARRAY_SIZE(lpuart_ports)) { + dev_err(&pdev->dev, "serial%d out of range\n", ret); +- ret = -EINVAL; +- goto failed_out_of_range; ++ return -EINVAL; + } + sport->port.line = ret; + + ret = lpuart_enable_clks(sport); + if (ret) +- goto failed_clock_enable; ++ return ret; + sport->port.uartclk = lpuart_get_baud_clk_rate(sport); + + lpuart_ports[sport->port.line] = sport; +@@ -2767,10 +2759,6 @@ static int lpuart_probe(struct platform_device *pdev) + uart_remove_one_port(&lpuart_reg, &sport->port); + failed_attach_port: + lpuart_disable_clks(sport); +-failed_clock_enable: +-failed_out_of_range: +- if (sport->id_allocated) +- ida_simple_remove(&fsl_lpuart_ida, sport->port.line); + return ret; + } + +@@ -2780,9 +2768,6 @@ static int lpuart_remove(struct platform_device *pdev) + + uart_remove_one_port(&lpuart_reg, &sport->port); + +- if (sport->id_allocated) +- ida_simple_remove(&fsl_lpuart_ida, sport->port.line); +- + lpuart_disable_clks(sport); + + if (sport->dma_tx_chan) +@@ -2912,7 +2897,6 @@ static int __init lpuart_serial_init(void) + + static void __exit lpuart_serial_exit(void) + { +- ida_destroy(&fsl_lpuart_ida); + platform_driver_unregister(&lpuart_driver); + uart_unregister_driver(&lpuart_reg); + } +-- +2.35.1 + diff --git a/queue-5.15/tty-serial-owl-fix-missing-clk_disable_unprepare-in-.patch b/queue-5.15/tty-serial-owl-fix-missing-clk_disable_unprepare-in-.patch new file mode 100644 index 00000000000..4e59bc66037 --- /dev/null +++ b/queue-5.15/tty-serial-owl-fix-missing-clk_disable_unprepare-in-.patch @@ -0,0 +1,37 @@ +From f917b2814b2b373cbee7ca2db7f6956524dadca0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 7 Mar 2022 10:51:35 +0000 +Subject: tty: serial: owl: Fix missing clk_disable_unprepare() in + owl_uart_probe + +From: Miaoqian Lin + +[ Upstream commit bcea0f547ec1a2ee44d429aaf0334633e386e67c ] + +Fix the missing clk_disable_unprepare() before return +from owl_uart_probe() in the error handling case. + +Fixes: abf42d2f333b ("tty: serial: owl: add "much needed" clk_prepare_enable()") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220307105135.11698-1-linmq006@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/tty/serial/owl-uart.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/tty/serial/owl-uart.c b/drivers/tty/serial/owl-uart.c +index 91f1eb0058d7..9a6611cfc18e 100644 +--- a/drivers/tty/serial/owl-uart.c ++++ b/drivers/tty/serial/owl-uart.c +@@ -731,6 +731,7 @@ static int owl_uart_probe(struct platform_device *pdev) + owl_port->port.uartclk = clk_get_rate(owl_port->clk); + if (owl_port->port.uartclk == 0) { + dev_err(&pdev->dev, "clock rate is zero\n"); ++ clk_disable_unprepare(owl_port->clk); + return -EINVAL; + } + owl_port->port.flags = UPF_BOOT_AUTOCONF | UPF_IOREMAP | UPF_LOW_LATENCY; +-- +2.35.1 + diff --git a/queue-5.15/ubi-fastmap-fix-high-cpu-usage-of-ubi_bgt-by-making-.patch b/queue-5.15/ubi-fastmap-fix-high-cpu-usage-of-ubi_bgt-by-making-.patch new file mode 100644 index 00000000000..e4eb2d6d12a --- /dev/null +++ b/queue-5.15/ubi-fastmap-fix-high-cpu-usage-of-ubi_bgt-by-making-.patch @@ -0,0 +1,300 @@ +From 5d978eeae0f5b789bf17d429bf456bdd0272859e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 10 May 2022 20:31:24 +0800 +Subject: ubi: fastmap: Fix high cpu usage of ubi_bgt by making sure wl_pool + not empty + +From: Zhihao Cheng + +[ Upstream commit d09e9a2bddba6c48e0fddb16c4383172ac593251 ] + +There at least 6 PEBs reserved on UBI device: +1. EBA_RESERVED_PEBS[1] +2. WL_RESERVED_PEBS[1] +3. UBI_LAYOUT_VOLUME_EBS[2] +4. MIN_FASTMAP_RESERVED_PEBS[2] + +When all ubi volumes take all their PEBs, there are 3 (EBA_RESERVED_PEBS + +WL_RESERVED_PEBS + MIN_FASTMAP_RESERVED_PEBS - MIN_FASTMAP_TAKEN_PEBS[1]) +free PEBs. Since commit f9c34bb529975fe ("ubi: Fix producing anchor PEBs") +and commit 4b68bf9a69d22dd ("ubi: Select fastmap anchor PEBs considering +wear level rules") applied, there is only 1 (3 - FASTMAP_ANCHOR_PEBS[1] - +FASTMAP_NEXT_ANCHOR_PEBS[1]) free PEB to fill pool and wl_pool, after +filling pool, wl_pool is always empty. So, UBI could be stuck in an +infinite loop: + + ubi_thread system_wq +wear_leveling_worker <-------------------------------------------------- + get_peb_for_wl | + // fm_wl_pool, used = size = 0 | + schedule_work(&ubi->fm_work) | + | + update_fastmap_work_fn | + ubi_update_fastmap | + ubi_refill_pools | + // ubi->free_count - ubi->beb_rsvd_pebs < 5 | + // wl_pool is not filled with any PEBs | + schedule_erase(old_fm_anchor) | + ubi_ensure_anchor_pebs | + __schedule_ubi_work(wear_leveling_worker) | + | +__erase_worker | + ensure_wear_leveling | + __schedule_ubi_work(wear_leveling_worker) -------------------------- + +, which cause high cpu usage of ubi_bgt: +top - 12:10:42 up 5 min, 2 users, load average: 1.76, 0.68, 0.27 +Tasks: 123 total, 3 running, 54 sleeping, 0 stopped, 0 zombie + + PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND + 1589 root 20 0 0 0 0 R 45.0 0.0 0:38.86 ubi_bgt0d + 319 root 20 0 0 0 0 I 15.2 0.0 0:15.29 kworker/0:3-eve + 371 root 20 0 0 0 0 I 14.9 0.0 0:12.85 kworker/3:3-eve + 20 root 20 0 0 0 0 I 11.3 0.0 0:05.33 kworker/1:0-eve + 202 root 20 0 0 0 0 I 11.3 0.0 0:04.93 kworker/2:3-eve + +In commit 4b68bf9a69d22dd ("ubi: Select fastmap anchor PEBs considering +wear level rules"), there are three key changes: + 1) Choose the fastmap anchor when the most free PEBs are available. + 2) Enable anchor move within the anchor area again as it is useful + for distributing wear. + 3) Import a candidate fm anchor and check this PEB's erase count during + wear leveling. If the wear leveling limit is exceeded, use the used + anchor area PEB with the lowest erase count to replace it. + +The anchor candidate can be removed, we can check fm_anchor PEB's erase +count during wear leveling. Fix it by: + 1) Removing 'fm_next_anchor' and check 'fm_anchor' during wear leveling. + 2) Preferentially filling one free peb into fm_wl_pool in condition of + ubi->free_count > ubi->beb_rsvd_pebs, then try to reserve enough + free count for fastmap non anchor pebs after the above prerequisites + are met. +Then, there are at least 1 PEB in pool and 1 PEB in wl_pool after calling +ubi_refill_pools() with all erase works done. + +Fetch a reproducer in [Link]. + +Fixes: 4b68bf9a69d22dd ("ubi: Select fastmap anchor PEBs ... rules") +Link: https://bugzilla.kernel.org/show_bug.cgi?id=215407 +Signed-off-by: Zhihao Cheng +Signed-off-by: Richard Weinberger +Signed-off-by: Sasha Levin +--- + drivers/mtd/ubi/fastmap-wl.c | 69 ++++++++++++++++++++++++------------ + drivers/mtd/ubi/fastmap.c | 11 ------ + drivers/mtd/ubi/ubi.h | 4 +-- + drivers/mtd/ubi/wl.c | 19 +++++----- + 4 files changed, 57 insertions(+), 46 deletions(-) + +diff --git a/drivers/mtd/ubi/fastmap-wl.c b/drivers/mtd/ubi/fastmap-wl.c +index 28f55f9cf715..053ab52668e8 100644 +--- a/drivers/mtd/ubi/fastmap-wl.c ++++ b/drivers/mtd/ubi/fastmap-wl.c +@@ -97,6 +97,33 @@ struct ubi_wl_entry *ubi_wl_get_fm_peb(struct ubi_device *ubi, int anchor) + return e; + } + ++/* ++ * has_enough_free_count - whether ubi has enough free pebs to fill fm pools ++ * @ubi: UBI device description object ++ * @is_wl_pool: whether UBI is filling wear leveling pool ++ * ++ * This helper function checks whether there are enough free pebs (deducted ++ * by fastmap pebs) to fill fm_pool and fm_wl_pool, above rule works after ++ * there is at least one of free pebs is filled into fm_wl_pool. ++ * For wear leveling pool, UBI should also reserve free pebs for bad pebs ++ * handling, because there maybe no enough free pebs for user volumes after ++ * producing new bad pebs. ++ */ ++static bool has_enough_free_count(struct ubi_device *ubi, bool is_wl_pool) ++{ ++ int fm_used = 0; // fastmap non anchor pebs. ++ int beb_rsvd_pebs; ++ ++ if (!ubi->free.rb_node) ++ return false; ++ ++ beb_rsvd_pebs = is_wl_pool ? ubi->beb_rsvd_pebs : 0; ++ if (ubi->fm_wl_pool.size > 0 && !(ubi->ro_mode || ubi->fm_disabled)) ++ fm_used = ubi->fm_size / ubi->leb_size - 1; ++ ++ return ubi->free_count - beb_rsvd_pebs > fm_used; ++} ++ + /** + * ubi_refill_pools - refills all fastmap PEB pools. + * @ubi: UBI device description object +@@ -120,21 +147,17 @@ void ubi_refill_pools(struct ubi_device *ubi) + wl_tree_add(ubi->fm_anchor, &ubi->free); + ubi->free_count++; + } +- if (ubi->fm_next_anchor) { +- wl_tree_add(ubi->fm_next_anchor, &ubi->free); +- ubi->free_count++; +- } + +- /* All available PEBs are in ubi->free, now is the time to get ++ /* ++ * All available PEBs are in ubi->free, now is the time to get + * the best anchor PEBs. + */ + ubi->fm_anchor = ubi_wl_get_fm_peb(ubi, 1); +- ubi->fm_next_anchor = ubi_wl_get_fm_peb(ubi, 1); + + for (;;) { + enough = 0; + if (pool->size < pool->max_size) { +- if (!ubi->free.rb_node) ++ if (!has_enough_free_count(ubi, false)) + break; + + e = wl_get_wle(ubi); +@@ -147,8 +170,7 @@ void ubi_refill_pools(struct ubi_device *ubi) + enough++; + + if (wl_pool->size < wl_pool->max_size) { +- if (!ubi->free.rb_node || +- (ubi->free_count - ubi->beb_rsvd_pebs < 5)) ++ if (!has_enough_free_count(ubi, true)) + break; + + e = find_wl_entry(ubi, &ubi->free, WL_FREE_MAX_DIFF); +@@ -286,20 +308,26 @@ static struct ubi_wl_entry *get_peb_for_wl(struct ubi_device *ubi) + int ubi_ensure_anchor_pebs(struct ubi_device *ubi) + { + struct ubi_work *wrk; ++ struct ubi_wl_entry *anchor; + + spin_lock(&ubi->wl_lock); + +- /* Do we have a next anchor? */ +- if (!ubi->fm_next_anchor) { +- ubi->fm_next_anchor = ubi_wl_get_fm_peb(ubi, 1); +- if (!ubi->fm_next_anchor) +- /* Tell wear leveling to produce a new anchor PEB */ +- ubi->fm_do_produce_anchor = 1; ++ /* Do we already have an anchor? */ ++ if (ubi->fm_anchor) { ++ spin_unlock(&ubi->wl_lock); ++ return 0; + } + +- /* Do wear leveling to get a new anchor PEB or check the +- * existing next anchor candidate. +- */ ++ /* See if we can find an anchor PEB on the list of free PEBs */ ++ anchor = ubi_wl_get_fm_peb(ubi, 1); ++ if (anchor) { ++ ubi->fm_anchor = anchor; ++ spin_unlock(&ubi->wl_lock); ++ return 0; ++ } ++ ++ ubi->fm_do_produce_anchor = 1; ++ /* No luck, trigger wear leveling to produce a new anchor PEB. */ + if (ubi->wl_scheduled) { + spin_unlock(&ubi->wl_lock); + return 0; +@@ -381,11 +409,6 @@ static void ubi_fastmap_close(struct ubi_device *ubi) + ubi->fm_anchor = NULL; + } + +- if (ubi->fm_next_anchor) { +- return_unused_peb(ubi, ubi->fm_next_anchor); +- ubi->fm_next_anchor = NULL; +- } +- + if (ubi->fm) { + for (i = 0; i < ubi->fm->used_blocks; i++) + kfree(ubi->fm->e[i]); +diff --git a/drivers/mtd/ubi/fastmap.c b/drivers/mtd/ubi/fastmap.c +index 6b5f1ffd961b..6e95c4b1473e 100644 +--- a/drivers/mtd/ubi/fastmap.c ++++ b/drivers/mtd/ubi/fastmap.c +@@ -1230,17 +1230,6 @@ static int ubi_write_fastmap(struct ubi_device *ubi, + fm_pos += sizeof(*fec); + ubi_assert(fm_pos <= ubi->fm_size); + } +- if (ubi->fm_next_anchor) { +- fec = (struct ubi_fm_ec *)(fm_raw + fm_pos); +- +- fec->pnum = cpu_to_be32(ubi->fm_next_anchor->pnum); +- set_seen(ubi, ubi->fm_next_anchor->pnum, seen_pebs); +- fec->ec = cpu_to_be32(ubi->fm_next_anchor->ec); +- +- free_peb_count++; +- fm_pos += sizeof(*fec); +- ubi_assert(fm_pos <= ubi->fm_size); +- } + fmh->free_peb_count = cpu_to_be32(free_peb_count); + + ubi_for_each_used_peb(ubi, wl_e, tmp_rb) { +diff --git a/drivers/mtd/ubi/ubi.h b/drivers/mtd/ubi/ubi.h +index 7c083ad58274..078112e23dfd 100644 +--- a/drivers/mtd/ubi/ubi.h ++++ b/drivers/mtd/ubi/ubi.h +@@ -489,8 +489,7 @@ struct ubi_debug_info { + * @fm_work: fastmap work queue + * @fm_work_scheduled: non-zero if fastmap work was scheduled + * @fast_attach: non-zero if UBI was attached by fastmap +- * @fm_anchor: The new anchor PEB used during fastmap update +- * @fm_next_anchor: An anchor PEB candidate for the next time fastmap is updated ++ * @fm_anchor: The next anchor PEB to use for fastmap + * @fm_do_produce_anchor: If true produce an anchor PEB in wl + * + * @used: RB-tree of used physical eraseblocks +@@ -601,7 +600,6 @@ struct ubi_device { + int fm_work_scheduled; + int fast_attach; + struct ubi_wl_entry *fm_anchor; +- struct ubi_wl_entry *fm_next_anchor; + int fm_do_produce_anchor; + + /* Wear-leveling sub-system's stuff */ +diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c +index 8455f1d47f3c..afcdacb9d0e9 100644 +--- a/drivers/mtd/ubi/wl.c ++++ b/drivers/mtd/ubi/wl.c +@@ -689,16 +689,16 @@ static int wear_leveling_worker(struct ubi_device *ubi, struct ubi_work *wrk, + + #ifdef CONFIG_MTD_UBI_FASTMAP + e1 = find_anchor_wl_entry(&ubi->used); +- if (e1 && ubi->fm_next_anchor && +- (ubi->fm_next_anchor->ec - e1->ec >= UBI_WL_THRESHOLD)) { ++ if (e1 && ubi->fm_anchor && ++ (ubi->fm_anchor->ec - e1->ec >= UBI_WL_THRESHOLD)) { + ubi->fm_do_produce_anchor = 1; +- /* fm_next_anchor is no longer considered a good anchor +- * candidate. ++ /* ++ * fm_anchor is no longer considered a good anchor. + * NULL assignment also prevents multiple wear level checks + * of this PEB. + */ +- wl_tree_add(ubi->fm_next_anchor, &ubi->free); +- ubi->fm_next_anchor = NULL; ++ wl_tree_add(ubi->fm_anchor, &ubi->free); ++ ubi->fm_anchor = NULL; + ubi->free_count++; + } + +@@ -1085,12 +1085,13 @@ static int __erase_worker(struct ubi_device *ubi, struct ubi_work *wl_wrk) + if (!err) { + spin_lock(&ubi->wl_lock); + +- if (!ubi->fm_disabled && !ubi->fm_next_anchor && ++ if (!ubi->fm_disabled && !ubi->fm_anchor && + e->pnum < UBI_FM_MAX_START) { +- /* Abort anchor production, if needed it will be ++ /* ++ * Abort anchor production, if needed it will be + * enabled again in the wear leveling started below. + */ +- ubi->fm_next_anchor = e; ++ ubi->fm_anchor = e; + ubi->fm_do_produce_anchor = 0; + } else { + wl_tree_add(e, &ubi->free); +-- +2.35.1 + diff --git a/queue-5.15/ubi-ubi_create_volume-fix-use-after-free-when-volume.patch b/queue-5.15/ubi-ubi_create_volume-fix-use-after-free-when-volume.patch new file mode 100644 index 00000000000..911720f3053 --- /dev/null +++ b/queue-5.15/ubi-ubi_create_volume-fix-use-after-free-when-volume.patch @@ -0,0 +1,49 @@ +From aa6b1d674f9a55462c6d8e17efa9f0a1114e6802 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 10 May 2022 20:31:26 +0800 +Subject: ubi: ubi_create_volume: Fix use-after-free when volume creation + failed + +From: Zhihao Cheng + +[ Upstream commit 8c03a1c21d72210f81cb369cc528e3fde4b45411 ] + +There is an use-after-free problem for 'eba_tbl' in ubi_create_volume()'s +error handling path: + + ubi_eba_replace_table(vol, eba_tbl) + vol->eba_tbl = tbl +out_mapping: + ubi_eba_destroy_table(eba_tbl) // Free 'eba_tbl' +out_unlock: + put_device(&vol->dev) + vol_release + kfree(tbl->entries) // UAF + +Fix it by removing redundant 'eba_tbl' releasing. +Fetch a reproducer in [Link]. + +Fixes: 493cfaeaa0c9b ("mtd: utilize new cdev_device_add helper function") +Link: https://bugzilla.kernel.org/show_bug.cgi?id=215965 +Signed-off-by: Zhihao Cheng +Signed-off-by: Richard Weinberger +Signed-off-by: Sasha Levin +--- + drivers/mtd/ubi/vmt.c | 1 - + 1 file changed, 1 deletion(-) + +diff --git a/drivers/mtd/ubi/vmt.c b/drivers/mtd/ubi/vmt.c +index 1bc7b3a05604..6ea95ade4ca6 100644 +--- a/drivers/mtd/ubi/vmt.c ++++ b/drivers/mtd/ubi/vmt.c +@@ -309,7 +309,6 @@ int ubi_create_volume(struct ubi_device *ubi, struct ubi_mkvol_req *req) + ubi->volumes[vol_id] = NULL; + ubi->vol_count -= 1; + spin_unlock(&ubi->volumes_lock); +- ubi_eba_destroy_table(eba_tbl); + out_acc: + spin_lock(&ubi->volumes_lock); + ubi->rsvd_pebs -= vol->reserved_pebs; +-- +2.35.1 + diff --git a/queue-5.15/usb-dwc3-gadget-replace-list_for_each_entry_safe-if-.patch b/queue-5.15/usb-dwc3-gadget-replace-list_for_each_entry_safe-if-.patch new file mode 100644 index 00000000000..4d5bcc40b62 --- /dev/null +++ b/queue-5.15/usb-dwc3-gadget-replace-list_for_each_entry_safe-if-.patch @@ -0,0 +1,116 @@ +From 05cfbc8d8d6c38588a8078891209e087ae661d7f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 14 Apr 2022 11:35:21 -0700 +Subject: usb: dwc3: gadget: Replace list_for_each_entry_safe() if using + giveback + +From: Wesley Cheng + +[ Upstream commit bf594d1d0c1d7b895954018043536ffd327844f9 ] + +The list_for_each_entry_safe() macro saves the current item (n) and +the item after (n+1), so that n can be safely removed without +corrupting the list. However, when traversing the list and removing +items using gadget giveback, the DWC3 lock is briefly released, +allowing other routines to execute. There is a situation where, while +items are being removed from the cancelled_list using +dwc3_gadget_ep_cleanup_cancelled_requests(), the pullup disable +routine is running in parallel (due to UDC unbind). As the cleanup +routine removes n, and the pullup disable removes n+1, once the +cleanup retakes the DWC3 lock, it references a request who was already +removed/handled. With list debug enabled, this leads to a panic. +Ensure all instances of the macro are replaced where gadget giveback +is used. + +Example call stack: + +Thread#1: +__dwc3_gadget_ep_set_halt() - CLEAR HALT + -> dwc3_gadget_ep_cleanup_cancelled_requests() + ->list_for_each_entry_safe() + ->dwc3_gadget_giveback(n) + ->dwc3_gadget_del_and_unmap_request()- n deleted[cancelled_list] + ->spin_unlock + ->Thread#2 executes + ... + ->dwc3_gadget_giveback(n+1) + ->Already removed! + +Thread#2: +dwc3_gadget_pullup() + ->waiting for dwc3 spin_lock + ... + ->Thread#1 released lock + ->dwc3_stop_active_transfers() + ->dwc3_remove_requests() + ->fetches n+1 item from cancelled_list (n removed by Thread#1) + ->dwc3_gadget_giveback() + ->dwc3_gadget_del_and_unmap_request()- n+1 deleted[cancelled_list] + ->spin_unlock + +Fixes: d4f1afe5e896 ("usb: dwc3: gadget: move requests to cancelled_list") +Signed-off-by: Wesley Cheng +Link: https://lore.kernel.org/r/20220414183521.23451-1-quic_wcheng@quicinc.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/dwc3/gadget.c | 20 ++++++++++++++++---- + 1 file changed, 16 insertions(+), 4 deletions(-) + +diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c +index c064ec41bf8c..99d0372ed840 100644 +--- a/drivers/usb/dwc3/gadget.c ++++ b/drivers/usb/dwc3/gadget.c +@@ -1955,10 +1955,10 @@ static void dwc3_gadget_ep_skip_trbs(struct dwc3_ep *dep, struct dwc3_request *r + static void dwc3_gadget_ep_cleanup_cancelled_requests(struct dwc3_ep *dep) + { + struct dwc3_request *req; +- struct dwc3_request *tmp; + struct dwc3 *dwc = dep->dwc; + +- list_for_each_entry_safe(req, tmp, &dep->cancelled_list, list) { ++ while (!list_empty(&dep->cancelled_list)) { ++ req = next_request(&dep->cancelled_list); + dwc3_gadget_ep_skip_trbs(dep, req); + switch (req->status) { + case DWC3_REQUEST_STATUS_DISCONNECTED: +@@ -1975,6 +1975,12 @@ static void dwc3_gadget_ep_cleanup_cancelled_requests(struct dwc3_ep *dep) + dwc3_gadget_giveback(dep, req, -ECONNRESET); + break; + } ++ /* ++ * The endpoint is disabled, let the dwc3_remove_requests() ++ * handle the cleanup. ++ */ ++ if (!dep->endpoint.desc) ++ break; + } + } + +@@ -3258,15 +3264,21 @@ static void dwc3_gadget_ep_cleanup_completed_requests(struct dwc3_ep *dep, + const struct dwc3_event_depevt *event, int status) + { + struct dwc3_request *req; +- struct dwc3_request *tmp; + +- list_for_each_entry_safe(req, tmp, &dep->started_list, list) { ++ while (!list_empty(&dep->started_list)) { + int ret; + ++ req = next_request(&dep->started_list); + ret = dwc3_gadget_ep_cleanup_completed_request(dep, event, + req, status); + if (ret) + break; ++ /* ++ * The endpoint is disabled, let the dwc3_remove_requests() ++ * handle the cleanup. ++ */ ++ if (!dep->endpoint.desc) ++ break; + } + } + +-- +2.35.1 + diff --git a/queue-5.15/usb-dwc3-pci-fix-pm_runtime_get_sync-error-checking.patch b/queue-5.15/usb-dwc3-pci-fix-pm_runtime_get_sync-error-checking.patch new file mode 100644 index 00000000000..7f17fe59985 --- /dev/null +++ b/queue-5.15/usb-dwc3-pci-fix-pm_runtime_get_sync-error-checking.patch @@ -0,0 +1,38 @@ +From be81534a429492055305a511d0e1201179b4c693 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 06:26:52 +0000 +Subject: usb: dwc3: pci: Fix pm_runtime_get_sync() error checking + +From: Zheng Yongjun + +[ Upstream commit a03e2ddab8e735e2cc315609b297b300e9cc60d2 ] + +If the device is already in a runtime PM enabled state +pm_runtime_get_sync() will return 1, so a test for negative +value should be used to check for errors. + +Fixes: 8eed00b237a28 ("usb: dwc3: pci: Runtime resume child device from wq") +Signed-off-by: Zheng Yongjun +Link: https://lore.kernel.org/r/20220422062652.10575-1-zhengyongjun3@huawei.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/dwc3/dwc3-pci.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/usb/dwc3/dwc3-pci.c b/drivers/usb/dwc3/dwc3-pci.c +index f08b2178fd32..9c8887615701 100644 +--- a/drivers/usb/dwc3/dwc3-pci.c ++++ b/drivers/usb/dwc3/dwc3-pci.c +@@ -256,7 +256,7 @@ static void dwc3_pci_resume_work(struct work_struct *work) + int ret; + + ret = pm_runtime_get_sync(&dwc3->dev); +- if (ret) { ++ if (ret < 0) { + pm_runtime_put_sync_autosuspend(&dwc3->dev); + return; + } +-- +2.35.1 + diff --git a/queue-5.15/usb-musb-fix-missing-of_node_put-in-omap2430_probe.patch b/queue-5.15/usb-musb-fix-missing-of_node_put-in-omap2430_probe.patch new file mode 100644 index 00000000000..3111f23c1e3 --- /dev/null +++ b/queue-5.15/usb-musb-fix-missing-of_node_put-in-omap2430_probe.patch @@ -0,0 +1,36 @@ +From 9c8c2ecce1367d76f6c7bacd14e68a04508b9212 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 9 Mar 2022 11:10:33 +0000 +Subject: usb: musb: Fix missing of_node_put() in omap2430_probe + +From: Miaoqian Lin + +[ Upstream commit 424bef51fa530389b0b9008c9e144e40c10e8458 ] + +The device_node pointer is returned by of_parse_phandle() with refcount +incremented. We should use of_node_put() on it when done. + +Fixes: 8934d3e4d0e7 ("usb: musb: omap2430: Don't use omap_get_control_dev()") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220309111033.24487-1-linmq006@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/musb/omap2430.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c +index f086960fe2b5..bd1de5c4c434 100644 +--- a/drivers/usb/musb/omap2430.c ++++ b/drivers/usb/musb/omap2430.c +@@ -363,6 +363,7 @@ static int omap2430_probe(struct platform_device *pdev) + control_node = of_parse_phandle(np, "ctrl-module", 0); + if (control_node) { + control_pdev = of_find_device_by_node(control_node); ++ of_node_put(control_node); + if (!control_pdev) { + dev_err(&pdev->dev, "Failed to get control device\n"); + ret = -EINVAL; +-- +2.35.1 + diff --git a/queue-5.15/usb-storage-karma-fix-rio_karma_init-return.patch b/queue-5.15/usb-storage-karma-fix-rio_karma_init-return.patch new file mode 100644 index 00000000000..4ce49f7d1e4 --- /dev/null +++ b/queue-5.15/usb-storage-karma-fix-rio_karma_init-return.patch @@ -0,0 +1,64 @@ +From 4e921a8d65b3645bc6b66459b287e4bb9e6fb069 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 22:43:59 +0800 +Subject: USB: storage: karma: fix rio_karma_init return + +From: Lin Ma + +[ Upstream commit b92ffb1eddd9a66a90defc556dcbf65a43c196c7 ] + +The function rio_karam_init() should return -ENOMEM instead of +value 0 (USB_STOR_TRANSPORT_GOOD) when allocation fails. + +Similarly, it should return -EIO when rio_karma_send_command() fails. + +Fixes: dfe0d3ba20e8 ("USB Storage: add rio karma eject support") +Acked-by: Alan Stern +Signed-off-by: Lin Ma +Link: https://lore.kernel.org/r/20220412144359.28447-1-linma@zju.edu.cn +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/storage/karma.c | 15 ++++++++------- + 1 file changed, 8 insertions(+), 7 deletions(-) + +diff --git a/drivers/usb/storage/karma.c b/drivers/usb/storage/karma.c +index 05cec81dcd3f..38ddfedef629 100644 +--- a/drivers/usb/storage/karma.c ++++ b/drivers/usb/storage/karma.c +@@ -174,24 +174,25 @@ static void rio_karma_destructor(void *extra) + + static int rio_karma_init(struct us_data *us) + { +- int ret = 0; + struct karma_data *data = kzalloc(sizeof(struct karma_data), GFP_NOIO); + + if (!data) +- goto out; ++ return -ENOMEM; + + data->recv = kmalloc(RIO_RECV_LEN, GFP_NOIO); + if (!data->recv) { + kfree(data); +- goto out; ++ return -ENOMEM; + } + + us->extra = data; + us->extra_destructor = rio_karma_destructor; +- ret = rio_karma_send_command(RIO_ENTER_STORAGE, us); +- data->in_storage = (ret == 0); +-out: +- return ret; ++ if (rio_karma_send_command(RIO_ENTER_STORAGE, us)) ++ return -EIO; ++ ++ data->in_storage = 1; ++ ++ return 0; + } + + static struct scsi_host_template karma_host_template; +-- +2.35.1 + diff --git a/queue-5.15/usb-typec-mux-check-dev_set_name-return-value.patch b/queue-5.15/usb-typec-mux-check-dev_set_name-return-value.patch new file mode 100644 index 00000000000..c50cdfe4602 --- /dev/null +++ b/queue-5.15/usb-typec-mux-check-dev_set_name-return-value.patch @@ -0,0 +1,58 @@ +From b87dec7d6c4ed169aa4aba5a89bd5e5037b8a537 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 15:23:47 -0700 +Subject: usb: typec: mux: Check dev_set_name() return value + +From: Bjorn Andersson + +[ Upstream commit b9fa0292490db39d6542f514117333d366ec0011 ] + +It's possible that dev_set_name() returns -ENOMEM, catch and handle this. + +Fixes: 3370db35193b ("usb: typec: Registering real device entries for the muxes") +Reported-by: Andy Shevchenko +Reviewed-by: Andy Shevchenko +Acked-by: Heikki Krogerus +Signed-off-by: Bjorn Andersson +Link: https://lore.kernel.org/r/20220422222351.1297276-4-bjorn.andersson@linaro.org +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/typec/mux.c | 14 ++++++++++---- + 1 file changed, 10 insertions(+), 4 deletions(-) + +diff --git a/drivers/usb/typec/mux.c b/drivers/usb/typec/mux.c +index c8340de0ed49..d2aaf294b649 100644 +--- a/drivers/usb/typec/mux.c ++++ b/drivers/usb/typec/mux.c +@@ -131,8 +131,11 @@ typec_switch_register(struct device *parent, + sw->dev.class = &typec_mux_class; + sw->dev.type = &typec_switch_dev_type; + sw->dev.driver_data = desc->drvdata; +- dev_set_name(&sw->dev, "%s-switch", +- desc->name ? desc->name : dev_name(parent)); ++ ret = dev_set_name(&sw->dev, "%s-switch", desc->name ? desc->name : dev_name(parent)); ++ if (ret) { ++ put_device(&sw->dev); ++ return ERR_PTR(ret); ++ } + + ret = device_add(&sw->dev); + if (ret) { +@@ -338,8 +341,11 @@ typec_mux_register(struct device *parent, const struct typec_mux_desc *desc) + mux->dev.class = &typec_mux_class; + mux->dev.type = &typec_mux_dev_type; + mux->dev.driver_data = desc->drvdata; +- dev_set_name(&mux->dev, "%s-mux", +- desc->name ? desc->name : dev_name(parent)); ++ ret = dev_set_name(&mux->dev, "%s-mux", desc->name ? desc->name : dev_name(parent)); ++ if (ret) { ++ put_device(&mux->dev); ++ return ERR_PTR(ret); ++ } + + ret = device_add(&mux->dev); + if (ret) { +-- +2.35.1 + diff --git a/queue-5.15/usb-usbip-add-missing-device-lock-on-tweak-configura.patch b/queue-5.15/usb-usbip-add-missing-device-lock-on-tweak-configura.patch new file mode 100644 index 00000000000..fea8dbf1570 --- /dev/null +++ b/queue-5.15/usb-usbip-add-missing-device-lock-on-tweak-configura.patch @@ -0,0 +1,49 @@ +From 05de46fe9bb15733cd0d0652157616b909e2e6ed Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 18:50:55 +0200 +Subject: usb: usbip: add missing device lock on tweak configuration cmd + +From: Niels Dossche + +[ Upstream commit d088fabace2ca337b275d1d4b36db4fe7771e44f ] + +The function documentation of usb_set_configuration says that its +callers should hold the device lock. This lock is held for all +callsites except tweak_set_configuration_cmd. The code path can be +executed for example when attaching a remote USB device. +The solution is to surround the call by the device lock. + +This bug was found using my experimental own-developed static analysis +tool, which reported the missing lock on v5.17.2. I manually verified +this bug report by doing code review as well. I runtime checked that +the required lock is not held. I compiled and runtime tested this on +x86_64 with a USB mouse. After applying this patch, my analyser no +longer reports this potential bug. + +Fixes: 2c8c98158946 ("staging: usbip: let client choose device configuration") +Reviewed-by: Shuah Khan +Signed-off-by: Niels Dossche +Link: https://lore.kernel.org/r/20220412165055.257113-1-dossche.niels@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/usbip/stub_rx.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/usb/usbip/stub_rx.c b/drivers/usb/usbip/stub_rx.c +index 325c22008e53..5dd41e8215e0 100644 +--- a/drivers/usb/usbip/stub_rx.c ++++ b/drivers/usb/usbip/stub_rx.c +@@ -138,7 +138,9 @@ static int tweak_set_configuration_cmd(struct urb *urb) + req = (struct usb_ctrlrequest *) urb->setup_packet; + config = le16_to_cpu(req->wValue); + ++ usb_lock_device(sdev->udev); + err = usb_set_configuration(sdev->udev, config); ++ usb_unlock_device(sdev->udev); + if (err && err != -ENODEV) + dev_err(&sdev->udev->dev, "can't set config #%d, error %d\n", + config, err); +-- +2.35.1 + diff --git a/queue-5.15/usb-usbip-fix-a-refcount-leak-in-stub_probe.patch b/queue-5.15/usb-usbip-fix-a-refcount-leak-in-stub_probe.patch new file mode 100644 index 00000000000..ba3d1344ea4 --- /dev/null +++ b/queue-5.15/usb-usbip-fix-a-refcount-leak-in-stub_probe.patch @@ -0,0 +1,49 @@ +From e2340bc9ee818e2e97f104980cf083fe2667c2a2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 10:02:57 +0800 +Subject: usb: usbip: fix a refcount leak in stub_probe() + +From: Hangyu Hua + +[ Upstream commit 9ec4cbf1cc55d126759051acfe328d489c5d6e60 ] + +usb_get_dev() is called in stub_device_alloc(). When stub_probe() fails +after that, usb_put_dev() needs to be called to release the reference. + +Fix this by moving usb_put_dev() to sdev_free error path handling. + +Find this by code review. + +Fixes: 3ff67445750a ("usbip: fix error handling in stub_probe()") +Reviewed-by: Shuah Khan +Signed-off-by: Hangyu Hua +Link: https://lore.kernel.org/r/20220412020257.9767-1-hbh25y@gmail.com +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Sasha Levin +--- + drivers/usb/usbip/stub_dev.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/usb/usbip/stub_dev.c b/drivers/usb/usbip/stub_dev.c +index d8d3892e5a69..3c6d452e3bf4 100644 +--- a/drivers/usb/usbip/stub_dev.c ++++ b/drivers/usb/usbip/stub_dev.c +@@ -393,7 +393,6 @@ static int stub_probe(struct usb_device *udev) + + err_port: + dev_set_drvdata(&udev->dev, NULL); +- usb_put_dev(udev); + + /* we already have busid_priv, just lock busid_lock */ + spin_lock(&busid_priv->busid_lock); +@@ -408,6 +407,7 @@ static int stub_probe(struct usb_device *udev) + put_busid_priv(busid_priv); + + sdev_free: ++ usb_put_dev(udev); + stub_device_free(sdev); + + return rc; +-- +2.35.1 + diff --git a/queue-5.15/vdpa-fix-error-logic-in-vdpa_nl_cmd_dev_get_doit.patch b/queue-5.15/vdpa-fix-error-logic-in-vdpa_nl_cmd_dev_get_doit.patch new file mode 100644 index 00000000000..be23d6330d6 --- /dev/null +++ b/queue-5.15/vdpa-fix-error-logic-in-vdpa_nl_cmd_dev_get_doit.patch @@ -0,0 +1,56 @@ +From ad0574f5e653146853ea36263e06d27fb5258400 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 18 May 2022 16:37:59 +0300 +Subject: vdpa: Fix error logic in vdpa_nl_cmd_dev_get_doit + +From: Eli Cohen + +[ Upstream commit 7a6691f1f89784f775fa0c54be57533445726068 ] + +In vdpa_nl_cmd_dev_get_doit(), if the call to genlmsg_reply() fails we +must not call nlmsg_free() since this is done inside genlmsg_reply(). + +Fix it. + +Fixes: bc0d90ee021f ("vdpa: Enable user to query vdpa device info") +Reviewed-by: Si-Wei Liu +Acked-by: Jason Wang +Signed-off-by: Eli Cohen +Message-Id: <20220518133804.1075129-2-elic@nvidia.com> +Signed-off-by: Michael S. Tsirkin +Signed-off-by: Sasha Levin +--- + drivers/vdpa/vdpa.c | 13 +++++++++---- + 1 file changed, 9 insertions(+), 4 deletions(-) + +diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c +index 12bf3d16a40f..86571498c1c2 100644 +--- a/drivers/vdpa/vdpa.c ++++ b/drivers/vdpa/vdpa.c +@@ -558,14 +558,19 @@ static int vdpa_nl_cmd_dev_get_doit(struct sk_buff *skb, struct genl_info *info) + goto mdev_err; + } + err = vdpa_dev_fill(vdev, msg, info->snd_portid, info->snd_seq, 0, info->extack); +- if (!err) +- err = genlmsg_reply(msg, info); ++ if (err) ++ goto mdev_err; ++ ++ err = genlmsg_reply(msg, info); ++ put_device(dev); ++ mutex_unlock(&vdpa_dev_mutex); ++ return err; ++ + mdev_err: + put_device(dev); + err: + mutex_unlock(&vdpa_dev_mutex); +- if (err) +- nlmsg_free(msg); ++ nlmsg_free(msg); + return err; + } + +-- +2.35.1 + diff --git a/queue-5.15/vdpa-ifcvf-set-pci-driver-data-in-probe.patch b/queue-5.15/vdpa-ifcvf-set-pci-driver-data-in-probe.patch new file mode 100644 index 00000000000..617ac46cde7 --- /dev/null +++ b/queue-5.15/vdpa-ifcvf-set-pci-driver-data-in-probe.patch @@ -0,0 +1,47 @@ +From 14cac5e84688278aee388b3ccf784ff6480d048c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 24 May 2022 13:55:57 +0800 +Subject: vdpa: ifcvf: set pci driver data in probe + +From: Jason Wang + +[ Upstream commit bd8bb9aed56b1814784a975e2dfea12a9adcee92 ] + +We should set the pci driver data in probe instead of the vdpa device +adding callback. Otherwise if no vDPA device is created we will lose +the pointer to the management device. + +Fixes: 6b5df347c6482 ("vDPA/ifcvf: implement management netlink framework for ifcvf") +Tested-by: Zheyu Ma +Signed-off-by: Jason Wang +Message-Id: <20220524055557.1938-1-jasowang@redhat.com> +Signed-off-by: Michael S. Tsirkin +Signed-off-by: Sasha Levin +--- + drivers/vdpa/ifcvf/ifcvf_main.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/drivers/vdpa/ifcvf/ifcvf_main.c b/drivers/vdpa/ifcvf/ifcvf_main.c +index 003530b19b4e..4fe8aa13ac68 100644 +--- a/drivers/vdpa/ifcvf/ifcvf_main.c ++++ b/drivers/vdpa/ifcvf/ifcvf_main.c +@@ -505,7 +505,6 @@ static int ifcvf_vdpa_dev_add(struct vdpa_mgmt_dev *mdev, const char *name) + } + + ifcvf_mgmt_dev->adapter = adapter; +- pci_set_drvdata(pdev, ifcvf_mgmt_dev); + + vf = &adapter->vf; + vf->dev_type = get_dev_type(pdev); +@@ -620,6 +619,8 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) + goto err; + } + ++ pci_set_drvdata(pdev, ifcvf_mgmt_dev); ++ + return 0; + + err: +-- +2.35.1 + diff --git a/queue-5.15/virtio-pci-fix-an-error-handling-path-in-vp_modern_p.patch b/queue-5.15/virtio-pci-fix-an-error-handling-path-in-vp_modern_p.patch new file mode 100644 index 00000000000..5c39f16c63e --- /dev/null +++ b/queue-5.15/virtio-pci-fix-an-error-handling-path-in-vp_modern_p.patch @@ -0,0 +1,37 @@ +From 5c1b6f9a7f8b11ca7aafab264a28a39dd1218640 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 3 Apr 2022 11:11:14 +0200 +Subject: virtio: pci: Fix an error handling path in vp_modern_probe() + +From: Christophe JAILLET + +[ Upstream commit 7a836a2aba09479c8e71fa43249eecc4af945f61 ] + +If an error occurs after a successful pci_request_selected_regions() call, +it should be undone by a corresponding pci_release_selected_regions() call, +as already done in vp_modern_remove(). + +Fixes: fd502729fbbf ("virtio-pci: introduce modern device module") +Signed-off-by: Christophe JAILLET +Message-Id: <237109725aad2c3c03d14549f777b1927c84b045.1648977064.git.christophe.jaillet@wanadoo.fr> +Signed-off-by: Michael S. Tsirkin +Signed-off-by: Sasha Levin +--- + drivers/virtio/virtio_pci_modern_dev.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/virtio/virtio_pci_modern_dev.c b/drivers/virtio/virtio_pci_modern_dev.c +index e11ed748e661..9ab66e44738e 100644 +--- a/drivers/virtio/virtio_pci_modern_dev.c ++++ b/drivers/virtio/virtio_pci_modern_dev.c +@@ -340,6 +340,7 @@ int vp_modern_probe(struct virtio_pci_modern_device *mdev) + err_map_isr: + pci_iounmap(pci_dev, mdev->common); + err_map_common: ++ pci_release_selected_regions(pci_dev, mdev->modern_bars); + return err; + } + EXPORT_SYMBOL_GPL(vp_modern_probe); +-- +2.35.1 + diff --git a/queue-5.15/watchdog-rti-wdt-fix-pm_runtime_get_sync-error-check.patch b/queue-5.15/watchdog-rti-wdt-fix-pm_runtime_get_sync-error-check.patch new file mode 100644 index 00000000000..1d9f6267697 --- /dev/null +++ b/queue-5.15/watchdog-rti-wdt-fix-pm_runtime_get_sync-error-check.patch @@ -0,0 +1,40 @@ +From 3462010196c2226d5517bbd08d5e3885b98e5659 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 07:08:23 +0000 +Subject: watchdog: rti-wdt: Fix pm_runtime_get_sync() error checking + +From: Miaoqian Lin + +[ Upstream commit b3ac0c58fa8934926360268f3d89ec7680644d7b ] + +If the device is already in a runtime PM enabled state +pm_runtime_get_sync() will return 1, so a test for negative +value should be used to check for errors. + +Fixes: 2d63908bdbfb ("watchdog: Add K3 RTI watchdog support") +Signed-off-by: Miaoqian Lin +Reviewed-by: Guenter Roeck +Link: https://lore.kernel.org/r/20220412070824.23708-1-linmq006@gmail.com +Signed-off-by: Guenter Roeck +Signed-off-by: Wim Van Sebroeck +Signed-off-by: Sasha Levin +--- + drivers/watchdog/rti_wdt.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/watchdog/rti_wdt.c b/drivers/watchdog/rti_wdt.c +index ae7f9357bb87..46c2a4bd9ebe 100644 +--- a/drivers/watchdog/rti_wdt.c ++++ b/drivers/watchdog/rti_wdt.c +@@ -227,7 +227,7 @@ static int rti_wdt_probe(struct platform_device *pdev) + + pm_runtime_enable(dev); + ret = pm_runtime_get_sync(dev); +- if (ret) { ++ if (ret < 0) { + pm_runtime_put_noidle(dev); + pm_runtime_disable(&pdev->dev); + return dev_err_probe(dev, ret, "runtime pm failed\n"); +-- +2.35.1 + diff --git a/queue-5.15/watchdog-ts4800_wdt-fix-refcount-leak-in-ts4800_wdt_.patch b/queue-5.15/watchdog-ts4800_wdt-fix-refcount-leak-in-ts4800_wdt_.patch new file mode 100644 index 00000000000..863424cf934 --- /dev/null +++ b/queue-5.15/watchdog-ts4800_wdt-fix-refcount-leak-in-ts4800_wdt_.patch @@ -0,0 +1,49 @@ +From 3e6c40866d3ab9b1836bb71cd5ac6c891b1a9d7a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 11 May 2022 15:42:03 +0400 +Subject: watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe + +From: Miaoqian Lin + +[ Upstream commit 5d24df3d690809952528e7a19a43d84bc5b99d44 ] + +of_parse_phandle() returns a node pointer with refcount +incremented, we should use of_node_put() on it when done. +Add missing of_node_put() in some error paths. + +Fixes: bf9006399939 ("watchdog: ts4800: add driver for TS-4800 watchdog") +Signed-off-by: Miaoqian Lin +Reviewed-by: Guenter Roeck +Link: https://lore.kernel.org/r/20220511114203.47420-1-linmq006@gmail.com +Signed-off-by: Guenter Roeck +Signed-off-by: Wim Van Sebroeck +Signed-off-by: Sasha Levin +--- + drivers/watchdog/ts4800_wdt.c | 5 ++++- + 1 file changed, 4 insertions(+), 1 deletion(-) + +diff --git a/drivers/watchdog/ts4800_wdt.c b/drivers/watchdog/ts4800_wdt.c +index c137ad2bd5c3..0ea554c7cda5 100644 +--- a/drivers/watchdog/ts4800_wdt.c ++++ b/drivers/watchdog/ts4800_wdt.c +@@ -125,13 +125,16 @@ static int ts4800_wdt_probe(struct platform_device *pdev) + ret = of_property_read_u32_index(np, "syscon", 1, ®); + if (ret < 0) { + dev_err(dev, "no offset in syscon\n"); ++ of_node_put(syscon_np); + return ret; + } + + /* allocate memory for watchdog struct */ + wdt = devm_kzalloc(dev, sizeof(*wdt), GFP_KERNEL); +- if (!wdt) ++ if (!wdt) { ++ of_node_put(syscon_np); + return -ENOMEM; ++ } + + /* set regmap and offset to know where to write */ + wdt->feed_offset = reg; +-- +2.35.1 +