samba - Mar 2024 - renaming over to a busy file: traces

20.03.2024 20:18, Ralph Boehme via samba:
> I guess the problem is that we can't lock two locking.tdb records
simultaneously. We already have the source file record locked, also locking the
the
> destination record is not possible.
Why it is not possible?

Second lock can't be done in waiting mode, it can only be done
in lock-or-fail mode obviously (or else it is too prone to deadlocks).

/mjt

On 3/20/24 19:11, Michael Tokarev wrote:
> 20.03.2024 20:18, Ralph Boehme via samba:
> 
>> I guess the problem is that we can't lock two locking.tdb records 
>> simultaneously. We already have the source file record locked, also 
>> locking the the destination record is not possible.
> 
> Why it is not possible?
> 
> Second lock can't be done in waiting mode, it can only be done
> in lock-or-fail mode obviously (or else it is too prone to deadlocks).
it's prone to deadlock because another process could try to acquire the 
locks on the records in the reverse order.

-slow

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20240320/9d85fdff/OpenPGP_signature.sig>