Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp4097688ybf; Tue, 3 Mar 2020 20:05:40 -0800 (PST) X-Google-Smtp-Source: ADFU+vvPTiVhQTQsbvKFu3QsXUxpd4Vj3a9+1E2oeYVB2jc427KF0Sa8hhDAtjk1X86jGR/PMNA3 X-Received: by 2002:a9d:7d04:: with SMTP id v4mr932989otn.308.1583294739953; Tue, 03 Mar 2020 20:05:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583294739; cv=none; d=google.com; s=arc-20160816; b=x6h5Lscsb3kJg/Bm5n4j4h3pl9O2Ts0ql+PqxqwJ7dwogAZKAfoEvw4MKGOhEn4VST h1Ds5BSNpSfYp7sCCQInxEtozE4CucvXHk4AymhEVQGLDIbiVH9wcP+h4cz0PRvU/ABM tmTSlzx2Ln504CWUBPhYN7p4mBMPN527xvG5Pbl08JnNnnlKHVnmAk+Furqmq6BKdWJN CYVLPEFI+07ddwgzzPGaAvo3BHsJFbnDOIjibfC9yMKOZ5tUlfIdCZ4DvzrUJKTC6jF+ CjvN49T0zcGL5pJf1ZKHQARVn+79QBLlUoF0CVuB5dEQ1RyZCpOjd1qPYKwFKhiVEeUW aU6Q== 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:reply-to:message-id :subject:cc:to:from:date:dkim-signature; bh=tcbgdWQEYbua0LATbDO07QDcg4C+1SVvLLNj7w+5WKs=; b=jRlRPOXQ3Ib3ddCwri29Na4vytZhd22JRpG5XmNMnPDkPeDVs62qi1nZVSOfzwzwkZ Si3qRW2DQ4fSteUNcFO7YaAF+TVwU9DtQCF+xyF8IMepe9GKQXnu0gmroh1m+NvTfMZl QHMmu1C+2PCYzGwh4KG0ppuiPU051IKBZkveDLsx8q2RnCYck67o3qma6RPw/MfmQPIK 0hrbE3aa4dz+29fcXlV6PKMH4ypzXxQA5OMN9eQMgGLydxJrPKSorBPMk38EKHCtLy/Z SeSxOnEUOCdL2jNS3Z6yyIZTFxgFZlYM75UvDEXW5WCvgaNFhT4UUHRkP+gFCad4LZv0 yglg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=j3Kw6Ptf; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d185si477214oig.189.2020.03.03.20.05.26; Tue, 03 Mar 2020 20:05:39 -0800 (PST) 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=pass header.i=@kernel.org header.s=default header.b=j3Kw6Ptf; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726094AbgCDEFQ (ORCPT + 99 others); Tue, 3 Mar 2020 23:05:16 -0500 Received: from mail.kernel.org ([198.145.29.99]:51592 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725796AbgCDEFQ (ORCPT ); Tue, 3 Mar 2020 23:05:16 -0500 Received: from paulmck-ThinkPad-P72.home (50-39-105-78.bvtn.or.frontiernet.net [50.39.105.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 2552D20842; Wed, 4 Mar 2020 04:05:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1583294716; bh=p68B3/NdMMEqbeyhZmAihrJUVvRMPdRtxZQobAvEOyM=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=j3Kw6Ptf84PP0JOZulhFtKrdFN3Dvd+4jR6BYn8Ca/sFmyWJN1NMIXcCFceMBbJVp 7q1/XrSmLvybJXlJ9Ji3OuS7Cj8OxCPUYUnBp2lPkydnFToZydwHD/X8HiJlV+OS1g t+eJhXsmGAMGSmjwtH2aoU2r0wVFkyD+i7C2CUcY= Received: by paulmck-ThinkPad-P72.home (Postfix, from userid 1000) id E291835226C4; Tue, 3 Mar 2020 20:05:15 -0800 (PST) Date: Tue, 3 Mar 2020 20:05:15 -0800 From: "Paul E. McKenney" To: Matthew Wilcox Cc: Qian Cai , elver@google.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH -next] lib: disable KCSAN for XArray Message-ID: <20200304040515.GX2935@paulmck-ThinkPad-P72> Reply-To: paulmck@kernel.org References: <20200304031551.1326-1-cai@lca.pw> <20200304033329.GZ29971@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200304033329.GZ29971@bombadil.infradead.org> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 03, 2020 at 07:33:29PM -0800, Matthew Wilcox wrote: > On Tue, Mar 03, 2020 at 10:15:51PM -0500, Qian Cai wrote: > > Functions like xas_find_marked(), xas_set_mark(), and xas_clear_mark() > > could happen concurrently result in data races, but those operate only > > on a single bit that are pretty much harmless. For example, > > Those aren't data races. The writes are protected by a spinlock and the > reads by the RCU read lock. If the tool can't handle RCU protection, > it's not going to be much use. Would KCSAN's ASSERT_EXCLUSIVE_BITS() help here? If not, you lost me on this one. RCU readers don't exclude lock-based writers. RCU readers -do- exclude pre-insertion initialization on the one hand, and those post-removal accesses that follow a grace period, but only if that grace period starts after the removal. In addition, the accesses due to rcu_dereference(), rcu_assign_pointer(), and similar are guaranteed to work even if they are concurrent. Or am I missing something subtle here? That said, you are permitted to define "data race" for your subsystem by choosing KCSAN settings, up to and including keeping KCSAN out entirely. Thanx, Paul