From: Dmitry Osipenko <digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
DRI Development
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH v2] drm/tegra: Check size of a submitted command buffer
Date: Sun, 14 May 2017 23:55:35 +0300 [thread overview]
Message-ID: <43378998-e75f-90bb-eadc-f17da41acce9@gmail.com> (raw)
In-Reply-To: <20170512192903.25491-1-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 12.05.2017 22:29, Dmitry Osipenko wrote:
> If command buffer claims a number of words that is higher than its BO can
> fit and a relocation lays past the BO, a kernel OOPS will be fired on that
> relocation address patching. This was triggered by an opentegra Xorg driver
> that erroneously pushed too many commands to the pushbuf.
>
For the record, this patch is superseded by the "drm/tegra: Check offsets of a
submitted command buffer and of relocations."
--
Dmitry
prev parent reply other threads:[~2017-05-14 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 19:29 [PATCH v2] drm/tegra: Check size of a submitted command buffer Dmitry Osipenko
[not found] ` <20170512192903.25491-1-digetx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-12 19:37 ` Erik Faye-Lund
2017-05-14 12:27 ` Mikko Perttunen
[not found] ` <5874d720-c911-b2bc-dc69-be2155505280-/1wQRMveznE@public.gmane.org>
2017-05-14 12:45 ` Dmitry Osipenko
[not found] ` <2eca9200-727a-5e6f-efa8-da0a7706c7a8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-14 12:56 ` Mikko Perttunen
[not found] ` <3eca952f-7c39-d701-15c1-1e243ba864b4-/1wQRMveznE@public.gmane.org>
2017-05-14 16:08 ` Dmitry Osipenko
2017-05-14 20:55 ` Dmitry Osipenko [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=43378998-e75f-90bb-eadc-f17da41acce9@gmail.com \
--to=digetx-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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