From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] driver: core: Prevent NULL pointer dereference in device name functions
Date: Mon, 13 Feb 2023 08:07:09 +0100 [thread overview]
Message-ID: <Y+nhnauiUDspXwNM@kroah.com> (raw)
In-Reply-To: <20230212220441.258258-1-alexander.sverdlin@gmail.com>
On Sun, Feb 12, 2023 at 11:04:41PM +0100, Alexander Sverdlin wrote:
> Prevent similar scenarios:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000038
> ...
> PC is at dev_driver_string+0x0/0x38
How did this "scenario" happen? What in-tree code caused this?
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---
> drivers/base/core.c | 3 +++
> include/linux/device.h | 5 +++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index a3e14143ec0c..4ff2ddea7c9b 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -2174,6 +2174,9 @@ const char *dev_driver_string(const struct device *dev)
> {
> struct device_driver *drv;
>
> + if (!dev)
> + return "<null>";
> +
None of these functions should be called with a NULL pointer as the
reference should have been properly gotten on them before calling these
functions. So let's fix up the callers please, something is really
wrong with them. Again, what in-tree code is causing this to happen?
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-13 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 22:04 Alexander Sverdlin
2023-02-13 7:07 ` Greg Kroah-Hartman [this message]
2023-02-13 7:12 ` Alexander Sverdlin
2023-02-13 7:16 ` Greg Kroah-Hartman
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=Y+nhnauiUDspXwNM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.sverdlin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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®