Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp21201428ybl; Sun, 5 Jan 2020 23:13:00 -0800 (PST) X-Google-Smtp-Source: APXvYqxtrj3e/ldHV7JRMLMqnCJiQp0VoIhe+DF2Ybx9ZzKAbSoth9i8T8VuhpdBqxaKTy3sh30D X-Received: by 2002:a9d:6f07:: with SMTP id n7mr110684287otq.112.1578294780729; Sun, 05 Jan 2020 23:13:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578294780; cv=none; d=google.com; s=arc-20160816; b=02oygZ8SVEFzdCUCCV3C8UKvp4MPOwWumHwX91R+8EZcTA0PdcRLJ3iLnl/FSA2dZr 1gMmxMfLlP9ONjo46t32A0pOmTgUSh4eY1d3FOvClDoHEnOhYoMyMKn2n9hgPGTLIyJt b2XnXjQ/KUljTHcf6sSq5d4Xd+fF6uEbopLuR9pcl3CqIFtGDR3HTK3rc1s0rxumHf9q 0kCpKMlMiLdpD2vSBT/rFBAfv84r5fxnAEx0bv2+L0SvuIp8/+S6Xjvl50feiL+zk9OX SOMCS685fKyNaZKCAP6kmEEWMcYmRyMZyrKmNfrn+yoBUVb5Xe5LqNd5wJAB3aEkTUbg XCmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=esTdrX5D7MTLTW+rnayOdTrMeF9TKqXQdWkkivOvSh4=; b=mN9iElpZx1p0c+l/YTfwCv1PkZZfhyHOh66f74JjqO1axOe0JwGbXOnM8yQrCx1viK b5dX78ac5C+sFt4TEu9JPIZFrMnK9k8Bu+rPf8tAmx7MLrwr6cB7RGFQyHBCQc6F+FFA oGX7BMnZK4HYfY0S1CyOFEomx3MVlyRuKdPTbY0fCNlIl9udzAe2yrMQfHsdr/3fZpiO UvM8YIsoW5ohbDD9jGYWz4BHLX6ri5VxZ9TMeQrSSJrEtueXy7tiWkTY8kotpXUvKd0l l1IeEAERzIhHq1BVL9aFoWoZvohJ/X/dQubpHbYlZ3MlilJhy+Wpse/ZJzleFA7bxIYF atrQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=SoLHbDPT; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 17si18028421oix.22.2020.01.05.23.12.48; Sun, 05 Jan 2020 23:13:00 -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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=SoLHbDPT; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726722AbgAFHLM (ORCPT + 99 others); Mon, 6 Jan 2020 02:11:12 -0500 Received: from mail-wm1-f68.google.com ([209.85.128.68]:53365 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726494AbgAFHLL (ORCPT ); Mon, 6 Jan 2020 02:11:11 -0500 Received: by mail-wm1-f68.google.com with SMTP id m24so13963134wmc.3 for ; Sun, 05 Jan 2020 23:11:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=esTdrX5D7MTLTW+rnayOdTrMeF9TKqXQdWkkivOvSh4=; b=SoLHbDPTN+qjDA8D2Hlh3G3IrERo2a+vpJnBIE4NQrkqN2lx9XhoImwCxNefsCiirS 81HhQxoF4mtRrGNh9zPbtHTWyfUiPscXDXPYJ/0pjcu6KT1F6QD9z5g/PcckApTbcy2A 1xvlEo1KAOzfH7u2Q51fwaJCX6aM9l5dcibTRBnmbC63MDO/+vu7mOldQbrcMUCdSzyN ipt8bnT+2hlsroK8XFKHSdVgTVzIcGgfxvQtOkpRg6bW1fYWsLnzFqtcvFc1ao4FC1wZ O64j6GIsmU5KMpauzzDHxCUy0LoDrQtu0+09CBcEsXbX4tCXfe6lyvs9bWv38zY5zuTb PX0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=esTdrX5D7MTLTW+rnayOdTrMeF9TKqXQdWkkivOvSh4=; b=aR64XAzBNGCfysuD/L9t1da4CWkDAC8ZQ1gOFVhHp+jeMb6Te5Ga7TgqjOPReqZjlc pODFOiMzUpTTCeRRXeKs/CFopg2sBSwhIc1Fyx3ZuDXmakIgzE3HLypZiyoa38VyAP89 D9+X7ylsAqXba5cX13E6nmyL2mXnryqHGQPSIlJrYQjrjwWaWo8SSIdwS938y8jtuQlO EQq3oIDj8iP3TtnxuCE4VubQSS7uMPwOD0H+UPZqxvx3K+j2k0+Xd0buLWGOIzO7bb8O jUV1gzWScyywYY/x0xlceM2ZHEQ6yAH1EDH47TU2aqdMEiogSgTzlu0oPl0onrZzgcNc M1Iw== X-Gm-Message-State: APjAAAXWQDO1r2EBDQqOzLr08wOJAti5TLE8Z96lHt4TFTOgt+tmiwPQ 4GF8+Cf3qJIT01rDHmg04uk= X-Received: by 2002:a7b:c19a:: with SMTP id y26mr32598399wmi.152.1578294669688; Sun, 05 Jan 2020 23:11:09 -0800 (PST) Received: from gmail.com (54033286.catv.pool.telekom.hu. [84.3.50.134]) by smtp.gmail.com with ESMTPSA id n3sm22456698wmc.27.2020.01.05.23.11.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 Jan 2020 23:11:09 -0800 (PST) Date: Mon, 6 Jan 2020 08:11:07 +0100 From: Ingo Molnar To: Borislav Petkov Cc: Chuansheng Liu , linux-kernel@vger.kernel.org, tony.luck@intel.com, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com Subject: Re: [PATCH] x86/mce/therm_throt: Fix the access of uninitialized therm_work Message-ID: <20200106071107.GA95725@gmail.com> References: <20200106064155.64-1-chuansheng.liu@intel.com> <20200106070759.GB12238@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200106070759.GB12238@zn.tnic> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Borislav Petkov wrote: > On Mon, Jan 06, 2020 at 06:41:55AM +0000, Chuansheng Liu wrote: > > In ICL platform, it is easy to hit bootup failure with panic > > in thermal interrupt handler during early bootup stage. > > > > Such issue makes my platform almost can not boot up with > > latest kernel code. > > > > The call stack is like: > > kernel BUG at kernel/timer/timer.c:1152! > > > > Call Trace: > > __queue_delayed_work > > queue_delayed_work_on > > therm_throt_process > > intel_thermal_interrupt > > ... > > > > When one CPU is up, the irq is enabled prior to CPU UP > > notification which will then initialize therm_worker. > > You mean the unmasking of the thermal vector at the end of > intel_init_thermal()? > > If so, why don't you move that to the end of the notifier and unmask it > only after all the necessary work like setting up the workqueues etc, is > done, and save yourself adding yet another silly bool? A debugging WARN_ON_ONCE() when the workqueue is not initialized yet would also be useful I suspect. This would turn any remaining race-crash boot failure in this area into a warning. Thanks, Ingo