rsync - Oct 2003 - rsync via ssh dumps core after being interrupted

Hi,

I'm using rsync (version 2.5.5  protocol version 26) on RedHat Linux 8.0:

rsync -ae ssh /tmp/junk/ otherhost:/tmp/junk

If I interrupt rsync (^C), sometimes rsync on the other host dumps core 
or uses all (!) available memory and all CPU.

gdb on a core file:

$ gdb -q /usr/bin/rsync /tmp/core.4576
(no debugging symbols found)...
Core was generated by `/usr/bin/rsync --server --sender -logDtprz 
--delete . /var/log/tomcat18039'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libpopt.so.0...done.
Loaded symbols for /usr/lib/libpopt.so.0
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/i686/libc.so.6...done.
Loaded symbols for /lib/i686/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
#0  0x42047ca7 in vfprintf () from /lib/i686/libc.so.6
(gdb) bt
#0  0x42047ca7 in vfprintf () from /lib/i686/libc.so.6
Cannot access memory at address 0xb6fc9f10
(gdb)

This happens on different host/host combinations. All hosts are on RHL 
8.0 with latest patches.

Regards,
Bernie

On Fri, Oct 31, 2003 at 09:18:59AM +0100, Bernhard Erdmann
wrote:
> If I interrupt rsync (^C), sometimes rsync on the other host dumps core 
> or uses all (!) available memory and all CPU.
Sounds like the bug that was handled by this fix in 2.5.6:

 * Prevent infinite recursion in cleanup code under certain circumstances.
   (Sviatoslav Sviridov and Marc Espie)

I'd suggest upgrading to 2.5.6.

..wayne..

I could not reproduce the error you describe on 2.5.5 protocol
version 26 - mine ran fine from one RHL8 box to another RHL8
box - both with that same version of rsync on them.  I tried
it several times with a large file in /tmp/junk to make sure
the rsync was still running when I hit Ctrl-C.  I couldn't
get it to leave processes lying around, nor could I get it to
dump core.

I found this posting in the rsync archives:

  http://www.mail-archive.com/rsync@lists.samba.org/msg06132.html

Fyi, it looks to me like the 2nd patch (cleanup.c) was incorporated
into the 2.5.6 code - the 2.5.6 code looks slightly different,
but the idea is there to stop "occasional infinite recursion",
which presumably is the cause of the problem.

-- 
Hardy Merrill
Red Hat, Inc.

Bernhard Erdmann [be@berdmann.de] wrote:
> Hi,
> 
> I'm using rsync (version 2.5.5  protocol version 26) on RedHat Linux
8.0:
> 
> rsync -ae ssh /tmp/junk/ otherhost:/tmp/junk
> 
> If I interrupt rsync (^C), sometimes rsync on the other host dumps core 
> or uses all (!) available memory and all CPU.
> 
> gdb on a core file:
> 
> $ gdb -q /usr/bin/rsync /tmp/core.4576
> (no debugging symbols found)...
> Core was generated by `/usr/bin/rsync --server --sender -logDtprz 
> --delete . /var/log/tomcat18039'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/lib/libpopt.so.0...done.
> Loaded symbols for /usr/lib/libpopt.so.0
> Reading symbols from /lib/libresolv.so.2...done.
> Loaded symbols for /lib/libresolv.so.2
> Reading symbols from /lib/i686/libc.so.6...done.
> Loaded symbols for /lib/i686/libc.so.6
> Reading symbols from /lib/ld-linux.so.2...done.
> Loaded symbols for /lib/ld-linux.so.2
> Reading symbols from /lib/libnss_files.so.2...done.
> Loaded symbols for /lib/libnss_files.so.2
> #0  0x42047ca7 in vfprintf () from /lib/i686/libc.so.6
> (gdb) bt
> #0  0x42047ca7 in vfprintf () from /lib/i686/libc.so.6
> Cannot access memory at address 0xb6fc9f10
> (gdb)
> 
> This happens on different host/host combinations. All hosts are on RHL 
> 8.0 with latest patches.
> 
> Regards,
> Bernie