Hi,
On 09/11/2020 16:38, Juergen Gross wrote:
The patches for XSA-343 produced some fallout, especially the event
channel locking has shown to be problematic.
Patch 1 is targeting fifo event channels for avoiding any races for the
case that the fifo queue has been changed for a specific event channel.
The second patch is modifying the per event channel locking scheme in
order to avoid deadlocks and problems due to the event channel lock
having been changed to require IRQs off by the XSA-343 patches.
Changes in V6:
- added patch 3 (Jan Beulich)
- switched some more read_trylock() cases to read_lock() (Jan Beulich)
Changes in V5:
- moved evtchn_write_[un]lock() to event_channel.c (Jan Beulich)
- used normal read_lock() in some cases (Jan Beulich)
Changes in V4:
- switched to real rwlock
Changes in V3:
- addressed comments
Juergen Gross (3):
xen/events: access last_priority and last_vcpu_id together
xen/evtchn: rework per event channel lock
xen/evtchn: revert 52e1fc47abc3a0123
While looking at the list of commits, I noticed that the first patch
hasn't been committed. They were all acked/reviewed, so I am a bit
puzzled why this was omitted...
I have nearly missed as I was expecting the 3 patches to be committed
together. May I suggest that in the future we reply to the cover letter
and mention which patches are (or not) committed?
Regarding patch #1, I will commit it tomorrow unless there are strong
objections against.
Cheers,
--
Julien Grall