From: "Jackie Liu" <liu.yun@linux.dev>
To: "Huacai Chen" <chenhuacai@kernel.org>
Cc: kernel@xen0n.name, loongarch@lists.linux.dev
Subject: Re: [PATCH 2/2] loongarch/env: fix missing NULL check after kstrdup()
Date: Thu, 18 Sep 2025 07:27:58 +0000 [thread overview]
Message-ID: <59f762f22d964641fb67d4c72d91958270dd453c@linux.dev> (raw)
In-Reply-To: <CAAhV-H6G7eMFCEiF9fijiyFELMKv5s1hUy=HK9iCU7RPrp2AJA@mail.gmail.com>
Hi Huacai.
2025年9月18日 15:15, "Huacai Chen" <chenhuacai@kernel.org mailto:chenhuacai@kernel.org?to=%22Huacai%20Chen%22%20%3Cchenhuacai%40kernel.org%3E > 写到:
>
> Hi, Jackie,
>
> Your partner has already sent a patch and be NAKed, don't you know?
>
> https://lore.kernel.org/loongarch/5169d057-28c9-439c-a6b7-1138b4f79e65@xen0n.name/T/#t
>
> Huacai
Yes, I was just reviewing the code and happened to check this while
investigating other crash issues. It looks like passing NULL to strsep
won’t cause a crash, so this can safely be ignored. Thanks for pointing
it out.
---
Jackie Liu
>
> On Thu, Sep 18, 2025 at 2:45 PM Jackie Liu <liu.yun@linux.dev> wrote:
>
> >
> > From: Jackie Liu <liuyun01@kylinos.cn>
> >
> > The result of kstrdup() may be NULL when memory allocation fails.
> > In init_cpu_fullname(), the return value was used directly by strsep()
> > without validation, which could lead to NULL pointer dereference.
> >
> > Add a proper check for the kstrdup() result and return -ENOMEM when
> > allocation fails.
> >
> > Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
> > ---
> > arch/loongarch/kernel/env.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/loongarch/kernel/env.c b/arch/loongarch/kernel/env.c
> > index c0a5dc9aeae2..b41a65ec45c3 100644
> > --- a/arch/loongarch/kernel/env.c
> > +++ b/arch/loongarch/kernel/env.c
> > @@ -49,6 +49,8 @@ static int __init init_cpu_fullname(void)
> > ret = of_property_read_string(root, "model", &model);
> > if (ret == 0) {
> > cpuname = kstrdup(model, GFP_KERNEL);
> > + if (!cpuname)
> > + return -ENOMEM;
> > loongson_sysconf.cpuname = strsep(&cpuname, " ");
> > }
> > of_node_put(root);
> > --
> > 2.51.0
> >
>
next prev parent reply other threads:[~2025-09-18 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 6:44 [PATCH 1/2] loongarch/vdso: add missing NULL check after kcalloc() Jackie Liu
2025-09-18 6:44 ` [PATCH 2/2] loongarch/env: fix missing NULL check after kstrdup() Jackie Liu
2025-09-18 7:15 ` Huacai Chen
2025-09-18 7:27 ` Jackie Liu [this message]
2025-09-18 7:17 ` [PATCH 1/2] loongarch/vdso: add missing NULL check after kcalloc() Huacai Chen
2025-09-18 7:24 ` Jackie Liu
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=59f762f22d964641fb67d4c72d91958270dd453c@linux.dev \
--to=liu.yun@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=loongarch@lists.linux.dev \
/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