From: Arvind Sankar <nivedita@alum.mit.edu>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: Linux 5.8-rc1
Date: Tue, 16 Jun 2020 18:28:19 -0400 [thread overview]
Message-ID: <20200616222819.GA1977632@rani.riverdale.lan> (raw)
In-Reply-To: <CAEJqkgij-_Z1S-F=ooHr=OYcE8biHr1Z-RGgOzHpC7Y0wm7BhA@mail.gmail.com>
On Wed, Jun 17, 2020 at 12:00:14AM +0200, Gabriel C wrote:
> Am Di., 16. Juni 2020 um 23:25 Uhr schrieb Arvind Sankar
> <nivedita@alum.mit.edu>:
> >
> > On Tue, Jun 16, 2020 at 11:17:08PM +0200, Gabriel C wrote:
> > > Am Di., 16. Juni 2020 um 22:33 Uhr schrieb Arvind Sankar
> > > <nivedita@alum.mit.edu>:
> > > >
> > > > Can you attach the output of gcc -dumpspecs and gcc -v? I suspect your
> > > > compiler enables stack protector by default. My distro compiler does
> > > > that too, but not if -ffreestanding is enabled (which it is for the
> > > > purgatory).
> > > >
> > >
> > > Files including config uploaded to there:
> > >
> > > http://crazy.dev.frugalware.org/kernel/
> > >
> >
> > Yeah, your gcc doesn't have the -ffreestanding handling. Mine (from
> > gentoo) has this in the -dumpspecs output:
> >
> > *cc1_options:
> > ... %{nostdlib|nodefaultlibs|ffreestanding:-fno-stack-protector} ...
> >
> > to switch off the default ssp when the standard libraries aren't available.
>
> I wondered what they enable to do that. it turns out it is a custom patch.
> While I think having that is not bad, such patches lead to bugs like this one.
Right. Debian also has a similar custom patch to adjust the specs. It
would probably be better if something were upstreamed :)
next prev parent reply other threads:[~2020-06-16 22:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 20:44 Linux 5.8-rc1 Linus Torvalds
2020-06-15 1:59 ` linux-next: stats (Was: Linux 5.8-rc1) Stephen Rothwell
2020-06-16 20:11 ` Linux 5.8-rc1 Gabriel C
2020-06-16 20:33 ` Arvind Sankar
2020-06-16 21:17 ` Gabriel C
2020-06-16 21:25 ` Arvind Sankar
2020-06-16 22:00 ` Gabriel C
2020-06-16 22:28 ` Arvind Sankar [this message]
2020-06-16 21:35 ` Gabriel C
2020-06-16 22:25 ` [PATCH] x86/purgatory: Add -fno-stack-protector Arvind Sankar
2020-06-17 0:06 ` Linus Torvalds
2020-06-16 20:37 ` Linux 5.8-rc1 Borislav Petkov
2020-06-16 21:19 ` Gabriel C
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=20200616222819.GA1977632@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).