From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) by kanga.kvack.org (Postfix) with ESMTP id A8C846B0088 for ; Sun, 14 Dec 2014 18:11:20 -0500 (EST) Received: by mail-qc0-f180.google.com with SMTP id i8so7802045qcq.39 for ; Sun, 14 Dec 2014 15:11:20 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20141214230208.GA9217@node.dhcp.inet.fi> References: <20141214202224.GH2672@kvack.org> <20141214215221.GI2672@kvack.org> <20141214141336.a0267e95.akpm@linux-foundation.org> <20141214230208.GA9217@node.dhcp.inet.fi> Date: Sun, 14 Dec 2014 15:11:19 -0800 Message-ID: Subject: Re: [GIT PULL] aio: changes for 3.19 From: Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: "Kirill A. Shutemov" Cc: Andrew Morton , Benjamin LaHaise , linux-aio@kvack.org, Linux Kernel , linux-mm , Pavel Emelyanov , Dmitry Monakhov On Sun, Dec 14, 2014 at 3:02 PM, Kirill A. Shutemov wrote: > > How can we know that it's okay to move vma around for random driver which > provide .mmap? Or I miss something obvious? I do think that it would likely be a good idea to require an explicit flag somewhere before we do "move_vma()". I agree that it's kind of odd that we just assume everything is safe to move. That said, drivers or other random mappings that know about the virtual address should largely be considered buggy and broken anyway. I'm not convinced it's a good idea for aio either, but it probably has a better excuse than most. Linus -- 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