Eric Farman cd37040ba9 vfio-ccw: Check initialized flag in cp_init() ... [ Upstream commit c6c82e0cd8 ] We have a really nice flag in the channel_program struct that indicates if it had been initialized by cp_init(), and use it as a guard in the other cp accessor routines, but not for a duplicate call into cp_init(). The possibility of this occurring is low, because that flow is protected by the private->io_mutex and FSM CP_PROCESSING state. But then why bother checking it in (for example) cp_prefetch() then? Let's just be consistent and check for that in cp_init() too. Fixes: 71189f263f ("vfio-ccw: make it safe to access channel programs") Signed-off-by: Eric Farman <farman@linux.ibm.com> Reviewed-by: Cornelia Huck <cohuck@redhat.com> Acked-by: Matthew Rosato <mjrosato@linux.ibm.com> Message-Id: <20210511195631.3995081-2-farman@linux.ibm.com> Signed-off-by: Cornelia Huck <cohuck@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>		2021-06-03 09:00:46 +02:00
..
block	s390/dasd: fix hanging IO request during DASD driver unbind	2021-03-17 17:06:28 +01:00
char	s390 updates for the 5.10 merge window	2020-10-16 12:36:38 -07:00
cio	vfio-ccw: Check initialized flag in cp_init()	2021-06-03 09:00:46 +02:00
crypto	s390/zcrypt: fix zcard and zqueue hot-unplug memleak	2021-05-11 14:47:11 +02:00
net	s390/qeth: schedule TX NAPI on QAOB completion	2021-03-25 09:04:13 +01:00
scsi	s390 updates for the 5.10 merge window	2020-10-16 12:36:38 -07:00
virtio	virtio/s390: implement virtio-ccw revision 2 correctly	2021-03-04 11:38:42 +01:00
Makefile	s390: remove pointless drivers-y in drivers/s390/Makefile	2019-09-16 13:21:51 +02:00