From: Yin Fengwei <fengwei.yin@intel.com>
To: Borislav Petkov <bp@suse.de>
Cc: Marco Elver <elver@google.com>, Carel Si <beibei.si@intel.com>,
"Joerg Roedel" <jroedel@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"lkp@lists.01.org" <lkp@lists.01.org>, lkp <lkp@intel.com>,
"bfields@fieldses.org" <bfields@fieldses.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>
Subject: Re: [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV?
Date: Wed, 5 Jan 2022 20:47:28 +0800 [thread overview]
Message-ID: <fa2f7d50-5226-726d-a9ad-2c42cb5c4054@intel.com> (raw)
In-Reply-To: <YdWCstlEW6k45+hH@zn.tnic>
On 1/5/2022 7:36 PM, Borislav Petkov wrote:
> On Wed, Jan 05, 2022 at 10:35:20AM +0800, Yin Fengwei wrote:
>> Did you get update from clang folks for this behavior? Thanks.
>
> No. Why?
My understanding:
it's better that clang restore its behavior to clang-12. Or people
need to use __no_profile annotation if want to add function before
GCOV/KASAN is initialized. Thanks.
Regards
Yin, Fengwei
>
WARNING: multiple messages have this Message-ID (diff)
From: Yin Fengwei <fengwei.yin@intel.com>
To: lkp@lists.01.org
Subject: Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV?
Date: Wed, 05 Jan 2022 20:47:28 +0800 [thread overview]
Message-ID: <fa2f7d50-5226-726d-a9ad-2c42cb5c4054@intel.com> (raw)
In-Reply-To: <YdWCstlEW6k45+hH@zn.tnic>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
On 1/5/2022 7:36 PM, Borislav Petkov wrote:
> On Wed, Jan 05, 2022 at 10:35:20AM +0800, Yin Fengwei wrote:
>> Did you get update from clang folks for this behavior? Thanks.
>
> No. Why?
My understanding:
it's better that clang restore its behavior to clang-12. Or people
need to use __no_profile annotation if want to add function before
GCOV/KASAN is initialized. Thanks.
Regards
Yin, Fengwei
>
next prev parent reply other threads:[~2022-01-05 12:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 14:41 [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage kernel test robot
2021-12-09 14:41 ` kernel test robot
2021-12-14 16:38 ` Borislav Petkov
2021-12-14 16:38 ` Borislav Petkov
2021-12-15 7:00 ` [LKP] " Carel Si
2021-12-15 7:00 ` Carel Si
2021-12-15 10:05 ` [LKP] " Borislav Petkov
2021-12-15 10:05 ` Borislav Petkov
2021-12-16 7:04 ` [LKP] " Yin Fengwei
2021-12-16 7:04 ` Yin Fengwei
2021-12-16 10:06 ` [LKP] " Borislav Petkov
2021-12-16 10:06 ` Borislav Petkov
2021-12-16 11:58 ` [LKP] " Carel Si
2021-12-16 11:58 ` Carel Si
2021-12-16 12:21 ` [LKP] " Yin Fengwei
2021-12-16 12:21 ` Yin Fengwei
2021-12-17 12:52 ` [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV? Borislav Petkov
2021-12-17 12:52 ` Borislav Petkov
2021-12-17 18:04 ` [LKP] " Nathan Chancellor
2021-12-17 18:04 ` Nathan Chancellor
2021-12-18 11:00 ` [LKP] " Borislav Petkov
2021-12-18 11:00 ` Borislav Petkov
2021-12-20 11:00 ` [PATCH] x86/mm: Prevent early boot triple-faults with instrumentation Borislav Petkov
2021-12-20 11:00 ` Borislav Petkov
2021-12-18 10:39 ` [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV? Yin Fengwei
2021-12-18 10:39 ` Yin Fengwei
2021-12-18 11:01 ` [LKP] " Borislav Petkov
2021-12-18 11:01 ` Borislav Petkov
2021-12-20 1:51 ` [LKP] " Yin Fengwei
2021-12-20 1:51 ` Yin Fengwei
2021-12-21 14:31 ` [LKP] " Carel Si
2021-12-21 14:31 ` Carel Si
2021-12-21 15:10 ` [LKP] " Marco Elver
2021-12-21 15:10 ` Marco Elver
2021-12-21 15:22 ` [LKP] " Borislav Petkov
2021-12-21 15:22 ` Borislav Petkov
2022-01-05 2:35 ` [LKP] " Yin Fengwei
2022-01-05 2:35 ` Yin Fengwei
2022-01-05 11:36 ` [LKP] " Borislav Petkov
2022-01-05 11:36 ` Borislav Petkov
2022-01-05 12:47 ` Yin Fengwei [this message]
2022-01-05 12:47 ` Yin Fengwei
2022-01-05 15:21 ` [LKP] " Borislav Petkov
2022-01-05 15:21 ` Borislav Petkov
2022-01-06 6:56 ` [LKP] " Yin Fengwei
2022-01-06 6:56 ` Yin Fengwei
2021-12-21 15:14 ` [LKP] " Borislav Petkov
2021-12-21 15:14 ` Borislav Petkov
2021-12-22 10:59 ` [tip: x86/mm] x86/mm: Prevent early boot triple-faults with instrumentation tip-bot2 for Borislav Petkov
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=fa2f7d50-5226-726d-a9ad-2c42cb5c4054@intel.com \
--to=fengwei.yin@intel.com \
--cc=beibei.si@intel.com \
--cc=bfields@fieldses.org \
--cc=bp@suse.de \
--cc=elver@google.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=llvm@lists.linux.dev \
--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 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.