I noticed since version 2.8.1.1-5.mga6 (so also 2.8.1.1-6.mga6), qemu-nbd can't attach properly device anymore. E.g. when you attach a device with -c to /dev/nbd0 and then do an fdisk to its device, you get the error: fdisk: cannot open /dev/nbd0: Inappropriate ioctl for device while with previous version 2.8.1.1-4.mga6 everything was working fine. So I suspect the latest round of security fixes in 2.8.1.1-5.mga6 has breaked something.
Do you have nbd module loaded ?
CC: (none) => tmb
yes, the nbd module is loaded. Under the same conditions, downgrading to qemu-2.8.1.1-4.mga6 I don't get those errors and the device is accessed flawlessly.
Could be the side effect of CVE-2017-9524-part2.patch? That patch is dealing with block devices.
No, can't be CVE-2017-9524-part2.patch alone, but probably both CVE-2017-9524-part1.patch, and CVE-2017-9524-part2.patch.
I confirm removing those two patches, i.e.: Patch0033: CVE-2017-9524-part1.patch Patch0034: CVE-2017-9524-part2.patch and rebuilding qemu have resolved the problems, so probably such patches are wrong or incomplete.
CC: (none) => marja11Assignee: bugsquad => thierry.vignaudSummary: qemu-nbd can't attach properly nbd device anymore => qemu-nbd can't attach properly nbd device anymore, unless CVE-2017-9524-part1.patch and CVE-2017-9524-part2.patch are removed.
Yeah, I will disable them for mga6 release and re-visit them in a post-release security update
Assignee: thierry.vignaud => tmb
Per last comment I assume this got fixed for long time ago before our current release...
Status: NEW => RESOLVEDCC: (none) => friResolution: (none) => FIXED