From: Austin Kim <hidden> Date: 2021-07-12 23:44:41
From: Austin Kim <redacted>
kcalloc() may return NULL when memory allocation fails.
So it is necessary to add NULL check after the call to kcalloc() is made.
Signed-off-by: Austin Kim <redacted>
---
security/security.c | 2 ++
1 file changed, 2 insertions(+)
From: James Morris <jmorris@namei.org> Date: 2021-07-14 19:12:34
On Tue, 13 Jul 2021, Austin Kim wrote:
quoted hunk
From: Austin Kim <redacted>
kcalloc() may return NULL when memory allocation fails.
So it is necessary to add NULL check after the call to kcalloc() is made.
Signed-off-by: Austin Kim <redacted>
---
security/security.c | 2 ++
1 file changed, 2 insertions(+)
From: Austin Kim <hidden> Date: 2021-07-14 21:45:07
2021년 7월 15일 (목) 오전 4:12, James Morris [off-list ref]님이 작성:
On Tue, 13 Jul 2021, Austin Kim wrote:
quoted
From: Austin Kim <redacted>
kcalloc() may return NULL when memory allocation fails.
So it is necessary to add NULL check after the call to kcalloc() is made.
Signed-off-by: Austin Kim <redacted>
---
security/security.c | 2 ++
1 file changed, 2 insertions(+)
From: Ken Goldman <hidden> Date: 2021-08-06 18:33:32
On 7/14/2021 5:44 PM, Austin Kim wrote:
2021년 7월 15일 (목) 오전 4:12, James Morris [off-list ref]님이 작성:
quoted
On Tue, 13 Jul 2021, Austin Kim wrote:
quoted
From: Austin Kim <redacted>
kcalloc() may return NULL when memory allocation fails.
So it is necessary to add NULL check after the call to kcalloc() is made.
Signed-off-by: Austin Kim <redacted>
---
security/security.c | 2 ++
1 file changed, 2 insertions(+)
I feel very sorry for my terrible mistake.
'if (ordered_lsms)' should have been 'if (!ordered_lsms)'.
I know it's a bit more typing, but
if (ordered_lsms == NULL)
compiles down to the same binary and avoids there errors that
try to treat a pointer as a boolean.