From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Initialise userptr mmu_notifier serial to 1
Date: Fri, 11 Jul 2014 12:53:54 +0100 [thread overview]
Message-ID: <53BFD052.4050508@linux.intel.com> (raw)
In-Reply-To: <20140711113541.GC12165@nuc-i3427.alporthouse.com>
On 07/11/2014 12:35 PM, Chris Wilson wrote:
> On Fri, Jul 11, 2014 at 12:31:12PM +0100, Tvrtko Ursulin wrote:
>>
>> On 07/11/2014 12:06 PM, Chris Wilson wrote:
>>> On Fri, Jul 11, 2014 at 12:00:26PM +0100, Tvrtko Ursulin wrote:
>>>> But it will be interesting to know what code managed to trigger this
>>>> race, because as we discussed on IRC it would indicate some pretty
>>>> wild userspace behaviour. Or lack of imagination on our part?
>>>
>>> A threaded client. One thread using userptr, the other doing munmap or
>>> free. Given enough embarrassment, it will happen every time.
>>
>> Yes fine, but I struggle to imagine what would be the intention of
>> such code or how did it manage to fail in such way. I hope the only
>> difference is not that userptr "upgraded" the failure mode for heap
>> corruption or memory management races in general.
>
> The mmu notifier is called everytime a process sneezes. It does not
> imply that our object is being invalidated, just that some portion of
> the current->mm is being modified.
Ah yes, I did not see the big picture.
Tvrtko
next prev parent reply other threads:[~2014-07-11 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 10:28 [PATCH 1/2] drm/i915: Abandon oom quickly if killed by a signal Chris Wilson
2014-07-11 10:28 ` [PATCH 2/2] drm/i915: Initialise userptr mmu_notifier serial to 1 Chris Wilson
2014-07-11 11:00 ` Tvrtko Ursulin
2014-07-11 11:06 ` Chris Wilson
2014-07-11 11:31 ` Tvrtko Ursulin
2014-07-11 11:35 ` Chris Wilson
2014-07-11 11:53 ` Tvrtko Ursulin [this message]
2014-07-11 14:02 ` Daniel Vetter
2014-07-11 14:06 ` Tvrtko Ursulin
2014-07-15 8:08 ` Daniel Vetter
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=53BFD052.4050508@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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.