On 26/09/2026 04:35, Collin Funk wrote:
I pushed this one after testing it on GNU/Linux, macOS, FreeBSD, and
NetBSD to confirm the memory limit wouldn't cause any trouble.
Thanks, Pádraig, for finding the version the bug was introduced in.
we should also probably apply the attached
to document that readlink is impacted also.
cheers,
Padraig
From 34e0d25617b4ca46f2277e4485948947b3c4c422 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?P=C3=A1draig=20Brady?= <[email protected]>
Date: Tue, 29 Sep 2026 14:04:17 +0100
Subject: [PATCH] doc: NEWS: mention readlink also had an infinite loop bug
* NEWS: Mention the readlink and realpath options
that trigger the infinite loop bug.
---
NEWS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 1cb5fb2e3..ab6f7beb3 100644
--- a/NEWS
+++ b/NEWS
@@ -4,7 +4,8 @@ GNU coreutils NEWS -*- outline -*-
** Bug fixes
- 'realpath' no longer loops infinitely when resolving a symbolic link which
+ 'realpath' without -s, or 'readlink' with -e,-f,-m no longer
+ loop infinitely when resolving a symbolic link which
resolves to a path beginning with the symbolic link itself.
[bug introduced in coreutils-9.0]
--
2.55.0
