From: <ye.xingchen@zte.com.cn>
To: richard.henderson@linaro.org
Cc: ink@jurassic.park.msu.ru, mattst88@gmail.com,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
chi.minghao@zte.com.cn
Subject: [PATCH] alpha: potential dereference of null pointer
Date: Tue, 17 Jan 2023 18:23:47 +0800 (CST) [thread overview]
Message-ID: <202301171823476416320@zte.com.cn> (raw)
From: Minghao Chi <chi.minghao@zte.com.cn>
The return value of kmalloc() needs to be checked.
To avoid use of null pointer in case of the failure of alloc.
Reported-by: Zeal Robot <zealci@zte.com.cn>
Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
---
arch/alpha/kernel/module.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/alpha/kernel/module.c b/arch/alpha/kernel/module.c
index 5b60c248de9e..5442b75a98c2 100644
--- a/arch/alpha/kernel/module.c
+++ b/arch/alpha/kernel/module.c
@@ -47,6 +47,8 @@ process_reloc_for_got(Elf64_Rela *rela,
}
g = kmalloc (sizeof (*g), GFP_KERNEL);
+ if (!g)
+ return;
g->next = chains[r_sym].next;
g->r_addend = r_addend;
g->got_offset = *poffset;
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: <ye.xingchen@zte.com.cn>
To: <richard.henderson@linaro.org>
Cc: <ink@jurassic.park.msu.ru>, <mattst88@gmail.com>,
<linux-alpha@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<chi.minghao@zte.com.cn>
Subject: [PATCH] alpha: potential dereference of null pointer
Date: Tue, 17 Jan 2023 18:23:47 +0800 (CST) [thread overview]
Message-ID: <202301171823476416320@zte.com.cn> (raw)
From: Minghao Chi <chi.minghao@zte.com.cn>
The return value of kmalloc() needs to be checked.
To avoid use of null pointer in case of the failure of alloc.
Reported-by: Zeal Robot <zealci@zte.com.cn>
Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
---
arch/alpha/kernel/module.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/alpha/kernel/module.c b/arch/alpha/kernel/module.c
index 5b60c248de9e..5442b75a98c2 100644
--- a/arch/alpha/kernel/module.c
+++ b/arch/alpha/kernel/module.c
@@ -47,6 +47,8 @@ process_reloc_for_got(Elf64_Rela *rela,
}
g = kmalloc (sizeof (*g), GFP_KERNEL);
+ if (!g)
+ return;
g->next = chains[r_sym].next;
g->r_addend = r_addend;
g->got_offset = *poffset;
--
2.25.1
next reply other threads:[~2023-01-17 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 10:23 ye.xingchen [this message]
2023-01-17 10:23 ` [PATCH] alpha: potential dereference of null pointer ye.xingchen
2023-01-18 18:16 ` Al Viro
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=202301171823476416320@zte.com.cn \
--to=ye.xingchen@zte.com.cn \
--cc=chi.minghao@zte.com.cn \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.