On Tue, Sep 29, 2015 at 10:35 AM, Chris Metcalf <cmetcalf@xxxxxxxxxx> wrote:
> On 09/28/2015 06:38 PM, Andy Lutomirski wrote:
>>
>> On Mon, Sep 28, 2015 at 2:54 PM, Chris Metcalf <cmetcalf@xxxxxxxxxx>
>> wrote:
>>>
>>> On 09/28/2015 04:51 PM, Andy Lutomirski wrote:
>>>>
>>>> On Mon, Sep 28, 2015 at 11:17 AM, Chris Metcalf <cmetcalf@xxxxxxxxxx>
>>>>>
>>>>> @@ -35,8 +36,12 @@ static inline enum ctx_state exception_enter(void)
>>>>> return 0;
>>>>>
>>>>> prev_ctx = this_cpu_read(context_tracking.state);
>>>>> - if (prev_ctx != CONTEXT_KERNEL)
>>>>> - context_tracking_exit(prev_ctx);
>>>>> + if (prev_ctx != CONTEXT_KERNEL) {
>>>>> + if (context_tracking_exit(prev_ctx)) {
>>>>> + if (task_isolation_strict())
>>>>> + task_isolation_exception();
>>>>> + }
>>>>> + }
>>>>>
>>>>> return prev_ctx;
>>>>> }
>>>>
>>>> x86 does not promise to call this function. In fact, x86 is rather
>>>> likely to stop ever calling this function in the reasonably near
>>>> future.
>>>
>>>
>>> Yes, in which case we'd have to do it the same way we are doing
>>> it for arm64 (see patch 09/11), by calling task_isolation_exception()
>>> explicitly from within the relevant exception handlers. If we start
>>> doing that, it's probably worth wrapping up the logic into a single
>>> inline function to keep the added code short and sweet.
>>>
>>> If in fact this might happen in the short term, it might be a good
>>> idea to hook the individual exception handlers in x86 now, and not
>>> hook the exception_enter() mechanism at all.
>>
>> It's already like that in Linus' tree.
>
>
> OK, I will restructure so that it doesn't rely on the context_tracking
> code at all, but instead requires a line of code in every relevant
> kernel exception handler.
>
>> FWIW, most of those exception handlers send signals, so it might pay
>> to do it in notify_die or die instead.
>
>
> Well, the most interesting category is things that don't actually
> trigger a signal (e.g. minor page fault) since those are things that
> cause significant issues with task isolation processes
> (kernel-induced jitter) but aren't otherwise user-visible,
> much like an undiscovered syscall in a third-party library
> can cause unexpected jitter.
Would it make sense to exempt the exceptions that result in signals?
After all, those are detectable even without your patches. Going
through all of the exception types:
divide_error, overflow, invalid_op, coprocessor_segment_overrun,
invalid_TSS, segment_not_present, stack_segment, alignment_check:
these all send signals anyway.
double_fault is fatal.
bounds: MPX faults can be silently fixed up, and those will need
notification. (Or user code should know not to do that, since it
requires an explicit opt in, and user code can flip it back off to get
the signals.)
general_protection: always signals except in vm86 mode.
int3: silently fixed if uprobes are in use, but I don't think
isolation cares about that. Otherwise signals.
debug: The perf hw_breakpoint can result in silent fixups, but those
require explicit opt-in from the admin. Otherwise, unless there's a
bug or a debugger, the user will get a signal. (As a practical
matter, the only interesting case is the undocumented ICEBP
instruction.)
math_error, simd_coprocessor_error: Sends a signal.
spurious_interrupt_bug: Irrelevant on any modern CPU AFAIK. We should
just WARN if this hits.
device_not_available: If you're using isolation without an FPU, you
have bigger problems.
page_fault: Needs notification.
NMI, MCE: arguably these should *not* notify or at least not fatally.
So maybe a better approach would be to explicitly notify for the
relevant entries: IRQs, non-signalling page faults, and non-signalling
MPX fixups. Other arches would have their own lists, but they're
probably also short except for emulated instructions.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
