Received: by 2002:a05:6358:4e97:b0:b3:742d:4702 with SMTP id ce23csp2267613rwb; Mon, 15 Aug 2022 02:03:23 -0700 (PDT) X-Google-Smtp-Source: AA6agR7sl8T8IjwFRw1eXpOs8a93iwR5hLOXM/BuCDaiEsR29dzTmIMcI3LpQo+cwIrE2sze3L7W X-Received: by 2002:a17:907:781a:b0:730:ccea:7c29 with SMTP id la26-20020a170907781a00b00730ccea7c29mr9945394ejc.85.1660554203298; Mon, 15 Aug 2022 02:03:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1660554203; cv=none; d=google.com; s=arc-20160816; b=O6nh+rnk3jg6EgJTkiIO35WhsDuMhqy5JurOKAeCrWhzs4fcUFBGAMpM7TCtaXaPEd hT7BQJSbDkdaEtdxgD85vtYR1BZyfywCOKRR4r1tkh5RUnCe+LWVC6qZBdJRRD9NwGCL rv5UysOh7IkdjJ9kukp7wYSxyFcGPoTthqQmRUJOy1RZzFiZl2hfvCaeVnofsYzLu5VM LWffzieOEUkKjxFKbX5axDl8RfhXvWNHOR9T1huO0pdm4a6Sqgd1PHS5m4b8mMtXC5dZ ReCwbW3GVB6Oi8oAw42sEtOSiT2imSfts5oSch9/pvMzqJwS1FJyH/Y+skDaMLcQrqdu G0Ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:robot-unsubscribe :robot-id:message-id:mime-version:references:in-reply-to:cc:subject :to:reply-to:sender:from:dkim-signature:dkim-signature:date; bh=IQWaK8qY9Rujxh5W8uD3V8R2QS0vMhGEuhjPCTuRwls=; b=nR3w+igdIIFG/V04MWMenVzlj9F0iCIUGO8LVCHcfLJS/MFPS44rGqcVZu7O54r8OC ekpwwpeppYZtm9PozIRNxg9ewML4dcuKO2LPtOmAdn0RoFECYdj0/wLK3LhS/FPniI19 zkDPcPhZoSNOy5uA83yO1d9acyaC5wIbJtdVSj4siXf0WuCKgscwW9G4jbrd2hgdw//y wf7KttCu6+ewAw9cOg5/RRsaJyBF+uLiW0vCxJKvRg+pY4PwnUEwsYxKk6usW0ZX/p0l hMtNydU21Qiuu2eFa/WJvMlUbYTxnedJvxoGaqoHCe0kYDT28m0D9zivdaPphq0qqbPX HP5A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=CFnq38Jv; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w18-20020a056402269200b0043e1c8b6187si8653438edd.1.2022.08.15.02.02.58; Mon, 15 Aug 2022 02:03:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=CFnq38Jv; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231737AbiHOIsU (ORCPT + 99 others); Mon, 15 Aug 2022 04:48:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41152 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229740AbiHOIsT (ORCPT ); Mon, 15 Aug 2022 04:48:19 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F420201BD; Mon, 15 Aug 2022 01:48:18 -0700 (PDT) Date: Mon, 15 Aug 2022 08:48:14 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1660553295; h=from:from:sender:sender:reply-to: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=IQWaK8qY9Rujxh5W8uD3V8R2QS0vMhGEuhjPCTuRwls=; b=CFnq38Jv4Tv7DdZXatgSSbvmXgToh6MDdUX2c12W0K20KA+khqiM9npOUq532h9tUywYQe SaLXjHFKahEsvLHs/bylDHaZUc1NB5P9Sm8xFZf4COkFck2Hcmn0/5e4KPNAwUpvccDOfd 2mnj1fE+S0UkDTRXZFtge/EkxULjjvtEBv2OAMWK3GHXg9wNnX4IlbwVTvHqGJ7Y5zyfUn B1z0ZZatqB5+uMJQVIIIHP9BcD0rJLWu2QrlYv2sj7rYR9+S6kK3jdSqYCTnnW0cYmJnbz nyG8ExWyzNDHsdm550Jr4sdumT6Y2JIKU7Dm2V54FkwUY8PXeO6M1PwDUje1Yw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1660553295; h=from:from:sender:sender:reply-to: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=IQWaK8qY9Rujxh5W8uD3V8R2QS0vMhGEuhjPCTuRwls=; b=Uimj+IhKe/i5RBJFtwJv1o1V+LRKQs2OnOwtNmReyYwZsG5m8KukOKlTRXz9gAOx8//7iq 0oXBlCVtGFCsTICg== From: "tip-bot2 for Nadav Amit" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: perf/urgent] x86/kprobes: Fix JNG/JNLE emulation Cc: Nadav Amit , Ingo Molnar , stable@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20220813225943.143767-1-namit@vmware.com> References: <20220813225943.143767-1-namit@vmware.com> MIME-Version: 1.0 Message-ID: <166055329407.401.4288744100235226056.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following commit has been merged into the perf/urgent branch of tip: Commit-ID: 8924779df820c53875abaeb10c648e9cb75b46d4 Gitweb: https://git.kernel.org/tip/8924779df820c53875abaeb10c648e9cb75b46d4 Author: Nadav Amit AuthorDate: Sat, 13 Aug 2022 15:59:43 -07:00 Committer: Ingo Molnar CommitterDate: Sun, 14 Aug 2022 11:27:17 +02:00 x86/kprobes: Fix JNG/JNLE emulation When kprobes emulates JNG/JNLE instructions on x86 it uses the wrong condition. For JNG (opcode: 0F 8E), according to Intel SDM, the jump is performed if (ZF == 1 or SF != OF). However the kernel emulation currently uses 'and' instead of 'or'. As a result, setting a kprobe on JNG/JNLE might cause the kernel to behave incorrectly whenever the kprobe is hit. Fix by changing the 'and' to 'or'. Fixes: 6256e668b7af ("x86/kprobes: Use int3 instead of debug trap for single-step") Signed-off-by: Nadav Amit Signed-off-by: Ingo Molnar Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20220813225943.143767-1-namit@vmware.com --- arch/x86/kernel/kprobes/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c index 74167dc..4c3c27b 100644 --- a/arch/x86/kernel/kprobes/core.c +++ b/arch/x86/kernel/kprobes/core.c @@ -505,7 +505,7 @@ static void kprobe_emulate_jcc(struct kprobe *p, struct pt_regs *regs) match = ((regs->flags & X86_EFLAGS_SF) >> X86_EFLAGS_SF_BIT) ^ ((regs->flags & X86_EFLAGS_OF) >> X86_EFLAGS_OF_BIT); if (p->ainsn.jcc.type >= 0xe) - match = match && (regs->flags & X86_EFLAGS_ZF); + match = match || (regs->flags & X86_EFLAGS_ZF); } __kprobe_emulate_jmp(p, regs, (match && !invert) || (!match && invert)); }