diff options
author | Peter Zijlstra <peterz@infradead.org> | 2019-02-14 10:30:52 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2019-04-03 09:36:27 +0200 |
commit | 6690e86be83ac75832e461c141055b5d601c0a6d (patch) | |
tree | ac9835c1ef68ed66a41977c0f7f9f788a0b6a6a4 /fs/omfs | |
parent | 5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539 (diff) | |
download | linux-next-6690e86be83ac75832e461c141055b5d601c0a6d.tar.gz |
sched/x86: Save [ER]FLAGS on context switch
Effectively reverts commit:
2c7577a75837 ("sched/x86_64: Don't save flags on context switch")
Specifically because SMAP uses FLAGS.AC which invalidates the claim
that the kernel has clean flags.
In particular; while preemption from interrupt return is fine (the
IRET frame on the exception stack contains FLAGS) it breaks any code
that does synchonous scheduling, including preempt_enable().
This has become a significant issue ever since commit:
5b24a7a2aa20 ("Add 'unsafe' user access functions for batched accesses")
provided for means of having 'normal' C code between STAC / CLAC,
exposing the FLAGS.AC state. So far this hasn't led to trouble,
however fix it before it comes apart.
Reported-by: Julien Thierry <julien.thierry@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: stable@kernel.org
Fixes: 5b24a7a2aa20 ("Add 'unsafe' user access functions for batched accesses")
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'fs/omfs')
0 files changed, 0 insertions, 0 deletions