Re: [PATCH] riscv: Use kcalloc() instead of kzalloc()

2024-03-20 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Sat, 20 Jan 2024 14:54:00 +0100 you wrote: > As noted in the "Deprecated Interfaces, Language Features, Attributes, > and Conventions" documentation [1], size calculations (especially > multiplication) should not b

Re: [PATCH] riscv: Use kcalloc() instead of kzalloc()

2024-01-22 Thread Gustavo A. R. Silva
On 1/20/24 07:54, Erick Archer wrote: As noted in the "Deprecated Interfaces, Language Features, Attributes, and Conventions" documentation [1], size calculations (especially multiplication) should not be performed in memory allocator (or similar) function arguments due to the risk of them ove

Re: [PATCH] riscv: Use kcalloc() instead of kzalloc()

2024-01-22 Thread Andrew Jones
On Sat, Jan 20, 2024 at 02:54:00PM +0100, Erick Archer wrote: > As noted in the "Deprecated Interfaces, Language Features, Attributes, > and Conventions" documentation [1], size calculations (especially > multiplication) should not be performed in memory allocator (or similar) > function arguments

Re: [PATCH] riscv: Use kcalloc() instead of kzalloc()

2024-01-21 Thread Alexandre Ghiti
Hi Erick, On 20/01/2024 14:54, Erick Archer wrote: As noted in the "Deprecated Interfaces, Language Features, Attributes, and Conventions" documentation [1], size calculations (especially multiplication) should not be performed in memory allocator (or similar) function arguments due to the risk

[PATCH] riscv: Use kcalloc() instead of kzalloc()

2024-01-20 Thread Erick Archer
As noted in the "Deprecated Interfaces, Language Features, Attributes, and Conventions" documentation [1], size calculations (especially multiplication) should not be performed in memory allocator (or similar) function arguments due to the risk of them overflowing. This could lead to values wrappin