Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-02-06 Thread Ryan Neph
On Thu, Feb 02, 2023 at 05:24:34AM +0300, Dmitry Osipenko wrote: > On 2/2/23 05:17, Dmitry Osipenko wrote: > > On 2/1/23 18:48, Rob Clark wrote: > >> On Wed, Feb 1, 2023 at 5:28 AM Dmitry Osipenko > >> wrote: > >>> > >>> On 1/27/23 01:58, Ryan Neph wrote: > An interrupted dma_fence_wait() bec

Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-02-01 Thread Dmitry Osipenko
On 1/27/23 01:58, Ryan Neph wrote: > An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned > to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to > retry the ioctl(), but the passed exbuf->fence_fd has been reset to -1, > making the retry attempt fail at sync_file_get_fen

Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-02-01 Thread Dmitry Osipenko
On 2/2/23 05:17, Dmitry Osipenko wrote: > On 2/1/23 18:48, Rob Clark wrote: >> On Wed, Feb 1, 2023 at 5:28 AM Dmitry Osipenko >> wrote: >>> >>> On 1/27/23 01:58, Ryan Neph wrote: An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUF

Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-02-01 Thread Dmitry Osipenko
On 2/1/23 18:48, Rob Clark wrote: > On Wed, Feb 1, 2023 at 5:28 AM Dmitry Osipenko > wrote: >> >> On 1/27/23 01:58, Ryan Neph wrote: >>> An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned >>> to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to >>> retry the ioctl(),

Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-02-01 Thread Rob Clark
On Wed, Feb 1, 2023 at 5:28 AM Dmitry Osipenko wrote: > > On 1/27/23 01:58, Ryan Neph wrote: > > An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned > > to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to > > retry the ioctl(), but the passed exbuf->fence_fd has been

Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-02-01 Thread Dmitry Osipenko
On 1/27/23 01:58, Ryan Neph wrote: > An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned > to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to > retry the ioctl(), but the passed exbuf->fence_fd has been reset to -1, > making the retry attempt fail at sync_file_get_fen

Re: [PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-01-27 Thread Rob Clark
On Fri, Jan 27, 2023 at 12:31 AM Ryan Neph wrote: > > An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned > to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to > retry the ioctl(), but the passed exbuf->fence_fd has been reset to -1, > making the retry attempt fail at

[PATCH] drm/virtio: exbuf->fence_fd unmodified on interrupted wait

2023-01-27 Thread Ryan Neph
An interrupted dma_fence_wait() becomes an -ERESTARTSYS returned to userspace ioctl(DRM_IOCTL_VIRTGPU_EXECBUFFER) calls, prompting to retry the ioctl(), but the passed exbuf->fence_fd has been reset to -1, making the retry attempt fail at sync_file_get_fence(). The uapi for DRM_IOCTL_VIRTGPU_EXECB