dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Hellstrom <thellstrom@vmware.com>,
	dri-devel@lists.freedesktop.org,
	linux-graphics-maintainer@vmware.com
Cc: pv-drivers@vmware.com, stable@vger.kernel.org
Subject: Re: [PATCH] drm: Fix an unwanted master inheritance v2
Date: Fri, 04 Dec 2015 10:25:20 +0200	[thread overview]
Message-ID: <87bna61uz3.fsf@intel.com> (raw)
In-Reply-To: <5660A5CB.1000702@vmware.com>

On Thu, 03 Dec 2015, Thomas Hellstrom <thellstrom@vmware.com> wrote:
> Hi,
>
> On 12/03/2015 12:12 PM, Jani Nikula wrote:
>> On Wed, 02 Dec 2015, Thomas Hellstrom <thellstrom@vmware.com> wrote:
>>> A client calling drmSetMaster() using a file descriptor that was opened
>>> when another client was master would inherit the latter client's master
>>> object and all its authenticated clients.
>>>
>>> This is unwanted behaviour, and when this happens, instead allocate a
>>> brand new master object for the client calling drmSetMaster().
>>>
>>> Fixes a BUG() throw in vmw_master_set().
>>>
>>> Cc: <stable@vger.kernel.org>
>>> Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
>> Drive-by bikeshedding, the actual change might look neater (and easier
>> to revert if something falls apart) if you extracted the
>> drm_new_set_master() abstraction as a separate non-functional prep
>> patch. Not insisting, just a thought.
>>
>> BR,
>> Jani.
> While you're probably right, I prefer to have this as a single patch to
> avoid ending up in a backporting nightmare for stable.

That's reasonable.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2015-12-04  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 17:24 [PATCH] drm: Fix an unwanted master inheritance v2 Thomas Hellstrom
2015-12-03 11:12 ` Jani Nikula
2015-12-03 20:27   ` Thomas Hellstrom
2015-12-04  8:25     ` Jani Nikula [this message]
2015-12-04 14:16 ` Emil Velikov

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=87bna61uz3.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=pv-drivers@vmware.com \
    --cc=stable@vger.kernel.org \
    --cc=thellstrom@vmware.com \
    /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