search for: recv_file_entry

https://bugzilla.samba.org/show_bug.cgi?id=8001 Summary: buffer overflow in recv_file_entry (maxpathlen doesn't works) Product: rsync Version: 3.0.8 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org...

https://bugzilla.samba.org/show_bug.cgi?id=8265 Summary: Long paths, hardlinks, 'special' files [was: Regression: sockets for 3.0.9pre1] Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: core AssignedTo:

...imations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations [receiver] ERROR: buffer overflow in recv_file_entry [receiver] rsync error: error allocating core memory buffers (code 22) at util.c(123) [receiver=3.0.5] I also tried rsync 2.6.9 on client side and I got: opening tcp connection to saturn.nildram.co.uk port 873 opening connection using --server --sender -vvlWHogDtpr --ignore-errors --numeric-ids...

...53 Dorg.mozilla%3Aen-US%3Aofficial%2526sa%253DN%2526start%253D100%2526um%253D1/ http%3A/icanhaspixiedust.com/category/characters-and-stars/mickey-mouse/http %253A/icanhaspixiedust.com/category/characters-and-stars/mickey-mouse/%26r%3 Dhttp%253A/images.google.com [receiver] ERROR: buffer overflow in recv_file_entry [receiver] rsync error: error allocating core memory buffers (code 22) at util.c(124) [receiver=3.0.6] overflow: xflags=0x7a l1=255 l2=784 lastname=/home/cpanelBackup/cpbackup/daily/haspixie/homedir/public_html/wp-c ontent/cache/supercache/icanhaspixiedust.com/category/characters-and-stars/m ickey-...

...patch and the --crtimes -H options (version 3.0.4). I can reliably demonstrate it (on OSX 10.5) by doing this several times (as root): rsync -v -N -axHAX --delete-during --fileflags --force-change /usr/ bin/ /tmp/foo/ I think I've tracked it down to the hard-link processing code in recv_file_entry() in flist.c around line 751: Essentially, all hard links but the first will get their modtime set correctly (from first->modtime), but their crtime is inherited (incorrectly) from the previous invocation of recv_file_entry. The obvious idea would be to add a crtime field to file_struct bu...

...15a) #1 0x4412dd in rule_matches /home/raj/rsync/rsync/exclude.c:696 #2 0x441921 in check_filter /home/raj/rsync/rsync/exclude.c:772 #3 0x441724 in name_is_excluded /home/raj/rsync/rsync/exclude.c:744 #4 0x4a2d76 in receive_xattr /home/raj/rsync/rsync/xattrs.c:835 #5 0x40beac in recv_file_entry /home/raj/rsync/rsync/flist.c:1108 #6 0x415bee in recv_file_list /home/raj/rsync/rsync/flist.c:2476 #7 0x454eaa in do_server_recv /home/raj/rsync/rsync/main.c:1036 #8 0x4556f4 in start_server /home/raj/rsync/rsync/main.c:1115 #9 0x4b20f2 in rsync_module /home/raj/rsync/rsync/clients...

It would appear something snuck in that breaks non-recursive remote listings when talking to a non-3.0.0pre1 version of rsync. The symptom itself is simple enough to see; rather than displaying member directories/regular files/symlinks/etc as one would expect, only non-directories (with the exception of '.') are listed. Other tidbits.. some obvious, some maybe not: - not limited to just

...00000e825 at pc 0x7ffff6ef8864 bp 0x7fffffff9b50 sp 0x7fffffff92f8 WRITE of size 11 at 0x60200000e825 thread T0 #0 0x7ffff6ef8863 in __asan_memcpy (/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/libasan.so.2+0x8c863) #1 0x4a2eef in receive_xattr /home/raj/rsync/rsync/xattrs.c:849 #2 0x40beac in recv_file_entry /home/raj/rsync/rsync/flist.c:1108 #3 0x415bee in recv_file_list /home/raj/rsync/rsync/flist.c:2476 #4 0x454eaa in do_server_recv /home/raj/rsync/rsync/main.c:1036 #5 0x4556f4 in start_server /home/raj/rsync/rsync/main.c:1115 #6 0x4b20f9 in rsync_module /home/raj/rsync/rsync/clients...

