similar to: [linux-next:master] BUILD REGRESSION a734662572708cf062e974f659ae50c24fc1ad17

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: 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: 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

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

* 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 > > >

That I should make? I have problems with the compiled kernel: I compiled the kernel 2.6.13.4 with make allnocoonfig, with make allyesconfig, with make defconfig, the LILO is generated automatically and when I restart the computer, it shows me the following error: kernel panic - not syncing : VFS : Unable to mount root fs on unknown-block (0,0) Rogel ------------------------- Que debo hacer?

That I should make? I have problems with the compiled kernel: I compiled the kernel 2.6.13.4 with make allnocoonfig, with make allyesconfig, with make defconfig, the LILO is generated automatically and when I restart the computer, it shows me the following error: kernel panic - not syncing : VFS : Unable to mount root fs on unknown-block (0,0) Rogel ------------------------- Que debo hacer?

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

From: Arnd Bergmann <arnd at arndb.de> This is a follow-up on a couple of patch series I sent in the past, enabling -Wextra (aside from stuff that is explicitly disabled), -Wcast-function-pointer-strict and -Wrestrict. I have tested these on 'defconfig' and 'allmodconfig' builds across all architectures, as well as many 'randconfig' builds on x86, arm and arm64. It

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 >

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does

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