From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752011AbbIQRIF (ORCPT ); Thu, 17 Sep 2015 13:08:05 -0400 Received: from e06smtp17.uk.ibm.com ([195.75.94.113]:52264 "EHLO e06smtp17.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751710AbbIQRIA (ORCPT ); Thu, 17 Sep 2015 13:08:00 -0400 X-Helo: d06dlp01.portsmouth.uk.ibm.com X-MailFrom: dingel@linux.vnet.ibm.com X-RcptTo: linux-kernel@vger.kernel.org Date: Thu, 17 Sep 2015 19:07:52 +0200 From: Dominik Dingel To: Paolo Bonzini , linux-crypto@vger.kernel.org, Tim Chen Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" , herbert@gondor.apana.org.au, Ingo Molnar , Peter Zijlstra Subject: Re: single_task_running() vs. preemption warnings (was Re: [PATCH] kvm: fix preemption warnings in kvm_vcpu_block) Message-ID: <20150917190752.27396fdb@BR9TG4T3.de.ibm.com> In-Reply-To: <55FAEE0C.60904@redhat.com> References: <1442507270-67227-1-git-send-email-dingel@linux.vnet.ibm.com> <55FAEE0C.60904@redhat.com> Organization: IBM X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15091717-0029-0000-0000-000006715CAB Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 Sep 2015 18:45:00 +0200 Paolo Bonzini wrote: > > > On 17/09/2015 18:27, Dominik Dingel wrote: > > + preempt_disable(); > > + solo = single_task_running(); > > + preempt_enable(); > > + > > cur = ktime_get(); > > - } while (single_task_running() && ktime_before(cur, stop)); > > That's the obvious way to fix it, but the TOCTTOU problem (which was in > the buggy code too) is obvious too. :) And the only other user of > single_task_running() in drivers/crypto/mcryptd.c has the same issue. Right, worst thing we fly another round. I am not sure about the case for mcryptd.c. I think it might be that the worker there is bounded to one cpu and will not be migrated. I really need to look more in the details what is happening with that worker. > In fact, because of the way the function is used ("maybe I can do a > little bit of work before going to sleep") it will likely be called many > times in a loop. This in turn means that: > > - any wrong result due to a concurrent process migration would be > rectified very soon > > - preempt_disable()/preempt_enable() can actually be just as expensive > or more expensive than single_task_running() itself. > > Therefore, I wonder if single_task_running() should just use > raw_smp_processor_id(). At least the TOCTTOU issue can be clearly > documented in the function comment, instead of being hidden behind each > of the callers. Yes to be useful it should probably call raw_smp_processor_id, and as a lot of code actually already does just does that I do not really see much down sides. @Tim, would it be okay if I change single_task_running and add a specific comment on top? > Thanks, > > Paolo >