aboutsummaryrefslogtreecommitdiffstats
path: root/arch/s390/mm
diff options
context:
space:
mode:
authorHarald Freudenberger <freude@linux.vnet.ibm.com>2017-05-24 10:26:29 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2017-06-02 14:30:12 +0200
commite385050873d1e19e40481d8cd868c9f60ebe46ac (patch)
tree3072228e0be6eaa316d52309752efcd32f69d277 /arch/s390/mm
parentMerge tag 'vfio-ccw-20170522' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw into fixes (diff)
downloadlinux-dev-e385050873d1e19e40481d8cd868c9f60ebe46ac.tar.xz
linux-dev-e385050873d1e19e40481d8cd868c9f60ebe46ac.zip
s390/zcrypt: Fix blocking queue device after unbind/bind.
When the association between a queue device and the driver is released via unbind and later re-associated the queue device was not operational any more. Reason was a wrong administration of the card/queue lists within the ap device driver. This patch introduces revised card/queue list handling within the ap device driver: when an ap device is detected it is initial not added to the card/queue list any more. With driver probe the card device is added to the card list/the queue device is added to the queue list within a card. With driver remove the device is removed from the card/queue list. Additionally there are some situations within the ap device live where the lists need update upon card/queue device release (for example device hot unplug or suspend/resume). Signed-off-by: Harald Freudenberger <freude@linux.vnet.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/mm')
0 files changed, 0 insertions, 0 deletions