From: Louis Chauvet <louis.chauvet@bootlin.com>
To: "José Expósito" <jose.exposito89@gmail.com>
Cc: airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, hamohammed.sa@gmail.com,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mairacanal@riseup.net, melissa.srw@gmail.com, mripard@kernel.org,
rodrigosiqueiramelo@gmail.com, thomas.petazzoni@bootlin.com,
tzimmermann@suse.de
Subject: Re: [PATCH] drm/vkms: Add missing check for CRTC initialization
Date: Wed, 18 Sep 2024 15:39:23 +0200 [thread overview]
Message-ID: <ZurYC1Ez8K0UsJ_Y@localhost.localdomain> (raw)
In-Reply-To: <20240917160208.2905-1-jose.exposito89@gmail.com>
Le 17/09/24 - 18:02, José Expósito a écrit :
> Hi Louis,
>
> > CRTC initialization call drm_mode_crtc_set_gamma_size without the proper
> > checks, introduce this check to avoid issues.
> >
> > Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
>
> Reviewed-by: José Expósito <jose.exposito89@gmail.com>
>
> > ---
> > drivers/gpu/drm/vkms/vkms_crtc.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> >
> > ---
> > base-commit: a6bb1f77a94335de67dba12e7f52651c115b82d2
> > change-id: 20240906-vkms-add-missing-check-e1b6ee8d1b39
> >
> > Best regards,
> >
> > diff --git a/drivers/gpu/drm/vkms/vkms_crtc.c b/drivers/gpu/drm/vkms/vkms_crtc.c
> > index 40b4d084e3ce..e4f93dfbd071 100644
> > --- a/drivers/gpu/drm/vkms/vkms_crtc.c
> > +++ b/drivers/gpu/drm/vkms/vkms_crtc.c
> > @@ -287,7 +287,12 @@ int vkms_crtc_init(struct drm_device *dev, struct drm_crtc *crtc,
> >
> > drm_crtc_helper_add(crtc, &vkms_crtc_helper_funcs);
> >
> > - drm_mode_crtc_set_gamma_size(crtc, VKMS_LUT_SIZE);
> > + ret = drm_mode_crtc_set_gamma_size(crtc, VKMS_LUT_SIZE);
> > + if (ret) {
> > + DRM_ERROR("Failed to set gamma size\n");
>
> This will conflit with "drm/vkms: Switch to dynamic allocation
> for CRTC" [1], where you switched to DRM_DEV_ERROR.
I did not check if my series had conflict between them, so I'm not
surprised. I will change it to the DEV variant and send a v2, espicially
since Leo [1] wants to work to clean the logging in VKMS :-)
[1]:https://lore.kernel.org/all/CAHhBtNqB=jQTnY1eu8or=toczr93ehUeuBkAZ7axFPr4ZHPjCQ@mail.gmail.com/
> No proferences about the log function, just a heads up so when
> you rebase one of the patches we keep logging consistent.
>
> [1] https://patchwork.kernel.org/project/dri-devel/patch/20240912-b4-vkms-allocated-v1-3-29abbaa14af9@bootlin.com/
>
> > + return ret;
> > + }
> > +
> > drm_crtc_enable_color_mgmt(crtc, 0, false, VKMS_LUT_SIZE);
> >
> > spin_lock_init(&vkms_out->lock);
> >
next prev parent reply other threads:[~2024-09-18 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 16:15 Louis Chauvet
2024-09-17 16:02 ` José Expósito
2024-09-18 13:39 ` Louis Chauvet [this message]
2024-09-25 0:02 ` Maíra Canal
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=ZurYC1Ez8K0UsJ_Y@localhost.localdomain \
--to=louis.chauvet@bootlin.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=jose.exposito89@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--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
all inboxes | Powered by JetHome®