linux-kernel - Re: [PATCH] libceph: handle EADDRNOTAVAIL more gracefully

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260211073317.M73faj98@linutronix.de>
Date: Wed, 11 Feb 2026 08:33:17 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Ionut Nechita (Wind River)" <ionut.nechita@...driver.com>
Cc: idryomov@...il.com, amarkuze@...hat.com, ceph-devel@...r.kernel.org,
	clrkwllms@...nel.org, ionut_n2001@...oo.com, jkosina@...e.com,
	jlayton@...nel.org, linux-kernel@...r.kernel.org,
	linux-rt-devel@...ts.linux.dev, rostedt@...dmis.org,
	sage@...dream.net, slava@...eyko.com, superm1@...nel.org,
	xiubli@...hat.com
Subject: Re: [PATCH] libceph: handle EADDRNOTAVAIL more gracefully

On 2026-02-10 09:19:29 [+0200], Ionut Nechita (Wind River) wrote:
> You're absolutely right that if the address became valid in 1-2s, the
> third or fourth attempt would succeed. The problem is that in our
> environment, EADDRNOTAVAIL does NOT resolve in 1-2 seconds. That was
> an incorrect generalization from simple DAD scenarios.
> 
> From the production dmesg (6.12.0-1-rt-amd64, StarlingX on Dell
> PowerEdge R720, IPv6-only Ceph cluster), the EADDRNOTAVAIL condition
> persists for much longer:
> 
>   13:20:52 - mon0 session lost, hunting begins, first error -99
>   13:57:03 - mon0 session finally re-established

My question again, is this specific to PREEMPT_RT or would also happen
in a !PREEMPT_RT setup?

Sebastian