wayland/protocol/tests.xml, branch 1.16[no description]http://git.sudomsg.com/mirror/wayland/atom/protocol/tests.xml?h=1.162018-01-09T15:20:00Ztests: Check for wrong fd delivery with zombie objects2018-01-09T15:20:00ZDerek Foremanderekf@osg.samsung.com2017-12-06T17:22:25Zurn:sha1:ff992951a7e6da0a8e54786ef7371ae420ce6c9c
Until recently, if an event attempting to deliver an fd to a zombie
object was demarshalled after the object was made into a zombie, we
leaked the fd and left it in the buffer.
If another event attempting to deliver an fd to a live object was in that
same buffer, the zombie's fd would be delivered instead.
This test recreates that situation.
While this is a ridiculously contrived way to force this race - delivering
an event from a destruction handler - I do have reports of this race
being hit in real world code.
Signed-off-by: Derek Foreman <derekf@osg.samsung.com>
Acked-by: Daniel Stone <daniels@collabora.com>
tests: Add a test for fd leaks on zombie objects2018-01-09T15:20:00ZDerek Foremanderekf@osg.samsung.com2017-12-06T17:22:24Zurn:sha1:f74c9b98db49ce16e037c3012590c4a24a4fc32e
Until recently, if a client destroying a resource raced with the
server generating an event on that resource that delivered a file
descriptor, we would leak the fd.
This tests for a leaked fd from that race condition.
Reviewed-by: Daniel Stone <daniels@collabora.com>
Signed-off-by: Derek Foreman <derekf@osg.samsung.com>