From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757874AbbJVNie (ORCPT ); Thu, 22 Oct 2015 09:38:34 -0400 Received: from casper.infradead.org ([85.118.1.10]:58256 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757092AbbJVNib (ORCPT ); Thu, 22 Oct 2015 09:38:31 -0400 Date: Thu, 22 Oct 2015 15:38:24 +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: <20151022133824.GR17308@twins.programming.kicks-ass.net> References: <1431624680-20153-1-git-send-email-aarcange@redhat.com> <1431624680-20153-15-git-send-email-aarcange@redhat.com> <20151022121056.GB7520@twins.programming.kicks-ass.net> <20151022132015.GF19147@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151022132015.GF19147@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, Oct 22, 2015 at 03:20:15PM +0200, Andrea Arcangeli wrote: > If schedule spontaneously wakes up a task in TASK_KILLABLE state that > would be a bug in the scheduler in my view. Luckily there doesn't seem > to be such a bug, or at least we never experienced it. Well, there will be a wakeup, just not the one you were hoping for. We have code that does: @cond = true; get_task_struct(p); queue(p) /* random wait somewhere */ for (;;) { prepare_to_wait(); if (@cond) break; ... handle_userfault() ... schedule(); ... dequeue(p) wake_up_process(p) ---> wakeup without userfault wakeup These races are (extremely) rare, but they do exist. Therefore one must never assume schedule() will not spuriously wake because of these things. Also, see: lkml.kernel.org/r/CA+55aFwHkOo+YGWKYROmce1-H_uG3KfEUmCkJUerTj=ojY2H6Q@mail.gmail.com