From d0b4ebca3ac6aab7b5aff7d9cd604984169a796b Mon Sep 17 00:00:00 2001
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Sat, 14 Nov 2020 12:07:50 +0100
Subject: rumpdisk: Comment on thread-safety requirements

---
 rumpdisk/block-rump.c | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'rumpdisk')

diff --git a/rumpdisk/block-rump.c b/rumpdisk/block-rump.c
index f7444260..afd91d49 100644
--- a/rumpdisk/block-rump.c
+++ b/rumpdisk/block-rump.c
@@ -335,6 +335,9 @@ device_get_status (void *d, dev_flavor_t flavor, dev_status_t status,
  * Short term strategy:
  *
  * Make device_read/write multithreaded.
+ * Note: this would require an rwlock between device_open/close/read/write, to
+ * protect against e.g. concurrent open, unexpected close while read/write is
+ * called, etc.
  *
  * Long term strategy:
  *
-- 
cgit v1.2.3