From: Denis Kirjanov <kirjanov@gmail.com>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: CONFIG_CC_STACKPROTECTOR_STRONG
Date: Tue, 9 Jul 2019 20:46:17 +0300 [thread overview]
Message-ID: <CAHj3AVmPkVuntnPjg5mseioBPT7KuBTT_HHmUsQyR04aANGz8w@mail.gmail.com> (raw)
In-Reply-To: <CAHhAz+gSnj8O+sM-939EqLvj_HL0BSQF4C452kn-GBxhyXODmw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1957 bytes --]
On Tuesday, July 9, 2019, Muni Sekhar <munisekharrms@gmail.com> wrote:
> On Tue, Jul 9, 2019 at 10:56 PM Denis Kirjanov <kirjanov@gmail.com> wrote:
> >
> >
> >
> > On Tuesday, July 9, 2019, Muni Sekhar <munisekharrms@gmail.com> wrote:
> >>
> >> Hi All,
> >>
> >>
> >> My Kernel is built with the following options:
> >>
> >>
> >>
> >> CONFIG_CC_STACKPROTECTOR=y
> >>
> >> CONFIG_CC_STACKPROTECTOR_STRONG=y
> >>
> >>
> >>
> >>
> >>
> >> We use out-of-tree kernel modules in our project and I need to measure
> the performance of it by using a bit older gcc version 4.8.5.
> >>
> >>
> >>
> >> I can build the modules with gcc above 5 version, but when I try to use
> gcc version 4.8.5 I’m getting the following error:
> >>
> >>
> >>
> >> Makefile:693: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:
> -fstack-protector-strong not supported by compiler
> >>
> >>
> >>
> >> So it looks like gcc 4.8.5 does not support CONFIG_CC_STACKPROTECTOR_STRONG
> option, but how to instruct gcc to ignore this one?
> >>
> >>
> >>
> >> In runtime, is it possible to instruct kernel to ignore
> “CONFIG_CC_STACKPROTECTOR_STRONG=y” (without building the kernel) by
> using sysctl or any other method?
> >>
> >>
> >
> >
> > Just disable it in your .config file
>
> I disabled in /lib/modules/$(uname -r)/build/.config, but still get
> that error. Does kernel needs to be recompiled?
>
> CONFIG_CC_STACKPROTECTOR=y
> # CONFIG_CC_STACKPROTECTOR_NONE is not set
> # CONFIG_CC_STACKPROTECTOR_REGULAR is not set
> # CONFIG_CC_STACKPROTECTOR_STRONG is not set
>
>
You have to disable it in your kernel source directory
and then run ‘make oldconfig’
> >
> >
> >>
> >> Any help is appreciated.
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Sekhar
> >
> >
> >
> > --
> > Regards / Mit besten Grüßen,
> > Denis
> >
>
>
> --
> Thanks,
> Sekhar
>
--
Regards / Mit besten Grüßen,
Denis
[-- Attachment #1.2: Type: text/html, Size: 2860 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-07-09 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 17:24 CONFIG_CC_STACKPROTECTOR_STRONG Muni Sekhar
2019-07-09 17:26 ` CONFIG_CC_STACKPROTECTOR_STRONG Denis Kirjanov
2019-07-09 17:32 ` CONFIG_CC_STACKPROTECTOR_STRONG Muni Sekhar
2019-07-09 17:46 ` Denis Kirjanov [this message]
2019-07-09 18:04 ` CONFIG_CC_STACKPROTECTOR_STRONG Muni Sekhar
2019-07-09 19:58 ` CONFIG_CC_STACKPROTECTOR_STRONG Greg KH
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=CAHj3AVmPkVuntnPjg5mseioBPT7KuBTT_HHmUsQyR04aANGz8w@mail.gmail.com \
--to=kirjanov@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=munisekharrms@gmail.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;
as well as URLs for NNTP newsgroup(s).