From: Linus Torvalds <torvalds@linux-foundation.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: "the arch/x86 maintainers" <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@suse.de>,
Julien Thierry <jthierry@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 3/3] objtool: Add relocation check for alternative sections
Date: Mon, 10 Feb 2020 17:51:44 -0800 [thread overview]
Message-ID: <CAHk-=wgN0RtGNnYHjnaxtjO3BxL=t-nTUnEEwZu5J--BDhb95A@mail.gmail.com> (raw)
In-Reply-To: <7b90b68d093311e4e8f6b504a9e1c758fd7e0002.1581359535.git.jpoimboe@redhat.com>
On Mon, Feb 10, 2020 at 10:33 AM Josh Poimboeuf <jpoimboe@redhat.com> wrote:
>
> So disallow relocations in alternative code, except where the x86 arch
> code allows it.
LGTM. Did this actually find anything? And if not, did you verify that
it would by intentionally creating a bad alternative (perhaps the
broken one from my patch?)
Linus
next prev parent reply other threads:[~2020-02-11 1:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 18:32 [PATCH 0/3] objtool: Relocation sanity check for alternatives Josh Poimboeuf
2020-02-10 18:32 ` [PATCH 1/3] objtool: Fail the kernel build on fatal errors Josh Poimboeuf
2020-02-11 7:51 ` Julien Thierry
2020-02-11 12:47 ` [tip: core/objtool] " tip-bot2 for Josh Poimboeuf
2020-02-13 22:11 ` Josh Poimboeuf
2020-02-14 0:10 ` Thomas Gleixner
2020-02-14 17:57 ` Josh Poimboeuf
2020-02-19 22:43 ` Nick Desaulniers
2020-02-20 0:44 ` Philip Li
2020-02-20 19:09 ` Nick Desaulniers
2020-02-10 18:32 ` [PATCH 2/3] objtool: Add is_static_jump() helper Josh Poimboeuf
2020-02-11 7:52 ` Julien Thierry
2020-02-11 12:47 ` [tip: core/objtool] " tip-bot2 for Josh Poimboeuf
2020-02-10 18:32 ` [PATCH 3/3] objtool: Add relocation check for alternative sections Josh Poimboeuf
2020-02-11 1:51 ` Linus Torvalds [this message]
2020-02-11 8:47 ` Borislav Petkov
2020-02-11 8:16 ` Julien Thierry
2020-02-11 12:47 ` [tip: core/objtool] " tip-bot2 for Josh Poimboeuf
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='CAHk-=wgN0RtGNnYHjnaxtjO3BxL=t-nTUnEEwZu5J--BDhb95A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bp@suse.de \
--cc=jpoimboe@redhat.com \
--cc=jthierry@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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).