From 7ddcb15289a25a478a6bf7f353f2b4754b4af017 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Mon, 3 Jun 2019 17:13:30 +0200 Subject: [PATCH 3/5] syscalls: 'with-lock-file' catches ENOSYS. * guix/build/syscalls.scm (call-with-file-lock): Catch ENOSYS raised by 'lock-file'. --- guix/build/syscalls.scm | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/guix/build/syscalls.scm b/guix/build/syscalls.scm index 3af41f2cf5..5c2eb3c14d 100644 --- a/guix/build/syscalls.scm +++ b/guix/build/syscalls.scm @@ -1084,13 +1084,24 @@ exception if it's already taken." #t) (define (call-with-file-lock file thunk) - (let ((port (lock-file file))) + (let ((port (catch 'system-error + (lambda () + (lock-file file)) + (lambda args + ;; When using the statically-linked Guile in the initrd, + ;; 'fcntl-flock' returns ENOSYS unconditionally. Ignore + ;; that error since we're typically the only process running + ;; at this point. + (if (= ENOSYS (system-error-errno args)) + #f + (apply throw args)))))) (dynamic-wind (lambda () #t) thunk (lambda () - (unlock-file port))))) + (when port + (unlock-file port)))))) (define-syntax-rule (with-file-lock file exp ...) "Wait to acquire a lock on FILE and evaluate EXP in that context." -- 2.21.0