Fix: Remove slot mapping at bankd when client disconnects
If a client disconnects before removing the slot mapping, the slotmap entry will not be removed automatically. A subsequent client connection for the same mapping will then trigger the the error: “ignoring identical slotmap.”
In a setup with multiple readers, there are multiple bankd worker threads. If a client re-connects, but if its connection is accepted by a different thread, subsequent reader access or unmapping will fail. There will be no mapping at the new thread.
The approach of this fix is to remove the slot mapping, if the client connection to the worker thread terminates.
