From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753040AbeAJVFM (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Wed, 10 Jan 2018 16:05:12 -0500
Received: from mail-it0-f50.google.com ([209.85.214.50]:36545 "EHLO
        mail-it0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752970AbeAJVFK (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 10 Jan 2018 16:05:10 -0500
X-Google-Smtp-Source: ACJfBotyodG95lE8KuIA4N1qiWiMGglcL5PwtiGmbKA9WpURYndiqhxalFSVtP35ooVGUVTlt5Wyq6SWGIkMR7Z4hNk=
MIME-Version: 1.0
In-Reply-To: <20180110205544.k2e534nkk27lkpjc@pd.tnic>
References: <20180110003139.10531-1-andi@firstfloor.org> <CA+55aFzyVFEUKaLpqxfwh5E9QFgMjzr+wVoYGxqTHVDkGcFkOw@mail.gmail.com>
 <1515568506.22302.72.camel@infradead.org> <1515578735.22302.91.camel@infradead.org>
 <20180110112815.mgciyf5acwacphkq@pd.tnic> <CA+55aFz=yU7Q87ooyokssaFEGBx8BL+Vzs=4z+OOzvg-K5tfbA@mail.gmail.com>
 <alpine.DEB.2.20.1801102053120.1919@nanos> <20180110201532.5jnji6ypfl6slzvb@treble>
 <CA+55aFzMzBwtfO1e=eC6oCx9mMMXPoRko0FvKKJrriUGqyQtEg@mail.gmail.com> <20180110205544.k2e534nkk27lkpjc@pd.tnic>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed, 10 Jan 2018 13:05:08 -0800
X-Google-Sender-Auth: TABKvBcVm5dhlpPdZJLkD9Yk5Kg
Message-ID: <CA+55aFykL6+9kJjP2J-y3D7h7s3KhASVJ_cULa12zk5o37=OsA@mail.gmail.com>
Subject: Re: [PATCH] x86/alternatives: Fix optimize_nops() checking
To: Borislav Petkov <bp@alien8.de>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        David Woodhouse <dwmw2@infradead.org>,
        Andi Kleen <andi@firstfloor.org>,
        "the arch/x86 maintainers" <x86@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Paul Turner <pjt@google.com>,
        Andrew Lutomirski <luto@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Tom Lendacky <thomas.lendacky@amd.com>,
        Tim Chen <tim.c.chen@linux.intel.com>,
        Greg Kroah-Hartman <gregkh@linux-foundation.org>,
        Dave Hansen <dave.hansen@intel.com>,
        Jiri Kosina <jikos@kernel.org>, Andi Kleen <ak@linux.intel.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

On Wed, Jan 10, 2018 at 12:55 PM, Borislav Petkov <bp@alien8.de> wrote:
>
> Ok, so the problem was: how to fixup jumps which are not the first
> instruction which is being replaced but a following one in the
> instruction bytes with which we replace.

What jumps do you have that need to be fixed up?

I really think we should avoid having things like that.

Any jumps *within* the alternatives should have been handled by the
assembler already.

And jumps between the alternatives and other places? Why do they exist?

            Linus