From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Borislav Petkov <bp@alien8.de>, kernel test robot <lkp@intel.com>
Cc: x86-ml <x86@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/urgent] BUILD SUCCESS WITH WARNING 064855a69003c24bd6b473b367d364e418c57625
Date: Thu, 19 Aug 2021 14:15:16 +0800 [thread overview]
Message-ID: <ced3f2ab-54b6-95d7-7f5b-b6bb6a299330@intel.com> (raw)
In-Reply-To: <YRjTkkpDjaWxEpjb@zn.tnic>
On 8/15/2021 4:42 PM, Borislav Petkov wrote:
> Hi,
>
> On Sun, Aug 15, 2021 at 04:36:40PM +0800, kernel test robot wrote:
>> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
>> branch HEAD: 064855a69003c24bd6b473b367d364e418c57625 x86/resctrl: Fix default monitoring groups reporting
>>
>> possible Warning in current branch:
>>
>> arch/x86/kernel/cpu/resctrl/monitor.c:310 __mon_event_count() error: uninitialized symbol 'm'.
>> arch/x86/kernel/cpu/resctrl/monitor.c:315 __mon_event_count() error: potentially dereferencing uninitialized 'm'.
>>
>> Warning ids grouped by kconfigs:
>>
>> gcc_recent_errors
>> `-- i386-randconfig-m021-20210812
>> |-- arch-x86-kernel-cpu-resctrl-monitor.c-__mon_event_count()-error:potentially-dereferencing-uninitialized-m-.
>> `-- arch-x86-kernel-cpu-resctrl-monitor.c-__mon_event_count()-error:uninitialized-symbol-m-.
>
> AFAIR, I had already asked you guys to make those reports more useful
> as, for example, adding a link to that randconfig above or even
> attaching it so that a person - not a machine - reading it, can
> *actually* act upon it.
>
> But that hasn't happened.
>
> Until it happens, I'm going to ignore all those reports from you.
>
Hi Borislav,
Sorry about it, the actual link is at
https://lists.01.org/hyperkitty/list/kbuild@lists.01.org/thread/PZVMY3VJU4QY4HQXHK3MLPQ2KZ5CNAYH/,
and it's still an internal report that the robot don't know whether it's
a false positive or not, we'll update the mail contents to avoid
misunderstanding.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2021-08-19 6:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 8:36 [tip:x86/urgent] BUILD SUCCESS WITH WARNING 064855a69003c24bd6b473b367d364e418c57625 kernel test robot
2021-08-15 8:42 ` Borislav Petkov
2021-08-15 10:22 ` Philip Li
2021-08-19 6:15 ` Chen, Rong A [this message]
2021-08-19 9:00 ` Borislav Petkov
2021-08-19 20:39 ` Reinette Chatre
2021-08-19 21:05 ` Borislav Petkov
2021-08-20 14:16 ` Babu Moger
2021-08-20 14:41 ` Reinette Chatre
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=ced3f2ab-54b6-95d7-7f5b-b6bb6a299330@intel.com \
--to=rong.a.chen@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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).