forked from Minki/linux
8f401ec1c8
At region creation time the next region-id is atomically cached so that
there is predictability of region device names. If that region is
destroyed and then a new one is created the region id increments. That
ends up looking like a memory leak, or is otherwise surprising that
identifiers roll forward even after destroying all previously created
regions.
Try to reuse rather than free old region ids at region release time.
While this fixes a cosmetic issue, the needlessly advancing memory
region-id gives the appearance of a memory leak, hence the "Fixes" tag,
but no "Cc: stable" tag.
Cc: Ben Widawsky <bwidawsk@kernel.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Fixes:
|
||
|---|---|---|
| .. | ||
| core.h | ||
| hdm.c | ||
| Makefile | ||
| mbox.c | ||
| memdev.c | ||
| pci.c | ||
| pmem.c | ||
| port.c | ||
| region.c | ||
| regs.c | ||
| suspend.c | ||