From: Lars Wendler <wendler.lars@web.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: CONFIG_PAGE_TABLE_ISOLATION=y on x86_64 causes gcc to segfault when building x86_32 binaries
Date: Thu, 4 Jan 2018 00:22:32 +0100 [thread overview]
Message-ID: <20180104002232.7927cfc6@abudhabi.paradoxon.rec> (raw)
In-Reply-To: <20180103154008.7rd4moyd2f7t3wt5@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
Am Wed, 3 Jan 2018 16:40:08 +0100
schrieb Borislav Petkov <bp@alien8.de>:
> On Wed, Jan 03, 2018 at 02:30:36PM +0100, Lars Wendler wrote:
> > Same problem with 4.15-rc6. So I suppose that means it's a general
> > issue.
>
> So gentoo recently broke the kernel, see
>
> 3ce120b16cc5 ("kbuild: add '-fno-stack-check' to kernel build
> options")
>
> and you say you hit the same problem with -rc6 and that commit is in
> there so your kernel is probably built with -fno-stack-check.
>
> Just a stab in the dark though: if you build your hello world program
> with -fno-stack-check, does it segfault still?
>
> Thx.
>
The issue you mention here only affects Gentoo hardened installations
which I never used.
Kind regards
Lars
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-03 23:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180103123723.1dd26828@abudhabi.paradoxon.rec>
2018-01-03 11:57 ` CONFIG_PAGE_TABLE_ISOLATION=y on x86_64 causes gcc to segfault when building x86_32 binaries Thomas Gleixner
2018-01-03 12:05 ` Thomas Gleixner
2018-01-03 13:30 ` Lars Wendler
2018-01-03 15:21 ` Thomas Gleixner
2018-01-03 15:42 ` Dave Hansen
2018-01-03 18:52 ` Thomas Gleixner
2018-01-03 22:12 ` Laura Abbott
2018-01-03 22:14 ` Andy Lutomirski
2018-01-03 22:22 ` Thomas Gleixner
2018-01-03 23:43 ` Andy Lutomirski
2018-01-03 22:27 ` Dave Hansen
2018-01-03 22:25 ` [tip:x86/pti] x86/pti: Switch to kernel CR3 at early in entry_SYSCALL_compat() tip-bot for Thomas Gleixner
2018-01-03 23:46 ` CONFIG_PAGE_TABLE_ISOLATION=y on x86_64 causes gcc to segfault when building x86_32 binaries Lars Wendler
2018-01-04 2:44 ` Boris Ostrovsky
2018-01-03 15:40 ` Borislav Petkov
2018-01-03 23:22 ` Lars Wendler [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=20180104002232.7927cfc6@abudhabi.paradoxon.rec \
--to=wendler.lars@web.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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).