From: Tony Lindgren <tony@atomide.com>
To: Kunwu Chan <chentao@kylinos.cn>
Cc: linux@armlinux.org.uk, ruslan.bilovol@ti.com,
linux-omap@vger.kernel.org, kunwu.chan@hotmail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init
Date: Thu, 30 Nov 2023 13:57:36 +0200 [thread overview]
Message-ID: <20231130115736.GB5169@atomide.com> (raw)
In-Reply-To: <20231123145237.609442-1-chentao@kylinos.cn>
* Kunwu Chan <chentao@kylinos.cn> [231123 16:53]:
> kasprintf() returns a pointer to dynamically allocated memory which can
> be NULL upon failure. When 'soc_dev_attr->family' is NULL,it'll trigger
> the null pointer dereference issue, such as in 'soc_info_show'.
Applying into fixes thanks.
Tony
prev parent reply other threads:[~2023-11-30 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:52 [PATCH] ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init Kunwu Chan
2023-11-30 11:57 ` Tony Lindgren [this message]
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=20231130115736.GB5169@atomide.com \
--to=tony@atomide.com \
--cc=chentao@kylinos.cn \
--cc=kunwu.chan@hotmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ruslan.bilovol@ti.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 read-only IMAP folder(s) and NNTP newsgroup(s).