Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933862AbbFWVl6 (ORCPT ); Tue, 23 Jun 2015 17:41:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37266 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933550AbbFWVlq (ORCPT ); Tue, 23 Jun 2015 17:41:46 -0400 Date: Tue, 23 Jun 2015 23:41:41 +0200 From: Andrea Arcangeli To: Dave Hansen Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, qemu-devel@nongnu.org, kvm@vger.kernel.org, linux-api@vger.kernel.org, Pavel Emelyanov , Sanidhya Kashyap , zhang.zhanghailiang@huawei.com, Linus Torvalds , "Kirill A. Shutemov" , Andres Lagar-Cavilla , Paolo Bonzini , Rik van Riel , Mel Gorman , Andy Lutomirski , Hugh Dickins , Peter Feiner , "Dr. David Alan Gilbert" , Johannes Weiner , "Huangpeng (Peter)" Subject: Re: [PATCH 10/23] userfaultfd: add new syscall to provide memory externalization Message-ID: <20150623214141.GB4312@redhat.com> References: <1431624680-20153-1-git-send-email-aarcange@redhat.com> <1431624680-20153-11-git-send-email-aarcange@redhat.com> <5589ACC3.3060401@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5589ACC3.3060401@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1439 Lines: 34 Hi Dave, On Tue, Jun 23, 2015 at 12:00:19PM -0700, Dave Hansen wrote: > Down in userfaultfd_wake_function(), it looks like you intended for a > len=0 to mean "wake all". But the validate_range() that we do from > userspace has a !len check in it, which keeps us from passing a len=0 in > from userspace. > Was that "wake all" for some internal use, or is the check too strict? It's for internal use or userfaultfd_release that has to wake them all (after setting ctx->released) if the uffd is closed. It avoids to enlarge the structure by depending on the invariant that userland cannot pass len=0. If we'd accept len=0 from userland as valid, I'd be safer if it does nothing like in madvise, I doubt we want to expose this non standard kernel internal behavior to userland. > I was trying to use the wake ioctl after an madvise() (as opposed to > filling things in using a userfd copy). madvise will return 0 if len=0, mremap would return -EINVAL if new_len is zero, mmap also returns -EINVAL if len is 0, not all MM syscalls are as permissive as madvise. Can't you pass the same len you pass to madvise to UFFDIO_WAKE (or just skip the call if the madvise len is zero)? Thanks, Andrea -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/