From: Florian Weimer <fweimer@redhat.com>
To: Alexander Popov <alex.popov@linux.com>
Cc: Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Tycho Andersen <tycho@tycho.ws>,
Laura Abbott <labbott@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Borislav Petkov <bp@alien8.de>,
Richard Sandiford <richard.sandiford@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Emese Revfy <re.emese@gmail.com>,
Thomas Garnier <thgarnie@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Steven Rostedt <rostedt@goodmis.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Will Deacon <will.deacon@arm.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
linux-arm-kernel@lists.infradead.org, gcc-bugs@gcc.gnu.org,
gcc-help@gcc.gnu.org
Subject: Re: Investigating a stack state mismatch in Linux kernel
Date: Thu, 15 Nov 2018 11:24:27 +0100 [thread overview]
Message-ID: <875zwyabac.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b7aad232-76e1-241f-00e2-77783ce30f87@linux.com> (Alexander Popov's message of "Wed, 14 Nov 2018 21:24:28 +0300")
* Alexander Popov:
> Of course, there is a naive solution for this issue -- just skip stackleak
> instrumentation for acpi_duplicate_processor_id(). But it would be great to find
> out the reasons behind this compiler behavior. It might help to create a better
> solution.
Please show us the RTL dumps with both compilers, both before and after
the plugin pass.
Thanks,
Florian
WARNING: multiple messages have this Message-ID (diff)
From: fweimer@redhat.com (Florian Weimer)
To: linux-arm-kernel@lists.infradead.org
Subject: Investigating a stack state mismatch in Linux kernel
Date: Thu, 15 Nov 2018 11:24:27 +0100 [thread overview]
Message-ID: <875zwyabac.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b7aad232-76e1-241f-00e2-77783ce30f87@linux.com> (Alexander Popov's message of "Wed, 14 Nov 2018 21:24:28 +0300")
* Alexander Popov:
> Of course, there is a naive solution for this issue -- just skip stackleak
> instrumentation for acpi_duplicate_processor_id(). But it would be great to find
> out the reasons behind this compiler behavior. It might help to create a better
> solution.
Please show us the RTL dumps with both compilers, both before and after
the plugin pass.
Thanks,
Florian
next prev parent reply other threads:[~2018-11-15 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 18:24 Investigating a stack state mismatch in Linux kernel Alexander Popov
2018-11-14 18:24 ` Alexander Popov
2018-11-15 10:24 ` Florian Weimer [this message]
2018-11-15 10:24 ` Florian Weimer
2018-11-15 20:51 ` Alexander Popov
2018-11-20 23:08 ` Alexander Popov
2018-11-20 23:08 ` Alexander Popov
2018-11-23 14:06 ` Alexander Monakov
2018-11-23 14:06 ` Alexander Monakov
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=875zwyabac.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=alex.popov@linux.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=re.emese@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=tycho@tycho.ws \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.