Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp2596087imm; Thu, 18 Oct 2018 18:13:44 -0700 (PDT) X-Google-Smtp-Source: ACcGV63+bYKUPWV5Gj6VV71M46J+tNEpaIqYJTFinJlxgxTCO8iRd7+Dgu2LJgiHvmWzWRBPjx/K X-Received: by 2002:a62:76d8:: with SMTP id r207-v6mr32910849pfc.216.1539911623972; Thu, 18 Oct 2018 18:13:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539911623; cv=none; d=google.com; s=arc-20160816; b=k3VLhSrprUYV/RYtC5Oy8DsSrXFp98RcHmOXg1L7WseMUKZcm78rJ3UuikbYhiGQ1b Etzf3F5qw9lTkawyNeYXf1bFpZBlxgKckAjHpj4jKAtb86aVz35rbXmjDktTMn7TCOmm t3fSBQ4/xfDA8X4liKk3kuOuoXfC6sASgSnFIBPSFpavUW0b4Pp0RcpBGgeProAo6MEY J+AzpTbso0q/aUIB3pRqUPmZRoFOYdUsBg9BNP7WdNSswm/wIHZSZOU7RdK+tFWu06bL 2zAqKzgscsEaOz+gAgWoskeDZPX7QbIpZk7Wj43gRAzQlSkmj6C8JfnlOcICog+kd4um OFlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=9jQn/dioE9zhtRKN6+jy9CJmqqQRt4+yM/mKXNuuj9Q=; b=BDuc26OJD+SIv+6z7rZ7Jh3UYR6Puv50qlzdMfP3d1/AIdxZyB6/2D+b/xA2v+UkJO p3nBftRY4PqimPUV1zTkTyuR4nZemgxjZOU8m97x3xWPpmaftmBBqqs0k2tT9Uf6vvIm YAjfupJVwKa4a2FwMo86KRRmbI/bm4fUOkROPdJcczfZFRp+0raPtTFcCndahu0YqjmP 9XEvtmneHfe5+Rc5uSRqEX236d/k4dBMDGT7krFbu5yUzb7nNz81Q7fCpCChy1v87hE7 OmyzKXNULjOW+sqX8UTpZ/BL0T9/jCZ9mXZgdQGiCG61pkLwBBJB57S8pNib4DGWlLqW 0ddQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w20-v6si22572550pgh.571.2018.10.18.18.13.28; Thu, 18 Oct 2018 18:13:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726918AbeJSJQb (ORCPT + 99 others); Fri, 19 Oct 2018 05:16:31 -0400 Received: from mail.kernel.org ([198.145.29.99]:52632 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726261AbeJSJQb (ORCPT ); Fri, 19 Oct 2018 05:16:31 -0400 Received: from vmware.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D3D5D2087A; Fri, 19 Oct 2018 01:12:46 +0000 (UTC) Date: Thu, 18 Oct 2018 21:12:45 -0400 From: Steven Rostedt To: "Paul E. McKenney" Cc: Joel Fernandes , Nikolay Borisov , linux-kernel@vger.kernel.org, Jonathan Corbet , Josh Triplett , Lai Jiangshan , linux-doc@vger.kernel.org, Mathieu Desnoyers Subject: Re: [PATCH RFC] doc: rcu: remove obsolete (non-)requirement about disabling preemption Message-ID: <20181018211245.10baf496@vmware.local.home> In-Reply-To: <20181019001932.GR2674@linux.ibm.com> References: <20181015201556.GA43575@joelaf.mtv.corp.google.com> <20181015210856.GE2674@linux.ibm.com> <20181016112611.GA27405@linux.ibm.com> <20181016204122.GA8176@joelaf.mtv.corp.google.com> <20181017161100.GP2674@linux.ibm.com> <20181017181505.GC107185@joelaf.mtv.corp.google.com> <20181017203324.GS2674@linux.ibm.com> <20181018020751.GB99677@joelaf.mtv.corp.google.com> <20181018144637.GD2674@linux.ibm.com> <20181019000350.GB89903@joelaf.mtv.corp.google.com> <20181019001932.GR2674@linux.ibm.com> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Oct 2018 17:19:32 -0700 "Paul E. McKenney" wrote: > I figured that whoever calls preempt_enable_no_resched() is taking the > responsibility for permitting preemption in the near future, and if they > fail to do so, they will get called on it. Hard to hide from the latency > tracer, after all. ;-) Correct, and doing a search of preempt_enable_no_resched() I see there's one in the ftrace ring buffer code, that was added a long time ago (2008) to fix a recursion bug that no longer exists, and this now can leak a preemption point. I'll have to go fix that :-( -- Steve