From: Greg KH <gregkh@linuxfoundation.org>
To: Kirill Marinushkin <k.marinushkin@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/retpoline: Fix forcing me to update my compiler
Date: Sat, 8 Dec 2018 14:20:05 +0100 [thread overview]
Message-ID: <20181208132005.GA658@kroah.com> (raw)
In-Reply-To: <7d8aa04f-9611-fb69-b11c-21ebcf4580fd@gmail.com>
On Sat, Dec 08, 2018 at 02:14:47PM +0100, Kirill Marinushkin wrote:
> >> First problem: I cannot compile the kernel with my version of compiler
>
> >> Second problem: when I disable the feature - it cannot take effect,
> >> because the parse-time error happens before `syncconfig`
>
> On 12/08/18 13:42, Borislav Petkov wrote:
> > Does this help?
> >
> > https://git.kernel.org/tip/25896d073d8a0403b07e6dec56f58e6c33678207
> >
>
> The patch which you mentioned fixes the second problem: now I can disable
> CONFIG_RETPOLINE.
> But, the first problem is still here: with defconfig and gcc v6.4.0, kernel
> doesn't build, with this message:
>
> ~~~~
> $ make
> scripts/kconfig/conf --syncconfig Kconfig
> You are building kernel with non-retpoline compiler.
> Please update your compiler.
> make: *** [arch/x86/Makefile:311: checkbin] Error 1
> ~~~~
>
> I don't think that this is a proper behavior. I suggest to allow compilation
No, you asked for retpoline, and your compiler can not provide that, so
erroring out is the correct behavior. It is worse for you to have an
option enabled and it not being enabled just because your compiler does
not support it. That way you do not have the false sense of security.
thanks,
greg k-h
prev parent reply other threads:[~2018-12-08 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 12:38 [PATCH] x86/retpoline: Fix forcing me to update my compiler Kirill Marinushkin
2018-12-08 12:42 ` Borislav Petkov
2018-12-08 13:14 ` Kirill Marinushkin
2018-12-08 13:20 ` Greg KH [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=20181208132005.GA658@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=k.marinushkin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhenzhong.duan@oracle.com \
/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