From: Lyude Paul <lyude@redhat.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Ma Ke <make24@iscas.ac.cn>,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Ben Skeggs <bskeggs@redhat.com>, Daniel Vetter <daniel@ffwll.ch>,
Danilo Krummrich <dakr@redhat.com>,
Dave Airlie <airlied@redhat.com>,
Karol Herbst <kherbst@redhat.com>
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@gmail.com>
Subject: Re: [PATCH v3] drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes
Date: Fri, 28 Jun 2024 13:49:10 -0400 [thread overview]
Message-ID: <790dbe8aee621b58ec0ef8d029106cb1c1830a31.camel@redhat.com> (raw)
In-Reply-To: <d0bef439-5e1d-4ce0-9a24-da74ddc29755@web.de>
Ma Ke - I assume you already know but you can just ignore this message
from Markus as it is just spam. Sorry about the trouble!
Markus, you've already been asked by Greg so I will ask a bit more
sternly in case there is actually a person on the other end: you've
already been asked to stop by Greg and are being ignored by multiple
kernel maintainers. If I keep seeing messages like this from you I will
assume you are a bot and I will block your email from both DRI related
mailing lists (nouveau and dri-devel) accordingly. You've done this 3
times now.
(...I doubt I'll get a response from Markus, but I certainly want to
make sure they are a bot and not an actual person before removing them
:)
On Thu, 2024-06-27 at 11:02 +0200, Markus Elfring wrote:
> > In nouveau_connector_get_modes(), the return value of
> > drm_mode_duplicate()
> > is assigned to mode, which will lead to a possible NULL pointer
> > dereference on failure of drm_mode_duplicate(). Add a check to
> > avoid npd.
>
> A) Can a wording approach (like the following) be a better change
> description?
>
> A null pointer is stored in the local variable “mode” after a call
> of the function “drm_mode_duplicate” failed. This pointer was
> passed to
> a subsequent call of the function “drm_mode_probed_add” where an
> undesirable
> dereference will be performed then.
> Thus add a corresponding return value check.
>
>
> B) How do you think about to append parentheses to the function name
> in the summary phrase?
>
>
> C) How do you think about to put similar results from static source
> code
> analyses into corresponding patch series?
>
>
> Regards,
> Markus
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
next prev parent reply other threads:[~2024-06-28 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 7:42 Ma Ke
2024-06-27 9:02 ` Markus Elfring
2024-06-28 17:49 ` Lyude Paul [this message]
2024-06-28 18:42 ` [v3] " Markus Elfring
2024-06-28 18:50 ` Lyude Paul
2024-06-28 19:02 ` Markus Elfring
2024-06-28 19:09 ` Lyude Paul
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=790dbe8aee621b58ec0ef8d029106cb1c1830a31.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Markus.Elfring@web.de \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=nouveau@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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®