Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2643135pxj; Mon, 14 Jun 2021 03:51:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxirvYiGN7pZCxH6JubtNrIMIRsE2f5QzshytNJNea8F2gxeQjO+Fc1glz8DE3rxh+8YTbE X-Received: by 2002:a05:6402:2689:: with SMTP id w9mr15713184edd.375.1623667908899; Mon, 14 Jun 2021 03:51:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623667908; cv=none; d=google.com; s=arc-20160816; b=oN68DCNP5niZFJQNEdFIpNLWEUQx2A0WlTPl9VkQC0uFy4Y8vnXTFXaZ/7V3CvkSpu BrNUplbVQ4YwFeJnMHSKRVx2RX6VdahUIP1qS5mpKxuuaf/jfAfeWk5MokP5hQ62l0fO QhkO04ioOTKKYA0y3VKbfBA+eN9RlC/ZIjClFSlhXguqFJblL2iKmRmhbU73tsBJYTfA nPiZhtgb7EVC0RTrpCBwv9ssYsgIwvOPNZFME14lgeqI+c7MtEMETqlh6bGcGMU2VN66 AAF8jkyLABRkCEFJDclbblp07iUguhh6EWSeESZasO/iRyLfFSMyS/nNu/Geaq7iK3LA OxbQ== 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=6NbEky+RLOanXfLfRed31TEItrl3hFzKUIGsWwUJGu8=; b=hYeEtG7S70uIjHXKIn4IGqJfJbbZ0owa9HXlJPIIL9Qo6jlhCBQ0R5pxFMMotQc1Og LambGHbqRv0Mu9/+um0H5LOm0Afty3UzkgMpmgw/9frNploOobnjZga2hKBz2+Swf+B3 a9ZOJ1ncmNS4iT4JHJ00/GTn55jZ1QtRnu+fiNr8caZp4QRvfyKujlCHMkufBtNtX2Y/ PJ792rrnkJK4PyB4CrG8LoAqAXJaQFa++e+vPy8BCR7GHeRw9pvLQ0Xbha9+d/gN/pxE ACEA5U5zVBK434RphpROB94NpsnOF+o6wQPNxDcrpeghEnLFMGNiYLO8xydiUzJ3zrPh sdzg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Lrg2vAPH; 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 e16si10737473ejj.154.2021.06.14.03.51.26; Mon, 14 Jun 2021 03:51:48 -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=Lrg2vAPH; 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 S233996AbhFNKwH (ORCPT + 99 others); Mon, 14 Jun 2021 06:52:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:50760 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234266AbhFNKou (ORCPT ); Mon, 14 Jun 2021 06:44:50 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 9996C61439; Mon, 14 Jun 2021 10:36:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1623666983; bh=SY/szsUB+ef9QE5b4m2yulKJ1fXnCLSbhSmIaLstYoQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Lrg2vAPHNOCkpxWvHYAh1K6vQlYc6gcn+jJWX1amYZsQFUxj2tEsQrEroZGDLe5rI SdqaHCLQlbeJ3UlAcWldVq5S/iqdU0r2i9wwNm0MdoTnl9avw4EiQo2kaAL7R+VqPz mjC6NQ5MwNfSPZ+ZC00o9LEoB1Bn78mh6C5m4oG8= 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.19 53/67] perf: Fix data race between pin_count increment/decrement Date: Mon, 14 Jun 2021 12:27:36 +0200 Message-Id: <20210614102645.564766829@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210614102643.797691914@linuxfoundation.org> References: <20210614102643.797691914@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 @@ -4155,7 +4155,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; }