Bug#1115729: Stable fix request: error in internal cancellation syscall handling, corrupting copy_file_range syscall return value
Joel Johnson wrote on Fri, Sep 19, 2025 at 08:45:10 -0600:
> Package: libc
> Version: 2.41-12
> Severity: grave
>
> (Marking as grave since it leads to data loss)
>
> An issue has been identified and fixed upstream causing data loss using
> copy_file_range. It is most prominent with OpenZFS but also appears to have
> potential impacts on FUSE. I would request that this be patched for a trixie
> update. I didn't see any existing issue for this, apologies if it's a
> duplicate.
>
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7107bebf19286f42dcb0a97581137a5893c16206
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=33245
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=79139
Morning. I haven't run into the buggy behaviour, but I did run into
this ticket in the apt-listchanges(1) output during an upgrade, and I'm
not sure whether the bug would impact me if I proceeded with the upgrade.
Two questions:
1. Considering this bug is described as "data loss" and appears in
apt-listchanges(1) output for folks upgrading oldstable→stable, could
someone please summarize situations in which the bug is known /not/
to occur even under 2.41-12 (currently in trixie)?
I'm not asking for an exhaustive list; just for common known-good
scenarios. Something of the form "It's safe to upgrade to trixie and
glibc/2.41-12 as long as you don't do X, Y, or Z" would be great.
2. The bug is fixed in 2.41-2 in experimental, but hasn't yet been fixed
in either sid or trixie (as requested by the OP). Is the bug
expected to be fixed in trixie?
I'm not sure what blocks 2.42 from being uploaded to sid.
I've verified the patch above (7107bebf19286f42dcb0a97581137a5893c16206)
applies cleanly to the version in trixie. I've tried to build it,
too; the build didn't actually pass, but at least it failed in the
same way with the patch and without it, and the failure may well be
unrelated to the patch. (I was building in a new trixie chroot.)
Thanks,
Daniel
P.S. The build failure:
> > +---------------------------------------------------------------------+
> > | Passed regression testing. Give yourself a hearty pat on the back. |
> > +---------------------------------------------------------------------+
> > touch /tmp/wd/glibc-2.41/stamp-dir/check_i386
> > Flavour cross-compiled, tests have been skipped.
> > touch /tmp/wd/glibc-2.41/stamp-dir/check_x32
> > CHECK SUMMARY
> > check for check_i386 passed
> > check for check_libc failed
> > FAIL: intl/tst-gettext
> > FAIL: io/tst-lchmod
> > make: *** [debian/rules.d/build.mk:195: build-arch-post-check] Error 1
> > rm /tmp/wd/glibc-2.41/stamp-dir/configure_libc /tmp/wd/glibc-2.41/stamp-dir/mkbuilddir_x32 /tmp/wd/glibc-2.41/stamp-dir/configure_i386 /tmp/wd/glibc-2.41/stamp-dir/mkbuilddir_libc /tmp/wd/glibc-2.41/stamp-dir/configure_x32 /tmp/wd/glibc-2.41/stamp-dir/mkbuilddir_i386
> > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Reply to: