Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2372044ybt; Tue, 16 Jun 2020 04:30:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwUWoseazN/3Zzvv5OtBddyN/lJfa3+c9dKvcqfspj478FGzmc8Tc02dKaiRP6fzagclafL X-Received: by 2002:a05:6402:6d6:: with SMTP id n22mr2199727edy.362.1592307052988; Tue, 16 Jun 2020 04:30:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592307052; cv=none; d=google.com; s=arc-20160816; b=pbv55u/I0sG9RxFt3poypYUYjmVnu6ErdXGNRvZLkeZDDXuCBD6KrShSjdwsqgWo+m esn59At7WpDrTUg5arhnEfCR39dzVJsvHaUiNHjbvamr12/Nz5+7HpkQh0TX4JA0tuu2 YRpmFWx59cXRwl+SyrC1SB/vOwXcvLGyyK4X7ZnymiNCGLpwzcCK97wN5lpq4ugNlLnI cPSxswchxYZQG9T3pELTnwBtV8WnH2QwbRxD/hgzsPHxU0+bU2C009YoOtzEO5ecUWVA /8TaxaFZKDFOHGE2dS/b0tbc6vrTXMu3fZJabaKUjRAYXW3MpjTDjwYUuBuIEdYEYV2a Ac+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=8XrojXvGsQrzvO/Ri1rEyqqDQsXzc/MuTUzoBCmek2U=; b=P9OaXILU9XXCH6ZTgbLMvaJFcvGoG8vv8WBIzsy1T/lLbkpY2jAF7a0T+DrC6/u6uy 9DG7LZSigCZZun1pOL7N3RtYrUijHfffUEPqCc01j41yKosPA0bPsmmfg3Jbxe+NhsO9 Cf2yVni5iwGTqm5tCuoUoYPvflcdEtltzcKt4oOCMpgB+YGWEGzYKsJu4hesNpftovKw CA03zdgiPJmbos3DX78XILV89WJSBbWO9pPnSFd1LsPyo9+gp+Nlg7JIw/jqU+SZA3v+ YkX0kN4/jGxTM6+w4Anj3upOOYfjrR4s6vF8oMU0EttjlbWwl0xBnrFppJ6Z1HPQWLN/ b1Ug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=agRdMFas; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y16si10594539edw.311.2020.06.16.04.30.29; Tue, 16 Jun 2020 04:30:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=agRdMFas; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728496AbgFPL2k (ORCPT + 99 others); Tue, 16 Jun 2020 07:28:40 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:31347 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728176AbgFPL2k (ORCPT ); Tue, 16 Jun 2020 07:28:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592306918; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8XrojXvGsQrzvO/Ri1rEyqqDQsXzc/MuTUzoBCmek2U=; b=agRdMFaspM9Nwa54S/L6hn5jNs9/RrbGaKFjSlzSF9gePzO7yBMQhhNlM8LvrxfmipCVxU MNQVfVpEUqtUdmv7+bWbMr2ijVu3jZ+MzbvA89Nnz7zTJusOaOfo0iizK0sxyLAaLG2NUW NShuqMXBWC8dSV0sdLwoXXMHB+O/lNI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-132-Ivfosb3VPqqUSd4F1p0T2w-1; Tue, 16 Jun 2020 07:28:35 -0400 X-MC-Unique: Ivfosb3VPqqUSd4F1p0T2w-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5DF3E835B5A; Tue, 16 Jun 2020 11:28:33 +0000 (UTC) Received: from prarit.bos.redhat.com (prarit-guest.7a2m.lab.eng.bos.redhat.com [10.16.222.26]) by smtp.corp.redhat.com (Postfix) with ESMTP id F32C378F0F; Tue, 16 Jun 2020 11:28:31 +0000 (UTC) Subject: Re: [PATCH v4] x86/split_lock: Sanitize userspace and guest error output To: linux-kernel@vger.kernel.org Cc: Sean Christopherson , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H. Peter Anvin" , Tony Luck , "Peter Zijlstra (Intel)" , Rahul Tanwar , Xiaoyao Li , Ricardo Neri , Dave Hansen References: <20200616112702.1703-1-prarit@redhat.com> From: Prarit Bhargava Message-ID: Date: Tue, 16 Jun 2020 07:28:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20200616112702.1703-1-prarit@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This was sent in error. Sorry, P. On 6/16/20 7:27 AM, Prarit Bhargava wrote: > There are two problems with kernel messages in fatal mode that were found > during testing of guests and userspace programs. > > The first is that no kernel message is output when the split lock detector > is triggered with a userspace program. As a result the userspace process > dies from receiving SIGBUS with no indication to the user of what caused > the process to die. > > The second problem is that only the first triggering guest causes a kernel > message to be output because the message is output with pr_warn_once(). > This also results in a loss of information to the user. > > While fixing these I noticed that the same message was being output > three times so I'm cleaning that up too. > > Fix fatal mode output, and use consistent messages for fatal and > warn modes for both userspace and guests. > > Co-developed-by: Sean Christopherson > Signed-off-by: Sean Christopherson > Cc: Thomas Gleixner > Cc: Ingo Molnar > Cc: Borislav Petkov > Cc: x86@kernel.org > Cc: "H. Peter Anvin" > Cc: Tony Luck > Cc: "Peter Zijlstra (Intel)" > Cc: Sean Christopherson > Cc: Rahul Tanwar > Cc: Xiaoyao Li > Cc: Ricardo Neri > Cc: Dave Hansen > --- > v2: Do not output a message if CPL 3 Alignment Check is turned on (xiaoyao.li) > v3: refactor code (sean.j.christopherson) > v4: Fix Sign off (sean.j.christopherson) > > arch/x86/kernel/cpu/intel.c | 22 ++++++++++------------ > 1 file changed, 10 insertions(+), 12 deletions(-) > > diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c > index 63926c94eb5f..3a373f0be674 100644 > --- a/arch/x86/kernel/cpu/intel.c > +++ b/arch/x86/kernel/cpu/intel.c > @@ -1074,11 +1074,14 @@ static void split_lock_init(void) > split_lock_verify_msr(sld_state != sld_off); > } > > -static void split_lock_warn(unsigned long ip) > +static bool handle_split_lock(unsigned long ip) > { > - pr_warn_ratelimited("#AC: %s/%d took a split_lock trap at address: 0x%lx\n", > + pr_warn("#AC: %s/%d took a split_lock trap at address: 0x%lx\n", > current->comm, current->pid, ip); > > + if (sld_state != sld_warn) > + return false; > + > /* > * Disable the split lock detection for this task so it can make > * progress and set TIF_SLD so the detection is re-enabled via > @@ -1086,18 +1089,13 @@ static void split_lock_warn(unsigned long ip) > */ > sld_update_msr(false); > set_tsk_thread_flag(current, TIF_SLD); > + return true; > } > > bool handle_guest_split_lock(unsigned long ip) > { > - if (sld_state == sld_warn) { > - split_lock_warn(ip); > + if (handle_split_lock(ip)) > return true; > - } > - > - pr_warn_once("#AC: %s/%d %s split_lock trap at address: 0x%lx\n", > - current->comm, current->pid, > - sld_state == sld_fatal ? "fatal" : "bogus", ip); > > current->thread.error_code = 0; > current->thread.trap_nr = X86_TRAP_AC; > @@ -1108,10 +1106,10 @@ EXPORT_SYMBOL_GPL(handle_guest_split_lock); > > bool handle_user_split_lock(struct pt_regs *regs, long error_code) > { > - if ((regs->flags & X86_EFLAGS_AC) || sld_state == sld_fatal) > + if (regs->flags & X86_EFLAGS_AC) > return false; > - split_lock_warn(regs->ip); > - return true; > + > + return handle_split_lock(regs->ip); > } > > /* >