Jeff Layton <jlayton@xxxxxxxxxx> writes: > > The problem is that these checks assume that dirtied_when is updated > periodically. If an inode is continuously being used for I/O it can be > persistently marked as dirty and will continue to age. Once the time > difference between dirtied_when and the jiffies value it is being > compared to is greater than or equal to half the maximum of the jiffies > type, the logic of the time_*() macros inverts and the opposite of what > is needed is returned. On 32-bit architectures that's just under 25 days > (assuming HZ == 1000). I wonder if this can happen in other places using jiffies time stamp too. Why not? Perhaps that check macro should be in timer.h and some auditing done over the whiole code base? -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
