This adds a driver on top of the rpmb subsystem for virtio-rpmb devices. Alex Bennée had an earlier virtio-rpmb driver in his RPMB series [1] but that stalled due to the user space API.
The one that merged later has no user space API and OP-TEE routes frames through it so this driver only needs to implement route_frames(). I added patch 1 to fix a use-after-free that I hit while testing removing the device (OP-TEE can still route frames after driver unregisters the rpmb device). I tested this with UML (virtio_uml) and a vhost-user backend I wrote for this on top of rust-vmm's vhost-device with KASAN, lockdep: - key programming - write counter - single and multi block write and read - MAC and counter failures - max_wr_cnt - unbinding the driver when the rpmb device is held With OP-TEE 4.11 on QEMU virt arm64 the secure_storage example TA keeps its objects in RPMB through the driver and an object written to in one boot is found in the one after. I have added myself in MAINTAINERS. I would like to maintain the driver. - haruka [1] https://lore.kernel.org/all/[email protected]/ Haruka Kuze (2): rpmb: stop the routing after unregister rpmb: add a virtio RPMB device driver MAINTAINERS | 7 + drivers/misc/Kconfig | 10 ++ drivers/misc/Makefile | 1 + drivers/misc/rpmb-core.c | 22 ++- drivers/misc/virtio_rpmb.c | 294 +++++++++++++++++++++++++++++++ include/linux/rpmb.h | 4 + include/uapi/linux/virtio_rpmb.h | 56 ++++++ 7 files changed, 391 insertions(+), 3 deletions(-) create mode 100644 drivers/misc/virtio_rpmb.c create mode 100644 include/uapi/linux/virtio_rpmb.h base-commit: c339f4010dea8b0d754f84ace70cd1b089878ef8 -- 2.55.0
