Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 297F5C05027 for ; Wed, 8 Feb 2023 06:57:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229879AbjBHG5J (ORCPT ); Wed, 8 Feb 2023 01:57:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229490AbjBHG5H (ORCPT ); Wed, 8 Feb 2023 01:57:07 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA8D0113C6 for ; Tue, 7 Feb 2023 22:57:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675839426; x=1707375426; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Paue5LGGuXlKFnksbvsnpvdQQOQrLPb711QKRAiuxEY=; b=O3PE0ITb6dWtlvpY0R1bxce+evAomBYIfjZg3QfjYC70rqNjXAX1Vfto j9Ppb/qhqHavXyc/142Ogrz15ZWawSDoENDYQ3xKy85UEY1OE/MCHf07y CP1quOKAx98yZ4MWLK8++fz/T3qddzXfKZFwJmZdVl9aDlD4TvqckPqqF yT+rA/nzOvOiKW/zyxC3otnDMwXpBLynCuazecZwtwnAUaVm1Ivr4Iv6T 6cIBmo/wnN1QVd87Vmf1ECmRuvE9iGK6qy39TEuMolGxLeGCvC6UlEn5S em6+Hy1zQj2rFUAQhTekdwV4NFnLzhqhdyZSBthiEKtyWtJsivIeoYck+ Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10614"; a="310078199" X-IronPort-AV: E=Sophos;i="5.97,280,1669104000"; d="scan'208";a="310078199" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Feb 2023 22:56:49 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10614"; a="660548264" X-IronPort-AV: E=Sophos;i="5.97,280,1669104000"; d="scan'208";a="660548264" Received: from tbacklun-mobl.amr.corp.intel.com (HELO [10.209.14.225]) ([10.209.14.225]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Feb 2023 22:56:49 -0800 Message-ID: Date: Tue, 7 Feb 2023 22:56:48 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH] x86/kprobes: Fix 1 byte conditional jump target Content-Language: en-US To: Nadav Amit Cc: "Masami Hiramatsu (Google)" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , X86 ML , kernel list , Peter Zijlstra References: <20230204210807.3930-1-namit@vmware.com> <20230207095424.42f4c0147f693a8cef25757c@kernel.org> <20230208002132.63b70cb9d6e5badad45fb828@kernel.org> <9fb39b3a-2edb-7fd3-2b7c-3a347478083f@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/7/23 22:34, Nadav Amit wrote: > As you said, I guess the change you and Masami proposed can be done on top of > this patch, which is (and was) only intended to fix the bug, and should > therefore go into 6.2. Nadav, To fix this issue, you proposed: p->ainsn.rel32 = *(s8 *)&insn->immediate.value; But, this is, um, rather obfuscated and potentially less correct compared to: p->ainsn.rel32 = insn->immediate.value; I'd appreciate it if you could update your patch to do this simpler thing and resend, unless there is a strong reason to do what you originally proposed.