From: Thomas Zeitlhofer <thomas.zeitlhofer+lkml@ze-it.at>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Hugh Dickins <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: "BUG: using smp_processor_id() in preemptible" with KPTI on 4.14.11
Date: Mon, 8 Jan 2018 01:37:14 +0100 [thread overview]
Message-ID: <20180108003714.gs4xx6sej7eocz3r@toau> (raw)
In-Reply-To: <20180107085319.rm7t4r67lyfxxyke@toau>
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 <path to rootfs>
_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
next prev parent reply other threads:[~2018-01-08 0:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 1:59 "BUG: using smp_processor_id() in preemptible" with KPTI on 4.14.11 Thomas Zeitlhofer
2018-01-04 10:20 ` Thomas Zeitlhofer
2018-01-04 10:51 ` Greg Kroah-Hartman
2018-01-04 12:43 ` Thomas Zeitlhofer
2018-01-04 12:55 ` Greg Kroah-Hartman
2018-01-04 15:25 ` Thomas Zeitlhofer
2018-01-04 15:37 ` Thomas Gleixner
2018-01-04 17:07 ` Peter Zijlstra
2018-01-04 18:38 ` Thomas Zeitlhofer
2018-01-06 21:38 ` Thomas Zeitlhofer
2018-01-07 8:17 ` Greg Kroah-Hartman
2018-01-07 8:53 ` Thomas Zeitlhofer
2018-01-08 0:37 ` Thomas Zeitlhofer [this message]
2018-01-04 22:11 ` [tip:x86/pti] x86/events/intel/ds: Use the proper cache flush method for mapping ds buffers tip-bot for Peter Zijlstra
2018-01-04 23:49 ` tip-bot for Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180108003714.gs4xx6sej7eocz3r@toau \
--to=thomas.zeitlhofer+lkml@ze-it.at \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.