From: Bjorn Helgaas <helgaas@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
bhelgaas@google.com, guohanjun@huawei.com,
George Cherian <george.cherian@marvell.com>
Subject: Re: [PATCH 0/2] fix memleak when using pci_iounmap()
Date: Fri, 28 Aug 2020 11:06:40 -0500 [thread overview]
Message-ID: <20200828160640.GA2157785@bjorn-Precision-5520> (raw)
In-Reply-To: <20200828063403.3995421-1-yangyingliang@huawei.com>
[+cc George]
On Fri, Aug 28, 2020 at 02:34:01PM +0800, Yang Yingliang wrote:
> config GENERIC_IOMAP is not selected on some arch, pci_iounmap()
> don't implement, when we using pci_iomap/pci_iounmap, it will
> lead to memory leak.
> This patch set moves the implemention of pci_iounmap() to
> lib/pci_iomap.c to fix this.
>
> Yang Yingliang (2):
> iomap: move some definitions to include/linux/io.h
> pci: fix memleak when calling pci_iomap/unmap()
>
> include/asm-generic/pci_iomap.h | 2 ++
> include/linux/io.h | 36 ++++++++++++++++++++++++++
> lib/iomap.c | 46 ---------------------------------
> lib/pci_iomap.c | 8 ++++++
> 4 files changed, 46 insertions(+), 46 deletions(-)
I haven't looked at this yet (and won't because of the build issues),
but please note George's previous similar work:
https://lore.kernel.org/linux-pci/20200824132046.3114383-1-george.cherian@marvell.com/
I haven't compared them, so just FYI that we'll have to integrate them
somehow.
If/when you repost this, please run "git log --oneline" and match the
subject styles. And add blank lines between paragraphs. Use "()"
consistently after function names. And please cc: George, of course.
Bjorn
prev parent reply other threads:[~2020-08-28 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 6:34 [PATCH 0/2] fix memleak when using pci_iounmap() Yang Yingliang
2020-08-28 6:34 ` [PATCH 1/2] iomap: move some definitions to include/linux/io.h Yang Yingliang
2020-08-28 6:34 ` [PATCH 2/2] pci: fix memleak when calling pci_iomap/unmap() Yang Yingliang
2020-08-28 10:19 ` kernel test robot
2020-08-28 11:24 ` kernel test robot
2020-08-28 13:35 ` kernel test robot
2020-08-28 16:06 ` Bjorn Helgaas [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=20200828160640.GA2157785@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=george.cherian@marvell.com \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yangyingliang@huawei.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