-
- Downloads
[S390] cio: introduce cio_update_schib
There is the chance that we get condition code 0 for a stsch but the resulting schib is not vaild. In the current code there are 2 cases: * we do a check for validity of the schib after stsch, but at this time we have already stored the invaild schib in the subchannel structure. This may lead to problems. * we don't do a check for validity, which is not that good either. The patch addresses both issues by introducing the stsch wrapper cio_update_schib which performs stsch on a local schib. This schib is only written back to the subchannel if it's valid. side note: For some functions (chp_events) the return codes are different now (-ENXIO vs -ENODEV) but this shouldn't do harm since the caller doesn't check for _specific_ errors. Signed-off-by:Sebastian Ott <sebott@linux.vnet.ibm.com> Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com>
Showing
- drivers/s390/cio/chsc_sch.c 1 addition, 1 deletiondrivers/s390/cio/chsc_sch.c
- drivers/s390/cio/cio.c 35 additions, 12 deletionsdrivers/s390/cio/cio.c
- drivers/s390/cio/cio.h 1 addition, 0 deletionsdrivers/s390/cio/cio.h
- drivers/s390/cio/cmf.c 5 additions, 3 deletionsdrivers/s390/cio/cmf.c
- drivers/s390/cio/device.c 4 additions, 9 deletionsdrivers/s390/cio/device.c
- drivers/s390/cio/device_fsm.c 17 additions, 11 deletionsdrivers/s390/cio/device_fsm.c
- drivers/s390/cio/device_pgid.c 1 addition, 1 deletiondrivers/s390/cio/device_pgid.c
- drivers/s390/cio/device_status.c 3 additions, 1 deletiondrivers/s390/cio/device_status.c
Loading
Please register or sign in to comment