buffer overflow in recv_file_entry

Jakob Unterwurzacher jakobunt at gmail.com
Tue Feb 18 11:09:36 UTC 2025


I have a backup job failing because of a long path with error message
(full output below, [1]):

> overflow: xflags=0x2078 l1=255 l2=775 lastname=looooong path....
> ERROR: buffer overflow in recv_file_entry [receiver]

It looks like the remote system (a Hetzner Storagebox) for some reason
has a maximum path length of 1024 (like in [2]), and I cannot change
rsync on the remote end.

My question is what I can do on the local end to not abort the rsync
run on long paths. I would like rsync to skip the file and move on.

Maybe compile the local rsync with MAXPATHLEN=1024?

Thanks,
Jakob


----
[1]:
overflow: xflags=0x2078 l1=255 l2=775
lastname=zzzzzzzzzzzzzzzzzzzzzzzzzzzzz/oIyIv1oSe8cavjje5iDXHA/cyKn9tCmlJaEMPdiMsv5ng/GAshj2PYPbZXURpANQ4boA/W397CKDs3eTN4lS7b5EJIg/sLxSBhXyCF5lzCyuSdTj2g/31D21Kpqry9WYfHSktHMmg/d5SbmKip6aoFlFq1cLAaPkegvpXYUQuNJp11sGv2Z3I/3sp1R1vkH8mcTHM-yeMpFQ/AjZaHYrMOm69GUCb0HwCukeUBJKFiaJyKe7MVf6xEgHcxeYR0lvAp44dgL8ZI6sVSuxRpR1uLBmppIpneaa1fJa1bSjnUyd9VsbY7HoISQF25ULXZZbYXrwrHnVjMGD8/2F6-BhftWDSqI5ZwHGPsZkEM8kbXvx5dMGE3S9Yd88kqcd837g1GWb1l1ciqGxMJ-_r8iAHOIk5ThkR4K3IF58sqFbYa8INKjqLQj9z4z8zIzRcI4Guk7wNlLQGYzrMT7vqN-teL9_ZLdpZMDPuGSA/cC7nTb7Gp0wYtG9MsYR9g8bfzc7zAE5y89I6n0xBnP2xICvGjzMdp0jiPVxakb3xVy1NxfSjzL9jMUNw6kLx24MglO_ZdmobL6ry08udomN-oTJ6zv8Il1BUrGWl2FGe/MEglgdbkQjtmC3Bfyme2RI9lbDeGkvFqTnaNPizwCkictXMqxbznyKKVbc6-hR4POhueRrKDmigfcNxtCAx9ZdwIV33wFWJiMI6WjY5RTGr7ujFvUrsG8K_wdPSUVNvU/gocryptfs.diriv
[receiver]
ERROR: buffer overflow in recv_file_entry [receiver]
rsync error: error allocating core memory buffers (code 22) at
util2.c(145) [receiver=3.2.2]
Command exited with non-zero status 22
967.19user 2034.19system 7:24:49elapsed 11%CPU (0avgtext+0avgdata
4533876maxresident)k

[2]: https://rsync.samba.narkive.com/sO9WR3YT/3-0-5-error-buffer-overflow-in-recv-file-entry-generator



More information about the rsync mailing list