search for: blktap2_ioctl_create_device

What is the purpose of the name member? And why is it that it''s being left uninitialized (causing the kernel driver to print garbage [in the 2.6.18 driver''s blktap_validate_params()] or even fail [in pv-ops'' blktap_device_validate_params()]) in tapdisk_control_open_image()? Thanks, Jan

>>> On 02.03.12 at 10:04, EMEA1.EMEA1-MH.GATEWAY wrote: > The message that you sent was undeliverable to the following: > > jake.wires@citrix.com (550 #5.1.0 Address rejected jake.wires@citrix.com) > daniel.stodden@citrix.com (550 #5.1.0 Address rejected daniel.stodden@citrix.com) > Who is considered the maintainer(s) of blktap2 code these days? Jan

I''m currently working on moving storage services into their own domain and I''ve been looking at blktap2. I''ve been trying to get an image mounted with blktap2 and for some odd reason and tapdisk2 keeps hanging instead of quitting at the end. I haven''t removed any of the storage startup code at this point so everything should be as it normally is in xen-unstable.

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>