* [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
@ 2020-09-17 1:12 kernel test robot
2020-09-17 6:12 ` Borislav Petkov
0 siblings, 1 reply; 6+ messages in thread
From: kernel test robot @ 2020-09-17 1:12 UTC (permalink / raw)
To: x86-ml; +Cc: linux-kernel
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti
branch HEAD: 767d46ab566dd489733666efe48732d523c8c332 Documentation: Add L1D flushing Documentation
Warning in current branch:
arch/x86/mm/tlb.c:426:36: sparse: expected void const [noderef] __percpu *__vpp_verify
arch/x86/mm/tlb.c:426:36: sparse: got bool *
arch/x86/mm/tlb.c:426:36: sparse: sparse: incorrect type in initializer (different address spaces)
Warning ids grouped by kconfigs:
gcc_recent_errors
`-- i386-randconfig-s002-20200916
|-- arch-x86-mm-tlb.c:sparse:expected-void-const-noderef-__percpu-__vpp_verify
|-- arch-x86-mm-tlb.c:sparse:got-bool
`-- arch-x86-mm-tlb.c:sparse:sparse:incorrect-type-in-initializer-(different-address-spaces)-expected-void-const-noderef-__percpu-__vpp_verify-got-bool
elapsed time: 722m
configs tested: 152
configs skipped: 2
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
m68k mvme16x_defconfig
sh ecovec24-romimage_defconfig
sh sh7763rdp_defconfig
arm pxa168_defconfig
arm integrator_defconfig
arc nsimosci_hs_defconfig
arc axs101_defconfig
sh landisk_defconfig
m68k atari_defconfig
arm colibri_pxa270_defconfig
sh rsk7264_defconfig
mips bmips_stb_defconfig
powerpc fsp2_defconfig
arc nps_defconfig
arm dove_defconfig
sh sh7710voipgw_defconfig
arm socfpga_defconfig
sh r7785rp_defconfig
s390 alldefconfig
mips nlm_xlp_defconfig
microblaze nommu_defconfig
sh se7780_defconfig
mips decstation_defconfig
mips malta_kvm_defconfig
arm pcm027_defconfig
powerpc storcenter_defconfig
mips cobalt_defconfig
arm axm55xx_defconfig
mips rm200_defconfig
m68k stmark2_defconfig
powerpc mpc885_ads_defconfig
sh kfr2r09_defconfig
c6x evmc6678_defconfig
c6x defconfig
arm stm32_defconfig
mips ci20_defconfig
m68k m5475evb_defconfig
arm tango4_defconfig
sh sh7785lcr_32bit_defconfig
xtensa xip_kc705_defconfig
powerpc tqm5200_defconfig
arm spear6xx_defconfig
mips jazz_defconfig
powerpc rainier_defconfig
powerpc ppc64e_defconfig
nios2 allyesconfig
arm sama5_defconfig
arm efm32_defconfig
mips tb0287_defconfig
mips db1xxx_defconfig
arm trizeps4_defconfig
powerpc mpc836x_mds_defconfig
powerpc tqm8xx_defconfig
powerpc katmai_defconfig
sh apsh4ad0a_defconfig
powerpc wii_defconfig
arm exynos_defconfig
ia64 bigsur_defconfig
mips rt305x_defconfig
powerpc mpc866_ads_defconfig
alpha alldefconfig
m68k apollo_defconfig
alpha defconfig
powerpc walnut_defconfig
riscv nommu_virt_defconfig
arc nsimosci_hs_smp_defconfig
powerpc klondike_defconfig
c6x evmc6472_defconfig
arc nsimosci_defconfig
mips tb0219_defconfig
arm mini2440_defconfig
arm lpd270_defconfig
powerpc mpc8315_rdb_defconfig
mips sb1250_swarm_defconfig
sh apsh4a3a_defconfig
powerpc eiger_defconfig
powerpc mpc7448_hpc2_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
csky defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a006-20200916
x86_64 randconfig-a004-20200916
x86_64 randconfig-a003-20200916
x86_64 randconfig-a002-20200916
x86_64 randconfig-a001-20200916
x86_64 randconfig-a005-20200916
i386 randconfig-a004-20200916
i386 randconfig-a006-20200916
i386 randconfig-a003-20200916
i386 randconfig-a001-20200916
i386 randconfig-a002-20200916
i386 randconfig-a005-20200916
i386 randconfig-a004-20200917
i386 randconfig-a006-20200917
i386 randconfig-a003-20200917
i386 randconfig-a001-20200917
i386 randconfig-a002-20200917
i386 randconfig-a005-20200917
i386 randconfig-a015-20200916
i386 randconfig-a014-20200916
i386 randconfig-a011-20200916
i386 randconfig-a013-20200916
i386 randconfig-a016-20200916
i386 randconfig-a012-20200916
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a014-20200916
x86_64 randconfig-a011-20200916
x86_64 randconfig-a016-20200916
x86_64 randconfig-a012-20200916
x86_64 randconfig-a015-20200916
x86_64 randconfig-a013-20200916
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
2020-09-17 1:12 [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332 kernel test robot
@ 2020-09-17 6:12 ` Borislav Petkov
[not found] ` <20200917073620.GA4946@intel.com>
0 siblings, 1 reply; 6+ messages in thread
From: Borislav Petkov @ 2020-09-17 6:12 UTC (permalink / raw)
To: kernel test robot, Li, Philip, Rong Chen; +Cc: x86-ml, linux-kernel
Hi guys,
On Thu, Sep 17, 2020 at 09:12:18AM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti
> branch HEAD: 767d46ab566dd489733666efe48732d523c8c332 Documentation: Add L1D flushing Documentation
>
> Warning in current branch:
>
> arch/x86/mm/tlb.c:426:36: sparse: expected void const [noderef] __percpu *__vpp_verify
> arch/x86/mm/tlb.c:426:36: sparse: got bool *
> arch/x86/mm/tlb.c:426:36: sparse: sparse: incorrect type in initializer (different address spaces)
>
> Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> `-- i386-randconfig-s002-20200916
> |-- arch-x86-mm-tlb.c:sparse:expected-void-const-noderef-__percpu-__vpp_verify
> |-- arch-x86-mm-tlb.c:sparse:got-bool
> `-- arch-x86-mm-tlb.c:sparse:sparse:incorrect-type-in-initializer-(different-address-spaces)-expected-void-const-noderef-__percpu-__vpp_verify-got-bool
this is another worthless bug report:
* No .config attached
* no build command line to know how you run sparse. I'm guessing with
C=1. But I should not have to guess.
Pls fix.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
[not found] ` <20200917073620.GA4946@intel.com>
@ 2020-09-17 8:00 ` Borislav Petkov
2020-09-17 13:37 ` Philip Li
0 siblings, 1 reply; 6+ messages in thread
From: Borislav Petkov @ 2020-09-17 8:00 UTC (permalink / raw)
To: Philip Li; +Cc: kernel test robot, Rong Chen, x86-ml, linux-kernel
On Thu, Sep 17, 2020 at 03:36:20PM +0800, Philip Li wrote:
> The 2nd type is this one, which is a summarized report of head
> to provide an overview. Most of time, repo owner can receive the
> bisected mail. For this time, the issue is reported against peterz-queue
> repo which has this 767d46ab56 head firstly. Since the head later appears
> in tip, we just gather all issues and send the summary to tip related
> recipients. But no more bisected mail.
Yeah, but that second report is not very helpful because nowhere it says
it is a summary and nowhere it has that link you pasted above so that
some other maintainer can go look.
Always put yourself in the recipient's shoes and ask yourself: "what can
the recipient do with this report and does it have everything in there
required to be able to reproduce the issue?"
If not, then it needs changing.
> We will consider how to show useful produce info in summary report as
> the feedback here, which is quite useful, such like pointing to the
> bisected mail. This would take some time, and we will add to our TODO
> as high priority.
Yes, that would be much appreciated. You can also tag your reports with
a unique hash which is then in an URL so that one can go and download the
.config and what else is needed. For example...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
2020-09-17 8:00 ` Borislav Petkov
@ 2020-09-17 13:37 ` Philip Li
2020-10-12 9:16 ` Rong Chen
0 siblings, 1 reply; 6+ messages in thread
From: Philip Li @ 2020-09-17 13:37 UTC (permalink / raw)
To: Borislav Petkov; +Cc: kernel test robot, Rong Chen, x86-ml, linux-kernel
On Thu, Sep 17, 2020 at 10:00:44AM +0200, Borislav Petkov wrote:
> On Thu, Sep 17, 2020 at 03:36:20PM +0800, Philip Li wrote:
> > The 2nd type is this one, which is a summarized report of head
> > to provide an overview. Most of time, repo owner can receive the
> > bisected mail. For this time, the issue is reported against peterz-queue
> > repo which has this 767d46ab56 head firstly. Since the head later appears
> > in tip, we just gather all issues and send the summary to tip related
> > recipients. But no more bisected mail.
>
> Yeah, but that second report is not very helpful because nowhere it says
> it is a summary and nowhere it has that link you pasted above so that
> some other maintainer can go look.
>
> Always put yourself in the recipient's shoes and ask yourself: "what can
> the recipient do with this report and does it have everything in there
> required to be able to reproduce the issue?"
>
> If not, then it needs changing.
thanks for the advice. We will provide update in 1-2 weeks for the progress
to make the report more informative and useful.
>
> > We will consider how to show useful produce info in summary report as
> > the feedback here, which is quite useful, such like pointing to the
> > bisected mail. This would take some time, and we will add to our TODO
> > as high priority.
>
> Yes, that would be much appreciated. You can also tag your reports with
> a unique hash which is then in an URL so that one can go and download the
> .config and what else is needed. For example...
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
2020-09-17 13:37 ` Philip Li
@ 2020-10-12 9:16 ` Rong Chen
2020-10-12 14:37 ` Borislav Petkov
0 siblings, 1 reply; 6+ messages in thread
From: Rong Chen @ 2020-10-12 9:16 UTC (permalink / raw)
To: Philip Li, Borislav Petkov; +Cc: kernel test robot, x86-ml, linux-kernel
Hi Boris,
On 9/17/20 9:37 PM, Philip Li wrote:
> On Thu, Sep 17, 2020 at 10:00:44AM +0200, Borislav Petkov wrote:
>> On Thu, Sep 17, 2020 at 03:36:20PM +0800, Philip Li wrote:
>>> The 2nd type is this one, which is a summarized report of head
>>> to provide an overview. Most of time, repo owner can receive the
>>> bisected mail. For this time, the issue is reported against peterz-queue
>>> repo which has this 767d46ab56 head firstly. Since the head later appears
>>> in tip, we just gather all issues and send the summary to tip related
>>> recipients. But no more bisected mail.
>> Yeah, but that second report is not very helpful because nowhere it says
>> it is a summary and nowhere it has that link you pasted above so that
>> some other maintainer can go look.
>>
>> Always put yourself in the recipient's shoes and ask yourself: "what can
>> the recipient do with this report and does it have everything in there
>> required to be able to reproduce the issue?"
>>
>> If not, then it needs changing.
> thanks for the advice. We will provide update in 1-2 weeks for the progress
> to make the report more informative and useful.
We have added the reported links in the report, you can find it in the
latest tip report:
[tip:master] BUILD REGRESSION 820e6f502f021417140bc8ee11f9c7be148ea844
tree/branch:https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
branch HEAD: 820e6f502f021417140bc8ee11f9c7be148ea844 Merge branch 'efi/core'
Error/Warning reports:
https://lore.kernel.org/lkml/202010112007.JDl1BSci-lkp@intel.com
Error/Warning in current branch:
tools/include/linux/types.h:30:18: error: typedef redefinition with different types ('uint64_t' (aka 'unsigned long') vs '__u64' (aka 'unsigned long long'))
tools/include/linux/types.h:31:17: error: typedef redefinition with different types ('int64_t' (aka 'long') vs '__s64' (aka 'long long'))
Error/Warning ids grouped by kconfigs:
clang_recent_errors
`-- x86_64-randconfig-a016-20201011
|-- tools-include-linux-types.h:error:typedef-redefinition-with-different-types-(-int64_t-(aka-long-)-vs-__s64-(aka-long-long-))
`-- tools-include-linux-types.h:error:typedef-redefinition-with-different-types-(-uint64_t-(aka-unsigned-long-)-vs-__u64-(aka-unsigned-long-long-))
Best Regards,
Rong Chen
>
>>> We will consider how to show useful produce info in summary report as
>>> the feedback here, which is quite useful, such like pointing to the
>>> bisected mail. This would take some time, and we will add to our TODO
>>> as high priority.
>> Yes, that would be much appreciated. You can also tag your reports with
>> a unique hash which is then in an URL so that one can go and download the
>> .config and what else is needed. For example...
>>
>> Thx.
>>
>> --
>> Regards/Gruss,
>> Boris.
>>
>> https://people.kernel.org/tglx/notes-about-netiquette
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
2020-10-12 9:16 ` Rong Chen
@ 2020-10-12 14:37 ` Borislav Petkov
0 siblings, 0 replies; 6+ messages in thread
From: Borislav Petkov @ 2020-10-12 14:37 UTC (permalink / raw)
To: Rong Chen; +Cc: Philip Li, kernel test robot, x86-ml, linux-kernel
On Mon, Oct 12, 2020 at 05:16:54PM +0800, Rong Chen wrote:
> We have added the reported links in the report, you can find it in the
> latest tip report:
>
> [tip:master] BUILD REGRESSION 820e6f502f021417140bc8ee11f9c7be148ea844
>
> tree/branch:https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> branch HEAD: 820e6f502f021417140bc8ee11f9c7be148ea844 Merge branch 'efi/core'
>
> Error/Warning reports:
>
> https://lore.kernel.org/lkml/202010112007.JDl1BSci-lkp@intel.com
Thanks, that link has all the info needed to reproduce AFAICT, as long
as you make sure to send it to a mailing list which gets archived by
lore.kernel.org - otherwise the redirection won't work.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-10-12 14:37 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-17 1:12 [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332 kernel test robot
2020-09-17 6:12 ` Borislav Petkov
[not found] ` <20200917073620.GA4946@intel.com>
2020-09-17 8:00 ` Borislav Petkov
2020-09-17 13:37 ` Philip Li
2020-10-12 9:16 ` Rong Chen
2020-10-12 14:37 ` Borislav Petkov
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).