Bug 235657 - /usr/libexec/atrun race causes missed jobs
Summary: /usr/libexec/atrun race causes missed jobs
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 12.2-STABLE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2019-02-11 05:46 UTC by karl
Modified: 2021-09-17 19:17 UTC (History)
4 users (show)

See Also:


Attachments
Diff against /usr/src/libexec/atrun directory (1.84 KB, patch)
2019-02-11 05:46 UTC, karl
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description karl 2019-02-11 05:46:11 UTC
Created attachment 201915 [details]
Diff against /usr/src/libexec/atrun directory

I have no idea why this hasn't bit people before, or isn't biting people now.... but it is biting me.

/usr/libexec/atrun is the "batch" job executor out of the cron and by default runs every 5 minutes.

The code has an unlink call in it that attempts to remove old jobs from the queue but unfortunately the queue code can select a job to run, call fork() to start it, post-fork() the child can give up the CPU before it opens the file containing the job and thus the queue code (which is in the parent) can execute the unlink before the child process gets the file open.  If this happens you get a "file not found" error in the cron log and the job doesn't run.

The attached patch fixes the potential race by moving the unlink into the child; it may not be the most-elegant, but it works.  Unfortunately due to the code's structure (it performs multiple tests on the file to be run for security reasons) there are multiple error exits and, in the event of any of those, you must unlink the file as well or it will try to run repeatedly -- yet you can't unlink it immediately after it is opened because some of the tests require it still be on the filesystem.
Comment 1 karl 2021-05-29 16:01:25 UTC
This is still present in 12.2-STABLE as of today... updated a multi-core system and had it repeatedly drop submitted "batch" jobs due to it.
Comment 2 karl 2021-05-30 14:31:40 UTC
This is still "active" as of 12.2 as a problem; updated the version impacted to reflect that fact.
Comment 3 Dave Baukus 2021-09-17 18:20:28 UTC
In my usage this is not an intermittent irritation on Stable-13, the "race" is hit every time. It would be nice to see this fix pulled into the current releases. It has been broken since Stable-12.
Comment 4 karl 2021-09-17 19:17:00 UTC
(In reply to Dave Baukus from comment #3)
It has been "nearly every time" for me since I went to 12.2 on one specific box, but is intermittent on others.  I suspect it has to do with how the scheduler interacts with the various cores in specific configurations.

Nonetheless I agree with you -- this needs fixed since when it happens the job disappears without a trace.