From d71ba930ab7a8a0ff09b46e9d177ca0feed34119 Mon Sep 17 00:00:00 2001
From: Alexandre Julliard <julliard@winehq.org>
Date: Fri, 21 Mar 2003 21:31:35 +0000
Subject: [PATCH] Ignore fcntl failure when setting a write lock on a read only
 file.

---
 server/fd.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/server/fd.c b/server/fd.c
index f063b06e39..05347def63 100644
--- a/server/fd.c
+++ b/server/fd.c
@@ -538,6 +538,12 @@ static int set_unix_lock( const struct fd *fd, file_pos_t start, file_pos_t end,
         case EAGAIN:
             set_error( STATUS_FILE_LOCK_CONFLICT );
             return 0;
+        case EBADF:
+            /* this can happen if we try to set a write lock on a read-only file */
+            /* we just ignore that error */
+            if (fl.l_type == F_WRLCK) return 1;
+            set_error( STATUS_ACCESS_DENIED );
+            return 0;
         case EOVERFLOW:
             /* this can happen if off_t is 64-bit but the kernel only supports 32-bit */
             /* in that case we shrink the limit and retry */