[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4094dc04-bb2c-a74e-8d4d-8879ac4e7761@users.sourceforge.net>
Date: Mon, 13 Feb 2017 12:12:51 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Dan Carpenter <dan.carpenter@...cle.com>,
linux-rdma@...r.kernel.org
Cc: Dennis Dalessandro <dennis.dalessandro@...el.com>,
Doug Ledford <dledford@...hat.com>,
Hal Rosenstock <hal.rosenstock@...il.com>,
Mike Marciniszyn <mike.marciniszyn@...el.com>,
Sean Hefty <sean.hefty@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: IB/hfi1: Use memdup_user() rather than duplicating its
implementation in hfi1_user_sdma_process_request()
>> Thanks for the patch, but this one is already taken care of along
>> with other similar uses of kmalloc/copy:
>>
>> http://marc.info/?l=linux-rdma&m=148656088729538&w=2
>>
>
> Michael's patch doesn't change user_sdma_free_request() so it introduces
> a kfreeing an error pointer bug.
Did you notice that another local variable “tmp” was introduced in the update step
“[PATCH 27/27] IB/hfi1: Code reuse with memdup_copy” so that
the mentioned function will usually get a null pointer after a failure there?
Regards,
Markus
Powered by blists - more mailing lists