From 563d56bc6170b6367d1f91d9a03ab3748cff24cd Mon Sep 17 00:00:00 2001 From: Christian Kellner Date: Sat, 14 Aug 2021 09:49:11 +0000 Subject: [PATCH] devices/loopback: it is flush_buf not flushbuf That ironically fix the underlying bug that flush_buf is trying to fix too, since now an exception is thrown and we are back to auto clear. The file fd is then closed when the process is terminated. Anyway, the right fix is to call the correct function. --- devices/org.osbuild.loopback | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/org.osbuild.loopback b/devices/org.osbuild.loopback index 9415103e..db1b7abd 100755 --- a/devices/org.osbuild.loopback +++ b/devices/org.osbuild.loopback @@ -123,7 +123,7 @@ class LoopbackService(devices.DeviceService): # seems to be required when clearing the fd of the # loop device (as of kernel 5.13.8) or otherwise # it leads to data loss. - self.lo.flushbuf() + self.lo.flush_buf() # clear the fd. Since it might not immediately be # cleared (due to a race with udev or some other