From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: "Fāng-ruì Sòng" <maskray@google.com>,
"Alexander Lobakin" <alexandr.lobakin@intel.com>,
linux-hardening@vger.kernel.org, x86@kernel.org,
"Borislav Petkov" <bp@alien8.de>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
"Kristen Carlson Accardi" <kristen@linux.intel.com>,
"Kees Cook" <keescook@chromium.org>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Tony Luck" <tony.luck@intel.com>,
"Bruce Schlobohm" <bruce.schlobohm@intel.com>,
"Jessica Yu" <jeyu@kernel.org>,
"kernel test robot" <lkp@intel.com>,
"Evgenii Shatokhin" <eshatokhin@virtuozzo.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Michal Marek" <michal.lkml@markovi.net>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Will Deacon" <will@kernel.org>, "Ingo Molnar" <mingo@redhat.com>,
"Christoph Hellwig" <hch@lst.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Nathan Chancellor" <nathan@kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Marios Pomonis" <pomonis@google.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
"Nicolas Pitre" <nico@fluxnic.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-arch@vger.kernel.org, live-patching@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v10 02/15] livepatch: avoid position-based search if `-z unique-symbol` is available
Date: Wed, 16 Feb 2022 12:01:20 -0800 [thread overview]
Message-ID: <20220216200120.djt6ijjenmcxmko6@treble> (raw)
In-Reply-To: <alpine.LSU.2.21.2202161606430.1475@pobox.suse.cz>
On Wed, Feb 16, 2022 at 04:15:20PM +0100, Miroslav Benes wrote:
> > > I subscribe to llvm@lists.linux.dev and happen to notice this message
> > > (can't keep up with the changes...)
> > > I am a bit concerned with this option and replied last time on
> > > https://lore.kernel.org/r/20220105032456.hs3od326sdl4zjv4@google.com
> > >
> > > My full reasoning is on
> > > https://maskray.me/blog/2020-11-15-explain-gnu-linker-options#z-unique-symbol
> >
> > Ah, right. Also discussed here:
> >
> > https://lore.kernel.org/all/20210123225928.z5hkmaw6qjs2gu5g@google.com/T/#u
> > https://lore.kernel.org/all/20210125172124.awabevkpvq4poqxf@treble/
> >
> > I'm not qualified to comment on LTO/PGO stability issues, but it doesn't
> > sound good. And we want to support livepatch for LTO kernels.
>
> Hm, bear with me, because I am very likely missing something which is
> clear to everyone else...
>
> Is the stability really a problem for the live patching (and I am talking
> about the live patching only here. It may be a problem elsewhere, but I am
> just trying to understand.)? I understand that two different kernel builds
> could have a different name mapping between the original symbols and their
> unique renames. Not nice. But we can prepare two different live patches
> for these two different kernels. Something one would like to avoid if
> possible, but it is not impossible. Am I missing something?
Maybe Fāng-ruì can clarify, but my understanding was that the stability
issue affects the kernel in general (particularly if LTO or PGO is
enabled) and isn't necessarily specific to livepatch itself.
--
Josh
next prev parent reply other threads:[~2022-02-16 20:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 18:57 [PATCH v10 00/15] Function Granular KASLR Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 01/15] modpost: fix removing numeric suffixes Alexander Lobakin
2022-05-03 0:57 ` Masahiro Yamada
2022-05-03 7:31 ` Petr Mladek
2022-05-23 18:04 ` Masahiro Yamada
2022-05-24 11:33 ` Alexander Lobakin
2022-05-24 13:40 ` Masahiro Yamada
2022-02-09 18:57 ` [PATCH v10 02/15] livepatch: avoid position-based search if `-z unique-symbol` is available Alexander Lobakin
2022-02-11 17:41 ` Josh Poimboeuf
2022-02-11 18:05 ` Fāng-ruì Sòng
2022-02-11 18:35 ` Josh Poimboeuf
2022-02-14 12:24 ` Alexander Lobakin
2022-02-14 18:10 ` Josh Poimboeuf
2022-02-16 20:32 ` Joe Lawrence
2022-02-16 22:13 ` Josh Poimboeuf
2022-02-16 15:15 ` Miroslav Benes
2022-02-16 20:01 ` Josh Poimboeuf [this message]
2022-02-18 16:31 ` Alexander Lobakin
2022-02-18 20:08 ` Josh Poimboeuf
2022-02-14 12:14 ` Alexander Lobakin
2022-02-14 18:57 ` Josh Poimboeuf
2022-02-16 15:06 ` Miroslav Benes
2022-02-16 19:57 ` Josh Poimboeuf
2022-02-17 7:45 ` Miroslav Benes
2022-02-09 18:57 ` [PATCH v10 03/15] kallsyms: randomize /proc/kallsyms output order Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 04/15] arch: introduce asm function sections Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 05/15] x86: support " Alexander Lobakin
2022-02-11 15:45 ` Peter Zijlstra
2022-02-14 11:49 ` Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 06/15] x86: decouple ORC table sorting into a separate file Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 07/15] Makefile: add config options and build scripts for FG-KASLR Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 08/15] x86/tools: Add relative relocs for randomized functions Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 09/15] x86: Add support for function granular KASLR Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 10/15] FG-KASLR: use a scripted approach to handle .text.* sections Alexander Lobakin
2022-02-11 15:37 ` Peter Zijlstra
2022-02-14 11:34 ` Alexander Lobakin
2022-02-14 11:59 ` Peter Zijlstra
2022-02-14 12:30 ` Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 11/15] x86/boot: allow FG-KASLR to be selected Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 12/15] module: add arch-indep FG-KASLR for randomizing function layout Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 13/15] module: use a scripted approach for FG-KASLR Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 14/15] Documentation: add documentation " Alexander Lobakin
2022-02-09 18:57 ` [PATCH v10 15/15] maintainers: add MAINTAINERS entry " Alexander Lobakin
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=20220216200120.djt6ijjenmcxmko6@treble \
--to=jpoimboe@redhat.com \
--cc=alexandr.lobakin@intel.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=bruce.schlobohm@intel.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=eshatokhin@virtuozzo.com \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@intel.com \
--cc=jeyu@kernel.org \
--cc=keescook@chromium.org \
--cc=kristen@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=miklos@szeredi.hu \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nico@fluxnic.net \
--cc=peterz@infradead.org \
--cc=pomonis@google.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).