From: Greg KH <greg@kroah.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] drm/syncobj: Stop reusing the same struct file for all syncobj -> fd
Date: Tue, 27 Mar 2018 09:29:50 +0200 [thread overview]
Message-ID: <20180327072950.GB8380@kroah.com> (raw)
In-Reply-To: <1522090837-13789-1-git-send-email-jason.ekstrand@intel.com>
On Mon, Mar 26, 2018 at 12:00:37PM -0700, Jason Ekstrand wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
>
> The vk cts test:
> dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary
>
> triggers a lot of
> VFS: Close: file count is 0
>
> Dave pointed out that clearing the syncobj->file from
> drm_syncobj_file_release() was sufficient to silence the test, but that
> opens a can of worm since we assumed that the syncobj->file was never
> unset. Stop trying to reuse the same struct file for every fd pointing
> to the drm_syncobj, and allocate one file for each fd instead.
>
> v2: Fixup return handling of drm_syncobj_fd_to_handle
> v2.1: [airlied: fix possible syncobj ref race]
> v2.2: [jekstrand: back-port to 4.14]
>
> Reported-by: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Tested-by: Dave Airlie <airlied@redhat.com>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Jason Ekstrand <jason@jlekstrand.net>
> Tested-by: Clayton Craft <clayton.a.craft@intel.com>
> ---
>
> The back-port from 4.15 to 4.14 was non-trivial. It'd be good if Chris and
> maybe Daniel could do a quick re-review.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2018-03-27 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 19:00 [PATCH] drm/syncobj: Stop reusing the same struct file for all syncobj -> fd Jason Ekstrand
2018-03-27 6:37 ` Jani Nikula
2018-03-27 7:29 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180327072950.GB8380@kroah.com \
--to=greg@kroah.com \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox