From: Greg Kroah-Hartman Date: Mon, 20 Jul 2026 10:53:22 +0000 (+0200) Subject: 6.6-stable patches X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=4202e3ac4befd9a2d557fecf46e764d10dc053ed;p=thirdparty%2Fkernel%2Fstable-queue.git 6.6-stable patches added patches: afs-fix-further-netns-teardown-to-cancel-the-preallocation-charger.patch afs-fix-netns-teardown-to-cancel-the-preallocation-charger.patch afs-fix-null-pointer-dereference-in-afs_get_tree.patch dt-bindings-media-sun4i-a10-video-engine-add-interconnect-properties.patch dt-bindings-power-imx93-add-mipi-phy-power-domain.patch fbcon-fix-null-pointer-dereference-for-a-console-without-vc_data.patch media-uvcvideo-avoid-partial-metadata-buffers.patch media-uvcvideo-fix-buffer-sequence-in-frame-gaps.patch media-uvcvideo-fix-sequence-number-when-no-eof.patch rxrpc-fix-leak-of-released-call-in-recvmsg-msg_peek.patch rxrpc-rxrpc_verify_data-ensure-rx_dec_buffer-alloc.patch serial-8250_omap-clear-rx_running-on-zero-length-dma-completes.patch serial-msm-disable-dma-for-kernel-console-uart.patch --- diff --git a/queue-6.6/afs-fix-further-netns-teardown-to-cancel-the-preallocation-charger.patch b/queue-6.6/afs-fix-further-netns-teardown-to-cancel-the-preallocation-charger.patch new file mode 100644 index 0000000000..5abcc797ce --- /dev/null +++ b/queue-6.6/afs-fix-further-netns-teardown-to-cancel-the-preallocation-charger.patch @@ -0,0 +1,52 @@ +From 2daf8ac812c3d78c642fe7652f62e29df5e3da20 Mon Sep 17 00:00:00 2001 +From: David Howells +Date: Wed, 24 Jun 2026 17:38:11 +0100 +Subject: afs: Fix further netns teardown to cancel the preallocation charger + +From: David Howells + +commit 2daf8ac812c3d78c642fe7652f62e29df5e3da20 upstream. + +When an afs network namespace is torn down, it cancels and waits for the +work item that keeps the preallocated rxrpc call/conn/peer queue charged +before disabling incoming (i.e. listen 0), but there's a small window in +which it can be requeued by an incoming call wending through the I/O +thread. + +Fix this by cancelling the charger work item again after reducing the +listen backlog to zero. + +Fixes: 47694fbc9d24 ("afs: Fix netns teardown to cancel the preallocation charger") +Reported-by: Jakub Kicinski +Signed-off-by: David Howells +Link: https://sashiko.dev/#/patchset/20260609140911.838677-1-dhowells%40redhat.com +cc: Li Daming +cc: Ren Wei +cc: Marc Dionne +cc: Jeffrey Altman +cc: Simon Horman +cc: linux-afs@lists.infradead.org +cc: stable@kernel.org +Link: https://patch.msgid.link/20260624163819.3017002-5-dhowells@redhat.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + fs/afs/rxrpc.c | 5 +++++ + 1 file changed, 5 insertions(+) + +--- a/fs/afs/rxrpc.c ++++ b/fs/afs/rxrpc.c +@@ -110,8 +110,13 @@ void afs_close_socket(struct afs_net *ne + _enter(""); + + cancel_work_sync(&net->charge_preallocation_work); ++ /* Future work items should now see ->live is false. */ ++ + kernel_listen(net->socket, 0); ++ ++ /* Make sure work items are no longer running. */ + flush_workqueue(afs_async_calls); ++ cancel_work_sync(&net->charge_preallocation_work); + + if (net->spare_incoming_call) { + afs_put_call(net->spare_incoming_call); diff --git a/queue-6.6/afs-fix-netns-teardown-to-cancel-the-preallocation-charger.patch b/queue-6.6/afs-fix-netns-teardown-to-cancel-the-preallocation-charger.patch new file mode 100644 index 0000000000..c275742e8c --- /dev/null +++ b/queue-6.6/afs-fix-netns-teardown-to-cancel-the-preallocation-charger.patch @@ -0,0 +1,64 @@ +From 47694fbc9d24ab6bf210f91e8efe06a10a478064 Mon Sep 17 00:00:00 2001 +From: David Howells +Date: Tue, 9 Jun 2026 15:09:08 +0100 +Subject: afs: Fix netns teardown to cancel the preallocation charger + +From: David Howells + +commit 47694fbc9d24ab6bf210f91e8efe06a10a478064 upstream. + +Fix the teardown of an afs network namespace to make sure it cancels the +work item that keeps the preallocated rxrpc call/conn/peer queue charged +before incoming calls are disabled (i.e. listen 0). + +Also, if net->live is false because the afs netns is being deleted, make +afs_charge_preallocation() skip charging and make afs_rx_new_call() avoid +requeuing the charger. + +(This was found by AI review). + +Fixes: 00e907127e6f ("rxrpc: Preallocate peers, conns and calls for incoming service requests") +Reported-by: Simon Horman +Signed-off-by: David Howells +cc: Li Daming +cc: Ren Wei +cc: Marc Dionne +cc: Jeffrey Altman +cc: linux-afs@lists.infradead.org +cc: stable@kernel.org +Link: https://patch.msgid.link/20260609140911.838677-5-dhowells@redhat.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + fs/afs/rxrpc.c | 6 ++++-- + 1 file changed, 4 insertions(+), 2 deletions(-) + +--- a/fs/afs/rxrpc.c ++++ b/fs/afs/rxrpc.c +@@ -109,6 +109,7 @@ void afs_close_socket(struct afs_net *ne + { + _enter(""); + ++ cancel_work_sync(&net->charge_preallocation_work); + kernel_listen(net->socket, 0); + flush_workqueue(afs_async_calls); + +@@ -727,7 +728,7 @@ void afs_charge_preallocation(struct wor + container_of(work, struct afs_net, charge_preallocation_work); + struct afs_call *call = net->spare_incoming_call; + +- for (;;) { ++ while (READ_ONCE(net->live)) { + if (!call) { + call = afs_alloc_call(net, &afs_RXCMxxxx, GFP_KERNEL); + if (!call) +@@ -772,7 +773,8 @@ static void afs_rx_new_call(struct sock + { + struct afs_net *net = afs_sock2net(sk); + +- queue_work(afs_wq, &net->charge_preallocation_work); ++ if (net->live) ++ queue_work(afs_wq, &net->charge_preallocation_work); + } + + /* diff --git a/queue-6.6/afs-fix-null-pointer-dereference-in-afs_get_tree.patch b/queue-6.6/afs-fix-null-pointer-dereference-in-afs_get_tree.patch new file mode 100644 index 0000000000..03bb9161ec --- /dev/null +++ b/queue-6.6/afs-fix-null-pointer-dereference-in-afs_get_tree.patch @@ -0,0 +1,62 @@ +From 0b70716081c6462be9b2928ad736d0d527b09678 Mon Sep 17 00:00:00 2001 +From: Matvey Kovalev +Date: Mon, 22 Jun 2026 10:08:37 +0100 +Subject: afs: fix NULL pointer dereference in afs_get_tree() + +From: Matvey Kovalev + +commit 0b70716081c6462be9b2928ad736d0d527b09678 upstream. + +afs_alloc_sbi() uses kzalloc for memory allocation. And, if +ctx->dyn_root is not null, as->cell and as->volume are null. +In trace_afs_get_tree() they are dereferenced. + +KASAN error message: + +KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] +CPU: 2 PID: 18478 Comm: syz-executor.7 Not tainted 5.10.246-syzkaller #0 +Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 +04/01/2014 +RIP: 0010:perf_trace_afs_get_tree+0x1d9/0x550 +include/trace/events/afs.h:1365 + +Call Trace: +trace_afs_get_tree include/trace/events/afs.h:1365 [inline] +afs_get_tree+0x922/0x1350 fs/afs/super.c:599 +vfs_get_tree+0x8e/0x300 fs/super.c:1572 +do_new_mount fs/namespace.c:3011 [inline] +path_mount+0x14a5/0x2220 fs/namespace.c:3341 +do_mount fs/namespace.c:3354 [inline] +__do_sys_mount fs/namespace.c:3562 [inline] +__se_sys_mount fs/namespace.c:3539 [inline] +__x64_sys_mount+0x283/0x300 fs/namespace.c:3539 + do_syscall_64+0x33/0x50 arch/x86/entry/common.c:46 +entry_SYSCALL_64_after_hwframe+0x67/0xd1 + +Found by Linux Verification Center (linuxtesting.org) with Syzkaller. + +Fixes: 80548b03991f5 ("afs: Add more tracepoints") +Cc: stable@vger.kernel.org +Signed-off-by: Matvey Kovalev +Signed-off-by: David Howells +Link: https://patch.msgid.link/20260622090856.2746629-4-dhowells@redhat.com +cc: Marc Dionne +cc: linux-afs@lists.infradead.org +Signed-off-by: Christian Brauner (Amutable) +Signed-off-by: Greg Kroah-Hartman +--- + fs/afs/super.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/fs/afs/super.c ++++ b/fs/afs/super.c +@@ -597,7 +597,8 @@ static int afs_get_tree(struct fs_contex + } + + fc->root = dget(sb->s_root); +- trace_afs_get_tree(as->cell, as->volume); ++ if (!ctx->dyn_root) ++ trace_afs_get_tree(as->cell, as->volume); + _leave(" = 0 [%p]", sb); + return 0; + diff --git a/queue-6.6/dt-bindings-media-sun4i-a10-video-engine-add-interconnect-properties.patch b/queue-6.6/dt-bindings-media-sun4i-a10-video-engine-add-interconnect-properties.patch new file mode 100644 index 0000000000..bd014307bf --- /dev/null +++ b/queue-6.6/dt-bindings-media-sun4i-a10-video-engine-add-interconnect-properties.patch @@ -0,0 +1,45 @@ +From 018f2dc3a42098d3b04edd1480adc51d268adb14 Mon Sep 17 00:00:00 2001 +From: Chen-Yu Tsai +Date: Thu, 25 Dec 2025 18:36:12 +0800 +Subject: dt-bindings: media: sun4i-a10-video-engine: Add interconnect properties + +From: Chen-Yu Tsai + +commit 018f2dc3a42098d3b04edd1480adc51d268adb14 upstream. + +The Allwinner video engine sits behind the MBUS that is represented as +an interconnect. + +Make sure that the interconnect properties are valid in the binding. + +Fixes: d41662e52a03 ("media: dt-bindings: media: allwinner,sun4i-a10-video-engine: Add R40 compatible") +Cc: stable@vger.kernel.org +Signed-off-by: Chen-Yu Tsai +Acked-by: Rob Herring (Arm) +Acked-by: Jernej Skrabec +Signed-off-by: Nicolas Dufresne +Signed-off-by: Hans Verkuil +Signed-off-by: Greg Kroah-Hartman +--- + Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml | 10 ++++++++++ + 1 file changed, 10 insertions(+) + +--- a/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml ++++ b/Documentation/devicetree/bindings/media/allwinner,sun4i-a10-video-engine.yaml +@@ -63,6 +63,16 @@ properties: + CMA pool to use for buffers allocation instead of the default + CMA pool. + ++ # FIXME: This should be made required eventually once every SoC will ++ # have the MBUS declared. ++ interconnects: ++ maxItems: 1 ++ ++ # FIXME: This should be made required eventually once every SoC will ++ # have the MBUS declared. ++ interconnect-names: ++ const: dma-mem ++ + required: + - compatible + - reg diff --git a/queue-6.6/dt-bindings-power-imx93-add-mipi-phy-power-domain.patch b/queue-6.6/dt-bindings-power-imx93-add-mipi-phy-power-domain.patch new file mode 100644 index 0000000000..28be91b1bd --- /dev/null +++ b/queue-6.6/dt-bindings-power-imx93-add-mipi-phy-power-domain.patch @@ -0,0 +1,33 @@ +From 6aa38ef0eab32df5409b72d62509de6ba09cea50 Mon Sep 17 00:00:00 2001 +From: Guoniu Zhou +Date: Tue, 9 Jun 2026 14:26:40 +0800 +Subject: dt-bindings: power: imx93: Add MIPI PHY power domain + +From: Guoniu Zhou + +commit 6aa38ef0eab32df5409b72d62509de6ba09cea50 upstream. + +Add MIPI PHY power domain for shared PHY resources used by both +MIPI DSI and CSI blocks. + +Signed-off-by: Guoniu Zhou +Reviewed-by: Frank Li +Acked-by: Krzysztof Kozlowski +Reviewed-by: Peng Fan +Fixes: e9aa77d413c9 ("soc: imx: add i.MX93 media blk ctrl driver") +Cc: stable@vger.kernel.org +Signed-off-by: Ulf Hansson +Signed-off-by: Greg Kroah-Hartman +--- + include/dt-bindings/power/fsl,imx93-power.h | 1 + + 1 file changed, 1 insertion(+) + +--- a/include/dt-bindings/power/fsl,imx93-power.h ++++ b/include/dt-bindings/power/fsl,imx93-power.h +@@ -11,5 +11,6 @@ + #define IMX93_MEDIABLK_PD_PXP 2 + #define IMX93_MEDIABLK_PD_LCDIF 3 + #define IMX93_MEDIABLK_PD_ISI 4 ++#define IMX93_MEDIABLK_PD_MIPI_PHY 5 + + #endif diff --git a/queue-6.6/fbcon-fix-null-pointer-dereference-for-a-console-without-vc_data.patch b/queue-6.6/fbcon-fix-null-pointer-dereference-for-a-console-without-vc_data.patch new file mode 100644 index 0000000000..82ff864fc4 --- /dev/null +++ b/queue-6.6/fbcon-fix-null-pointer-dereference-for-a-console-without-vc_data.patch @@ -0,0 +1,61 @@ +From 5fae9a928482d4845bca169a3a098789203a1ca4 Mon Sep 17 00:00:00 2001 +From: Ian Bridges +Date: Wed, 24 Jun 2026 16:11:36 -0500 +Subject: fbcon: fix NULL pointer dereference for a console without vc_data + +From: Ian Bridges + +commit 5fae9a928482d4845bca169a3a098789203a1ca4 upstream. + +fbcon_new_modelist() runs when a framebuffer's modelist changes. For each +console mapped to it with fb_display[i].mode set, it reads vc_cons[i].d and +passes the vc_num to fbcon_set_disp(). This assumes a console with a mode +set has a vc_data, but it can be NULL. fbcon_set_disp() sets +fb_display[i].mode before it checks vc_data, and fbcon_deinit() leaves the +mode set after the vc_data is freed. fbcon_new_modelist() then dereferences +the NULL vc_data. + +Keep fb_display[i].mode set only while the console has a vc_data. Check +vc_data before setting the mode in fbcon_set_disp(), and clear the mode in +fbcon_deinit(). The existing mode check in fbcon_new_modelist() then skips +such consoles. + +Reported-by: syzbot+42525d636f430fd5d983@syzkaller.appspotmail.com +Closes: https://syzkaller.appspot.com/bug?extid=42525d636f430fd5d983 +Cc: stable@vger.kernel.org +Assisted-by: Claude:claude-opus-4-8 +Signed-off-by: Ian Bridges +Signed-off-by: Helge Deller +Signed-off-by: Greg Kroah-Hartman +--- + drivers/video/fbdev/core/fbcon.c | 7 ++++--- + 1 file changed, 4 insertions(+), 3 deletions(-) + +--- a/drivers/video/fbdev/core/fbcon.c ++++ b/drivers/video/fbdev/core/fbcon.c +@@ -1183,6 +1183,7 @@ static void fbcon_deinit(struct vc_data + int idx; + + fbcon_free_font(p); ++ p->mode = NULL; + idx = con2fb_map[vc->vc_num]; + + if (idx == -1) +@@ -1361,14 +1362,14 @@ static void fbcon_set_disp(struct fb_inf + + p = &fb_display[unit]; + +- if (var_to_display(p, var, info)) +- return; +- + vc = vc_cons[unit].d; + + if (!vc) + return; + ++ if (var_to_display(p, var, info)) ++ return; ++ + default_mode = vc->vc_display_fg; + svc = *default_mode; + t = &fb_display[svc->vc_num]; diff --git a/queue-6.6/media-uvcvideo-avoid-partial-metadata-buffers.patch b/queue-6.6/media-uvcvideo-avoid-partial-metadata-buffers.patch new file mode 100644 index 0000000000..eb9ef11158 --- /dev/null +++ b/queue-6.6/media-uvcvideo-avoid-partial-metadata-buffers.patch @@ -0,0 +1,82 @@ +From a15b773fe4ffa450b56347cc506b2d1405600f5d Mon Sep 17 00:00:00 2001 +From: Ricardo Ribalda +Date: Fri, 17 Apr 2026 05:19:29 +0000 +Subject: media: uvcvideo: Avoid partial metadata buffers + +From: Ricardo Ribalda + +commit a15b773fe4ffa450b56347cc506b2d1405600f5d upstream. + +If the metadata queue that is empty receives a new buffer while we are +in the middle of processing a frame, the first metadata buffer will +contain partial information. + +Avoid this by tracking the state of the metadata buffer and making sure +that it is in sync with the data buffer. + +Now that we are at it, make sure that we skip buffers of size 1 or 0. +They are not allowed by the spec... but it is a simple check to add and +better be safe than sorry. + +Fixes: 088ead255245 ("media: uvcvideo: Add a metadata device node") +Cc: stable@vger.kernel.org +Signed-off-by: Ricardo Ribalda +Link: https://patch.msgid.link/20260417-uvc-meta-partial-v2-2-31d274af7d2d@chromium.org +Reviewed-by: Hans de Goede +Signed-off-by: Hans de Goede +Signed-off-by: Hans Verkuil +Signed-off-by: Greg Kroah-Hartman +--- + drivers/media/usb/uvc/uvc_video.c | 13 +++++++++---- + 1 file changed, 9 insertions(+), 4 deletions(-) + +--- a/drivers/media/usb/uvc/uvc_video.c ++++ b/drivers/media/usb/uvc/uvc_video.c +@@ -1122,7 +1122,9 @@ static void uvc_video_stats_stop(struct + * uvc_video_decode_end will never be called with a NULL buffer. + */ + static int uvc_video_decode_start(struct uvc_streaming *stream, +- struct uvc_buffer *buf, const u8 *data, int len) ++ struct uvc_buffer *buf, ++ struct uvc_buffer *meta_buf, ++ const u8 *data, int len) + { + u8 header_len; + u8 fid; +@@ -1195,6 +1197,8 @@ static int uvc_video_decode_start(struct + + /* TODO: Handle PTS and SCR. */ + buf->state = UVC_BUF_STATE_ACTIVE; ++ if (meta_buf) ++ meta_buf->state = UVC_BUF_STATE_ACTIVE; + } + + /* +@@ -1411,7 +1415,7 @@ static void uvc_video_decode_meta(struct + ktime_t time; + const u8 *scr; + +- if (!meta_buf || length == 2) ++ if (length <= 2 || !meta_buf || meta_buf->state != UVC_BUF_STATE_ACTIVE) + return; + + has_pts = mem[1] & UVC_STREAM_PTS; +@@ -1528,7 +1532,7 @@ static void uvc_video_decode_isoc(struct + /* Decode the payload header. */ + mem = urb->transfer_buffer + urb->iso_frame_desc[i].offset; + do { +- ret = uvc_video_decode_start(stream, buf, mem, ++ ret = uvc_video_decode_start(stream, buf, meta_buf, mem, + urb->iso_frame_desc[i].actual_length); + if (ret == -EAGAIN) + uvc_video_next_buffers(stream, &buf, &meta_buf); +@@ -1577,7 +1581,8 @@ static void uvc_video_decode_bulk(struct + */ + if (stream->bulk.header_size == 0 && !stream->bulk.skip_payload) { + do { +- ret = uvc_video_decode_start(stream, buf, mem, len); ++ ret = uvc_video_decode_start(stream, buf, meta_buf, mem, ++ len); + if (ret == -EAGAIN) + uvc_video_next_buffers(stream, &buf, &meta_buf); + } while (ret == -EAGAIN); diff --git a/queue-6.6/media-uvcvideo-fix-buffer-sequence-in-frame-gaps.patch b/queue-6.6/media-uvcvideo-fix-buffer-sequence-in-frame-gaps.patch new file mode 100644 index 0000000000..3f35d0403f --- /dev/null +++ b/queue-6.6/media-uvcvideo-fix-buffer-sequence-in-frame-gaps.patch @@ -0,0 +1,67 @@ +From 2f24ac8dd87983a55f0498898f34a5f2b735b802 Mon Sep 17 00:00:00 2001 +From: Ricardo Ribalda +Date: Mon, 23 Mar 2026 09:53:53 +0000 +Subject: media: uvcvideo: Fix buffer sequence in frame gaps + +From: Ricardo Ribalda + +commit 2f24ac8dd87983a55f0498898f34a5f2b735b802 upstream. + +In UVC, the FID flips with every frame. For every FID flip, we increase +the stream sequence number. + +Now, if a FID flips multiple times and there is no data transferred between +the flips, the buffer sequence number will be set to the value of the +stream sequence number after the first flip. + +Userspace uses the buffer sequence number to determine if there have been +missing frames. With the current behaviour, userspace will think that the +gap is in the wrong location. + +This patch modifies uvc_video_decode_start() to provide the correct buffer +sequence number and timestamp. + +Cc: stable@kernel.org +Fixes: 650b95feee35 ("[media] uvcvideo: Generate discontinuous sequence numbers when frames are lost") +Signed-off-by: Ricardo Ribalda +Reviewed-by: Hans de Goede +Signed-off-by: Hans de Goede +Signed-off-by: Hans Verkuil +Signed-off-by: Greg Kroah-Hartman +--- + drivers/media/usb/uvc/uvc_video.c | 17 +++++++++++++---- + 1 file changed, 13 insertions(+), 4 deletions(-) + +--- a/drivers/media/usb/uvc/uvc_video.c ++++ b/drivers/media/usb/uvc/uvc_video.c +@@ -1151,6 +1151,19 @@ static int uvc_video_decode_start(struct + stream->sequence++; + if (stream->sequence) + uvc_video_stats_update(stream); ++ ++ /* ++ * On a FID flip initialize sequence number and timestamp. ++ * ++ * The driver already takes care of injecting FID flips for ++ * UVC_QUIRK_STREAM_NO_FID and UVC_QUIRK_MJPEG_NO_EOF. ++ */ ++ if (buf) { ++ buf->buf.field = V4L2_FIELD_NONE; ++ buf->buf.sequence = stream->sequence; ++ buf->buf.vb2_buf.timestamp = ++ ktime_to_ns(uvc_video_get_time()); ++ } + } + + uvc_video_clock_decode(stream, buf, data, len); +@@ -1191,10 +1204,6 @@ static int uvc_video_decode_start(struct + return -ENODATA; + } + +- buf->buf.field = V4L2_FIELD_NONE; +- buf->buf.sequence = stream->sequence; +- buf->buf.vb2_buf.timestamp = ktime_to_ns(uvc_video_get_time()); +- + /* TODO: Handle PTS and SCR. */ + buf->state = UVC_BUF_STATE_ACTIVE; + if (meta_buf) diff --git a/queue-6.6/media-uvcvideo-fix-sequence-number-when-no-eof.patch b/queue-6.6/media-uvcvideo-fix-sequence-number-when-no-eof.patch new file mode 100644 index 0000000000..4b2eb78bce --- /dev/null +++ b/queue-6.6/media-uvcvideo-fix-sequence-number-when-no-eof.patch @@ -0,0 +1,149 @@ +From f078966ca1fb1b3865d8e6bbe2705cfd277fc637 Mon Sep 17 00:00:00 2001 +From: Ricardo Ribalda +Date: Mon, 23 Mar 2026 09:53:52 +0000 +Subject: media: uvcvideo: Fix sequence number when no EOF + +From: Ricardo Ribalda + +commit f078966ca1fb1b3865d8e6bbe2705cfd277fc637 upstream. + +If the driver could not detect the EOF, the sequence number is increased +twice: + 1) When we enter uvc_video_decode_start() with the old buffer and FID has + flipped => We return -EAGAIN and last_fid is not flipped + 2) When we enter uvc_video_decode_start() with the new buffer. + +Fix this issue by moving the new frame detection logic earlier in +uvc_video_decode_start(). + +This also has some nice side affects: + +- The error status from the new packet will no longer get propagated + to the previous frame-buffer. +- uvc_video_clock_decode() will no longer update the previous frame + buf->stf with info from the new packet. +- uvc_video_clock_decode() and uvc_video_stats_decode() will no longer + get called twice for the same packet. + +Cc: stable@kernel.org +Fixes: 650b95feee35 ("[media] uvcvideo: Generate discontinuous sequence numbers when frames are lost") +Reported-by: Hans de Goede +Closes: https://lore.kernel.org/linux-media/CANiDSCuj4cPuB5_v2xyvAagA5FjoN8V5scXiFFOeD3aKDMqkCg@mail.gmail.com/T/#me39fb134e8c2c085567a31548c3403eb639625e4 +Signed-off-by: Ricardo Ribalda +Reviewed-by: Laurent Pinchart +Reviewed-by: Hans de Goede +Signed-off-by: Hans de Goede +Signed-off-by: Hans Verkuil +Signed-off-by: Greg Kroah-Hartman +--- + drivers/media/usb/uvc/uvc_video.c | 92 +++++++++++++++++++------------------- + 1 file changed, 47 insertions(+), 45 deletions(-) + +--- a/drivers/media/usb/uvc/uvc_video.c ++++ b/drivers/media/usb/uvc/uvc_video.c +@@ -1144,6 +1144,53 @@ static int uvc_video_decode_start(struct + fid = data[1] & UVC_STREAM_FID; + + /* ++ * Mark the buffer as done if we're at the beginning of a new frame. ++ * End of frame detection is better implemented by checking the EOF ++ * bit (FID bit toggling is delayed by one frame compared to the EOF ++ * bit), but some devices don't set the bit at end of frame (and the ++ * last payload can be lost anyway). We thus must check if the FID has ++ * been toggled. ++ * ++ * stream->last_fid is initialized to -1, and buf->bytesused to 0, ++ * so the first isochronous frame will never trigger an end of frame ++ * detection. ++ * ++ * Empty buffers (bytesused == 0) don't trigger end of frame detection ++ * as it doesn't make sense to return an empty buffer. This also ++ * avoids detecting end of frame conditions at FID toggling if the ++ * previous payload had the EOF bit set. ++ */ ++ if (fid != stream->last_fid && buf && buf->bytesused != 0) { ++ uvc_dbg(stream->dev, FRAME, ++ "Frame complete (FID bit toggled)\n"); ++ buf->state = UVC_BUF_STATE_READY; ++ ++ return -EAGAIN; ++ } ++ ++ /* ++ * Some cameras, when running two parallel streams (one MJPEG alongside ++ * another non-MJPEG stream), are known to lose the EOF packet for a frame. ++ * We can detect the end of a frame by checking for a new SOI marker, as ++ * the SOI always lies on the packet boundary between two frames for ++ * these devices. ++ */ ++ if (stream->dev->quirks & UVC_QUIRK_MJPEG_NO_EOF && ++ (stream->cur_format->fcc == V4L2_PIX_FMT_MJPEG || ++ stream->cur_format->fcc == V4L2_PIX_FMT_JPEG) && ++ buf && buf->bytesused != 0) { ++ const u8 *packet = data + header_len; ++ ++ if (len >= header_len + 2 && ++ packet[0] == 0xff && packet[1] == JPEG_MARKER_SOI) { ++ buf->state = UVC_BUF_STATE_READY; ++ buf->error = 1; ++ stream->last_fid ^= UVC_STREAM_FID; ++ return -EAGAIN; ++ } ++ } ++ ++ /* + * Increase the sequence number regardless of any buffer states, so + * that discontinuous sequence numbers always indicate lost frames. + */ +@@ -1210,51 +1257,6 @@ static int uvc_video_decode_start(struct + meta_buf->state = UVC_BUF_STATE_ACTIVE; + } + +- /* +- * Mark the buffer as done if we're at the beginning of a new frame. +- * End of frame detection is better implemented by checking the EOF +- * bit (FID bit toggling is delayed by one frame compared to the EOF +- * bit), but some devices don't set the bit at end of frame (and the +- * last payload can be lost anyway). We thus must check if the FID has +- * been toggled. +- * +- * stream->last_fid is initialized to -1, so the first isochronous +- * frame will never trigger an end of frame detection. +- * +- * Empty buffers (bytesused == 0) don't trigger end of frame detection +- * as it doesn't make sense to return an empty buffer. This also +- * avoids detecting end of frame conditions at FID toggling if the +- * previous payload had the EOF bit set. +- */ +- if (fid != stream->last_fid && buf->bytesused != 0) { +- uvc_dbg(stream->dev, FRAME, +- "Frame complete (FID bit toggled)\n"); +- buf->state = UVC_BUF_STATE_READY; +- return -EAGAIN; +- } +- +- /* +- * Some cameras, when running two parallel streams (one MJPEG alongside +- * another non-MJPEG stream), are known to lose the EOF packet for a frame. +- * We can detect the end of a frame by checking for a new SOI marker, as +- * the SOI always lies on the packet boundary between two frames for +- * these devices. +- */ +- if (stream->dev->quirks & UVC_QUIRK_MJPEG_NO_EOF && +- (stream->cur_format->fcc == V4L2_PIX_FMT_MJPEG || +- stream->cur_format->fcc == V4L2_PIX_FMT_JPEG)) { +- const u8 *packet = data + header_len; +- +- if (len >= header_len + 2 && +- packet[0] == 0xff && packet[1] == JPEG_MARKER_SOI && +- buf->bytesused != 0) { +- buf->state = UVC_BUF_STATE_READY; +- buf->error = 1; +- stream->last_fid ^= UVC_STREAM_FID; +- return -EAGAIN; +- } +- } +- + stream->last_fid = fid; + + return header_len; diff --git a/queue-6.6/rxrpc-fix-leak-of-released-call-in-recvmsg-msg_peek.patch b/queue-6.6/rxrpc-fix-leak-of-released-call-in-recvmsg-msg_peek.patch new file mode 100644 index 0000000000..71bec36a62 --- /dev/null +++ b/queue-6.6/rxrpc-fix-leak-of-released-call-in-recvmsg-msg_peek.patch @@ -0,0 +1,40 @@ +From 4bdb9e471f5b1ac9cbe4add5de7ff085a0ec303c Mon Sep 17 00:00:00 2001 +From: David Howells +Date: Wed, 24 Jun 2026 17:38:17 +0100 +Subject: rxrpc: Fix leak of released call in recvmsg(MSG_PEEK) + +From: David Howells + +commit 4bdb9e471f5b1ac9cbe4add5de7ff085a0ec303c upstream. + +Fix rxrpc_recvmsg() to also drop the ref it holds on an already-released +call if MSG_PEEK is in force (the function holds a ref on the call +irrespective of whether MSG_PEEK is specified or not). + +Fixes: 962fb1f651c2 ("rxrpc: Fix recv-recv race of completed call") +Link: https://sashiko.dev/#/patchset/20260616155749.2125907-1-dhowells%40redhat.com +Signed-off-by: David Howells +cc: Marc Dionne +cc: Jeffrey Altman +cc: Simon Horman +cc: linux-afs@lists.infradead.org +cc: stable@kernel.org +Link: https://patch.msgid.link/20260624163819.3017002-11-dhowells@redhat.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + net/rxrpc/recvmsg.c | 3 +-- + 1 file changed, 1 insertion(+), 2 deletions(-) + +--- a/net/rxrpc/recvmsg.c ++++ b/net/rxrpc/recvmsg.c +@@ -429,8 +429,7 @@ try_again: + if (test_bit(RXRPC_CALL_RELEASED, &call->flags)) { + rxrpc_see_call(call, rxrpc_call_see_already_released); + mutex_unlock(&call->user_mutex); +- if (!(flags & MSG_PEEK)) +- rxrpc_put_call(call, rxrpc_call_put_recvmsg); ++ rxrpc_put_call(call, rxrpc_call_put_recvmsg); + goto try_again; + } + diff --git a/queue-6.6/rxrpc-rxrpc_verify_data-ensure-rx_dec_buffer-alloc.patch b/queue-6.6/rxrpc-rxrpc_verify_data-ensure-rx_dec_buffer-alloc.patch new file mode 100644 index 0000000000..aed7995d37 --- /dev/null +++ b/queue-6.6/rxrpc-rxrpc_verify_data-ensure-rx_dec_buffer-alloc.patch @@ -0,0 +1,52 @@ +From 16c8ae9735c5bd7e54dd7478d6348e0fc860842d Mon Sep 17 00:00:00 2001 +From: Jeffrey Altman +Date: Tue, 9 Jun 2026 15:09:05 +0100 +Subject: rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc + +From: Jeffrey Altman + +commit 16c8ae9735c5bd7e54dd7478d6348e0fc860842d upstream. + +rxrpc_recvmsg_data() calls rxrpc_verify_data() whenever the +rxrpc_call.rx_dec_buffer is unallocated and assumes that upon +successful return that rx_dec_buffer must be allocated. +However, rxrpc_verify_data() does not request an allocation if +the rxrpc_skb_priv.len is zero. + +In addition, failure to allocate rx_dec_buffer will result in a +call to skb_copy_bits() with a NULL destination which can +trigger a NULL pointer dereference. + +To prevent these issues rxrpc_verify_data() is modified to +always attempt to allocate the rxrpc_call.rx_dec_buffer if it +is NULL. + +This issue was identified with assistance of a private +sashiko instance. + +Fixes: d2bc90cf6c75cb ("rxrpc: Fix DATA decrypt vs splice() by copying data to buffer in recvmsg") +Reported-by: Simon Horman +Signed-off-by: Jeffrey Altman +Signed-off-by: David Howells +cc: Jiayuan Chen +cc: Marc Dionne +cc: linux-afs@lists.infradead.org +cc: stable@kernel.org +Link: https://patch.msgid.link/20260609140911.838677-2-dhowells@redhat.com +Signed-off-by: Jakub Kicinski +Signed-off-by: Greg Kroah-Hartman +--- + net/rxrpc/recvmsg.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/net/rxrpc/recvmsg.c ++++ b/net/rxrpc/recvmsg.c +@@ -157,7 +157,7 @@ static int rxrpc_verify_data(struct rxrp + struct rxrpc_skb_priv *sp = rxrpc_skb(skb); + int ret; + +- if (sp->len > call->rx_dec_bsize) { ++ if (sp->len > call->rx_dec_bsize || !call->rx_dec_buffer) { + /* Make sure we can hold a 1412-byte jumbo subpacket and make + * sure that the buffer size is aligned to a crypto blocksize. + */ diff --git a/queue-6.6/serial-8250_omap-clear-rx_running-on-zero-length-dma-completes.patch b/queue-6.6/serial-8250_omap-clear-rx_running-on-zero-length-dma-completes.patch new file mode 100644 index 0000000000..5c9e450ee2 --- /dev/null +++ b/queue-6.6/serial-8250_omap-clear-rx_running-on-zero-length-dma-completes.patch @@ -0,0 +1,50 @@ +From 061b627ba534230a18ec4d7251562af12325d06a Mon Sep 17 00:00:00 2001 +From: Matthias Feser +Date: Tue, 26 May 2026 07:35:09 +0000 +Subject: serial: 8250_omap: clear rx_running on zero-length DMA completes + +From: Matthias Feser + +commit 061b627ba534230a18ec4d7251562af12325d06a upstream. + +On AM33xx RX DMA only triggers when the FIFO reaches the +configured threshold (typically 48 bytes). For smaller bursts +no DMA request is issued and the FIFO is drained by RX timeout. + +In this case __dma_rx_do_complete() can legitimately see count == 0. + +The current code exits early in this case and does not clear +dma->rx_running, leaving the DMA state inconsistent. This can +prevent RX DMA from restarting and may cause +omap_8250_rx_dma_flush() to fail, marking DMA as broken. + +Fix this by clearing dma->rx_running once the DMA transfer has +completed or been terminated, even if no data was transferred. + +Fixes: a5fd8945a478 ("serial: 8250: 8250_omap.c: Clear DMA RX running status only after DMA termination is done") +Cc: stable +Signed-off-by: Matthias Feser +Reviewed-by: Moteen Shah +Link: https://patch.msgid.link/BE3P281MB55155F2F5795E411F5A65282EE0B2@BE3P281MB5515.DEUP281.PROD.OUTLOOK.COM +Signed-off-by: Greg Kroah-Hartman +Signed-off-by: Greg Kroah-Hartman +--- + drivers/tty/serial/8250/8250_omap.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/drivers/tty/serial/8250/8250_omap.c ++++ b/drivers/tty/serial/8250/8250_omap.c +@@ -953,11 +953,12 @@ static void __dma_rx_do_complete(struct + dev_err(p->port.dev, "teardown incomplete\n"); + } + } ++ ++ dma->rx_running = 0; + if (!count) + goto out; + ret = tty_insert_flip_string(tty_port, dma->rx_buf, count); + +- dma->rx_running = 0; + p->port.icount.rx += ret; + p->port.icount.buf_overrun += count - ret; + out: diff --git a/queue-6.6/serial-msm-disable-dma-for-kernel-console-uart.patch b/queue-6.6/serial-msm-disable-dma-for-kernel-console-uart.patch new file mode 100644 index 0000000000..b142830562 --- /dev/null +++ b/queue-6.6/serial-msm-disable-dma-for-kernel-console-uart.patch @@ -0,0 +1,52 @@ +From 22dd2777e6c180e1c945b00f6d18550979436324 Mon Sep 17 00:00:00 2001 +From: Stephan Gerhold +Date: Mon, 6 Jul 2026 20:03:32 +0200 +Subject: serial: msm: Disable DMA for kernel console UART + +From: Stephan Gerhold + +commit 22dd2777e6c180e1c945b00f6d18550979436324 upstream. + +At the moment, concurrent writes from userspace and the kernel to the +console can trigger a race condition that results in an infinite loop of +the same messages printed over and over again. This is most likely to +happen during system startup or shutdown when the init system starts/stops +a large number of system services that interact with various kernel code. + +When userspace writes to the TTY device, the driver initiates an +asynchronous DMA transfer and releases the port lock. At the same moment, +the kernel printk path might grab the port lock and re-configure the UART +controller for PIO, without waiting for the DMA operation to complete. It +seems like this collision results in zero progress being reported for the +DMA engine, so the same text is printed to the console over and over again. + +For the kernel console, we want a reliable output path that will be +functional even during crashes etc. So rather than implementing complex +code to synchronize the kernel console write routines with the userspace +DMA write routines, simply disable DMA for the console UART instance. + +Similar checks exist in many other serial drivers, e.g. 8250_port.c, +imx.c, sh-sci.c etc. + +Cc: stable +Fixes: 3a878c430fd6 ("tty: serial: msm: Add TX DMA support") +Signed-off-by: Stephan Gerhold +Acked-by: Konrad Dybcio +Link: https://patch.msgid.link/20260706-serial-msm-console-dma-collision-v1-1-3179b8cb1d89@linaro.org +Signed-off-by: Greg Kroah-Hartman +--- + drivers/tty/serial/msm_serial.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +--- a/drivers/tty/serial/msm_serial.c ++++ b/drivers/tty/serial/msm_serial.c +@@ -1221,7 +1221,8 @@ static int msm_startup(struct uart_port + data |= MSM_UART_MR1_AUTO_RFR_LEVEL0 & rfr_level; + msm_write(port, data, MSM_UART_MR1); + +- if (msm_port->is_uartdm) { ++ /* Disable DMA for console to prevent PIO/DMA collisions */ ++ if (msm_port->is_uartdm && !uart_console(port)) { + msm_request_tx_dma(msm_port, msm_port->uart.mapbase); + msm_request_rx_dma(msm_port, msm_port->uart.mapbase); + } diff --git a/queue-6.6/series b/queue-6.6/series index f69152770e..4c778141ca 100644 --- a/queue-6.6/series +++ b/queue-6.6/series @@ -342,3 +342,16 @@ bpf-restrict-jit-predictor-flush-to-cbpf.patch bpf-skip-redundant-ibpb-in-pack-allocator.patch bpf-prefer-packs-that-won-t-trigger-an-ibpb-flush-on.patch bpf-prefer-dirty-packs-for-ebpf-allocations.patch +media-uvcvideo-avoid-partial-metadata-buffers.patch +media-uvcvideo-fix-buffer-sequence-in-frame-gaps.patch +media-uvcvideo-fix-sequence-number-when-no-eof.patch +dt-bindings-media-sun4i-a10-video-engine-add-interconnect-properties.patch +dt-bindings-power-imx93-add-mipi-phy-power-domain.patch +serial-msm-disable-dma-for-kernel-console-uart.patch +serial-8250_omap-clear-rx_running-on-zero-length-dma-completes.patch +rxrpc-rxrpc_verify_data-ensure-rx_dec_buffer-alloc.patch +rxrpc-fix-leak-of-released-call-in-recvmsg-msg_peek.patch +afs-fix-netns-teardown-to-cancel-the-preallocation-charger.patch +afs-fix-null-pointer-dereference-in-afs_get_tree.patch +afs-fix-further-netns-teardown-to-cancel-the-preallocation-charger.patch +fbcon-fix-null-pointer-dereference-for-a-console-without-vc_data.patch