Andrew Tridgell fde5a66531 avoid a deadlock the fetch_lock code. The deadlock could happen when ...

a client held the chainlock, and the daemon received a dmaster reply
at the same time. The daemon would not be able to process the dmaster
reply, due to the lock, but the fetch lock cannot make progres until
the dmaster reply is processed.

The solution is to not hold the lock in the client while talking to
the daemon. The client has to retry the lock after the record has
migrated. This means that forward progress is not guaranteed. We'll
have to see if that matters in practice.

(This used to be ctdb commit 737e5a1253cb048222c595a474aff71c99fc554f)

2007-04-19 10:03:20 +10:00

ctdb

avoid a deadlock the fetch_lock code. The deadlock could happen when

2007-04-19 10:03:20 +10:00

Description

https://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub)

samba

453 MiB

Languages

C 76.3%

Python 18.9%

Shell 2.8%

Perl 1.4%

Rust 0.3%

Other 0.1%