* [PATCH v2] powerpc/mm: Fix null-pointer dereference in pgtable_cache_add
@ 2023-11-30 9:09 Kunwu Chan
2023-12-01 10:17 ` Michael Ellerman
0 siblings, 1 reply; 3+ messages in thread
From: Kunwu Chan @ 2023-11-30 9:09 UTC (permalink / raw)
To: mpe, npiggin, christophe.leroy
Cc: linuxppc-dev, linux-kernel, Kunwu Chan, kunwu.chan
kasprintf() returns a pointer to dynamically allocated memory
which can be NULL upon failure. Ensure the allocation was successful
by checking the pointer validity.
Suggested-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
---
v2: Use "panic" instead of "return"
---
arch/powerpc/mm/init-common.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/powerpc/mm/init-common.c b/arch/powerpc/mm/init-common.c
index 119ef491f797..9788950b33f5 100644
--- a/arch/powerpc/mm/init-common.c
+++ b/arch/powerpc/mm/init-common.c
@@ -139,6 +139,8 @@ void pgtable_cache_add(unsigned int shift)
align = max_t(unsigned long, align, minalign);
name = kasprintf(GFP_KERNEL, "pgtable-2^%d", shift);
+ if (!name)
+ panic("Failed to allocate memory for order %d", shift);
new = kmem_cache_create(name, table_size, align, 0, ctor(shift));
if (!new)
panic("Could not allocate pgtable cache for order %d", shift);
--
2.34.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] powerpc/mm: Fix null-pointer dereference in pgtable_cache_add
2023-11-30 9:09 [PATCH v2] powerpc/mm: Fix null-pointer dereference in pgtable_cache_add Kunwu Chan
@ 2023-12-01 10:17 ` Michael Ellerman
2023-12-04 2:27 ` Kunwu Chan
0 siblings, 1 reply; 3+ messages in thread
From: Michael Ellerman @ 2023-12-01 10:17 UTC (permalink / raw)
To: Kunwu Chan, npiggin, christophe.leroy
Cc: linuxppc-dev, linux-kernel, Kunwu Chan, kunwu.chan
Kunwu Chan <chentao@kylinos.cn> writes:
> kasprintf() returns a pointer to dynamically allocated memory
> which can be NULL upon failure. Ensure the allocation was successful
> by checking the pointer validity.
>
> Suggested-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
> ---
> v2: Use "panic" instead of "return"
> ---
> arch/powerpc/mm/init-common.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/powerpc/mm/init-common.c b/arch/powerpc/mm/init-common.c
> index 119ef491f797..9788950b33f5 100644
> --- a/arch/powerpc/mm/init-common.c
> +++ b/arch/powerpc/mm/init-common.c
> @@ -139,6 +139,8 @@ void pgtable_cache_add(unsigned int shift)
>
> align = max_t(unsigned long, align, minalign);
> name = kasprintf(GFP_KERNEL, "pgtable-2^%d", shift);
> + if (!name)
> + panic("Failed to allocate memory for order %d", shift);
> new = kmem_cache_create(name, table_size, align, 0, ctor(shift));
> if (!new)
> panic("Could not allocate pgtable cache for order %d", shift);
It would be nice to avoid two calls to panic. Can you reorganise the
logic so that there's only one? Initialising new to NULL might help.
cheers
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] powerpc/mm: Fix null-pointer dereference in pgtable_cache_add
2023-12-01 10:17 ` Michael Ellerman
@ 2023-12-04 2:27 ` Kunwu Chan
0 siblings, 0 replies; 3+ messages in thread
From: Kunwu Chan @ 2023-12-04 2:27 UTC (permalink / raw)
To: Michael Ellerman, npiggin, christophe.leroy
Cc: linuxppc-dev, linux-kernel, kunwu.chan
Sure,i'll follow your suggestion in v3 patch:
1. set new to NULL
2. add a 'if' judgment before 'kmem_cache_create'
Thanks,
Kunwu
On 2023/12/1 18:17, Michael Ellerman wrote:
> avoid two calls to panic
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-12-04 2:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-30 9:09 [PATCH v2] powerpc/mm: Fix null-pointer dereference in pgtable_cache_add Kunwu Chan
2023-12-01 10:17 ` Michael Ellerman
2023-12-04 2:27 ` Kunwu Chan
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 NNTP newsgroup(s).