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  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:	Fri, 24 Jun 2011 20:46:29 +0900
From:	Hiroyuki Kamezawa <>
To:	Michal Hocko <>
Cc:	KAMEZAWA Hiroyuki <>,
	Christoph Hellwig <>,,,
	Andrew Morton <>,
	Hugh Dickins <>,
	Rik van Riel <>,
	Michel Lespinasse <>,
	Mel Gorman <>, Lutz Vieweg <>
Subject: Re: [PATCH] mm: preallocate page before lock_page at filemap COW.
 (WasRe: [PATCH V2] mm: Do not keep page locked during page fault while
 charging it for memcg

2011/6/24 Michal Hocko <>:
> Sorry, forgot to send my
> Reviewed-by: Michal Hocko <mhocko@...e>


> I still have concerns about this way to handle the issue. See the follow
> up discussion in other thread (
> Anyway I think that we do not have many other options to handle this.
> Either we unlock, charge, lock&restes or we preallocate, fault in
I agree.

> Or am I missing some other ways how to do it? What do others think about
> these approaches?

Yes, I'd like to hear other mm specialists' suggestion. and I'll think
other way, again.
Anyway, memory reclaim with holding a lock_page() can cause big latency
or starvation especially when memcg is used. It's better to avoid it.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists