On Thu, 5 Feb 2026, Paul Gevers wrote:
Hi Tim,
On Sun, 16 Nov 2025 19:51:13 +0000 (GMT) Tim Woodall
<[email protected]> wrote:
I'm attaching a set of patches that I think includes a resolution of this
bug.
I've not yet done more than very basic testing but I'm expecting to start
running this in live from tomorrow backported to bookworm.
The patches are as follows:
fix-race.patch - supplied previously but acng is unusable without this.
fuse3-debian.patch - the changes to the debian directory to resolve this
bug.
fuse3.patch - the changes to the source to resolve this bug.
deprecation-debian.patch - fix to resolve a deprecation warning in the
debian directory
deprecation.patch - fix to remove OpenSSL deprecation warnings plus extra
runtime tests for SHA256 and SHA512 correctness
buildhelper.patch - trivial change to use cmake if available and generate
compile-commands.json
I'm recently seeing a lot of failures with apt-cacher-ng on the loong64 host
of ci.debian.net, which appeared to me to be related to parallel downloads of
InRelease. Chris only took the fuse3.patch to fix bug 1084459 (the bug where
this bug was cloned from) and now I'm wondering if the race you fixed with
fix-race.patch is more likely to occur after the switch to fuse3. What
happens if the race isn't fixed and two requests for the same file come in?
What I'm seeing is a lot of failures with this error by apt:
503 Cannot allocate memory [IP: 127.0.0.1 3142]
Paul
Hi, the fuse3 patch has nothing at all to do with the races. It's only
relevant for acngfs (which probably isn't worth keeping in the code TBH
but I thought a patch to update to fuse3 was more likely to be accepted.)
The data races are down to concurrent downloads. They result in a
corrupted file in acng's cache and the only fix is to delete the corrupt
file and try again. Release files update often enough that wait is also
an option, but a corrupted kernel deb, for example, will stay broken for
ages.
I don't know about memory errors, the common symptom is a hash sum
mismatch. But it's been so long now since I had an issue that I've
forgotten details of the posdible failures. From what I recall, the apt
failures when it happens vary, hangs forever, hash mismatch, 503 errors.
I could believe that acng could run out of memory as a result of this
but I can't say if it's an error I ever saw.
Tim.