...: bugzilla.samba.org-prf at jf-luce.name QA Contact: rsync-qa at samba.org This is for creation time patch. The 2nd hard link is reported that its creation time is modified. I traced into rsync and the creation time is the one of the file just before it. I think I got it : after this, in recv_file_entry(), in flist.c, line 787 in version 3.1.3 if (first_hlink_ndx >= flist->ndx_start) { struct file_struct *first = flist->files[first_hlink_ndx - flist->ndx_start]; file_length = F_LENGTH(first); we should add "crtime = f_crtime(first);" just after. -- You are receiv...

...-DHAVE_CONFIG_H -Wall -W -c flist.c -o flist.o flist.c: In function 'send_file_entry': flist.c:381: error: 'struct file_struct' has no member named 'fileflags' flist.c:384: error: 'struct file_struct' has no member named 'fileflags' flist.c: In function 'recv_file_entry': flist.c:815: error: request for member 'unum' in something not a structure or union flist.c: In function 'make_file': flist.c:1128: error: request for member 'unum' in something not a structure or union make: *** [flist.o] Error 1 The rsync-2.6.9 source and flags...

...onpro/release/4.7.2_fedora-LINUX-g/include/libinc/librtm.h -> ../../../4.7.2_fedora-LINUX/include/libinc/librtm.h filevault/visionpro/release/4.7.2_fedora-LINUX-g/include/libinc/mysql.h -> ../../../4.7.2_fedora-LINUX/include/libinc/mysql.h overflow: linkname_len=2751 ERROR: buffer overflow in recv_file_entry [receiver] rsync error: error allocating core memory buffers (code 22) at util.c(123) [receiver=3.0.0] rsync: writefd_unbuffered failed to write 5 bytes [generator]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1500) [generator=3.0.0] hotlap:Source brian$ Wha...

...FreeBSD 6.3 server. Both are running rsync 3.0.6. The transfer keeps dying with the following errors. On the receiver I'm getting the following error 2009/09/01 11:27:58 [23670] overflow: xflags=0x546 l1=0 l2=10376 lastname= [generator] 2009/09/01 11:27:58 [23670] ERROR: buffer overflow in recv_file_entry [generator] 2009/09/01 11:27:58 [23670] rsync error: error allocating core memory buffers (code 22) at util.c(123) [generator=3.0.6] On the sender I get 2009/09/01 11:50:10 [13901] rsync: writefd_unbuffered failed to write 803 bytes to socket [sender]: Broken pipe (32) 2009/09/01 11:50:10 [13...

All seems to compile ok but I get the following warnings on interix 3.5 flist.c: In function `recv_file_entry': flist.c:840: warning: comparison between signed and unsigned flist.c:874: warning: comparison between signed and unsigned flist.c:876: warning: right shift count >= width of type flist.c: In function `make_file': flist.c:1178: warning: comparison between signed and unsigned flist.c:122...

...amaged file system. After fsck there were some symlinks broken, pointing to nowhere (or better pointing to an empty file name, it showed up as "filename ->" in "ls -al"). Rsync fails to sync these symlinks, it just breaks with the following message: ERROR: buffer overflow in recv_file_entry Instead I wished either rsync correctly sync'ing these - or if empty symlinks cannot be created it should skip these and issue a warning but not exit with a buffer overflow. Manually deleting the broken symlinks from the source solved this (thus setting this bug to "minor"), but it...

Hi, I've been using rsync (OSX Tiger now Leopard) to backup my home folder daily using -a -H -A -X link-dest=dir to make incremental backups. There was a problem though since many files especially images, movies etc would be recopied each time instead of creating hard links. I have been testing the pre5 release and found that it seems to make hard links correctly for all files. I