From: "Danilo Krummrich" <dakr@kernel.org>
To: "Timur Tabi" <ttabi@nvidia.com>
Cc: "ojeda@kernel.org" <ojeda@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] gpu: nova-core: check for overflow to DMATRFBASE1
Date: Fri, 23 Jan 2026 17:23:19 +0100 [thread overview]
Message-ID: <DFW3VSJRDEOG.374RHLBPHFVVZ@kernel.org> (raw)
In-Reply-To: <be1f31d3036fa12af42133dc09fa22c27cd71764.camel@nvidia.com>
On Fri Jan 23, 2026 at 12:44 AM CET, Timur Tabi wrote:
> On Wed, 2026-01-07 at 14:16 -0600, Timur Tabi wrote:
>> The NV_PFALCON_FALCON_DMATRFBASE/1 register pair supports DMA addresses
>> up to 49 bits only, but the write to DMATRFBASE1 could exceed that.
>> To mitigate, check first that the DMA address will fit.
>>
>> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
>> Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
>> Fixes: 69f5cd67ce41 ("gpu: nova-core: add falcon register definitions and base code")
>> Signed-off-by: Timur Tabi <ttabi@nvidia.com>
>
> Danilo, is it too late to make 6.20 with this patch?
This patch is already in drm-rust-next.
prev parent reply other threads:[~2026-01-23 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 20:16 [PATCH v2 1/2] gpu: nova-core: check for overflow to DMATRFBASE1 Timur Tabi
2026-01-07 20:16 ` [PATCH v2 2/2] gpu: nova-core: add missing newlines to several print strings Timur Tabi
2026-01-07 20:48 ` John Hubbard
2026-01-08 23:12 ` John Hubbard
2026-01-08 23:22 ` Danilo Krummrich
2026-01-12 14:15 ` Danilo Krummrich
2026-01-22 23:44 ` [PATCH v2 1/2] gpu: nova-core: check for overflow to DMATRFBASE1 Timur Tabi
2026-01-23 16:23 ` Danilo Krummrich [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=DFW3VSJRDEOG.374RHLBPHFVVZ@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=ttabi@nvidia.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