Re: [Xen-devel] [PATCHv1] evtchn: don't reuse ports that are still "busy"

>>> On 30.11.15 at 18:59, wrote: > When using the FIFO ABI a guest may close an event channel that is > still LINKED. If this port is reused, subsequent events may be lost > because they may become pending on the wrong queue. > > This could be fixed by requiring guests

Re: [Xen-devel] [PATCHv1] evtchn: don't reuse ports that are still "busy"

>>> On 01.12.15 at 15:04, wrote: > On 01/12/15 12:49, Jan Beulich wrote: > On 30.11.15 at 18:59, wrote: >>> --- a/xen/common/event_channel.c >>> +++ b/xen/common/event_channel.c >>> @@ -170,7 +170,8 @@ static int get_free_port(struct domain

Re: [Xen-devel] [PATCHv1] evtchn: don't reuse ports that are still "busy"

On 01/12/15 12:49, Jan Beulich wrote: On 30.11.15 at 18:59, wrote: >> --- a/xen/common/event_channel.c >> +++ b/xen/common/event_channel.c >> @@ -170,7 +170,8 @@ static int get_free_port(struct domain *d) >> { >> if ( port > d->max_evtchn_port ) >>

[Xen-devel] [PATCHv1] evtchn: don't reuse ports that are still "busy"

When using the FIFO ABI a guest may close an event channel that is still LINKED. If this port is reused, subsequent events may be lost because they may become pending on the wrong queue. This could be fixed by requiring guests to only close event channels that are not linked. This is difficult