Hi,

On Wed Jan 21, 2026 at 11:41 AM CET, Paul Barker wrote:
[...]
> diff --git 
> a/meta/recipes-core/coreutils/coreutils/0001-fix-lseek-copy-loop.patch 
> b/meta/recipes-core/coreutils/coreutils/0001-fix-lseek-copy-loop.patch
> new file mode 100644
> index 000000000000..75286dc43cb9
> --- /dev/null
> +++ b/meta/recipes-core/coreutils/coreutils/0001-fix-lseek-copy-loop.patch
> @@ -0,0 +1,35 @@
> +From bd528f923482223649aa84be7d131e69356149da Mon Sep 17 00:00:00 2001
> +From: =?UTF-8?q?P=C3=A1draig=20Brady?= <[email protected]>
> +Date: Sun, 4 Jan 2026 12:45:46 +0000
> +Subject: [PATCH] copy: fix possible infinite loop with SEEK_HOLE
> +
> +Commit v9.8-95-g4c0cf3864 intended to initialize
> +ext_start to src_pos, as was described at:
> +https://lists.gnu.org/r/coreutils/2025-11/msg00035.html
> +However ipos was inadvertently used, which is only
> +valid the first time through the loop.
> +
> +* src/copy-file-data.c (lseek_copy): Use scan_inference->hole_start
> +only with the initial offset passed to lseek_copy().
> +* NEWS: Mention the bug fix.
> +Reported at https://github.com/coreutils/coreutils/issues/159
> +
> +Upstream-Status: Backport (commit bd528f923482223649aa84be7d131e69356149da)

I wonder if having the reason between brackets and not parenthesis is important
here? That's what we document but they could interchangeable, I don't know for
sure.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#229809): 
https://lists.openembedded.org/g/openembedded-core/message/229809
Mute This Topic: https://lists.openembedded.org/mt/117379155/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to