On Wed, Oct 2, 2024 at 3:25 PM Jeff King <peff@xxxxxxxx> wrote: > The solution then is to avoid letting any client threads run (or at > least create cookies) until we know we're listening for fs events. > Naively I would say we should just have the fs event thread signal us > that it's ready before we spawn any of the client threads. But it looks > like we explicitly start those threads first in fsmonitor_run_daemon_1(): I submitted a fix that followed this approach as it is easy to understand and should not have any unexpected behaviour. Could you please check it? https://lore.kernel.org/git/pull.1804.git.1727862424713.gitgitgadget@xxxxxxxxx/ Koji Nakamaru
