Re: [PATCH 1/1] be2net: Don't leak iomapped memory on removal.

2016-03-04 Thread Sergei Shtylyov
Hello. On 3/4/2016 1:35 AM, Douglas Miller wrote: 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

Re: [PATCH 1/1] be2net: Don't leak iomapped memory on removal.

2016-03-03 Thread Sathya Perla
On Fri, Mar 4, 2016 at 4:05 AM, Douglas Miller wrote: > 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

[PATCH 1/1] be2net: Don't leak iomapped memory on removal.

2016-03-03 Thread Douglas Miller
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 requ