Regression in rsync since the glibc 2.32 update (including the 2.33 update too)

tadgy · 02-22-2021, 01:41 PM

There is a regression in rsync since version 3.2.3 tag -2 (including the post mass rebuild for glibc 2.33 version with the -3 tag) which prevents the setting of permissions when /proc is not available - which occurs when using the option:

Code:

use chroot = true

(or leaving it unset since true is the default)

To demonstrate, just create a rsync daemon process that utilises "use chroot" option and try to upload a file to a repository - it produces the error:

Code:

Operation not supported

This is apparently due to glibc implementing lchmod() in a less than perfect way as discussed here: https://github.com/WayneD/rsync/issues/109 and in various distributions specific bugtrackers.

The solution, as detailed in the above link, is to patch rsync to not detect the lchmod() call on Linux hosts - there is already a commit in git to implement this.

I've had to revert the rsync package on slackware.uk to the (pre glibc 2.32) version ending with the -1 tag, which is unaffected.

Hope this can get fixed ASAP

Didier Spaier · 02-23-2021, 06:23 AM

Code:

Mon Feb 22 20:58:01 UTC 2021
<snip>
n/rsync-3.2.3-x86_64-4.txz:  Rebuilt.
  Don't use lchmod(). Thanks to tadgy.

gus3 · 02-23-2021, 07:53 PM

A mention in the ChangeLog.txt. Good on ya, mate.