Pekka Enberg wrote:Yeah, this is also a guarding thing. When a dirty page is released
the budget which was allocated for it has to be freed. If this function
is called, then the budget was not freed, which must never happen.
So what guarantees that no one calls invalidate_complete_page() or
fallback_migrate_page(), for example?
At the first glance it looks like it might be called, but for clean pages,
which is not the problem, but there is this assert which may give fake
alarm. Need to look closer at this. Thanks for the note.