From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-hardening@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: rebuild GCC plugins when the compiler is upgraded
Date: Thu, 4 Mar 2021 20:25:00 -0600 [thread overview]
Message-ID: <20210305022500.cyi3cfwgt2t6mona@treble> (raw)
In-Reply-To: <CAHk-=wj6t2i1BgmWP1Zb2WVF3zZzkHvsxsALJk7VpfKm6UgLcw@mail.gmail.com>
On Thu, Mar 04, 2021 at 03:37:14PM -0800, Linus Torvalds wrote:
> On Thu, Mar 4, 2021 at 3:20 PM Kees Cook <keescook@chromium.org> wrote:
> >
> > This seems fine to me, but I want to make sure Josh has somewhere to
> > actually go with this. Josh, does this get you any closer?
No, this doesn't seem to help me at all.
> > It sounds like the plugins need to move to another location for
> > packaged kernels?
>
> Well, it might be worth extending the stuff that gets installed with
> /lib/modules/<kernel-version>/ with enough information and
> infrastruvcture to then build any external modules.
The gcc plugins live in scripts/, which get installed by "make
modules_install" already. So the plugins' source and makefiles are in
/lib/modules/<kernel-version>/build/scripts/gcc-plugins.
So everything needed for building the plugins is already there. We just
need the kernel makefiles to rebuild the plugins locally, when building
an external module.
--
Josh
next prev parent reply other threads:[~2021-03-05 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 11:37 Masahiro Yamada
2021-03-04 23:20 ` Kees Cook
2021-03-04 23:37 ` Linus Torvalds
2021-03-05 2:25 ` Josh Poimboeuf [this message]
2021-03-06 1:28 ` Josh Poimboeuf
2021-03-06 2:18 ` Masahiro Yamada
2021-03-06 2:50 ` Josh Poimboeuf
2021-03-09 20:31 ` Josh Poimboeuf
2021-03-10 13:44 ` Masahiro Yamada
2021-03-18 17:57 ` 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=20210305022500.cyi3cfwgt2t6mona@treble \
--to=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=torvalds@linux-foundation.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®