Date: Sun, 1 Jan 2017 21:56:39 +0100
From: Martin Husemann <[email protected]>
Message-ID: <[email protected]>
| Not updating mtime may have some justification in this case, but we better
| check standards and avoid being the odd one out for no real good reason.
I have managed to confirm that the problem exists in current, current from a
while ago (7.99.23 I think I tested) and current from before the Netbsd-7
branch (I tested 6.99.30 which is quite a long time back) - and that it
is fixed in 7.0_STABLE (I tested a version from mid December). (I don't
really have a setup for doing version bisects, so which versions I could
easily test was kind of spotty,,.)
That's a very weird sequence of break/work ... it was broken long ago,
aparently got fixed somewhere (I have not seen where yet) and now is
broken again.
Please file a PR for this (an ATF test would probably also be useful - the
locking part of your test isn't relevant though) - you can assign it to me
if you like, but I am unlikely to have more time for this until next week,
so if anyone else has some idea what is happening, feel free to fix it!
kre
