linux-kernel - Re: [RFC][PATCH] release mmap_sem before starting migration (Was Re: Need to take mmap_sem lock in move

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:	Thu, 5 Feb 2009 10:15:03 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	Swamy Gowda <swamy@...ident.com>, linux-kernel@...r.kernel.org,
	Brice.Goglin@...ia.fr, "linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [RFC][PATCH] release mmap_sem before starting migration (Was
 Re: Need to take mmap_sem lock in move_pages.

On Wed, 4 Feb 2009 10:39:19 -0500 (EST)
Christoph Lameter <cl@...ux-foundation.org> wrote:

> On Wed, 4 Feb 2009, KAMEZAWA Hiroyuki wrote:
> 
> > mmap_sem can be released after page table walk ends.
> 
> No. read lock on mmap_sem must be held since the migrate functions
> manipulate page table entries. Concurrent large scale changes to the page
> tables (splitting vmas, remapping etc) must not be possible.
> 
Just for clarification:

1. changes in page table is not problem from the viewpoint of kernel.
   (means no panic, no leak,...)
2. But this loses "atomic" aspect of migration and will allow unexpected
   behaviors.
   (means the page-mapping status after sys_move may not be what user expects.)


Thanks,
-Kame

--
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/