| Summary: | qemu-nbd can't attach properly nbd device anymore, unless CVE-2017-9524-part1.patch and CVE-2017-9524-part2.patch are removed. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Giuseppe Ghibò <ghibomgx> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, marja11, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | qemu-2.8.1.1-5.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Giuseppe Ghibò
2017-07-06 22:09:23 CEST
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.
Marja Van Waes
2017-07-07 14:32:27 CEST
CC:
(none) =>
marja11 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 =>
RESOLVED |