vfio-ccw: make it safe to access channel programs

Browse source

When we get a solicited interrupt, the start function may have
been cleared by a csch, but we still have a channel program
structure allocated. Make it safe to call the cp accessors in
any case, so we can call them unconditionally.

While at it, also make sure that functions called from other parts
of the code return gracefully if the channel program structure
has not been initialized (even though that is a bug in the caller).

Reviewed-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Farhan Ali <alifm@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>

...

This commit is contained in:

Cornelia Huck 2019-01-21 09:55:18 +01:00

parent 1c410fd6a5

commit 71189f263f

3 changed files with 27 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

21

drivers/s390/cio/vfio_ccw_cp.c

View file

2

drivers/s390/cio/vfio_ccw_cp.h

View file

5

drivers/s390/cio/vfio_ccw_fsm.c

View file