Hi,

You know I'm getting the feeling it is me and not you who is confused here...

Yeah sorry I'm not sure how I messed this up. I was bouncing around many different versions of both the kernel module and the userspace program load testing it in different ways to force the different bugs and I guess I just somehow screwed this up? I'm not sure how Claude missed it, but I'm in the driver's seat here so I should have found that myself. Can't blame robots for everything.

In any case, thanks so much for the clarification! I will adapt the debian bug report I created to instead cherry-pick the commits from the 2.6.20 branch instead of concocting commits of my own monstrosity like I did.

Sorry for the noise! Thanks for the info this is the best possible outcome since you fixed my problem before I even asked for it!

Cheers,
Thomas

On 6/25/26 22:11, Gert Doering wrote:
Hi,

On Thu, Jun 25, 2026 at 04:06:16PM +0200, Thomas Nyberg via Openvpn-devel wrote:
Full disclosure: I used Claude for a lot of this work including the text
below. That said, I was very thorough in all the testing I've done here and
been careful to verify the bugs and was careful to read through the details
below. But I don't want to pretend like there weren't robots involved...

7791f535 ("dco: process messages immediately after read", fixes #919) is in
master and release/2.7, but not in release/2.6. 2.6.x DCO server deployments
are still exposed to the underlying bug, and it bites hard at scale. I'd
like to ask whether you'd consider a release/2.6 backport -- and, since
it can't be > a straight cherry-pick, what form you'd prefer.

I'm confused.  My release/2.6 git log says

commit e78a8af2f5ce5ef3bbfefc2dc8efeca84027c018
Author: Ralf Lici <[email protected]>
Date:   Tue Apr 21 10:49:01 2026 +0200

     dco: backport immediate notification processing on Linux and FreeBSD
Backport the immediate DCO message processing model from commit 7791f53
     ("dco: process messages immediately after read").
...
     Github: OpenVPN/openvpn#900
     Github: OpenVPN/openvpn#918
     Github: OpenVPN/openvpn#931
     Github: fixes OpenVPN/openvpn#919
     Github: closes OpenVPN/openvpn#945

... and this went into 2.6.20 release.

Can you ask claude what it is talking about?

gert





_______________________________________________
Openvpn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to