From: Greg KH <gregkh@linuxfoundation.org>
To: "Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dwmw@amazon.co.uk" <dwmw@amazon.co.uk>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
Andi Kleen <ak@linux.intel.com>,
"jeyu@kernel.org" <jeyu@kernel.org>
Subject: Re: [PATCH] retpoline/module: Taint kernel for missing retpoline in module
Date: Sat, 13 Jan 2018 16:37:57 +0100 [thread overview]
Message-ID: <20180113153757.GB25956@kroah.com> (raw)
In-Reply-To: <0575AF4FD06DD142AD198903C74E1CC87A5C9013@FMSMSX151.amr.corp.intel.com>
On Sat, Jan 13, 2018 at 02:38:51PM +0000, Van De Ven, Arjan wrote:
> > > When the a module hasn't been compiled with a retpoline
> > > aware compiler, print a warning and set a taint flag.
> >
> > Isn't that caught by the "build with a different compiler/version" check
> > that we have? Or used to have? If not, can't we just make it into that
> > type of check to catch this type of problem no matter what type of
> > feature/option it is trying to catch?
>
>
> making retpoline part of the modversion hash thingy could make sense.
>
> but I kinda feel this is a bit overkill; it's not a function issue if
> you get this wrong, and if you run an ancient or weird out of tree
> module there's a real chance you have other security fun as well ;-)
Sure, but take pity on the crazy distro developers who have to support
crap like this. They really want to know if a module is built
differently from the kernel, to force the user to know they are on their
own.
modversion seems like a trivial thing to mix this into, and solves the
distro issue at the same time.
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-13 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 17:55 [PATCH] retpoline/module: Taint kernel for missing retpoline in module Andi Kleen
2018-01-12 19:01 ` David Woodhouse
2018-01-12 19:17 ` Andi Kleen
2018-01-13 14:12 ` Greg KH
2018-01-13 14:38 ` Van De Ven, Arjan
2018-01-13 15:37 ` Greg KH [this message]
2018-01-13 14:53 ` Andi Kleen
2018-01-13 15:36 ` Greg KH
2018-01-13 18:20 ` Andi Kleen
2018-01-16 20:08 ` Andi Kleen
2018-01-15 12:47 ` David Laight
2018-01-15 12:53 ` Van De Ven, Arjan
2018-01-15 13:01 ` David Woodhouse
2018-01-15 14:08 ` David Laight
2018-01-15 16:48 ` Andi Kleen
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=20180113153757.GB25956@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=arjan.van.de.ven@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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