Stolee describes an integration bug between fsmonitor and the untracked cache. When fsmonitor fails or gives a trivial response, refresh_fsmonitor() clears CE_FSMONITOR_VALID and stops using fsmonitor for the untracked cache. That can leave untracked cache entries marked valid.
His example is that git update-index --refresh can save a replacement fsmonitor token without scanning untracked directories. If the next query reports no changes, fsmonitor use is enabled again. git status then trusts directory contents cached before the event history was lost, so new untracked files can remain invisible.
Junio C Hamano first asked whether the patch could replace ik/fsmonitor-untracked-cache-trivial-response, an earlier topic that had been left unreviewed for a month. He later described the fix as "rather a blunt instrument" but said being without acceleration is much better than being fast and incorrect. He said he will queue it.