Received: by 10.192.165.148 with SMTP id m20csp267206imm; Thu, 26 Apr 2018 21:13:29 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoqctzck+cCh6q3Fi9LnnQIbzQnZotX67M69LSMv/bkFwvRFfCVnsEKE1ntz1WcQbiD1NZY X-Received: by 2002:a63:316:: with SMTP id 22-v6mr694592pgd.277.1524802409690; Thu, 26 Apr 2018 21:13:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524802409; cv=none; d=google.com; s=arc-20160816; b=x7FSzuGLNgRdcDeHymfwUJm7OZaJiH2nzAow7rWjwLEwBp+67JGge2lYgSmsmmObXR +j2wvS6BIUFLSpVvvyygvSsMpVbcoMFUBGhAm7eSCkdK1A+0MAiGj+jV+/ix7YqnFpQK bLksnri5vdDfDoglBJMcLKrP7RoUILYI+2vSJqxQwFKm5S0Q+TZgBfaNrL1JSeIigO07 rd2zwG0Vb6iFcHgcftOva/v2U0ogFtgbwIcEwpuejRXHYh1aaOSShftFOxggHD8xcAnS xfBFY+zw1Ei08fCIubuF5IiC2K1kD0ypKjdlZ7+iBPkJ/KRx13rKHmBw2MFlQ/XFmyDy WIBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature:arc-authentication-results; bh=wVgMn/TPYp8hqg9NJpzMJ1ykRfV+WTt4gBaadQEVm5A=; b=GTk3MTJeLXjBaiaOH8zNieUH8x4UVHoFsixbCJFvQes7GR6yJOiR9rBxfxWyNVk6t7 wKNQTjwicc/+ARI6mCXYFNxadrQT4xCmQ+ymqQUfZ6WltCJXPtsKUIhaQ5SZBUypMm7+ 862JJkJmxtO7+ZYKFO9QWTu83/21hE5pd4hA7GCkjJr0igh216J95oSkKUD6ksakeoB2 3To2qSvGKLmmnkZFv6yjAzfyTK+ZANr0QK5h6QlkjA2LbN3cTFN/10xAoHGs6a0Rx0QX ihIlUlmhJYC1vj1Pb+UXxZxlb+0eZThpChvWRz8Xo8qJ895tXYiMp7HAjj16XYhVJXG5 iFRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=QFB9hVru; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o6si449359pfh.229.2018.04.26.21.13.04; Thu, 26 Apr 2018 21:13:29 -0700 (PDT) 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; dkim=pass header.i=@google.com header.s=20161025 header.b=QFB9hVru; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751416AbeD0ELT (ORCPT + 99 others); Fri, 27 Apr 2018 00:11:19 -0400 Received: from mail-pg0-f66.google.com ([74.125.83.66]:32970 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750877AbeD0ELS (ORCPT ); Fri, 27 Apr 2018 00:11:18 -0400 Received: by mail-pg0-f66.google.com with SMTP id i194-v6so538063pgd.0 for ; Thu, 26 Apr 2018 21:11:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:to:cc:subject:date:message-id; bh=wVgMn/TPYp8hqg9NJpzMJ1ykRfV+WTt4gBaadQEVm5A=; b=QFB9hVruA6DwRvTz/m9MYtyUET+ewr4MMTJddnUGM4n7j72mXn+dDzn98ID3sE80Fl Xs9J2sA/ppfkCdpaFtcJiJd2ql5wZPNtqcKIkj+Pw4zzxTmHwBI9jdTgSW98WdehkRoZ FuLBi014sBez8G03nzPLNfgqNjXQIvElO/cad8gHMXn7rvl6R09Rar0sfxrv4CtEjmyB HKstLgh0G+p7b3Vnj0fcZrZZGBEbiq42FOngCj8xiRIJjFQpKXfaowgV4iYa8vEhXeFE wE0OGc3NoSljw7lvt/tDvHEZry4r4nYQ42PXo00NvFIiZtMZ8KfyvcbBObL6sq/SgjdB NstQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=wVgMn/TPYp8hqg9NJpzMJ1ykRfV+WTt4gBaadQEVm5A=; b=VGig4XbIltqWxD85GztBnG5EnlJVW0OUBWBcueVDcIM5ZltnY1HOPLOn/rzLwTu6vm Zm73GLWd7Am3Rf8Wm1dUWO7tmHZ5Hj8hk8SEarLTTtI4nuRSDUEg/5VGBbBNDeVmo5IV gpQMaMTq7nWjubk4ji9czqHKHR0EN9aIuT66pbuh+PJrtVrLcuMuAZGbhL8noB8Uxq0c 2uCxpKq0uB3FEiDZg0q8QdUuUElGKonLTj4ZwzSj6WBkOjJp7LzBGm5j3Y9cokT5Jocr NwBgZZa1eG6kkqJ1z0JrQLJUA8ZUJTNWBH3pWsJcnK1tBtQeK1oPL9xtYUnzl039NsZZ JhPg== X-Gm-Message-State: ALQs6tBVRnTq/APWy8yrPkp7uQe10FxSH3XtkQNWQTxOo+l+TwRrO5cC Haw7LUiZbDUyKjTykscMnnvAyycW288= X-Received: by 2002:a63:aa01:: with SMTP id e1-v6mr699355pgf.331.1524802276487; Thu, 26 Apr 2018 21:11:16 -0700 (PDT) Received: from joelaf.mtv.corp.google.com ([2620:0:1000:1600:3122:ea9c:d178:eb]) by smtp.gmail.com with ESMTPSA id l19-v6sm478782pgn.44.2018.04.26.21.11.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 21:11:15 -0700 (PDT) From: Joel Fernandes To: linux-kernel@vger.kernel.org Cc: Joel Fernandes , Steven Rostedt , Peter Zilstra , Ingo Molnar , Mathieu Desnoyers , Tom Zanussi , Namhyung Kim , Thomas Glexiner , Boqun Feng , Paul McKenney , Frederic Weisbecker , Randy Dunlap , Masami Hiramatsu , Fenguang Wu , Baohong Liu , Vedang Patel , kernel-team@android.com Subject: [PATCH] softirq: reorder trace_softirqs_on to prevent lockdep splat Date: Thu, 26 Apr 2018 21:11:00 -0700 Message-Id: <20180427041100.133772-1-joelaf@google.com> X-Mailer: git-send-email 2.17.0.441.gb46fe60e1d-goog Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and CONFIG_PREEMPTIRQ_EVENTS=y. $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable --- [ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled) [ 26.112636] WARNING: CPU: 0 PID: 118 at kernel/locking/lockdep.c:3854 [...] [ 26.144229] Call Trace: [ 26.144926] [ 26.145506] lock_acquire+0x55/0x1b0 [ 26.146499] ? __do_softirq+0x46f/0x4d9 [ 26.147571] ? __do_softirq+0x46f/0x4d9 [ 26.148646] trace_preempt_on+0x8f/0x240 [ 26.149744] ? trace_preempt_on+0x4d/0x240 [ 26.150862] ? __do_softirq+0x46f/0x4d9 [ 26.151930] preempt_count_sub+0x18a/0x1a0 [ 26.152985] __do_softirq+0x46f/0x4d9 [ 26.153937] irq_exit+0x68/0xe0 [ 26.154755] smp_apic_timer_interrupt+0x271/0x280 [ 26.156056] apic_timer_interrupt+0xf/0x20 [ 26.157105] The problem is the softirqs annotation in lockdep goes out of sync with the reality of the world that softirq is still off. This causes a lockdep splat because the preempt_count_sub can call into a preemptoff tracer or the trace events code, which inturn can call into lockdep *before* softirqs are really turned back on, which can cause a softirqs invalid annotation splat in lockdep. The same issue was fixed in local_bh_disable_ip which has a comment so: /* * The preempt tracer hooks into preempt_count_add and will break * lockdep because it calls back into lockdep after SOFTIRQ_OFFSET * is set and before current->softirq_enabled is cleared. * We must manually increment preempt_count here and manually * call the trace_preempt_off later. */ I have done a similar change to the local_bh_enable path to fix it. Cc: Steven Rostedt Cc: Peter Zilstra Cc: Ingo Molnar Cc: Mathieu Desnoyers Cc: Tom Zanussi Cc: Namhyung Kim Cc: Thomas Glexiner Cc: Boqun Feng Cc: Paul McKenney Cc: Frederic Weisbecker Cc: Randy Dunlap Cc: Masami Hiramatsu Cc: Fenguang Wu Cc: Baohong Liu Cc: Vedang Patel Cc: kernel-team@android.com Signed-off-by: Joel Fernandes --- kernel/softirq.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/kernel/softirq.c b/kernel/softirq.c index 177de3640c78..8a040bcaa033 100644 --- a/kernel/softirq.c +++ b/kernel/softirq.c @@ -139,9 +139,13 @@ static void __local_bh_enable(unsigned int cnt) { lockdep_assert_irqs_disabled(); + if (preempt_count() == cnt) + trace_preempt_on(CALLER_ADDR0, get_lock_parent_ip()); + if (softirq_count() == (cnt & SOFTIRQ_MASK)) trace_softirqs_on(_RET_IP_); - preempt_count_sub(cnt); + + __preempt_count_sub(cnt); } /* -- 2.17.0.441.gb46fe60e1d-goog