lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 5 May 2020 20:15:43 -0400 From: Jared Rossi <jrossi@...ux.ibm.com> To: Eric Farman <farman@...ux.ibm.com>, Cornelia Huck <cohuck@...hat.com>, Halil Pasic <pasic@...ux.ibm.com> Cc: linux-s390@...r.kernel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [PATCH v3 0/1] vfio-ccw: Enable transparent CCW IPL from DASD Remove the explicit prefetch check when using vfio-ccw devices. This check does not trigger in practice as all Linux channel programs are intended to use prefetch. Version 3 improves logging by including the UUID of the vfio device that triggers the warning. A custom rate limit is used because the generic rate limit of 10 per 5 seconds will still result in multiple warnings during IPL. The warning message has been clarfied to reflect that a channel program will be executed using prefetch even though prefetch was not specified. The text of warning itself does not explicitly refer to non-prefetching channel programs as unsupported because it will trigger during IPL, which is a normal and expected sequence. Likewise, because we expect the message to appear during IPL, the warning also does not explicitly alert to the potential of an error, rather it simply notes that a channel program is being executed in a way other than specified. Verson 3 also makes some word choice changes to the documentation. Jared Rossi (1): vfio-ccw: Enable transparent CCW IPL from DASD Documentation/s390/vfio-ccw.rst | 6 ++++++ drivers/s390/cio/vfio_ccw_cp.c | 19 ++++++++++++------- 2 files changed, 18 insertions(+), 7 deletions(-) -- 2.17.0
Powered by blists - more mailing lists