From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753851AbcCNStP (ORCPT ); Mon, 14 Mar 2016 14:49:15 -0400 Received: from mail-ob0-f177.google.com ([209.85.214.177]:36430 "EHLO mail-ob0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276AbcCNStN (ORCPT ); Mon, 14 Mar 2016 14:49:13 -0400 MIME-Version: 1.0 In-Reply-To: References: <20160314120202.GD15800@pd.tnic> From: Andy Lutomirski Date: Mon, 14 Mar 2016 11:48:47 -0700 Message-ID: Subject: Re: [PATCH v4 2/5] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops To: Linus Torvalds Cc: Paolo Bonzini , xen-devel , Arjan van de Ven , Borislav Petkov , X86 ML , Andrew Morton , KVM list , Andy Lutomirski , "linux-kernel@vger.kernel.org" , Peter Zijlstra Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 14, 2016 at 11:40 AM, Linus Torvalds wrote: > On Mon, Mar 14, 2016 at 11:24 AM, Andy Lutomirski wrote: >> >> The code in my queue is, literally: >> >> bool ex_handler_rdmsr_unsafe(const struct exception_table_entry *fixup, >> struct pt_regs *regs, int trapnr) >> { >> WARN_ONCE(1, "unchecked MSR access error: RDMSR from 0x%x", >> (unsigned int)regs->cx); >> >> /* Pretend that the read succeeded and returned 0. */ >> regs->ip = ex_fixup_addr(fixup); >> regs->ax = 0; >> regs->dx = 0; >> return true; >> } >> EXPORT_SYMBOL(ex_handler_rdmsr_unsafe); > > I guess I can live with this, as long as we also extend the > early-fault handling to work with the special exception handlers. OK, will do. I need to rewrork the early IDT code a bit so it generates a real pt_regs layout, but that's arguably a cleanup anyway. --Andy