From: Yisheng Xie <xieyisheng1@huawei.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
shivasharan.srikanteshwara@broadcom.com, jejb@linux.vnet.ibm.com,
megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Shu Wang <shuwang@redhat.com>
Subject: Re: [PATCH 2/2] scsi: megaraid: Track the page allocations for struct fusion_context
Date: Thu, 26 Oct 2017 09:17:29 +0800 [thread overview]
Message-ID: <5a4a6b21-bd94-910a-a278-265b848a50a5@huawei.com> (raw)
In-Reply-To: <yq17evjieug.fsf@oracle.com>
Hi Martin K. Peterseni 1/4 ?
Thanks for comment!
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, sorry to disturb. Please ignore
this one.
Thanks
Yisheng Xie
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-10-26 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1508925428-51660-1-git-send-email-xieyisheng1@huawei.com>
2017-10-25 9:57 ` Yisheng Xie
2017-10-25 12:36 ` Martin K. Petersen
2017-10-26 1:17 ` Yisheng Xie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a4a6b21-bd94-910a-a278-265b848a50a5@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=shuwang@redhat.com \
--cc=sumit.saxena@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox