lkml.org 
[lkml]   [2020]   [May]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [patch V4 part 1 02/36] x86/hw_breakpoint: Prevent data breakpoints on cpu_entry_area
    On Sat, May 9, 2020 at 2:23 AM Lai Jiangshan
    <jiangshanlai+lkml@gmail.com> wrote:
    >
    > On Tue, May 5, 2020 at 10:15 PM Thomas Gleixner <tglx@linutronix.de> wrote:
    > >
    > > From: Andy Lutomirski <luto@kernel.org>
    > >
    > > A data breakpoint near the top of an IST stack will cause unresoverable
    > > recursion. A data breakpoint on the GDT, IDT, or TSS is terrifying.
    > > Prevent either of these from happening.
    > >
    >
    > What happen when a data breakpoint on the direct GDT (load_direct_gdt())
    > and the debug IDT (load_debug_idt()) which are not considered in this patch?
    >

    I have no idea, and learning the answer may involve talking to the
    respective CPU vendors' microcode engineers. We should probably block
    those, too.

    \
     
     \ /
      Last update: 2020-05-09 21:09    [W:4.745 / U:0.716 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site