On 6/9/20 7:22 PM, Julia Lawall wrote:
>
>
> On Mon, 8 Jun 2020, Denis Efremov wrote:
>
>> Check that the rule matches vmemdup_user implementation.
>> memdup_user is out of scope because we are not matching
>> kmalloc_track_caller() function.
>
> Is this a bit over-enginered?
Last patch
On Mon, 8 Jun 2020, Denis Efremov wrote:
> Check that the rule matches vmemdup_user implementation.
> memdup_user is out of scope because we are not matching
> kmalloc_track_caller() function.
Is this a bit over-enginered? More precisely, even if it is nice to check
that the API definition
2 matches
Mail list logo