From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sun, 14 Dec 2014 18:08:09 -0500 From: Benjamin LaHaise Subject: Re: [GIT PULL] aio: changes for 3.19 Message-ID: <20141214230809.GK2672@kvack.org> References: <20141214202224.GH2672@kvack.org> <20141214215221.GI2672@kvack.org> <20141214141336.a0267e95.akpm@linux-foundation.org> <20141214230208.GA9217@node.dhcp.inet.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141214230208.GA9217@node.dhcp.inet.fi> Sender: owner-linux-mm@kvack.org List-ID: To: "Kirill A. Shutemov" Cc: Andrew Morton , Linus Torvalds , linux-aio@kvack.org, Linux Kernel , linux-mm , Pavel Emelyanov , Dmitry Monakhov On Mon, Dec 15, 2014 at 01:02:08AM +0200, Kirill A. Shutemov wrote: > But it seems the problem is bigger than what the patch fixes. To me we are > too permisive on what vma can be remapped. > > How can we know that it's okay to move vma around for random driver which > provide .mmap? Or I miss something obvious? Most drivers do not care if a vma is moved within the virtual address space of a process. The aio ring buffer is special in that it gets unmapped when userspace does an io_destroy(), and io_destroy() has to know what the address is moved to in order to perform the unmap. Normal drivers don't perform the unmap themselves. -ben -- "Thought is the essence of where you are now." -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org