Bug 1135099

Summary:	Should send data message for file copy of 0 size
Product:	Red Hat Enterprise Linux 6	Reporter:	Marc-Andre Lureau <marcandre.lureau>
Component:	spice-gtk	Assignee:	Marc-Andre Lureau <marcandre.lureau>
Status:	CLOSED ERRATA	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	astepano, cfergeau, dblechte, rbalakri, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-gtk-0.26-1.el6	Doc Type:	Bug Fix
Doc Text:	Cause: missing SPICE protocol message when dragging 0-byte file from client to guest Consequence: resource leak on the guest (file descriptor) Fix: make sure the expected SPICE message is sent to the guest even for 0-byte files Result: no more resource leak	Story Points:	---
Clone Of:
Clones:	1135104 1135105 (view as bug list)		Environment:
Last Closed:	2015-07-22 06:31:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1185434
Bug Blocks:	1135104, 1135105

Description Marc-Andre Lureau 2014-08-28 19:55:56 UTC

Description of problem:

spice-gtk doesn't send data message for 0-size files, however both linux and windows agents are expecting to receive it, or they will keep a file open, thus leaking it.

Version-Release number of selected component (if applicable):

any with file copy/xfer support

How reproducible:

100%

Steps to Reproduce:
1. dnd 0-size files to remote desktop

Actual results:

spice-vdagent number of open fd keeps growing

Expected results:

number of fd shouldn't grow.

Comment 2 Marc-Andre Lureau 2014-08-28 20:20:00 UTC

posted:
http://lists.freedesktop.org/archives/spice-devel/2014-August/017291.html

Comment 7 errata-xmlrpc 2015-07-22 06:31:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1322.html