From: sashiko-bot@kernel.org
To: "Leandro Ribeiro" <leandro.ribeiro@collabora.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 02/12] vkms: properly compute gamma LUT size in vkms_atomic_check()
Date: Fri, 06 Nov 2026 20:25:50 +0000 [thread overview]
Message-ID: <sashiko-outbox-202203@kernel.org> (raw)
In-Reply-To: <20261106201813.129911-3-leandro.ribeiro@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/vkms: missing Fixes trailer for LUT size fix in
vkms_atomic_check()
--
commit ce5b5586969b38a36fc2d39e5403ee7e86059811
Author: Leandro Ribeiro <leandro.ribeiro@collabora.com>
> vkms: properly compute gamma LUT size in vkms_atomic_check()
>
> Gamma LUT size is being computed wrongly, dividing blob size by
> sizeof(struct drm_color_lut *). But the blob is an array of struct
> drm_color_lut.
>
> Replace sizeof(struct drm_color_lut *) with sizeof(struct
> drm_color_lut), properly validating the userspace gamma LUT size.
>
> Issue caught by Sashiko bot:
> https://sashiko.dev/#/patchset/20260804203351.148521-1-leandro.ribeiro@collabora.com?part=1
>
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Reviewed-by: Robert Mader <robert.mader@collabora.com>
> Tested-by: Robert Mader <robert.mader@collabora.com>
> Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
[Severity: Low]
Since this fixes the gamma LUT size check in vkms_atomic_check(), which
rejected valid 129-to-256-entry LUTs on 32-bit architectures where
sizeof(struct drm_color_lut *) is 4 bytes instead of 8, should the commit
message include:
Fixes: db1f254f2cfa ("drm/vkms: Add support to 1D gamma LUT")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106201813.129911-1-leandro.ribeiro@collabora.com?part=2
next prev parent reply other threads:[~2026-11-06 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 20:18 [PATCH v2 00/12] drm/vkms: improve color curve LUTs precision Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 01/12] drm/vkms: rename VKMS_LUT_SIZE to VKMS_GAMMA_LUT_SIZE Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 02/12] vkms: properly compute gamma LUT size in vkms_atomic_check() Leandro Ribeiro
2026-11-06 20:25 ` sashiko-bot [this message]
2026-11-12 12:07 ` Oarora Etimis
2026-11-06 20:18 ` [PATCH v2 03/12] drm/vkms: allow color curve LUTs to have different sizes Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 04/12] drm/vkms: remove TEST_LUT_SIZE Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 05/12] drm/vkms: remove linear_eotf Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 06/12] drm/vkms: improve the way in which we access LUT member Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 07/12] drm/vkms: rename struct vkms_color_lut::base to y Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 08/12] drm/vkms: rename get_lut_index() to get_uniform_lut_index() Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 09/12] drm/vkms: add support to non-uniform LUT for internal color curves Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 10/12] drm/vkms: test sRGB and inverse sRGB LUTs using more samples Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 11/12] drm/vkms: add script to create optimized LUTs for color curves Leandro Ribeiro
2026-11-06 20:18 ` [PATCH v2 12/12] drm/vkms: replace uniform sRGB LUT and its inverse with optimal ones Leandro Ribeiro
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=sashiko-outbox-202203@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=leandro.ribeiro@collabora.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.