(Correct Sean Christopherson's email address) On Mon, Apr 26, 2021 at 6:40 PM Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > On 26/04/21 11:33, Lai Jiangshan wrote: > > When handle_interrupt_nmi_irqoff() is called, we may lose the > > CPU-hidden-NMI-masked state due to IRET of #DB, #BP or other traps > > between VMEXIT and handle_interrupt_nmi_irqoff(). > > > > But the NMI handler in the Linux kernel*expects* the CPU-hidden-NMI-masked > > state is still set in the CPU for no nested NMI intruding into the beginning > > of the handler. > > > > The original code "int $2" can provide the needed CPU-hidden-NMI-masked > > when entering #NMI, but I doubt it about this change. > > How would "int $2" block NMIs? Sorry, I haven't checked it. > The hidden effect of this change (and I > should have reviewed better the effect on the NMI entry code) is that > the call will not use the IST anymore. > > However, I'm not sure which of the two situations is better: entering > the NMI handler on the IST without setting the hidden NMI-blocked flag > could be a recipe for bad things as well. The change makes the ASM NMI entry called on the kernel stack. But the ASM NMI entry expects it on the IST stack and it plays with "NMI executing" variable on the IST stack. In this change, the stranded ASM NMI entry will use the wrong/garbage "NMI executing" variable on the kernel stack and may do some very wrong thing. On Mon, Apr 26, 2021 at 9:59 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > > But the NMI handler in the Linux kernel*expects* the CPU-hidden-NMI-masked > > > > state is still set in the CPU for no nested NMI intruding into the beginning > > > > of the handler. > > > This is incorrect. The Linux kernel has for some time handled the case of > nested NMIs. It had to, to implement the ftrace break point updates, as it > would trigger an int3 in an NMI which would "unmask" the NMIs. It has also > been a long time bug where a page fault could do the same (the reason you > could never do a dump all tasks from NMI without triple faulting!). > > But that's been fixed a long time ago, and I even wrote an LWN article > about it ;-) > > https://lwn.net/Articles/484932/ > > The NMI handler can handle the case of nested NMIs, and implements a > software "latch" to remember that another NMI is to be executed, if there > is a nested one. And it does so after the first one has finished. Sorry, in my reply, "the NMI handler" meant to be the ASM entry installed on the IDT table which really expects to be NMI-masked at the beginning. The C NMI handler can handle the case of nested NMIs, which is useful here. I think we should change it to call the C NMI handler directly here as Andy Lutomirski suggested: On Mon, Apr 26, 2021 at 11:09 PM Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > The C NMI code has its own reentrancy protection and has for years. > It should work fine for this use case. I think this is the right way.
