linux-kernel - Re: [RFC PATCH 20/26] UBIFS: add VFS operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Apr 2008 18:14:50 +0300
From:	Adrian Hunter <ext-adrian.hunter@...ia.com>
To:	Artem.Bityutskiy@...ia.com
CC:	Pekka Enberg <penberg@...helsinki.fi>,
	Artem Bityutskiy <dedekind@...dex.ru>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 20/26] UBIFS: add VFS operations

Artem Bityutskiy wrote:
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/