Jan Beulich
2012-Mar-02 09:05 UTC
BLKTAP2_IOCTL_CREATE_DEVICE vs. struct blktap2_params'' name member
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
Maybe Matching Threads
- Fwd: Message Status - Undeliverable (Re: BLKTAP2_IOCTL_CREATE_DEVICE vs. struct blktap2_params' name member)
- Interesting lockdep message coming out of blktap
- [PATCH] x86/hvm: increase struct hvm_vcpu_io's mmio_large_read
- Dom0 reboot when several VM reboot at the same time
- Dom0 reboot when several VM reboot at the same time