From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756191AbaKTHpK (ORCPT ); Thu, 20 Nov 2014 02:45:10 -0500 Received: from mail-wg0-f43.google.com ([74.125.82.43]:43715 "EHLO mail-wg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750917AbaKTHpI (ORCPT ); Thu, 20 Nov 2014 02:45:08 -0500 Date: Thu, 20 Nov 2014 08:45:02 +0100 From: Ingo Molnar To: Andy Lutomirski Cc: Linus Torvalds , Andi Kleen , Borislav Petkov , the arch/x86 maintainers , Linux Kernel Mailing List , Peter Zijlstra , Oleg Nesterov , Tony Luck Subject: Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep Message-ID: <20141120074501.GA3805@gmail.com> References: <20141119192928.GL12538@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andy Lutomirski wrote: > On Wed, Nov 19, 2014 at 3:59 PM, Linus Torvalds > wrote: > > On Wed, Nov 19, 2014 at 3:49 PM, Andy Lutomirski wrote: > >> > >> My only real objection is that it's going to be ugly and > >> error prone. It'll have to be something like: > > > > No. > > > >> because the whole point of this series is to make the IST > >> entries not be atomic when they come from userspace. > > > > Andy, you need to lay off the drugs. > > > > No drugs, just imprecision. This series doesn't change NMI > handling at all. It only changes machine_check int3, debug, > and stack_segment. (Why is #SS using IST stacks anyway?) We made most of those preemptible in -rt and changed it away from the IST. I never got a good explanation from anyone for why they were IST in the first place - histeric accident or such. Feel free to clean this up too! Thanks, Ingo