similar to: [linux-next:master] BUILD REGRESSION 9d99040b1bc8dbf385a8aa535e9efcdf94466e19

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 3689b0ef08b70e4e03b82ebd37730a03a672853a Add linux-next specific files for 20240523 Unverified Error/Warning (likely false positive, please contact us if interested): drivers/gpu/drm/xe/xe_drm_client.c:272 show_runtime() error: uninitialized symbol 'hwe'.

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 4118d9533ff3a5d16efb476a0d00afceecd92cf5 Add linux-next specific files for 20240411 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202404120101.dAQBAzh3-lkp at intel.com Error/Warning: (recently discovered and may have been fixed) huge_memory.c:(.text+0x1778): undefined reference

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 727900b675b749c40ba1f6669c7ae5eb7eb8e837 Add linux-next specific files for 20240403 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202404031246.aq5Yr5KO-lkp at intel.com https://lore.kernel.org/oe-kbuild-all/202404031346.wpIhNpyF-lkp at intel.com

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: a6bd6c9333397f5a0e2667d4d82fef8c970108f2 Add linux-next specific files for 20240328 Error/Warning: (recently discovered and may have been fixed) ERROR: modpost: "memcpy" [crypto/chacha20poly1305.ko] undefined! ERROR: modpost: "memcpy" [fs/efs/efs.ko] undefined! ERROR:

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: a734662572708cf062e974f659ae50c24fc1ad17 Add linux-next specific files for 20230801 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202307251531.p8ZLFTMZ-lkp at intel.com https://lore.kernel.org/oe-kbuild-all/202308020154.Xrcb9bWT-lkp at intel.com Error/Warning: (recently

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 1843e16d2df9d98427ef8045589571749d627cf7 Add linux-next specific files for 20240307 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202403071947.NUYuBx0G-lkp at intel.com Error/Warning: (recently discovered and may have been fixed) fs/btrfs/extent_io.c:3246:26: warning:

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: 1c6f93977947dbba1fc4d250c4eb8a7d4cfdecf1 Add linux-next specific files for 20230704 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202306260401.qZlYQpV2-lkp at intel.com https://lore.kernel.org/oe-kbuild-all/202306301709.lvrxzyCj-lkp at intel.com

-Wenum-compare is buggy / bogus. We should turn this warning off in our build scripts if possible. On Tue, Jun 26, 2012 at 5:15 PM, Yuri <yuri at rawbw.com> wrote: > I just switched gcc from 4.6.2 to 4.7.1 and see the massive amount of > warnings, see few examples below. > They mostly didn't exist with gcc-4.6.2. > > rev.159224 > > Yuri > > >

I just switched gcc from 4.6.2 to 4.7.1 and see the massive amount of warnings, see few examples below. They mostly didn't exist with gcc-4.6.2. rev.159224 Yuri /usr/home/yuri/llvm-2012-06/latest-unpatched/llvm-fix/include/llvm/ADT/PointerUnion.h:56:10: warning: enumeral mismatch in conditional expression:

Greetings, I got the below dmesg and the first bad commit is commit b70aa55ec9532d5f5d3e367e4cad8997b1135f86 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk> [ 277.857736] blk-mq: CPU -> queue map [ 277.871142] CPU 0

Greetings, I got the below dmesg and the first bad commit is commit b70aa55ec9532d5f5d3e367e4cad8997b1135f86 Author: Jens Axboe <axboe at kernel.dk> Date: Fri May 24 20:22:33 2013 +0200 virtio_blk: blk-mq support Pretend we have 4 issue queues. Signed-off-by: Jens Axboe <axboe at kernel.dk> [ 277.857736] blk-mq: CPU -> queue map [ 277.871142] CPU 0

* wang.yi59 at zte.com.cn <wang.yi59 at zte.com.cn> wrote: > Hi Ingo, > > > * Yi Wang <wang.yi59 at zte.com.cn> wrote: > > > > > We may get -Wmissing-prototypes warnings when building > > > kernel with W=1, it's better to fix them as global function > > > signature can be changed and caller who use the old unchanged > > >

On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: > Andrey, > > I believe that on Xen we should disable kasan, would like confirmation I guess Xen guests won't work with kasan because Xen guests doesn't setup shadow (kasan_map_early_shadow() is not called in xen guests). Disabling kasan for Xen in Kconfig is undesirable because that will disable kasan for allmodconfig and

On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: > Andrey, > > I believe that on Xen we should disable kasan, would like confirmation I guess Xen guests won't work with kasan because Xen guests doesn't setup shadow (kasan_map_early_shadow() is not called in xen guests). Disabling kasan for Xen in Kconfig is undesirable because that will disable kasan for allmodconfig and

On 03/03/2015 05:16 PM, Konrad Rzeszutek Wilk wrote: > On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote: >> On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: >>> Andrey, >>> >>> I believe that on Xen we should disable kasan, would like confirmation >> >> I guess Xen guests won't work with kasan because Xen guests doesn't setup

On 03/03/2015 05:16 PM, Konrad Rzeszutek Wilk wrote: > On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote: >> On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: >>> Andrey, >>> >>> I believe that on Xen we should disable kasan, would like confirmation >> >> I guess Xen guests won't work with kasan because Xen guests doesn't setup

On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote: > On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: > > Andrey, > > > > I believe that on Xen we should disable kasan, would like confirmation > > I guess Xen guests won't work with kasan because Xen guests doesn't setup shadow > (kasan_map_early_shadow() is not called in xen guests). > >

On Tue, Mar 03, 2015 at 06:38:20PM +0300, Andrey Ryabinin wrote: > On 03/03/2015 05:16 PM, Konrad Rzeszutek Wilk wrote: > > On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote: > >> On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: > >>> Andrey, > >>> > >>> I believe that on Xen we should disable kasan, would like confirmation >

On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote: > On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: > > Andrey, > > > > I believe that on Xen we should disable kasan, would like confirmation > > I guess Xen guests won't work with kasan because Xen guests doesn't setup shadow > (kasan_map_early_shadow() is not called in xen guests). > >

On Tue, Mar 03, 2015 at 06:38:20PM +0300, Andrey Ryabinin wrote: > On 03/03/2015 05:16 PM, Konrad Rzeszutek Wilk wrote: > > On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote: > >> On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote: > >>> Andrey, > >>> > >>> I believe that on Xen we should disable kasan, would like confirmation >