[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25c40edd-7c4a-5e6a-2079-6ffd356da7e8@huawei.com>
Date: Sat, 28 Oct 2017 08:28:12 +0800
From: Yisheng Xie <xieyisheng1@...wei.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
CC: <kashyap.desai@...adcom.com>, <sumit.saxena@...adcom.com>,
<shivasharan.srikanteshwara@...adcom.com>,
<jejb@...ux.vnet.ibm.com>, <megaraidlinux.pdl@...adcom.com>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Shu Wang <shuwang@...hat.com>
Subject: Re: [PATCH 2/2] scsi: megaraid: Track the page allocations for struct
fusion_context
hi Martin ,
On 2017/10/25 20:36, Martin K. Petersen wrote:
>
> Yisheng,
>
>> I have get many kmemleak reports just similar to commit 70c54e210ee9
>> (scsi: megaraid_sas: fix memleak in megasas_alloc_cmdlist_fusion)
>> on v4.14-rc6, however it seems have a different stroy:
>
> Do you still see leaks reported with the megaraid driver update recently
> merged into 4.15/scsi-queue?
>
No, the related code have been optimized and __get_free_pages is not used
to allocate fusion_context anymore. So, please ignore this one, and sorry
for disturbing.
BTW, what about the Patch 1/2, which is just a minor clean up?
Thanks
Yisheng Xie
Powered by blists - more mailing lists