> >> Inorder to report the kzalloc failure, I have just used a pr_debug
> >> statement. If it looks ugly, should I change the function's return value
> >> to int and give out an -ENOMEM ?
> >
> > Yes, please do that - and obviously add the checks to the calling code.
>
> But I cannot find any c
On Wednesday 21 May 2014 02:47 PM, Lee Jones wrote:
>> Change from V1 -> V2: Fix a potential null pointer dereference as reported
>> by kbuild test robot .
>>
>> Inorder to report the kzalloc failure, I have just used a pr_debug
>> statement. If it looks ugly, should I change the function's ret
> Change from V1 -> V2: Fix a potential null pointer dereference as reported by
> kbuild test robot .
>
> Inorder to report the kzalloc failure, I have just used a pr_debug statement.
> If it looks ugly, should I change the function's return value to int and give
> out an -ENOMEM ?
Yes, please
H1,
Change from V1 -> V2: Fix a potential null pointer dereference as reported by
kbuild test robot .
Inorder to report the kzalloc failure, I have just used a pr_debug statement.
If it looks ugly, should I change the function's return value to int and give
out an -ENOMEM ?
From 6615c7a995a6b
4 matches
Mail list logo
