mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Shu Wang <shuwang@redhat.com>
Subject: Re: [PATCH 2/2] scsi: megaraid: Track the page allocations for struct fusion_context
Date: Sat, 28 Oct 2017 08:28:12 +0800	[thread overview]
Message-ID: <25c40edd-7c4a-5e6a-2079-6ffd356da7e8@huawei.com> (raw)
In-Reply-To: <yq17evjieug.fsf@oracle.com>

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

  reply	other threads:[~2017-10-28  0:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  9:57 [PATCH 1/2] scsi: megaraid: Remove redundant code in megasas_alloc_cmds Yisheng Xie
2017-10-25  9:57 ` [PATCH 2/2] scsi: megaraid: Track the page allocations for struct fusion_context Yisheng Xie
2017-10-25 12:36   ` Martin K. Petersen
2017-10-28  0:28     ` Yisheng Xie [this message]
2017-10-31 12:15       ` Martin K. Petersen
2017-10-31 17:36 ` [PATCH 1/2] scsi: megaraid: Remove redundant code in megasas_alloc_cmds Sumit Saxena
2017-11-03 15:26 ` Martin K. Petersen

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=25c40edd-7c4a-5e6a-2079-6ffd356da7e8@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-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
all inboxes | Powered by JetHome®