From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: X86 ML <x86@kernel.org>, Kees Cook <kees@kernel.org>,
alyssa.milburn@intel.com, scott.d.constable@intel.com,
Joao Moreira <joao@overdrivepizza.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Sami Tolvanen <samitolvanen@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
ojeda@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86,ibt: Use UDB instead of 0xEA
Date: Tue, 28 Oct 2025 11:55:57 -0700 [thread overview]
Message-ID: <7623dfcf-f6ed-4caf-bb60-7fa953f0778c@zytor.com> (raw)
In-Reply-To: <CAADnVQKns0xLA+oEdgF-gZ9W=pqjkL2h2OcUQxH+CvJ=vVL-0A@mail.gmail.com>
On 2025-09-02 12:37, Alexei Starovoitov wrote:
>
> I suspect that 'reserved' opcode will not be used any time soon.
> If 10 years from now the opcode is used in some future CPU that CPU
> is better to be not vulnerable and CFI, FineIBT things will be
> gone from the kernel by then.
> So I would do absolutely nothing and just ignore the lack of blessing.
>
What makes you say that? *Please* don't make these kinds of assumptions -- it
causes massive headaches for both us chip makers and for users.
-hpa
prev parent reply other threads:[~2025-10-28 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 19:13 Peter Zijlstra
2025-09-02 8:19 ` Peter Zijlstra
2025-09-02 10:46 ` Peter Zijlstra
2025-09-02 16:04 ` Alexei Starovoitov
2025-09-02 19:26 ` Peter Zijlstra
2025-09-02 19:37 ` Alexei Starovoitov
2025-09-02 19:57 ` Peter Zijlstra
2025-10-28 18:55 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7623dfcf-f6ed-4caf-bb60-7fa953f0778c@zytor.com \
--to=hpa@zytor.com \
--cc=alexei.starovoitov@gmail.com \
--cc=alyssa.milburn@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=joao@overdrivepizza.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=scott.d.constable@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®