From: Hans de Goede <hdegoede@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] x86/purgatory: Disable various profiling and sanitizing options
Date: Tue, 17 Mar 2020 14:08:38 +0100 [thread overview]
Message-ID: <aee4ff4d-05f0-9d55-eb19-1d8df520e6c9@redhat.com> (raw)
In-Reply-To: <20200313182815.GF8142@zn.tnic>
Hi,
On 3/13/20 7:28 PM, Borislav Petkov wrote:
> On Thu, Mar 12, 2020 at 12:49:50PM +0100, Hans de Goede wrote:
>> Since the purgatory is a special stand-alone binary, we need to disable
>
> Pls use passive voice in your commit message: no "we" or "I", etc, and
> describe your changes in imperative mood.
>
> Also, pls read section "2) Describe your changes" in
> Documentation/process/submitting-patches.rst for more details.
Ok, fixed for v6 and I've also rebased the series on tip/master for v6.
Regards,
Hans
>
>> various profiling and sanitizing options. Having these options enabled
>> typically will cause dependency on various special symbols exported by
>> special libs / stubs used by these frameworks. Since the purgatory is
>> special we do not link against these stubs causing missing symbols in
>> the purgatory if we do not disable these options.
>>
>> This commit syncs the set of disabled profiling and sanitizing options
>
> Avoid having "This patch" or "This commit" in the commit message. It is
> tautologically useless.
>
> Also, do
>
> $ git grep 'This patch' Documentation/process
>
> for more details.
>
> Those two review comments apply to patch 2's commit message too, pls fix
> them there too.
>
>> with that from drivers/firmware/efi/libstub/Makefile, adding
>> -DDISABLE_BRANCH_PROFILING to the CFLAGS and setting:
>>
>> GCOV_PROFILE := n
>> UBSAN_SANITIZE := n
>>
>> This fixes broken references to ftrace_likely_update when
>> CONFIG_TRACE_BRANCH_PROFILING is enabled and to __gcov_init and
>> __gcov_exit when CONFIG_GCOV_KERNEL is enabled.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> Changes in v5:
>> -Not only add -DDISABLE_BRANCH_PROFILING to the CFLAGS but also set:
>> GCOV_PROFILE := n
>> UBSAN_SANITIZE := n
>>
>> Changes in v4:
>> -This is a new patch in v4 of this series
>> ---
>> arch/x86/purgatory/Makefile | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> $ test-apply.sh -g /tmp/01-x86-purgatory-disable_various_profiling_and_sanitizing_options.patch
> checking file arch/x86/purgatory/Makefile
> Hunk #1 FAILED at 17.
> Hunk #2 succeeded at 27 (offset 2 lines).
> 1 out of 2 hunks FAILED
>
> This happens because tip/master already has KCSAN merged in and it adds
>
> KCSAN_SANITIZE := n
>
> there.
>
> Please redo the patches against current tip/master.
>
> Thx.
>
prev parent reply other threads:[~2020-03-17 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 11:49 Hans de Goede
2020-03-12 11:49 ` [PATCH v5 2/2] x86/purgatory: Make sure we fail the build if purgatory.ro has missing symbols Hans de Goede
2020-03-13 18:28 ` [PATCH v5 1/2] x86/purgatory: Disable various profiling and sanitizing options Borislav Petkov
2020-03-17 13:08 ` Hans de Goede [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=aee4ff4d-05f0-9d55-eb19-1d8df520e6c9@redhat.com \
--to=hdegoede@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®