Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp3549779ima; Mon, 4 Feb 2019 00:53:49 -0800 (PST) X-Google-Smtp-Source: ALg8bN6yverhNxsHSwyhaLTHyP5dhCu/b5VNdOuBUSMiqxLVqrvCfkCEDPSHdh9F+z8KjEjLm6lA X-Received: by 2002:a63:c904:: with SMTP id o4mr45169239pgg.331.1549270429585; Mon, 04 Feb 2019 00:53:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549270429; cv=none; d=google.com; s=arc-20160816; b=CqUIDYUjGbQmVxxg/nIv7oBHL3+NWlJorakT3bn+5wrzLCPe5oAKUx1Nncd+Uyfjm9 iufTjuLKPHlUFv8X05rFC7TH0Ji8e+D97Gk7j2l3i7/0D2e/DIRXswAyl+AYN1FrK2lK dJgmbTj6Lp2apSxzPjbMGBja6CNZDSMyuORBNQwv3KUI8T4Z3u1SqEtgC7gLixTjOPrD dudTUKckQMz/LyJXjBHbpck80/ihqEaW9FsO7mzPDqP7yYeT3JCtvZmMpFJJRmnLOIsJ 0ATT6OvpNw6FlFe/7GVjp8n/Dtf+DqdfBK/gF15y63xTGf5s0uaK381V46FQ5t/+bjvJ 8tPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:mime-version:robot-unsubscribe:robot-id :git-commit-id:subject:to:references:in-reply-to:reply-to:cc :message-id:from:date; bh=7zoQmUQjJcsBiykxTj1Ziy+G6pApDsLFQLo7py8ZGLg=; b=qKPMkO8zuSXGdyl2kDM8BcP8FA5SzrzmiCqd22JsE1x+uXbCXNFSgc74dFQMUA/jPU hBMzyLJMenlMqk0i6mmhVo7OWLYEUfE/Mo5tWsGVGGb5QpMzZpI6nE8W6kYF+QVUdXsr fk9dvP2mAkd9dNz3zC9ZSJoz5le2JrEJmtLC48ebu5Kc5ydDWWOfkUz9Acy+ejy0eydf PKjkmCOXtr7JSROS+ZMByL+1CS5uJRZyKNF4G+GT7+lGPP7iqt9KqGn8YNl21O1riKkS 4vKcIPoI5FJByhahCYKjQNh9K5BylmkDQd+wscay97mIn2c/7D908d1ECwBwBwlfZZLK EaJg== ARC-Authentication-Results: i=1; mx.google.com; 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 n4si4762004pgd.10.2019.02.04.00.53.34; Mon, 04 Feb 2019 00:53:49 -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; 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 S1728503AbfBDIwv (ORCPT + 99 others); Mon, 4 Feb 2019 03:52:51 -0500 Received: from terminus.zytor.com ([198.137.202.136]:59961 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727213AbfBDIwv (ORCPT ); Mon, 4 Feb 2019 03:52:51 -0500 Received: from terminus.zytor.com (localhost [127.0.0.1]) by terminus.zytor.com (8.15.2/8.15.2) with ESMTPS id x148qTrV357533 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 4 Feb 2019 00:52:29 -0800 Received: (from tipbot@localhost) by terminus.zytor.com (8.15.2/8.15.2/Submit) id x148qT0a357530; Mon, 4 Feb 2019 00:52:29 -0800 Date: Mon, 4 Feb 2019 00:52:29 -0800 X-Authentication-Warning: terminus.zytor.com: tipbot set sender to tipbot@zytor.com using -f From: tip-bot for Elena Reshetova Message-ID: Cc: elena.reshetova@intel.com, tglx@linutronix.de, mingo@kernel.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, keescook@chromium.org, jolsa@redhat.com, peterz@infradead.org, acme@redhat.com, ishkamiel@gmail.com, hpa@zytor.com, alexander.shishkin@linux.intel.com, dwindsor@gmail.com Reply-To: keescook@chromium.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, mingo@kernel.org, tglx@linutronix.de, elena.reshetova@intel.com, dwindsor@gmail.com, alexander.shishkin@linux.intel.com, hpa@zytor.com, ishkamiel@gmail.com, peterz@infradead.org, acme@redhat.com, jolsa@redhat.com In-Reply-To: <1548678448-24458-3-git-send-email-elena.reshetova@intel.com> References: <1548678448-24458-3-git-send-email-elena.reshetova@intel.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:perf/core] perf/ring_buffer: Convert ring_buffer.refcount to refcount_t Git-Commit-ID: fecb8ed2ce7010db373f8517ee815380d8e3c0c4 X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline X-Spam-Status: No, score=-0.8 required=5.0 tests=ALL_TRUSTED,BAYES_00, FREEMAIL_FORGED_REPLYTO,T_DATE_IN_FUTURE_96_Q autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on terminus.zytor.com Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: fecb8ed2ce7010db373f8517ee815380d8e3c0c4 Gitweb: https://git.kernel.org/tip/fecb8ed2ce7010db373f8517ee815380d8e3c0c4 Author: Elena Reshetova AuthorDate: Mon, 28 Jan 2019 14:27:27 +0200 Committer: Ingo Molnar CommitDate: Mon, 4 Feb 2019 08:46:16 +0100 perf/ring_buffer: Convert ring_buffer.refcount to refcount_t atomic_t variables are currently used to implement reference counters with the following properties: - counter is initialized to 1 using atomic_set() - a resource is freed upon counter reaching zero - once counter reaches zero, its further increments aren't allowed - counter schema uses basic atomic operations (set, inc, inc_not_zero, dec_and_test, etc.) Such atomic variables should be converted to a newly provided refcount_t type and API that prevents accidental counter overflows and underflows. This is important since overflows and underflows can lead to use-after-free situation and be exploitable. The variable ring_buffer.refcount is used as pure reference counter. Convert it to refcount_t and fix up the operations. ** Important note for maintainers: Some functions from refcount_t API defined in lib/refcount.c have different memory ordering guarantees than their atomic counterparts. Please check Documentation/core-api/refcount-vs-atomic.rst for more information. Normally the differences should not matter since refcount_t provides enough guarantees to satisfy the refcounting use cases, but in some rare cases it might matter. Please double check that you don't have some undocumented memory guarantees for this variable usage. For the ring_buffer.refcount it might make a difference in following places: - ring_buffer_get(): increment in refcount_inc_not_zero() only guarantees control dependency on success vs. fully ordered atomic counterpart - ring_buffer_put(): decrement in refcount_dec_and_test() only provides RELEASE ordering and ACQUIRE ordering + control dependency on success vs. fully ordered atomic counterpart Suggested-by: Kees Cook Signed-off-by: Elena Reshetova Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: David Windsor Reviewed-by: Hans Liljestrand Cc: Alexander Shishkin Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: acme@kernel.org Cc: namhyung@kernel.org Link: https://lkml.kernel.org/r/1548678448-24458-3-git-send-email-elena.reshetova@intel.com Signed-off-by: Ingo Molnar --- kernel/events/core.c | 4 ++-- kernel/events/internal.h | 3 ++- kernel/events/ring_buffer.c | 2 +- 3 files changed, 5 insertions(+), 4 deletions(-) diff --git a/kernel/events/core.c b/kernel/events/core.c index 677164d54547..284232edf9be 100644 --- a/kernel/events/core.c +++ b/kernel/events/core.c @@ -5393,7 +5393,7 @@ struct ring_buffer *ring_buffer_get(struct perf_event *event) rcu_read_lock(); rb = rcu_dereference(event->rb); if (rb) { - if (!atomic_inc_not_zero(&rb->refcount)) + if (!refcount_inc_not_zero(&rb->refcount)) rb = NULL; } rcu_read_unlock(); @@ -5403,7 +5403,7 @@ struct ring_buffer *ring_buffer_get(struct perf_event *event) void ring_buffer_put(struct ring_buffer *rb) { - if (!atomic_dec_and_test(&rb->refcount)) + if (!refcount_dec_and_test(&rb->refcount)) return; WARN_ON_ONCE(!list_empty(&rb->event_list)); diff --git a/kernel/events/internal.h b/kernel/events/internal.h index 6dc725a7e7bc..4718de2a04e6 100644 --- a/kernel/events/internal.h +++ b/kernel/events/internal.h @@ -4,13 +4,14 @@ #include #include +#include /* Buffer handling */ #define RING_BUFFER_WRITABLE 0x01 struct ring_buffer { - atomic_t refcount; + refcount_t refcount; struct rcu_head rcu_head; #ifdef CONFIG_PERF_USE_VMALLOC struct work_struct work; diff --git a/kernel/events/ring_buffer.c b/kernel/events/ring_buffer.c index ed6409300ef5..0a71d16ca41b 100644 --- a/kernel/events/ring_buffer.c +++ b/kernel/events/ring_buffer.c @@ -284,7 +284,7 @@ ring_buffer_init(struct ring_buffer *rb, long watermark, int flags) else rb->overwrite = 1; - atomic_set(&rb->refcount, 1); + refcount_set(&rb->refcount, 1); INIT_LIST_HEAD(&rb->event_list); spin_lock_init(&rb->event_lock);