Hide Forgot
Description of problem: I'm looking at some fixes/updates for the RHEL 6.2 x86_64 qemu-kvm package. The package applies 1675 patches against the 0.12.1.2 qemu source. the patches are very well documented and point to RHEL Bugzilla bugs to show which issue they fix (some obvious ones such as man page location changes). However of the 491 bugs these patches fix a large number of them are private. However this makes it impossible to work out which of these 491 bugs are fixed in subsiquent versions of qmeu. I understand why these bugs maybe private for customer specific data protection, however without seeing the bugzilla -> upstream bug id reference that are held within these bugzilla bugs it is pretty much impossible to work out what versions fix what bugs and which patches are relevent to subsiquent kvm versions. Is there anyway the list of bugs out of the 491 bugs patches in the qemu-kvm package can be mapped with no detail to the upstream bug reference Version-Release number of selected component (if applicable): 0.12.1.2 How reproducible: every time Steps to Reproduce: 1.view patch and relevent bugzilla information eg: 749806 2.see upsteam bug reference held in the bugzilla reference 3.view upsteam bug reference to see if issue is fixed in subsiquent versions and map out what version Actual results: 1.view patch and relevent bugzilla information eg: 749806 2. get access denied message 3. stop work - cannot continue Expected results: see above Additional info:
(In reply to comment #0) > Description of problem: > I'm looking at some fixes/updates for the RHEL 6.2 x86_64 qemu-kvm package. The > package applies 1675 patches against the 0.12.1.2 qemu source. > the patches are very well documented and point to RHEL Bugzilla bugs to show > which issue they fix (some obvious ones such as man page location changes). > However of the 491 bugs these patches fix a large number of them are private. > However this makes it impossible to work out which of these 491 bugs are fixed > in subsiquent versions of qmeu. I understand why these bugs maybe private for > customer specific data protection, however without seeing the bugzilla -> > upstream bug id reference that are held within these bugzilla bugs it is pretty > much impossible to work out what versions fix what bugs and which patches are > relevent to subsiquent kvm versions. > > Is there anyway the list of bugs out of the 491 bugs patches in the qemu-kvm > package can be mapped with no detail to the upstream bug reference What exactly what you like? Information about those 491 bugs? What kind of information? Michal
> > What exactly what you like? Information about those 491 bugs? What kind of > information? Sorry, I meant 'what exactly would you like?' as the first sentence. Michal
no problem, I feel bad logging the bug as I was happy to do the legwork myself, but the volume of bugs marked as "private" made it pretty tough to do. I'm basically looking to find out which of those BZ bugs, map to upstream bugs, so I can a.) work out which of these bugs have been fixed in which upstream qemu version b.) work out what the additional bugs/patches that are not bugs in upstream do (eg: obvious ones like set the location of the man page dir)
(In reply to comment #4) > no problem, > > I feel bad logging the bug as I was happy to do the legwork myself, but the > volume of bugs marked as "private" made it pretty tough to do. > > I'm basically looking to find out which of those BZ bugs, map to upstream bugs, > so I can > > a.) work out which of these bugs have been fixed in which upstream qemu version > b.) work out what the additional bugs/patches that are not bugs in upstream do > (eg: obvious ones like set the location of the man page dir) Ok, what exact information would you like ? Is the bug summary enough as you already have the patch file or would you like more information? Michal
sorry - I may have not explained clearly. The bug in this report is just an example. There are over 400 patches, which a good ammount are marked as private. without manually going through each patch, working out what each one does and then looking if and how that's fixed in later versions of qemu, I have no way of validating which of these Red Hat patch fixes are a.) bugs in qemu upstream b.) the upstream bug number this Red Hat bug fixes. Basically, I need to check some differences between the patched qemu 0.12 source RHEL 6 is shipping with, and qemu 0.14.1 upstream. I'm trying to work out which 0.12 upstream bugs the RHEL patches fix, so I can discount them, which ones are RHEL specific patches (eg: install locations, man page fix) so I can ignore them/create a patch to do the same in the 0.14.1 source and which ones are RHEL specific fixes for issues that are still open in 0.14.1 there are 1700+ patches in the qemu packages so without the ability to check the 400 Bugzilla bugs and how they relate to Qemu upsteam bugs it's going to be a real slog.
Hi Matt. We'll take your issues as suggestions for improvements in our processes and tools, but we don't have such a list right now. You're welcome to open a support request or escalate the issue somehow via the customer portal if you really need it, but unfortunately there's not much we can do at this moment at the development level.
Matt, the work you want to do is great, let's see how we could help: Normally the patches included on the qemu-kvm packages have decent patch descriptions. We really aim to get the problems and solutions described inside the patch description, and we aim to include the upstream status of those patches every time. Also, we actively try to apply patches to RHEL only after the corresponding fix is applied upstream (but there may be exceptions some times). Those patch descriptions are available on the source RPM package for qemu-kvm, so they are public and you can read them. I will take a random patch from the package, as an example: $ ls *.patch | shuf -n1 kvm-usb-ehci-always-call-ehci_queues_rip_unused-for-peri.patch Inside the public .patch file we have these pieces of information, among other info (and a long explanation for the patch): ----------- Bugzilla: 758104 Upstream commit: 7bce354e148b0ae0ceae7582574810adc6fab4e4 Upstream: http://patchwork.ozlabs.org/patch/144354/ (waiting for next usb pull request) --------- So, hopefully you should be able to figure out the upstream status of those patches by simply looking at the .patch file, in case the bug is private on Bugzilla. Probably if you grep for "upstream|cherry-pick" on the .patch files, you will be able to extract lots of upstream commit IDs, for patches that are already applied upstream. Also note: it's rare for RHEL qemu-kvm bugs on Bugzilla to contain references to upstream bug IDs. It's much more common to have our patches linked to upstream commit IDs or qemu-devel message-ids instead, as not every fix on Qemu have corresponding bug reports on the bug tracker. And this information (commit IDs or message-ids on qemu-devel) is normally inside the public .patch file instead of Bugzilla. I know that even with that information available, you will probably have questions on some cases, sometimes the patch description is not clear enough, and I will be glad to help you understand the upstream status of specific patches. Maybe we could set up a wiki page somewhere (or even a Google Docs spreadsheet, as it allows simultaneous editing) where we could help you do this patch triage?
Fantastic information thank you very much. I should be able to make a start on this and come back with much easier specific questions.