From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master] BUILD REGRESSION 442630f691a1537b7e0cc35e3d580222077549cb
Date: Tue, 08 Oct 2019 20:46:46 +0800 [thread overview]
Message-ID: <5d9c8536.zdNn906x4Ki/Igk7%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 442630f691a1537b7e0cc35e3d580222077549cb Add linux-next specific files for 20191008
Regressions in current branch:
drivers/video/fbdev/hyperv_fb.c:1013:25: sparse: sparse: cast removes address space '<asn:2>' of expression
drivers/video/fbdev/hyperv_fb.c:1017:27: sparse: expected char [noderef] <asn:2> *screen_base
drivers/video/fbdev/hyperv_fb.c:1017:27: sparse: got unsigned char *dio_vp
drivers/video/fbdev/hyperv_fb.c:1017:27: sparse: sparse: incorrect type in assignment (different address spaces)
include/linux/rcupdate.h:651:9: sparse: sparse: context imbalance in 'dump_tasks' - unexpected unlock
Error ids grouped by kconfigs:
recent_errors
`-- x86_64-allmodconfig
|-- drivers-video-fbdev-hyperv_fb.c:sparse:expected-char-noderef-asn-screen_base
|-- drivers-video-fbdev-hyperv_fb.c:sparse:got-unsigned-char-dio_vp
|-- drivers-video-fbdev-hyperv_fb.c:sparse:sparse:cast-removes-address-space-asn-of-expression
|-- drivers-video-fbdev-hyperv_fb.c:sparse:sparse:incorrect-type-in-assignment-(different-address-spaces)-expected-char-noderef-asn-screen_base-got-eref-asn-screen_base
`-- include-linux-rcupdate.h:sparse:sparse:context-imbalance-in-dump_tasks-unexpected-unlock
elapsed time: 216m
configs tested: 137
i386 allnoconfig
i386 defconfig
i386 alldefconfig
xtensa common_defconfig
openrisc or1ksim_defconfig
nios2 3c120_defconfig
xtensa iss_defconfig
c6x evmc6678_defconfig
c6x allyesconfig
nios2 10m50_defconfig
openrisc simple_smp_defconfig
x86_64 randconfig-e004-201940
x86_64 randconfig-e001-201940
x86_64 randconfig-e003-201940
x86_64 randconfig-e002-201940
i386 randconfig-e003-201940
i386 randconfig-e004-201940
i386 randconfig-e001-201940
i386 randconfig-e002-201940
m68k multi_defconfig
m68k m5475evb_defconfig
h8300 h8300h-sim_defconfig
h8300 edosk2674_defconfig
m68k sun3_defconfig
h8300 h8s-sim_defconfig
m68k allmodconfig
sparc64 allmodconfig
sparc defconfig
sparc64 allnoconfig
sparc64 defconfig
arm allmodconfig
arm at91_dt_defconfig
arm64 defconfig
arm multi_v5_defconfig
arm64 allyesconfig
arm allnoconfig
arm efm32_defconfig
arm sunxi_defconfig
arm64 allnoconfig
arm exynos_defconfig
arm shmobile_defconfig
arm multi_v7_defconfig
arc allyesconfig
powerpc defconfig
microblaze nommu_defconfig
powerpc ppc64_defconfig
microblaze mmu_defconfig
arc defconfig
powerpc allnoconfig
ia64 allmodconfig
ia64 allnoconfig
ia64 defconfig
ia64 alldefconfig
i386 randconfig-d002-201940
x86_64 randconfig-d002-201940
x86_64 randconfig-d004-201940
i386 randconfig-d004-201940
x86_64 randconfig-d003-201940
i386 randconfig-d003-201940
x86_64 randconfig-d001-201940
i386 randconfig-d001-201940
um x86_64_defconfig
um i386_defconfig
um defconfig
arm64 allmodconfig
mips allmodconfig
mips 32r2_defconfig
mips malta_kvm_defconfig
mips 64r6el_defconfig
mips allnoconfig
mips fuloong2e_defconfig
sh allmodconfig
sh rsk7269_defconfig
sh sh7785lcr_32bit_defconfig
sh allnoconfig
sh titan_defconfig
s390 allnoconfig
s390 debug_defconfig
s390 allmodconfig
s390 defconfig
i386 randconfig-b001-201940
x86_64 randconfig-b002-201940
x86_64 randconfig-b003-201940
i386 randconfig-b003-201940
i386 randconfig-b004-201940
x86_64 randconfig-b004-201940
x86_64 randconfig-b001-201940
i386 randconfig-b002-201940
x86_64 randconfig-a004-201940
x86_64 randconfig-a001-201940
i386 randconfig-a002-201940
x86_64 randconfig-a002-201940
i386 randconfig-a001-201940
i386 randconfig-a003-201940
i386 randconfig-a004-201940
x86_64 randconfig-a003-201940
parisc c3000_defconfig
parisc b180_defconfig
parisc defconfig
parisc allnoconfig
x86_64 randconfig-g002-201940
i386 randconfig-g004-201940
x86_64 randconfig-g001-201940
i386 randconfig-g002-201940
x86_64 randconfig-g004-201940
x86_64 randconfig-g003-201940
i386 randconfig-g003-201940
i386 randconfig-g001-201940
x86_64 randconfig-h002-201940
x86_64 randconfig-h001-201940
i386 randconfig-h004-201940
i386 randconfig-h003-201940
x86_64 randconfig-h003-201940
i386 randconfig-h002-201940
i386 randconfig-h001-201940
x86_64 randconfig-h004-201940
i386 randconfig-f002-201940
i386 randconfig-f001-201940
x86_64 randconfig-f003-201940
x86_64 randconfig-f004-201940
x86_64 randconfig-f002-201940
i386 randconfig-f003-201940
x86_64 randconfig-f001-201940
i386 randconfig-f004-201940
x86_64 allmodconfig
riscv allnoconfig
riscv defconfig
nds32 defconfig
alpha defconfig
nds32 allnoconfig
x86_64 lkp
x86_64 rhel
x86_64 rhel-7.6
x86_64 fedora-25
x86_64 kexec
x86_64 allyesconfig
i386 allmodconfig
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
reply other threads:[~2019-10-08 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5d9c8536.zdNn906x4Ki/Igk7%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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