public inbox for goredo-devel@lists.cypherpunks.ru
Atom feed
From: Sergey Matveev <stargrave@stargrave•org>
To: goredo-devel@lists.cypherpunks.ru
Subject: Re: resource deadlock avoided messages
Date: Mon, 25 Sep 2023 19:14:39 +0300 [thread overview]
Message-ID: <ZRGx74oYIMB_OUSL@stargrave.org> (raw)
In-Reply-To: <4cd15382-990f-4229-9aa9-2aade0ad4ab3@spacefrogg.net>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
*** goredo [2023-09-24 13:17]:
>Is it really an issue when goredo is unable to grab a lock?
I read man page about fcntl's locking mechanisms and discovered that
Linux kernel can issue EDEADLK error even if no deadlock actually
exists, that is expected/known behaviour. So in 1.32.0 release I
explicitly check for that error and silently retry taking the lock. At
last that message will disappear. Do not know why I missed that issue
description in the man page.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: 12AD 3268 9C66 0D42 6967 FD75 CB82 0563 2107 AD8A
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-25 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 19:12 Several issues since 1.30 spacefrogg
2023-09-23 19:16 ` resource deadlock avoided messages Sergey Matveev
2023-09-24 11:17 ` goredo
2023-09-25 16:14 ` Sergey Matveev [this message]
2023-09-23 19:16 ` Target runs multiple times in single session Sergey Matveev
2023-09-23 19:17 ` Slow/buffered output of targets finished messages Sergey Matveev
2023-09-23 19:17 ` Unclear what target the output relates to Sergey Matveev
2023-09-24 11:10 ` goredo
2023-09-25 16:20 ` Sergey Matveev
2023-09-28 13:55 ` spacefrogg
2023-09-30 16:57 ` Sergey Matveev
2023-10-16 13:24 ` Sergey Matveev