[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH 04/12] evtchn: evtchn_set_priority() needs to acquire the per-channel lock
On 29.09.2020 18:31, Paul Durrant wrote: >> -----Original Message----- >> From: Xen-devel <xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf Of Jan >> Beulich >> Sent: 28 September 2020 11:58 >> To: xen-devel@xxxxxxxxxxxxxxxxxxxx >> Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>; George Dunlap >> <George.Dunlap@xxxxxxxxxxxxx>; Ian >> Jackson <iwj@xxxxxxxxxxxxxx>; Julien Grall <julien@xxxxxxx>; Wei Liu >> <wl@xxxxxxx>; Stefano Stabellini >> <sstabellini@xxxxxxxxxx> >> Subject: [PATCH 04/12] evtchn: evtchn_set_priority() needs to acquire the >> per-channel lock >> >> evtchn_fifo_set_pending() (invoked with the per-channel lock held) has >> two uses of the channel's priority field. > > AFAICT it is invoked with only the sending end's lock held... In the interdomain case you mean? >> The field gets updated by >> evtchn_fifo_set_priority() with only the per-domain event_lock held, >> i.e. the two reads may observe two different values. While the 2nd use >> could - afaict - in principle be replaced by q->priority, I think >> evtchn_set_priority() should acquire the per-channel lock in any event. > > ... so how is this going to help? Indeed, this will require more thought then. Jan
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |