From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andi Kleen <andi@firstfloor.org>, Borislav Petkov <bp@alien8.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep
Date: Mon, 23 May 2016 18:48:20 -0700 [thread overview]
Message-ID: <CA+55aFysHFxi3+gM69rpj445QQ352ZRucjw23ZeTBj-azp6pqg@mail.gmail.com> (raw)
In-Reply-To: <CALCETrXw0-KCSrjBDeKSp8GZQ8hmJXqH+2=UVPurgL7cAK6iJw@mail.gmail.com>
On Mon, May 23, 2016 at 6:23 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>>
>> Or we could just let ksoftirqd do its thing and stop raising
>> HARDIRQ_COUNT. We could add a new preempt count field just for IST
>> (yuck). We could try to hijack a different preempt count field
>> (NMI?). But I kind of like the idea of just reinstating the original
>> patch of explicitly checking that we're on a safe stack in schedule
>> and __might_sleep, since that is the actual condition we care about.
>
> Ping? I can still trigger this fairly easily on 4.6.
.. I haven't seen a patch from you, last I saw that was kind of what I expected.
That said, I still despise your patch. Why can't you just fix
"in_interrupt()" and be done with it. The original patch was like 50
lines of changes for somethinig that feels like it should be a
one-liner.
And no, we don't add idiotic new config symbols for things like "I
have this one-liner trivial arch helper". What we do is to just test
for such a helper with "#ifdef" (and if it's a inline function we do
#define xyz xyz" so that the #ifdef works).
So the original patch in this thread is still off the table,
especially since there was absolutely no explanation for why it should
be such a crazy complicated thing.
What exactly is it you are nervous about scheduling in NMI's? I agree
that that would be disastrous, but it's not supposed to actually
happen.
Linus
next prev parent reply other threads:[~2016-05-24 1:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 23:15 [PATCH v3 0/3] Handle IST interrupts from userspace on the normal stack Andy Lutomirski
2014-11-18 23:15 ` [PATCH v3 1/3] uprobes, x86: Fix _TIF_UPROBE vs _TIF_NOTIFY_RESUME Andy Lutomirski
2014-11-18 23:15 ` [PATCH v3 2/3] x86, entry: Switch stacks on a paranoid entry from userspace Andy Lutomirski
2014-11-18 23:15 ` [PATCH v3 3/3] sched, x86: Check that we're on the right stack in schedule and __might_sleep Andy Lutomirski
2014-11-19 18:40 ` Linus Torvalds
2014-11-19 19:23 ` Andy Lutomirski
2014-11-19 19:29 ` Andi Kleen
2014-11-19 19:44 ` Linus Torvalds
2014-11-19 23:04 ` Andy Lutomirski
2014-11-19 23:23 ` Linus Torvalds
2014-11-19 23:32 ` Thomas Gleixner
2014-11-19 23:42 ` Linus Torvalds
2014-11-19 23:49 ` Andy Lutomirski
2014-11-19 23:59 ` Linus Torvalds
2014-11-20 0:13 ` Andy Lutomirski
2014-11-20 0:37 ` Linus Torvalds
2014-11-20 0:46 ` Andy Lutomirski
2014-11-20 1:09 ` Linus Torvalds
2014-11-20 1:11 ` Andy Lutomirski
2014-11-20 10:28 ` Borislav Petkov
2014-11-20 23:25 ` Andy Lutomirski
2014-11-20 7:45 ` Ingo Molnar
2016-02-29 5:27 ` Andy Lutomirski
2016-05-24 1:23 ` Andy Lutomirski
2016-05-24 1:48 ` Linus Torvalds [this message]
2016-05-24 2:09 ` Andy Lutomirski
2016-05-24 2:16 ` Linus Torvalds
2014-11-19 18:29 ` [PATCH v3 0/3] Handle IST interrupts from userspace on the normal stack Luck, Tony
2014-11-19 22:15 ` [PATCH] x86, mce: Get rid of TIF_MCE_NOTIFY and associated mce tricks Luck, Tony
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=CA+55aFysHFxi3+gM69rpj445QQ352ZRucjw23ZeTBj-azp6pqg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).