From: Thomas Zimmermann <tzimmermann@suse.de>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
javierm@redhat.com, robdclark@gmail.com,
quic_abhinavk@quicinc.com
Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
kernel test robot <lkp@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/msm: Fix possible uninitialized access in fbdev
Date: Wed, 22 Feb 2023 13:42:51 +0100 [thread overview]
Message-ID: <08e3340e-b459-0e60-4bba-30716b675e05@suse.de> (raw)
In-Reply-To: <c62e64e6-4114-2411-b80b-8cdc112a4393@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]
Hi
Am 22.02.23 um 13:37 schrieb Dmitry Baryshkov:
> On 22/02/2023 14:37, Thomas Zimmermann wrote:
>> Do not run drm_fb_helper_unprepare() if fbdev allocation fails. Avoids
>> access to an uninitialized pointer. Original bug report is at [1].
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> Fixes: 3fb1f62f80a1 ("drm/fb-helper: Remove drm_fb_helper_unprepare()
>> from drm_fb_helper_fini()")
>> Link:
>> https://lore.kernel.org/oe-kbuild-all/202302220810.9dymwCQ8-lkp@intel.com/ # 1
>> ---
>> drivers/gpu/drm/msm/msm_fbdev.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
Impressive response time. Thanks a lot.
Best regards
Thomas
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-02-22 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 12:37 [PATCH] drm/msm: Fix possible uninitialized access in fbdev Thomas Zimmermann
2023-02-22 12:37 ` Dmitry Baryshkov
2023-02-22 12:42 ` Thomas Zimmermann [this message]
2023-02-24 17:58 ` Abhinav Kumar
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=08e3340e-b459-0e60-4bba-30716b675e05@suse.de \
--to=tzimmermann@suse.de \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.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