bfs sends spurious B_STAT_MODIFICATION_TIME notifications after file change
|Reported by:||bonefish||Owned by:||axeld|
After a file has been changed (or just
touched) BFS starts sending out
B_STAT_MODIFICATION_TIME whenever the file is closed after opening it for writing, even if the file wasn't modified. Can be reproduced with the attached test programs:
- Start monitoring a file that hasn't been changed in this session, yet:
- Verify that no spurious notification are sent yet (the test program waits 3s before closing the file):
- Touch the file. Notifications are received as expected.
open_for_writingagain. This time after
close()a spurious notification is received.
Tested in the package-management branch, which corresponds to master hrev45747.