Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2635266pxj; Mon, 14 Jun 2021 03:38:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzk9aneMPvqE1Ln9H5C9ywy55GptPXFKr64qT72QAXtTMvayY3ClcdcFn9N2CPQJiAXGgbQ X-Received: by 2002:a17:907:2d88:: with SMTP id gt8mr4907106ejc.449.1623667110806; Mon, 14 Jun 2021 03:38:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623667110; cv=none; d=google.com; s=arc-20160816; b=wMAc7gVtCBU5oXIe+Z1PU6RnFEK+6F8TezxRPzvLrHSiKcXC2iODkcJRW5LORsavdt +ple8N3vx/749nuUBBmbvybnQSwcD5jBlMm/Kl3iXLMQR3mYbXM/lNuXC8feUNcTNc+2 qWbS4RHYi/02pi2NbVXh25u8f8JfIrvIMEuSHZQsEQaVQgV0SNTdGvtVPV73pT0ARU5c ydaNbHinX79GEJOepjsQs8IEIqanGVKYdIkVl36c4pDHAZbitZOUcBvsFBJUK3UZq56t wPQvFlsIe8Z8w2CMwiQ3xdaowOSWvHYRfCNZMRdHjdpPpve+ClcQ3Jp5fzJSadei+hsV 6u9A== 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=rdXZiZJLOpqt0V4Dq9AsGvxesCkpUTQblocB0XGm2ps=; b=HdbbkXrPNsXeq+mKcYOhkN2AdOrAybtP5FmvURBrh3Lr/Nx3S5nTGpMPC+uvUDH9Ch o/EX5NQrOX6fLoaHHsakqHhRrpVfDUdJh99u7Tkq6wljcVTgUFL8Q+oLjgXx6QcVLPr5 Rt1SbZeI7Bf5Z1D2JYb7o2TtWXiFNwWa2UFeDkpEVOOxfS9Vavo2VhugkB6kW5i0JYBY S4C2RPDAZPhAQDklxQ8yZ5bqX8jTIWtHjCD1nq925gfMcQYLQ46NMlQjUjgWMSx5Q5r3 6jE++2Ibl/yosW2jo5PqeIm1aZk0VYFy33RQppCAxPHOUETdQU30XLuyv8ew9qiKDi7P lcBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=oX5wrMvu; 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 z21si9633139edd.20.2021.06.14.03.38.07; Mon, 14 Jun 2021 03:38:30 -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=oX5wrMvu; 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 S233659AbhFNKgo (ORCPT + 99 others); Mon, 14 Jun 2021 06:36:44 -0400 Received: from mail.kernel.org ([198.145.29.99]:39012 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233355AbhFNKd4 (ORCPT ); Mon, 14 Jun 2021 06:33:56 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 75343611BE; Mon, 14 Jun 2021 10:31:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1623666710; bh=k41R0Kv18ZKHAa/wQnzfh4ju+xUwjKz4ZbRlEjqZ5N8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=oX5wrMvu8UvxkGFFqF9JNPIkECXYOImiFBgjfPrZ/KPWV2kWqzydZYg0V0a1Oo0// HdybtxvjNDsyzUU5S1tg49XAbtMWKnfbZu/PebW70QVch83rdm3P7LdnUL/0rBNZoe 3WGW+tsBeIlQOpB6rhFmL0JoW+lo4OvGCtbvJH/o= 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.9 34/42] perf: Fix data race between pin_count increment/decrement Date: Mon, 14 Jun 2021 12:27:25 +0200 Message-Id: <20210614102643.790442311@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210614102642.700712386@linuxfoundation.org> References: <20210614102642.700712386@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 @@ -3782,7 +3782,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; }