Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3311618imu; Sun, 11 Nov 2018 12:07:48 -0800 (PST) X-Google-Smtp-Source: AJdET5dr609YKCqxS0QpahMNDQ6/WWORFZ4A86iV9mCH2TvF2j6Tr1Mo4SiE5e199vk2dKkPGL+c X-Received: by 2002:a63:5517:: with SMTP id j23-v6mr14716641pgb.208.1541966868344; Sun, 11 Nov 2018 12:07:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541966868; cv=none; d=google.com; s=arc-20160816; b=kp9LydtTdzsMlBDzb1iUJVVZERhdRZx64fNainzL7FjhhuI0lnNYECX3iXnmqpEwTS UDtvAjJaIp5EOBTZB3IEoy7GXz7YdCBQaXt01bSbfN2QqUHgtDQlU1fkI/4HiErf7WQp 49z3GMIFcLVqh+a8oig07xsBambaDBbtCNAdkh3YYaFXHeK9zununNeK08uoRGbsNDw3 HIM8cknzS6seFK0gIIEM++Jbj5sGw3oj53Q0KLWAMyK7rdtPNoaKOgji8yw01yFgf0gE 0E8LK63NRVhTs9f/aqyu3Yu9Lfq1deN4ACWkyqCtm9duYvlnGIcnMFtY6vXmY32QXTMS Z6+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=hs/cFiw6jaPMNhqXNG6jGXPLyAhi3iOWXn/ziv0UK1k=; b=Gow9MF+AlpBVzm3YPH5g3PCBVnhn8LLRebR42X0+SeCI3A95toLZvCH4q8f+Oy1L7O zqG6Ojh5O9jElPYYBuiQaVjketd5kvlVwB9E3WFHUUWT7dxBMJNXbzPNkpHIJPFJbXwr +QLrNKnv41QYE5ehMxLbtKjZf9U0NmWklnhqXBiqrA6LX0YrUQisC9dWzMwyzerhvoXj 6OAcHyLZGpmNyp6FwkDKLwKii5/cFPjDqIO8/Xnt3GKf5vdsWdnvuck5L7l5iQ6R+wtZ LC4ibPsRryQ9TBiRbKYxM4K1ASZ4aFXiIo0y0pTms+oUxmfZjX4HOUxa7NGQTWstlAvn JUwA== 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 g6si8662949pgn.57.2018.11.11.12.07.33; Sun, 11 Nov 2018 12:07:48 -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 S1731339AbeKLFzb (ORCPT + 99 others); Mon, 12 Nov 2018 00:55:31 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:51894 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730984AbeKLFza (ORCPT ); Mon, 12 Nov 2018 00:55:30 -0500 Received: from [192.168.4.242] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gLvt4-0000oM-4Z; Sun, 11 Nov 2018 19:59:14 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gLvsR-0001W1-7M; Sun, 11 Nov 2018 19:58:35 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Ingo Molnar" , "Steven Rostedt (VMware)" , "Mikulas Patocka" Date: Sun, 11 Nov 2018 19:49:05 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) Subject: [PATCH 3.16 114/366] branch-check: fix long->int truncation when profiling branches In-Reply-To: X-SA-Exim-Connect-IP: 192.168.4.242 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.61-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Mikulas Patocka commit 2026d35741f2c3ece73c11eb7e4a15d7c2df9ebe upstream. The function __builtin_expect returns long type (see the gcc documentation), and so do macros likely and unlikely. Unfortunatelly, when CONFIG_PROFILE_ANNOTATED_BRANCHES is selected, the macros likely and unlikely expand to __branch_check__ and __branch_check__ truncates the long type to int. This unintended truncation may cause bugs in various kernel code (we found a bug in dm-writecache because of it), so it's better to fix __branch_check__ to return long. Link: http://lkml.kernel.org/r/alpine.LRH.2.02.1805300818140.24812@file01.intranet.prod.int.rdu2.redhat.com Cc: Ingo Molnar Fixes: 1f0d69a9fc815 ("tracing: profile likely and unlikely annotations") Signed-off-by: Mikulas Patocka Signed-off-by: Steven Rostedt (VMware) [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben Hutchings --- include/linux/compiler.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/include/linux/compiler.h +++ b/include/linux/compiler.h @@ -105,7 +105,7 @@ void ftrace_likely_update(struct ftrace_ #define unlikely_notrace(x) __builtin_expect(!!(x), 0) #define __branch_check__(x, expect) ({ \ - int ______r; \ + long ______r; \ static struct ftrace_branch_data \ __attribute__((__aligned__(4))) \ __attribute__((section("_ftrace_annotated_branch"))) \