[Bug 1746995] Re: regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication fails

[Steve Beattie]

Hi,

Florian has a proposed patch submitted to rsync upstream
https://lists.samba.org/archive/rsync/2018-February/031478.html for
review. I've incorporated Florian's patch into test packages for Ubuntu
16.04 and 17.10 (and will have other releases later) in a test ppa at
https://launchpad.net/~sbeattie/+archive/ubuntu/lp1746995 . It would be
appreciated if people seeing this issue with glusterfs' geo-replication
can confirm that the patched version of rsync in that ppa address the
issue for them.

Thanks, and my apologies for your inconvenience.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1746995

Title:
  regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication
  fails

Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  Since somewhere in the Jan 14-18 range my glusterfs georeplication
  reports Faulty. Georeplication uses rsync internally, and tracking
  this this down leads to an exit code 3 out of rsync.

  I have no stacktraces myself, but I found this report about the same
  problem:

  https://www.spinics.net/lists/gluster-users/msg33568.html

  with traces:

  
  strace rsync :

  30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0
  30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0
  30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0
  30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0
  30743 23:34:47 close(3)                 = 0
  30743 23:34:47 write(2, "rsync: getcwd(): No such file or directory (2)", 46) = 46
  30743 23:34:47 write(2, "\n", 1)        = 1
  30743 23:34:47 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 0x7fa4fdf404b0}, NULL, 8) = 0
  30743 23:34:47 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 0x7fa4fdf404b0}, NULL, 8) = 0
  30743 23:34:47 write(2, "rsync error: errors selecting input/output files, dirs (code 3) at util.c(1056) [Receiver=3.1.1]", 96) = 96
  30743 23:34:47 write(2, "\n", 1)        = 1
  30743 23:34:47 exit_group(3)            = ?
  30743 23:34:47 +++ exited with 3 +++

  
  The Changelog of glibc mentions that getcwd has been changed:

    * SECURITY UPDATE: Buffer underflow in realpath()
      - debian/patches/any/cvs-make-getcwd-fail-if-path-is-no-absolute.diff:
        Make getcwd(3) fail if it cannot obtain an absolute path
      - CVE-2018-1000001

  and downgrading glibc to (2.23-0ubuntu3) indeed fixes my
  georeplication problem. 0ubuntu3 is the latest version that is
  available in the repositories, other than 0ubuntu10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1746995/+subscriptions