From: Timur Tabi <ttabi@nvidia.com>
To: "pengpeng@iscas.ac.cn" <pengpeng@iscas.ac.cn>,
"lyude@redhat.com" <lyude@redhat.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"simona@ffwll.ch" <simona@ffwll.ch>
Subject: Re: [PATCH] drm/nouveau/gsp: validate sequencer command span
Date: Wed, 22 Jul 2026 13:36:47 +0000 [thread overview]
Message-ID: <ab66a9fa67984252c5b1562345313e4ae724bc49.camel@nvidia.com> (raw)
In-Reply-To: <20260722042123.39900-1-pengpeng@iscas.ac.cn>
On Wed, 2026-07-22 at 12:21 +0800, Pengpeng Hou wrote:
> The GSP sequencer RPC contains a variable command stream. The handler
> currently walks commands using the stream header length without first
> proving that the stream, each command payload, or a register-save slot
> fits in the received RPC and its fixed save area.
>
> Validate the stream and each command against the RPC payload before
> walking it, and reject register-save indexes beyond the fixed save
> array.
>
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
Does this fix an known bug, or is it just something that an AI told you could be a problem?
prev parent reply other threads:[~2026-07-22 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 4:21 Pengpeng Hou
2026-07-22 13:36 ` Timur Tabi [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=ab66a9fa67984252c5b1562345313e4ae724bc49.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=pengpeng@iscas.ac.cn \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®