Artem Bityutskiy wrote:
quoted text
> 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.

Dirty pages are not released.

In UBIFS, clean pages do not have PagePrivate(page) set and so releasepage() is not called.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/