Re: [PATCH v2] vhost: fix VDUSE device destruction failure

2024-03-05 Thread David Marchand
On Mon, Mar 4, 2024 at 11:36 AM David Marchand wrote: > > From: Maxime Coquelin > > VDUSE_DESTROY_DEVICE ioctl can fail because the device's > chardev is not released despite close syscall having been > called. It happens because the events handler thread is > still polling the file descriptor. >

Re: [PATCH v2] vhost: fix VDUSE device destruction failure

2024-03-04 Thread Maxime Coquelin
Le lun. 4 mars 2024, 11:36, David Marchand a écrit : > From: Maxime Coquelin > > VDUSE_DESTROY_DEVICE ioctl can fail because the device's > chardev is not released despite close syscall having been > called. It happens because the events handler thread is > still polling the file descriptor. > >

[PATCH v2] vhost: fix VDUSE device destruction failure

2024-03-04 Thread David Marchand
From: Maxime Coquelin VDUSE_DESTROY_DEVICE ioctl can fail because the device's chardev is not released despite close syscall having been called. It happens because the events handler thread is still polling the file descriptor. fdset_pipe_notify() is not enough because it does not ensure the not