From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 11A2FC3A59D for ; Fri, 16 Aug 2019 20:49:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E2E0B2171F for ; Fri, 16 Aug 2019 20:49:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727676AbfHPUtS (ORCPT ); Fri, 16 Aug 2019 16:49:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:41812 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727568AbfHPUtS (ORCPT ); Fri, 16 Aug 2019 16:49:18 -0400 Received: from oasis.local.home (rrcs-76-79-140-27.west.biz.rr.com [76.79.140.27]) (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 EEC602077C; Fri, 16 Aug 2019 20:49:16 +0000 (UTC) Date: Fri, 16 Aug 2019 16:49:12 -0400 From: Steven Rostedt To: Joel Fernandes Cc: Alan Stern , Mathieu Desnoyers , Valentin Schneider , linux-kernel , Peter Zijlstra , Thomas Gleixner , paulmck , Boqun Feng , Will Deacon , David Howells , Linus Torvalds Subject: Re: [PATCH 1/1] Fix: trace sched switch start/stop racy updates Message-ID: <20190816164912.078b6e01@oasis.local.home> In-Reply-To: References: <241506096.21688.1565977319832.JavaMail.zimbra@efficios.com> X-Mailer: Claws Mail 3.17.3 (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 Fri, 16 Aug 2019 16:44:10 -0400 Joel Fernandes wrote: > I am also more on the side of using *_ONCE. To me, by principal, I > would be willing to convert any concurrent plain access using _ONCE, > just so we don't have to worry about it now or in the future and also > documents the access. > > Perhaps the commit message can be reworded to mention that the _ONCE > is an additional clean up for safe access. The most I'll take is two separate patches. One is going to be marked for stable as it fixes a real bug. The other is more for cosmetic or theoretical issues, that I will state clearly "NOT FOR STABLE", such that the autosel doesn't take them. -- Steve