Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2640265pxj; Mon, 14 Jun 2021 03:46:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxCUu1BijosiHJBl+Pidu5WWkxResAQ2HR0p9dGUrA8vF4a4PQZBhqhNyeiBFC7G+6IvOYQ X-Received: by 2002:a05:6402:54f:: with SMTP id i15mr16010993edx.339.1623667611933; Mon, 14 Jun 2021 03:46:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623667611; cv=none; d=google.com; s=arc-20160816; b=DT4ReGLxbMw8zZc+0l2MaU6GZ91pzAYUfs13EVw7bAi9Rxrx3KRGyKmEZ/3YNHpblT bQ/clSqJrGDbC0NrYMhYM66nrbue3PO7NINiHOU3kuB1uK21E29DPU9XrnaCHCm3CuP4 ovAJOx1LoracLQm7iy/plaHRiKo+H8KvIV2yn1ropXLrwoxYmNMTGr/074B5U6TxXffM Tklu77CzZo6F27fKvrACqNkPuXAEM0OVYm1HL7guNo3rrFqYUYjLmfju+pjzPMm6Dd9E p7LOXiKSl/Vz5eyFT0v8wm0K8v396l5ElxQVd3OmHbMAMWpqDMI9p9UIE0F2L48/3kND t2iQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=hcNsOoJsfUd27uW6VTnB98qeH3q07NIMFycXxJ1J0Fo=; b=xZp8iu/5Jsf5mV+SZppUS73xSzrGffN2DMEchCRMqfxEeUEUMC4BVU94qVqYBZK7q2 vZ6At54SFRw5ZjORHQf0AlBTZbrygwO6IZtO/zgMji/IJHMbX8cwDxeY8+xQgofGLB7W m815+IMzQbkpnNaiaywuf9Ootp6pv+qu999ko0t9jmzXGh/+ppsj8ViRDlxoxn8KdAOO 1aMOgCvkK7gf7OrZuhoIqSPeHVyoEOZx9/+vLiAIVwET5Z7bYvnBBa5r6/7T6J7Wb5Km 55LukMl2/9KAl/qEYCxotbGwpevSX4kpq/7Vb6W65nT2VkMPQjDesN4nOvJa+LTUou1n 1WsQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=FWSj+UIY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n17si11179712edr.161.2021.06.14.03.46.26; Mon, 14 Jun 2021 03:46:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=FWSj+UIY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234214AbhFNKok (ORCPT + 99 others); Mon, 14 Jun 2021 06:44:40 -0400 Received: from mail.kernel.org ([198.145.29.99]:45208 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233790AbhFNKh6 (ORCPT ); Mon, 14 Jun 2021 06:37:58 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id C905260D07; Mon, 14 Jun 2021 10:33:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1623666814; bh=/O3Xs7G6M0+2ZWVpSyktVZV4LV/vKeCGp2CA+VL914g=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=FWSj+UIYGDql4G3Y9+b4H8MTsXJ3Hz+cbujkcOwCFu6hgVgNlcjfQ1io/42E0FVQ0 FOJdPHhO1L24UM+CYN55UhsVGRCiBOmJgy0GviTVhfaT0muQQmHec0o5BrTPok/RSj bsA32ohZtNBIyu7zCpiziSsGJU156ziCjoZuvLns= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, syzbot+142c9018f5962db69c7e@syzkaller.appspotmail.com, Marco Elver , "Peter Zijlstra (Intel)" Subject: [PATCH 4.14 39/49] perf: Fix data race between pin_count increment/decrement Date: Mon, 14 Jun 2021 12:27:32 +0200 Message-Id: <20210614102643.145302519@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210614102641.857724541@linuxfoundation.org> References: <20210614102641.857724541@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Marco Elver commit 6c605f8371159432ec61cbb1488dcf7ad24ad19a upstream. KCSAN reports a data race between increment and decrement of pin_count: write to 0xffff888237c2d4e0 of 4 bytes by task 15740 on cpu 1: find_get_context kernel/events/core.c:4617 __do_sys_perf_event_open kernel/events/core.c:12097 [inline] __se_sys_perf_event_open kernel/events/core.c:11933 ... read to 0xffff888237c2d4e0 of 4 bytes by task 15743 on cpu 0: perf_unpin_context kernel/events/core.c:1525 [inline] __do_sys_perf_event_open kernel/events/core.c:12328 [inline] __se_sys_perf_event_open kernel/events/core.c:11933 ... Because neither read-modify-write here is atomic, this can lead to one of the operations being lost, resulting in an inconsistent pin_count. Fix it by adding the missing locking in the CPU-event case. Fixes: fe4b04fa31a6 ("perf: Cure task_oncpu_function_call() races") Reported-by: syzbot+142c9018f5962db69c7e@syzkaller.appspotmail.com Signed-off-by: Marco Elver Signed-off-by: Peter Zijlstra (Intel) Link: https://lkml.kernel.org/r/20210527104711.2671610-1-elver@google.com Signed-off-by: Greg Kroah-Hartman --- kernel/events/core.c | 2 ++ 1 file changed, 2 insertions(+) --- a/kernel/events/core.c +++ b/kernel/events/core.c @@ -3918,7 +3918,9 @@ find_get_context(struct pmu *pmu, struct cpuctx = per_cpu_ptr(pmu->pmu_cpu_context, cpu); ctx = &cpuctx->ctx; get_ctx(ctx); + raw_spin_lock_irqsave(&ctx->lock, flags); ++ctx->pin_count; + raw_spin_unlock_irqrestore(&ctx->lock, flags); return ctx; }