From: Kees Cook <kees@kernel.org>
To: Louis Chauvet <louis.chauvet@bootlin.com>
Cc: Haneen Mohammed <hamohammed.sa@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Melissa Wen <melissa.srw@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] drm/vkms: Adjust vkms_state->active_planes allocation type
Date: Wed, 30 Apr 2025 12:06:43 -0700 [thread overview]
Message-ID: <202504301205.B3AD2E7@keescook> (raw)
In-Reply-To: <823d4d24-da80-4834-95ca-d5698edfe18f@bootlin.com>
On Mon, Apr 28, 2025 at 10:18:34AM +0200, Louis Chauvet wrote:
>
>
> Le 26/04/2025 à 08:14, Kees Cook a écrit :
> > In preparation for making the kmalloc family of allocators type aware,
> > we need to make sure that the returned type from the allocation matches
> > the type of the variable being assigned. (Before, the allocator would
> > always return "void *", which can be implicitly cast to any pointer type.)
> >
> > The assigned type is "struct vkms_plane_state **", but the returned type
> > will be "struct drm_plane **". These are the same size (pointer size), but
> > the types don't match. Adjust the allocation type to match the assignment.
>
> I think this is an issue, can you add the proper Fixup tag in this commit?
I think trailers updating tools like b4 will pick this up:
Fixes: 8b1865873651 ("drm/vkms: totally reworked crc data tracking")
Would you rather I send a v2 with the Fixes added?
>
> With this:
>
> Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
Thanks!
-Kees
--
Kees Cook
next prev parent reply other threads:[~2025-04-30 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 6:14 [PATCH] drm/vkms: Adjust vkms_state->active_planes allocation type Kees Cook
2025-04-28 8:18 ` Louis Chauvet
2025-04-30 19:06 ` Kees Cook [this message]
2025-05-06 8:23 ` Louis Chauvet
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=202504301205.B3AD2E7@keescook \
--to=kees@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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