From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v6 2/2] drm: Avoid suspicious operations in drm_fb_dma_get_gem_addr()
Date: Wed, 21 Jan 2026 11:41:33 +0100 [thread overview]
Message-ID: <DFU7D0YSLOLZ.ZICBM13OPGVT@intel.com> (raw)
In-Reply-To: <20260120154824.1864085-3-krzysztof.karas@intel.com>
Hi Krzysztof,
On Tue Jan 20, 2026 at 4:48 PM CET, Krzysztof Karas wrote:
> In cases where dma_addr is a 64-bit value its calculation is
> still carried out using 32-bit arithmetic, which could
> occassionally cause a truncation of values before they are
s/occassionally/occasionally
> extended to 64 bits. Cast one of the operands to dma_addr_t,
> so 64-bit arithmetic is used.
>
> Cc: Danilo Krummrich <dakr@redhat.com>
> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> ---
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
next prev parent reply other threads:[~2026-01-21 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 15:48 [PATCH v6 0/2] Miscellaneous fixes in drm code Krzysztof Karas
2026-01-20 15:48 ` [PATCH v6 1/2] drm: Warn before division by 0 would occur Krzysztof Karas
2026-01-20 15:48 ` [PATCH v6 2/2] drm: Avoid suspicious operations in drm_fb_dma_get_gem_addr() Krzysztof Karas
2026-01-21 10:41 ` Sebastian Brzezinka [this message]
2026-01-20 17:25 ` ✓ i915.CI.BAT: success for Miscellaneous fixes in drm code Patchwork
2026-01-21 4:42 ` ✗ i915.CI.Full: failure " Patchwork
2026-01-29 11:31 ` [PATCH v6 0/2] " Andi Shyti
2026-01-29 13:10 ` Jani Nikula
2026-01-29 13:37 ` Andi Shyti
2026-01-29 14:29 ` Andi Shyti
2026-01-29 14:29 ` Joonas Lahtinen
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=DFU7D0YSLOLZ.ZICBM13OPGVT@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.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 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.