From: Ken Goldman <kgold@linux.ibm.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-security-module <linux-security-module@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel-team@lge.com
Subject: Re: [PATCH] LSM: add NULL check for kcalloc()
Date: Fri, 6 Aug 2021 14:33:25 -0400 [thread overview]
Message-ID: <b58ae08c-c3b9-12a9-f862-bebfed8a01f2@linux.ibm.com> (raw)
In-Reply-To: <CADLLry6RmSDuB4nmVKDEiqxXmEU0xrhMn2wieuuVTypMWqc4cQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
On 7/14/2021 5:44 PM, Austin Kim wrote:
> 2021년 7월 15일 (목) 오전 4:12, James Morris <jmorris@namei.org>님이 작성:
>>
>> On Tue, 13 Jul 2021, Austin Kim wrote:
>>
>>> From: Austin Kim <austin.kim@lge.com>
>>>
>>> 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 <austin.kim@lge.com>
>>> ---
>>> security/security.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/security/security.c b/security/security.c
>>> index 09533cbb7221..f885c9e9bc35 100644
>>> --- a/security/security.c
>>> +++ b/security/security.c
>>> @@ -321,6 +321,8 @@ static void __init ordered_lsm_init(void)
>>>
>>> ordered_lsms = kcalloc(LSM_COUNT + 1, sizeof(*ordered_lsms),
>>> GFP_KERNEL);
>>> + if (ordered_lsms)
>>> + return;
>>
>> Your logic is reversed here.
>
> 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.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4490 bytes --]
prev parent reply other threads:[~2021-08-06 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 23:44 [PATCH] LSM: add NULL check for kcalloc() Austin Kim
2021-07-14 19:05 ` James Morris
2021-07-14 21:44 ` Austin Kim
2021-08-06 18:33 ` Ken Goldman [this message]
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=b58ae08c-c3b9-12a9-f862-bebfed8a01f2@linux.ibm.com \
--to=kgold@linux.ibm.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 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).