From: Javier Martinez Canillas <javierm@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Maxime Ripard <maxime@cerno.tech>,
Thomas Zimmermann <tzimmermann@suse.de>,
Javier Martinez Canillas <javierm@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>,
Changcheng Deng <deng.changcheng@zte.com.cn>,
Daniel Vetter <daniel@ffwll.ch>,
Guenter Roeck <linux@roeck-us.net>, Helge Deller <deller@gmx.de>,
Sam Ravnborg <sam@ravnborg.org>,
Xiyu Yang <xiyuyang19@fudan.edu.cn>,
Zhen Lei <thunder.leizhen@huawei.com>,
Zheyu Ma <zheyuma97@gmail.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: [PATCH 0/2] fbdev: Fix a NULL pointer dereference in fb_release()
Date: Mon, 2 May 2022 15:09:42 +0200 [thread overview]
Message-ID: <20220502130944.363776-1-javierm@redhat.com> (raw)
Hello,
This small series contains fixes for two bugs I found in fbmem.c, that may
explain a bug reported in the rpi4 [0] when using simplefb and vc4 drivers.
I was not able to reproduce the mentioned bug, but looking at the code I
think that it might explain the issue.
I've tested these patches in a rpi4 with both simplefb and vc4 drivers
built-in and did not find any regression.
[0]: https://github.com/raspberrypi/linux/issues/5011
Best regards,
Javier
Javier Martinez Canillas (2):
fbdev: Check in file_fb_info() if the fb_info was already been freed
fbdev: Make fb_release() return -ENODEV if fbdev was unregistered
drivers/video/fbdev/core/fbmem.c | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-02 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 13:09 Javier Martinez Canillas [this message]
2022-05-02 13:09 ` [PATCH 1/2] fbdev: Check in file_fb_info() if the fb_info was already been freed Javier Martinez Canillas
2022-05-02 13:26 ` Thomas Zimmermann
2022-05-02 13:36 ` Javier Martinez Canillas
2022-05-02 13:09 ` [PATCH 2/2] fbdev: Make fb_release() return -ENODEV if fbdev was unregistered Javier Martinez Canillas
2022-05-02 13:20 ` Thomas Zimmermann
2022-05-02 13:39 ` Javier Martinez Canillas
2022-05-04 9:47 ` Daniel Vetter
2022-05-04 10:09 ` Javier Martinez Canillas
2022-05-04 10:15 ` Daniel Vetter
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=20220502130944.363776-1-javierm@redhat.com \
--to=javierm@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=deng.changcheng@zte.com.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maxime@cerno.tech \
--cc=sam@ravnborg.org \
--cc=thunder.leizhen@huawei.com \
--cc=tzimmermann@suse.de \
--cc=xiyuyang19@fudan.edu.cn \
--cc=zheyuma97@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;
as well as URLs for NNTP newsgroup(s).