From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3) Date: Thu, 31 Jan 2019 12:39:27 -0800 Message-ID: <20190131203927.GY6118@tassilo.jf.intel.com> References: <7c7ec3d9-9af6-8a1d-515d-64dcf8e89b78@linux.ibm.com> <20190125160056.GG6118@tassilo.jf.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Cong Wang Cc: Ravi Bangoria , lkml , Jiri Olsa , Peter Zijlstra , linux-perf-users@vger.kernel.org, Arnaldo Carvalho de Melo , eranian@google.com, vincent.weaver@maine.edu, "Naveen N. Rao" List-Id: linux-perf-users.vger.kernel.org > Yeah, a loop stuck looks really scary inside an NMI handler. > Should I just go ahead to send a patch to remove this warning? > Or probably turn it into a pr_info()? Not at this point. Would need to fix the PMU reset first to be more selective. -Andi