Bug 681962 - backport fair event-channel notification
Summary: backport fair event-channel notification
Keywords:
Status: CLOSED DUPLICATE of bug 456171
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen
Version: 5.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Paolo Bonzini
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 514490 KernelXenUpstream
TreeView+ depends on / blocked
 
Reported: 2011-03-03 18:16 UTC by Paolo Bonzini
Modified: 2011-04-18 08:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-18 08:41:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Paolo Bonzini 2011-03-03 18:16:15 UTC
The following patches have been forward ported recently to pvops from 2.6.18-xen.hg: 

      * 324:7fe1c6d02a2b 
      * 325:b2768401db94 
      * 988:c88a02a22a05 
      * 990:427276ac595d 
      * 991:9ba6d9f3fbc0

For RHEL5 the issue could even be exploited by a malicious domU to cause a DoS towards any domain whose backends have higher event channel numbers.  I doubt it's severe enough to need a CVE, though.

There is also no hurry to backport them to RHEL6 pvops (where we have no dom0 support), but it could be done for 6.2/6.3.

Comment 1 Paolo Bonzini 2011-03-03 18:18:42 UTC
To test, start 5-10 guests 1 minute from each other, possibly with drives backed by a ram-disk (i.e. large files in tmpfs).  fsmark/iozone on the guests should give roughly the same performance.

Comment 3 Paolo Bonzini 2011-04-18 08:41:14 UTC
c/s 324 and 325 went in as part of bug 456171; the others are cleanups, or otherwise provide diminishing returns.  Not worth it.

*** This bug has been marked as a duplicate of bug 456171 ***


Note You need to log in before you can comment on or make changes to this bug.