From: Douglas Miller <dougmill@linux.vnet.ibm.com>
To: netdev@vger.kernel.org
Cc: sathya.perla@broadcom.com, ajit.khaparde@broadcom.com,
padmanabh.ratnakar@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com
Subject: [PATCH 0/1] be2net: Don't leak iomapped memory on removal.
Date: Thu, 3 Mar 2016 16:35:48 -0600 [thread overview]
Message-ID: <1457044549-10563-1-git-send-email-dougmill@linux.vnet.ibm.com> (raw)
The adapter->pcicfg resource is either mapped via pci_iomap() or
derived from adapter->db. During be_remove() this resource was ignored
and so could remain mapped after remove.
Add a flag to track whether adapter->pcicfg was mapped or not, then
use that flag in be_unmap_pci_bars() to unmap if required.
Signed-off-by: Douglas Miller <dougmill@linux.vnet.ibm.com>
next reply other threads:[~2016-03-03 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:35 Douglas Miller [this message]
2016-03-03 22:35 ` [PATCH 1/1] be2net: Don't leak iomapped memory on removal Douglas Miller
2016-03-04 5:00 ` Sathya Perla
2016-03-04 13:18 ` Sergei Shtylyov
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=1457044549-10563-1-git-send-email-dougmill@linux.vnet.ibm.com \
--to=dougmill@linux.vnet.ibm.com \
--cc=ajit.khaparde@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=padmanabh.ratnakar@broadcom.com \
--cc=sathya.perla@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@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;
as well as URLs for NNTP newsgroup(s).