From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f175.google.com (mail-qc0-f175.google.com [209.85.216.175]) by kanga.kvack.org (Postfix) with ESMTP id CFAB282BDC for ; Thu, 25 Sep 2014 17:16:53 -0400 (EDT) Received: by mail-qc0-f175.google.com with SMTP id o8so5864521qcw.6 for ; Thu, 25 Sep 2014 14:16:53 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTPS id u8si3772359qgd.112.2014.09.25.14.16.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Sep 2014 14:16:43 -0700 (PDT) Date: Thu, 25 Sep 2014 23:16:04 +0200 From: Andrea Arcangeli Subject: Re: [PATCH v2] kvm: Faults which trigger IO release the mmap_sem Message-ID: <20140925211604.GA4590@redhat.com> References: <1410811885-17267-1-git-send-email-andreslc@google.com> <1410976308-7683-1-git-send-email-andreslc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1410976308-7683-1-git-send-email-andreslc@google.com> Sender: owner-linux-mm@kvack.org List-ID: To: Andres Lagar-Cavilla Cc: Gleb Natapov , Radim Krcmar , Paolo Bonzini , Rik van Riel , Peter Zijlstra , Mel Gorman , Andy Lutomirski , Andrew Morton , Sasha Levin , Jianyu Zhan , Paul Cassella , Hugh Dickins , Peter Feiner , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, "Dr. David Alan Gilbert" Hi Andres, On Wed, Sep 17, 2014 at 10:51:48AM -0700, Andres Lagar-Cavilla wrote: > + if (!locked) { > + VM_BUG_ON(npages != -EBUSY); > + Shouldn't this be VM_BUG_ON(npages)? Alternatively we could patch gup to do: case -EHWPOISON: + case -EBUSY: return i ? i : ret; - case -EBUSY: - return i; I need to fix gup_fast slow path to start with FAULT_FLAG_ALLOW_RETRY similarly to what you did to the KVM slow path. gup_fast is called without the mmap_sem (incidentally its whole point is to only disable irqs and not take the locks) so the enabling of FAULT_FLAG_ALLOW_RETRY initial pass inside gup_fast should be all self contained. It shouldn't concern KVM which should be already fine with your patch, but it will allow the userfaultfd to intercept all O_DIRECT gup_fast in addition to KVM with your patch. Eventually get_user_pages should be obsoleted in favor of get_user_pages_locked (or whoever we decide to call it) so the userfaultfd can intercept all kind of gups. gup_locked is same as gup except for one more "locked" parameter at the end, I called the parameter locked instead of nonblocking because it'd be more proper to call "nonblocking" gup the FOLL_NOWAIT kind which is quite the opposite (in fact as the mmap_sem cannot be dropped in the non blocking version). ptrace ironically is better off sticking with a NULL locked parameter and to get a sigbus instead of risking hanging on the userfaultfd (which would be safe as it can be killed, but it'd be annoying if erroneously poking into a hole during a gdb session). It's still possible to pass NULL as parameter to get_user_pages_locked to achieve that. So the fact some callers won't block in handle_userfault because FAULT_FLAG_ALLOW_RETRY is not set and the userfault cannot block, may come handy. What I'm trying to solve in this context is that the userfault cannot safely block without FAULT_FLAG_ALLOW_RETRY because we can't allow userland to take the mmap_sem for an unlimited amount of time without requiring special privileges, so if handle_userfault wants to blocks within a gup invocation, it must first release the mmap_sem hence FAULT_FLAG_ALLOW_RETRY is always required at the first attempt for any virtual address. With regard to the last sentence, there's actually a race with MADV_DONTNEED too, I'd need to change the code to always pass FAULT_FLAG_ALLOW_RETRY (your code also would need to loop and insisting with the __get_user_pages(locked) version to solve it). The KVM ioctl worst case would get an -EFAULT if the race materializes for example. It's non concerning though because that can be solved in userland somehow by separating ballooning and live migration activities. Thanks, Andrea -- 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