From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757373AbbJVMLW (ORCPT ); Thu, 22 Oct 2015 08:11:22 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:43693 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757279AbbJVMLU (ORCPT ); Thu, 22 Oct 2015 08:11:20 -0400 Date: Thu, 22 Oct 2015 14:10:56 +0200 From: Peter Zijlstra To: Andrea Arcangeli 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 , Dave Hansen , Paolo Bonzini , Rik van Riel , Mel Gorman , Andy Lutomirski , Hugh Dickins , Peter Feiner , "Dr. David Alan Gilbert" , Johannes Weiner , "Huangpeng (Peter)" Subject: Re: [PATCH 14/23] userfaultfd: wake pending userfaults Message-ID: <20151022121056.GB7520@twins.programming.kicks-ass.net> References: <1431624680-20153-1-git-send-email-aarcange@redhat.com> <1431624680-20153-15-git-send-email-aarcange@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1431624680-20153-15-git-send-email-aarcange@redhat.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 14, 2015 at 07:31:11PM +0200, Andrea Arcangeli wrote: > @@ -255,21 +259,23 @@ int handle_userfault(struct vm_area_struct *vma, unsigned long address, > * through poll/read(). > */ > __add_wait_queue(&ctx->fault_wqh, &uwq.wq); > - for (;;) { > - set_current_state(TASK_KILLABLE); > - if (!uwq.pending || ACCESS_ONCE(ctx->released) || > - fatal_signal_pending(current)) > - break; > - spin_unlock(&ctx->fault_wqh.lock); > + set_current_state(TASK_KILLABLE); > + spin_unlock(&ctx->fault_wqh.lock); > > + if (likely(!ACCESS_ONCE(ctx->released) && > + !fatal_signal_pending(current))) { > wake_up_poll(&ctx->fd_wqh, POLLIN); > schedule(); > + ret |= VM_FAULT_MAJOR; > + } So what happens here if schedule() spontaneously wakes for no reason? I'm not sure enough of userfaultfd semantics to say if that would be bad, but the code looks suspiciously like it relies on schedule() not to do that; which is wrong. > + __set_current_state(TASK_RUNNING); > + /* see finish_wait() comment for why list_empty_careful() */ > + if (!list_empty_careful(&uwq.wq.task_list)) { > spin_lock(&ctx->fault_wqh.lock); > + list_del_init(&uwq.wq.task_list); > + spin_unlock(&ctx->fault_wqh.lock); > } > - __remove_wait_queue(&ctx->fault_wqh, &uwq.wq); > - __set_current_state(TASK_RUNNING); > - spin_unlock(&ctx->fault_wqh.lock); > > /* > * ctx may go away after this if the userfault pseudo fd is