Red Hat Bugzilla – Bug 171308
Uploaded file corrupted when two connections from same client uploading same file simultaneously
Last modified: 2007-11-30 17:07:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1)
Description of problem:
I am using Redhat EL3 (AS) Taroon Update 5 with kernel 2.4.21-32.0.1.ELsmp. The vsftpd.conf is in /etc/vsftpd and it is started by "service vsftpd start".
The vsftpd configuration is mostly in default settings. I have tested a number some other vsftpd version (v1.2.2 rpm package for rh9), also encounter this problem. I have also tuned some of the vsftpd configuratons such as "enable chroot user", "enable ascii upload" etc and this bug is reproduced in all the tests.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Launch 2 ftp connections to the ftp server
2.start uploading a file from both connections to the same destination folder
3.make sure both connections are transfering the same file simultaneously
Actual Results: the resulting upload will be corrupted with file size around double of the orginal file
Expected Results: A correct copy of upload from the most recent transfer (the connection which ends later )
It seems that the two ftp transfer streams somehow merged due to the identical file name.
I've got a patch for this issue, it's on proposed list for next RHEL update.
(In reply to comment #2)
> I've got a patch for this issue, it's on proposed list for next RHEL update.
Hi, can you send me the patch for testing? or do i have to request through my
Created attachment 120244 [details]
rename patch for vsftpd-1.2.1
This patch renames the target file and overwrites the same file..
Would be great if you can test it and prove that it's correct.
Hi, man , Thanks the patch works perfectly.
Added to Update propose list
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.