From: Martin Peres <martin.peres@free.fr>
To: dri-devel@lists.freedesktop.org
Subject: Re: Rendering when dropped master
Date: Fri, 20 Dec 2013 10:31:41 +0100 [thread overview]
Message-ID: <52B40E7D.6010008@free.fr> (raw)
In-Reply-To: <52B3EA56.5050206@vmware.com>
On 20/12/2013 07:57, Thomas Hellstrom wrote:
> So this is a potential issue that needs to be brought up sooner or later:
>
> Let's say a client is authenticated by the current master.
> Then the master drops, and we have a new master (fast user switching for
> example).
>
> What's the status of the clients authenticated by old masters?
> Should they be allowed to render and use memory resources or shouldn't they?
>
> A typical example where this could pose a problem is where user 1 opens
> a drm connection, authenticates itself and then drops master.
> Then user 2 starts an X server and exposes all DRI contents to user 1?
>
> /Thomas
I wouldn't worry about that since all clients should use render nodes
instead.
If you worry about this, help making the switch to them happen.
Martin/mupuf
next prev parent reply other threads:[~2013-12-20 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 6:57 Rendering when dropped master Thomas Hellstrom
2013-12-20 9:31 ` Martin Peres [this message]
2013-12-20 9:55 ` Thomas Hellstrom
2013-12-20 9:59 ` Martin Peres
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=52B40E7D.6010008@free.fr \
--to=martin.peres@free.fr \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.