Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754860AbeAHAh2 (ORCPT + 1 other); Sun, 7 Jan 2018 19:37:28 -0500 Received: from vie01a-dmta-pe06-2.mx.upcmail.net ([84.116.36.15]:25861 "EHLO vie01a-dmta-pe06-2.mx.upcmail.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754722AbeAHAh0 (ORCPT ); Sun, 7 Jan 2018 19:37:26 -0500 X-SourceIP: 84.112.117.109 Date: Mon, 8 Jan 2018 01:37:14 +0100 From: Thomas Zeitlhofer To: Greg Kroah-Hartman Cc: Peter Zijlstra , Thomas Gleixner , Hugh Dickins , LKML Subject: Re: "BUG: using smp_processor_id() in preemptible" with KPTI on 4.14.11 Message-ID: <20180108003714.gs4xx6sej7eocz3r@toau> References: <20180104105111.GA2754@kroah.com> <20180104124320.eawuo6q7wnwzpf7s@toau> <20180104125528.GA15548@kroah.com> <20180104152516.3sql2ayoemlephig@toau> <20180104170712.GB3040@hirez.programming.kicks-ass.net> <20180104183800.ewx42etmmzk5b544@toau> <20180106213838.zxzbvufa3j7xeyhe@toau> <20180107081718.GB9509@kroah.com> <20180107085319.rm7t4r67lyfxxyke@toau> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180107085319.rm7t4r67lyfxxyke@toau> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Sun, Jan 07, 2018 at 09:53:19AM +0100, Thomas Zeitlhofer wrote: > On Sun, Jan 07, 2018 at 09:17:18AM +0100, Greg Kroah-Hartman wrote: > > On Sat, Jan 06, 2018 at 10:38:38PM +0100, Thomas Zeitlhofer wrote: [...] > > > While solving the previous problem, this patch also introduces new > > > "fun and games"... > > > > > > Now, terminating a systemd-nspawn container, reliably crashes the > > > host (so far tested only on Haswell, if that matters). Once, I was > > > able to capture the following trace: > > > > Is this also reproducable on Linus's tree right now? > > It is reproducible with this patch on top of 4.15-rc6 (might be able > to test Linus's current tree later that day). Some more testing showed that this is not caused by the patch after all, sorry for the noise. The crash happens quite reliably, but with a rather low probability it does not occur. When I have tested 4.14.11 without the patch it was obviously such a low probability event - in the meantime 4.14.11 without the patch also crashed. The situation is also unchanged with 4.15-rc7. Interestingly, it happens only when using the boot switch "-b", i.e.: systemd-nspawn -b -D _and_ terminating the container by pressing ^] three times. Other combinations (e.g., no "-b" and terminating with ^]^]^], "-b" and terminating by running shutdown inside the container) work just fine. Anyway, this is already off-topic and might be subject to a different thread... Thanks, Thomas