[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <236195a3-b607-5cf6-ac60-8c5ea2e95b41@cogentembedded.com>
Date: Thu, 30 May 2019 12:22:15 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Gen Zhang <blackgod016574@...il.com>
Cc: paul@...l-moore.com, sds@...ho.nsa.gov, eparis@...isplace.org,
ccross@...roid.com, selinux@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] hooks: fix a missing-check bug in selinux_add_mnt_opt()
On 30.05.2019 12:18, Gen Zhang wrote:
>> On 30.05.2019 11:06, Gen Zhang wrote:
>>
>>> In selinux_add_mnt_opt(), 'val' is allcoted by kmemdup_nul(). It returns
>>
>> Allocated?
> Thanks for your reply, Sergei. I used 'allocated' because kmemdup_nul()
> does some allocation in its implementation. And its docs descrips:
Describes?
> "Return: newly allocated copy of @s with NUL-termination or %NULL in
> case of error". I think it is proper to use 'allocated' here. But it
> could be 'assigned', which is better, right?
I was only trying to point out the typos in this word. :-)
> Thanks
> Gen
>>
>>> NULL when fails. So 'val' should be checked.
>>>
>>> Signed-off-by: Gen Zhang <blackgod016574@...il.com>
>> [...]
MBR, Sergei
Powered by blists - more mailing lists