tree 0e5d92a7fc005a17174bb02c768512164efb01dd
parent c103ed09b4a174bdeba2de646bdd1b0545b1bd89
author Matthew Wilcox <matthew@wil.cx> 1567573374 +0000
committer Johannes Weiner <hannes@cmpxchg.org> 1567573374 +0000

Make sure nobody's leaking resources

Currently, releasing a resource also releases all of its children.  That
made sense when request_resource was the main method of dividing up the
memory map.  With the increased use of insert_resource, it seems to me that
we should instead reparent the newly orphaned resources.  Before we do
that, let's make sure that nobody's actually relying on the current
semantics.

Signed-off-by: Matthew Wilcox <matthew@wil.cx>
Cc: Greg KH <greg@kroah.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>