From: "Martin Liška" <mliska@suse.cz>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Miguel Ojeda <ojeda@kernel.org>,
Lai Jiangshan <laijs@linux.alibaba.com>,
Joerg Roedel <jroedel@suse.de>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Arvind Sankar <nivedita@alum.mit.edu>,
Chester Lin <clin@suse.com>, Juergen Gross <jgross@suse.com>,
andrew.cooper3@citrix.com, linux-toolchains@vger.kernel.org
Subject: Re: [PATCH 02/24] x86/traps: Move arch/x86/kernel/traps.c to arch/x86/entry/
Date: Wed, 8 Sep 2021 09:33:37 +0200 [thread overview]
Message-ID: <124a19ef-0b50-2cf2-c6cc-12f443706883@suse.cz> (raw)
In-Reply-To: <CAKwvOd=HfA-08N6LqCS54QcYBcuRgqjcuhVk0dioEte_DxqVqg@mail.gmail.com>
On 9/7/21 23:12, Nick Desaulniers wrote:
> On Fri, Sep 3, 2021 at 12:36 AM Martin Liška <mliska@suse.cz> wrote:
>>
>> On 9/2/21 19:05, Nick Desaulniers wrote:
>>> IIRC GCC only
>>> added the attribute recently in the 10.X release, so it might be too
>>> new to rely on quite yet.
>>
>> The no_stack_protector attribute was actually added in the GCC 11.x release:
>> https://gcc.gnu.org/gcc-11/changes.html
>
> Ah right, that lays more weight though that this feature is still too
> new to rely on quite yet.
Sure.
> Martin, do you know if what happens with
> regards to inlining when the callee and caller mismatch on this
> function attribute in GCC? This is very much a problem for the
> kernel.
That's a know issue that was already discusses both in a Kernel mailing and
GCC bugzilla:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94722#c9
Martin
>
>> Note the compiler is definitely used by Fedora, openSUSE Tumbleweed
>> and other cutting edge distributions.
>
> Kernel supports GCC 4.9+ currently. This feature can only be emulated
> with the coarse grain -fno-stack-protector (or gnu_inline with out of
> line assembler definition...:( ).
>
prev parent reply other threads:[~2021-09-08 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210831175025.27570-1-jiangshanlai@gmail.com>
[not found] ` <20210831175025.27570-3-jiangshanlai@gmail.com>
[not found] ` <YTCGov+vvAMvso7q@suse.de>
[not found] ` <1f327579-e62a-df65-0763-e88243829db3@linux.alibaba.com>
[not found] ` <YTCsWpSmPYvXa1xz@hirez.programming.kicks-ass.net>
[not found] ` <4c589fef-8c98-a6fc-693f-b205a7710e42@linux.alibaba.com>
[not found] ` <YTC+FTo4uLLdyBxA@hirez.programming.kicks-ass.net>
[not found] ` <YTDS/p/bnsTFzNES@hirez.programming.kicks-ass.net>
2021-09-02 17:05 ` [PATCH 02/24] x86/traps: Move arch/x86/kernel/traps.c to arch/x86/entry/ Nick Desaulniers
2021-09-02 17:19 ` Miguel Ojeda
2021-09-02 17:23 ` Nick Desaulniers
2021-09-03 7:36 ` Martin Liška
2021-09-07 21:12 ` Nick Desaulniers
2021-09-08 7:33 ` Martin Liška [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=124a19ef-0b50-2cf2-c6cc-12f443706883@suse.cz \
--to=mliska@suse.cz \
--cc=andrew.cooper3@citrix.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=bristot@redhat.com \
--cc=clin@suse.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jiangshanlai@gmail.com \
--cc=jroedel@suse.de \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=ndesaulniers@google.com \
--cc=nivedita@alum.mit.edu \
--cc=ojeda@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).