linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zheng Zengkai <zhengzengkai@huawei.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: <linux-security-module@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <jmorris@namei.org>,
	<serge@hallyn.com>, <weiyongjun1@huawei.com>
Subject: Re: [PATCH] tomoyo: Avoid potential null pointer access
Date: Thu, 26 Nov 2020 14:33:55 +0800	[thread overview]
Message-ID: <01d29bbf-9d77-c787-b2c2-d88a6a5047f7@huawei.com> (raw)
In-Reply-To: <cfc96d99-adff-6eb9-9685-422587830eb8@i-love.sakura.ne.jp>

Hello, Tetsuo

Got it , Thank you for your explanation.

> Hello, Zheng.
>
> Thank you for a patch, but I won't apply this patch.
> Expected behavior is that tomoyo_warn_oom() is called
> if tomoyo_memory_ok() is called with entry == NULL.
>
> Adding __GFP_NOWARN might be OK, but returning without tomoyo_warn_oom() is NG.
>
> On 2020/11/25 21:10, Zheng Zengkai wrote:
>> Calls to kzalloc() should be null-checked in order to avoid
>> any potential failures or unnecessary code execution.
>> Fix this by adding null checks for _entry_ right after allocation.
>>
>> Fixes: 57c2590fb7fd ("TOMOYO: Update profile structure")
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Zheng Zengkai <zhengzengkai@huawei.com>
> Nacked-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>

As your say,  I found the function tomoyo_assign_namespace( )

in security/tomoyo/domain.c has the similar situation,

Can I add __GFP_NOWARN for both and remove the null check for _entry_ in 
tomoyo_assign_namespace( )?

diff --git a/security/tomoyo/common.c b/security/tomoyo/common.c
index 4bee32bfe16d..bc54d3c8c70a 100644
--- a/security/tomoyo/common.c
+++ b/security/tomoyo/common.c
@@ -498,7 +498,7 @@ static struct tomoyo_profile *tomoyo_assign_profile
         ptr = ns->profile_ptr[profile];
         if (ptr)
                 return ptr;
-       entry = kzalloc(sizeof(*entry), GFP_NOFS);
+       entry = kzalloc(sizeof(*entry), GFP_NOFS | __GFP_NOWARN);
         if (mutex_lock_interruptible(&tomoyo_policy_lock))
                 goto out;
         ptr = ns->profile_ptr[profile];
diff --git a/security/tomoyo/domain.c b/security/tomoyo/domain.c
index dc4ecc0b2038..c6e5cc5cc7cd 100644
--- a/security/tomoyo/domain.c
+++ b/security/tomoyo/domain.c
@@ -473,9 +473,7 @@ struct tomoyo_policy_namespace 
*tomoyo_assign_namespace(const char *domainname)
                 return ptr;
         if (len >= TOMOYO_EXEC_TMPSIZE - 10 || 
!tomoyo_domain_def(domainname))
                 return NULL;
-       entry = kzalloc(sizeof(*entry) + len + 1, GFP_NOFS);
-       if (!entry)
-               return NULL;
+       entry = kzalloc(sizeof(*entry) + len + 1, GFP_NOFS | __GFP_NOWARN);
         if (mutex_lock_interruptible(&tomoyo_policy_lock))
                 goto out;
         ptr = tomoyo_find_namespace(domainname, len);

>> ---
>>   security/tomoyo/common.c | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/security/tomoyo/common.c b/security/tomoyo/common.c
>> index 4bee32bfe16d..99b4fafcb100 100644
>> --- a/security/tomoyo/common.c
>> +++ b/security/tomoyo/common.c
>> @@ -499,6 +499,8 @@ static struct tomoyo_profile *tomoyo_assign_profile
>>   	if (ptr)
>>   		return ptr;
>>   	entry = kzalloc(sizeof(*entry), GFP_NOFS);
>> +	if (!entry)
>> +		return NULL;
>>   	if (mutex_lock_interruptible(&tomoyo_policy_lock))
>>   		goto out;
>>   	ptr = ns->profile_ptr[profile];
>>
> .
>

  reply	other threads:[~2020-11-26  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 12:10 [PATCH] tomoyo: Avoid potential null pointer access Zheng Zengkai
2020-11-25 12:25 ` Tetsuo Handa
2020-11-26  6:33   ` Zheng Zengkai [this message]
2020-11-26  6:57     ` Tetsuo Handa
2020-11-27  7:17       ` Zheng Zengkai
2020-11-27 10:52         ` Tetsuo Handa

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=01d29bbf-9d77-c787-b2c2-d88a6a5047f7@huawei.com \
    --to=zhengzengkai@huawei.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=serge@hallyn.com \
    --cc=weiyongjun1@huawei.com \
    /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).