Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4093711ybl; Tue, 20 Aug 2019 06:58:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqzPZPneNiw6V3do/yRWW0jrdaXuhBPOU6rvruCym8vK2V/uQMp2Fh3jYQ9ZSOgMv/FKymkf X-Received: by 2002:a17:90a:c68c:: with SMTP id n12mr112351pjt.33.1566309493957; Tue, 20 Aug 2019 06:58:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566309493; cv=none; d=google.com; s=arc-20160816; b=Itxfp3YwfwCDdS2Ev4WQ+soJKN74ANsfqevTbtjl9UCDYK+lzsDOnxwJ7YJxs/Oe3u xMpb4HpvVjX3tjRp81vfXOjR/QmGVHxdPDOWLrrZ7l77qgxodFRGRZ6QDXxo+TEjo8qk eccFJz0ZprHZULoUl5+8GlD5FhWlq/9Jj/h0cHI+UiRmpVNa+ZQW+pTUzKKm8eIhggOX j37NNRmcnSB6FMzEyN3yAgJKj7YaKqFjoZW0Ei0m/Ab4NODuS/npZzOm0/2u2mO7Qzr5 k3UbsQjOiJBePQOI+Ii6AVjELubNPOJXIUy3+ILI8E8XLYgtFWWtuY8SU1I2xOBdHLZ7 jl3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=3FZMVIbuRNp32d8JMD1EkMNHi8iS7iY8D8CYQ+VI9+w=; b=L6UzPg0cyKfzZYZE6Ayu+B56z74OKXn+S2qd1X/FaxlrBOLXS8zpGkqaq4VgrU8ZTj ks4FST7dQofLM4YgwOmSw3C1yYYb7a5caDFGwFP7mmkIkIbdzJTv3JjHIm+2C3stMuBY AU14f/luHtrW191ffAASbMHlXe1H3SrZIUW/I7H6k6bp6nVpfdJoQggnZY7Cb5Xe3dzB ierrGV9cpCMqVdYhkQr8pvF2QazezJxkAaXgZW/G3punobOSkdLPYDQV5QtFEWkL6emN JCsiKx/X9KvZwMeRCgMyXGcEq6o/4CrbHD+ltnMSMhaOxv8yvpUqjqPR8cs81nlOALnu UHmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=QFXgNKpB; 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 t5si44774pjo.12.2019.08.20.06.57.58; Tue, 20 Aug 2019 06:58:13 -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; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=QFXgNKpB; 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 S1730243AbfHTN4c (ORCPT + 99 others); Tue, 20 Aug 2019 09:56:32 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:46472 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730197AbfHTN4b (ORCPT ); Tue, 20 Aug 2019 09:56:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3FZMVIbuRNp32d8JMD1EkMNHi8iS7iY8D8CYQ+VI9+w=; b=QFXgNKpB5rOao8Qx5vOD3t9UB Ab4npiAfKzsEfTNL1y0FugkBkUUDwsk0YCkLIk4JE2kSl5UdnuDlnI+nv+UKRz/yRSYS9m8yaFCwP sJ/rIW+KRkKR2k7rUWAuX9j463kqqEWmrxxNS2fejyZ3zldMrUyttcw4Lvda+h2EB5QlduO/jCKTp zVUUQlX5LM+aBg8HkD2Rt8MhPeXqWN+JwB4uC2UZKM9pmPDEFc5l85bNxqgOnD34vLxO79ABuPt73 hCRvdpysPApN+SuqIObefSHXobfBFVrQCWpB55ogSOec+bBCCYRFiu2yuTXLrq6IaGU4zqBGAbn4V RnP7gKe4Q==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=noisy.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.92 #3 (Red Hat Linux)) id 1i04cR-0002Sn-0S; Tue, 20 Aug 2019 13:56:15 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id EEAA230768C; Tue, 20 Aug 2019 15:55:40 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 1126120A99A00; Tue, 20 Aug 2019 15:56:12 +0200 (CEST) Date: Tue, 20 Aug 2019 15:56:12 +0200 From: Peter Zijlstra To: Linus Torvalds Cc: Mathieu Desnoyers , Thomas Gleixner , Joel Fernandes , Alan Stern , rostedt , Valentin Schneider , linux-kernel , paulmck , Boqun Feng , Will Deacon , David Howells Subject: Re: [PATCH 1/1] Fix: trace sched switch start/stop racy updates Message-ID: <20190820135612.GS2332@hirez.programming.kicks-ass.net> References: <241506096.21688.1565977319832.JavaMail.zimbra@efficios.com> <1642847744.23403.1566005809759.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Aug 17, 2019 at 01:08:02AM -0700, Linus Torvalds wrote: > The data tearing issue is almost a non-issue. We're not going to add > WRITE_ONCE() to these kinds of places for no good reason. Paulmck actually has an example of that somewhere; ISTR that particular case actually got fixed by GCC, but I'd really _love_ for some compiler people (both GCC and LLVM) to state that their respective compilers will not do load/store tearing for machine word sized load/stores. Without this written guarantee (which supposedly was in older GCC manuals but has since gone missing), I'm loathe to rely on it. Yes, it is very rare, but it is a massive royal pain to debug if/when it does do happen.