Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2220011ybd; Thu, 27 Jun 2019 08:42:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqxdRTPzi/xud8G232PqGjwgponKNWGtkxpf8DEb+xjLgIeUQ1e9LKMhkSTt80d6+slLrBfE X-Received: by 2002:a17:90a:dd42:: with SMTP id u2mr6878563pjv.118.1561650177741; Thu, 27 Jun 2019 08:42:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561650177; cv=none; d=google.com; s=arc-20160816; b=qKIXyGjYIpgGnbnz3sHwY5HiRM8QR3DmDbkH1ONR9Pe5PBiycEUXpze6N+jyFuM43i p77GyDQoejfqutUXxRUXDRlKgkuBwA3QQ28pC58mUbV8n1hmvM+Iva60EYRrKC0dKucz TdLT8GwL09H1e++ISiUP3XXgAveFveZXU2GfIqjeAGbQ3XRGGqXiQZeLVNCD9jBW7lwh RCMSYLpPBJ6CUFaOtR/UyEihwCjlUDCmsGaWToXdNg0e7TbbEEbqz91WXYDYAfTlNSbq pmnvcglPOIgf0cG83eh48hDH/6rNKRG4X8r4JCo81TLADFPL8p9EMknkkqYwEHiXw+NK hBug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=QdgaUYT2PaAKZsPsTmWsJv5fjayE9ehNV1SbDkzjewA=; b=tm4fp4z5BgJWVGERHlnZZKlBnosmQqUBa81NjSi03mOKf1i/Fpub2CgUbNxmL2R1yD HP+SPSdwkx8fbiUKwpxIOlsNe2tFqqW2pjLqBg/f8lD6dJDAs3tsqc2JW7FL2o5EEj0P ogPI9hvQ9EVfhVJWoXEDT67hKm2eNRrbsxJJ0Lg0zsF+bm71fn04vaSHYj2M+3JCZapU Gt7bHTV00TvR1BqECXzR+YAaX00p71fc9WxLV3TZTDFd2+lU8mN3cgNpj+2SVopakGO+ r5vKoxeXmbu5HbsUVTH9Q/iRRVMOeVwiJ1XSgArMzGXGhdQ5g6fmIbanCMf86tUVf+Q7 PPSQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=EovcUH63; 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 l13si5476879pjq.69.2019.06.27.08.42.41; Thu, 27 Jun 2019 08:42:57 -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=@joelfernandes.org header.s=google header.b=EovcUH63; 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 S1726542AbfF0Pmd (ORCPT + 99 others); Thu, 27 Jun 2019 11:42:33 -0400 Received: from mail-lf1-f66.google.com ([209.85.167.66]:33484 "EHLO mail-lf1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726497AbfF0Pmc (ORCPT ); Thu, 27 Jun 2019 11:42:32 -0400 Received: by mail-lf1-f66.google.com with SMTP id y17so1923192lfe.0 for ; Thu, 27 Jun 2019 08:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QdgaUYT2PaAKZsPsTmWsJv5fjayE9ehNV1SbDkzjewA=; b=EovcUH634m6WUf69St5UAzSvsrpd5u/ghfbOaLlVWaDekoh12bRgmDTX959HEC+u9Z /r80EGYTHU4SJWk0AosG7kfKYQW26oRj335YeGD476/k/tN5EHX5BsSTO8ob7Jl5hWDX Psqz8iXxB9d3pt0BZqZtyIGFIxcLhOVtxsqx4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QdgaUYT2PaAKZsPsTmWsJv5fjayE9ehNV1SbDkzjewA=; b=W2K8QXKDoNi+bBo4sEX3xDYlsYaod1/WqemHcI8tc3Ge65FygyTeQcJgN8LKYZq3o/ B3ud2cvpQ6ltvaqO+21lHi3uJvjYjSenelPUqD1Q92ormS3AAAffJ1O0MR85HYJ8tZOZ gYGs8/RIiKjcXBFLKBwgr7YJxQ2CnJ2Lj4onu0C3RMJ7D/9nUOc4VxwkC/jElH/1Q7gj 9KzN4TZD+R4v7aDNJHGvWtndt1On42XmZGqYsBon6JhcowqakXdpEMe7P02WWzS33fEl yo/DXuPdDig9CCW769pz9hkyuP5pqftjKOz8nURRXKTIQvWipfQRwEQeKMNYTph5ViDH C9YA== X-Gm-Message-State: APjAAAUmvtRbrJKSsu+bxq064oJM7A7japFqy28638GvfU3vDw/NFOJg 1RVelEOKqyukXEZaWxeeF0+xAVijInwYm2xjSt5UiQ== X-Received: by 2002:a19:7912:: with SMTP id u18mr2159784lfc.81.1561650150827; Thu, 27 Jun 2019 08:42:30 -0700 (PDT) MIME-Version: 1.0 References: <20190626135447.y24mvfuid5fifwjc@linutronix.de> <20190626162558.GY26519@linux.ibm.com> <20190627142436.GD215968@google.com> <20190627103455.01014276@gandalf.local.home> <20190627153031.GA249127@google.com> <20190627154011.vbje64x6auaknhx4@linutronix.de> In-Reply-To: <20190627154011.vbje64x6auaknhx4@linutronix.de> From: Joel Fernandes Date: Thu, 27 Jun 2019 11:42:19 -0400 Message-ID: Subject: Re: [RFC] Deadlock via recursive wakeup via RCU with threadirqs To: Sebastian Andrzej Siewior Cc: Steven Rostedt , "Paul E. McKenney" , rcu , LKML , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Josh Triplett , Mathieu Desnoyers , Lai Jiangshan Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 27, 2019 at 11:40 AM Sebastian Andrzej Siewior wrote: > > On 2019-06-27 11:37:10 [-0400], Joel Fernandes wrote: > > Sebastian it would be nice if possible to trace where the > > t->rcu_read_unlock_special is set for this scenario of calling > > rcu_read_unlock_special, to give a clear idea about whether it was > > really because of an IPI. I guess we could also add additional RCU > > debug fields to task_struct (just for debugging) to see where there > > unlock_special is set. > > > > Is there a test to reproduce this, or do I just boot an intel x86_64 > > machine with "threadirqs" and run into it? > > Do you want to send me a patch or should I send you my kvm image which > triggers the bug on boot? I think the kvm image would be better so I reproduce it on my side. After that I can share any debug patches with you if they are useful. Thanks.