netdev - Re: [PATCH net-next 2/2] net: ipv6: ioam6: fix double reallocation

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 for Android: free password hash cracker in your pocket

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

Message-ID: <046af9bf-6693-414b-9c65-1a1f982a66a6@uliege.be>
Date: Thu, 10 Apr 2025 18:16:42 +0200
From: Justin Iurman <justin.iurman@...ege.be>
To: netdev@...r.kernel.org
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, horms@...nel.org
Subject: Re: [PATCH net-next 2/2] net: ipv6: ioam6: fix double reallocation

On 4/10/25 17:24, Justin Iurman wrote:
> If the dst_entry is the same post transformation (which is a valid use
> case for IOAM), we don't add it to the cache to avoid a reference loop.
> Instead, we use a "fake" dst_entry and add it to the cache as a signal.
> When we read the cache, we compare it with our "fake" dst_entry and
> therefore detect if we're in the special case.

FYI: double reallocation also happens in seg6_iptunnel and rpl_iptunnel 
and was fixed previously. However, they don't need this patch, since 
it's for the case "dst_entry is the same post transformation", which is 
due to pathological configurations in their cases.