search for: allyesconfig

...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: 'last_extent_end' may be used uninitialized [-Wmaybe-uninitialized] Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead |-- arc-allmodconfig | |-- dr...

...715 | `-- ERROR:memcpy-fs-efs-efs.ko-undefined |-- alpha-randconfig-r062-20240328 | `-- ERROR:memcpy-crypto-chacha20poly1305.ko-undefined |-- parisc-allmodconfig | `-- drivers-gpu-drm-nouveau-nvif-object.c:error:memcpy-accessing-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset |-- parisc-allyesconfig | `-- drivers-gpu-drm-nouveau-nvif-object.c:error:memcpy-accessing-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset |-- sh-allmodconfig | `-- drivers-pwm-pwm-stm32.c:error:implicit-declaration-of-function-devm_clk_rate_exclusive_get |-- sh-allyesconfig | `-- drivers-pwm-pwm-stm32.c:error...

...s-i2c-busses-i2c-virtio.c:error:field-designator-restore-does-not-refer-to-any-field-in-type-struct-virtio_driver `-- mips-sb1250_swarm_defconfig `-- clang:error:unknown-argument:msym32 elapsed time: 725m configs tested: 111 configs skipped: 5 tested configs: alpha allyesconfig gcc alpha defconfig gcc alpha randconfig-r026-20230731 gcc arc alldefconfig gcc arc allyesconfig gcc arc defconfig gcc arc...

...sparc64-linux-ld: memory.c:(.text+0xee4): undefined reference to `mthp_stats' sparc64-linux-ld: vmscan.c:(.text+0x4dc0): undefined reference to `mthp_stats' vmscan.c:(.text+0x4db8): undefined reference to `mthp_stats' Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allyesconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | `-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size |-- arm-allmodconfig...

...d-)-)-converts-to-incompatible-function-type `-- lib-kunit-test.c:warning:cast-from-void-(-)(const-void-)-to-kunit_action_t-(aka-void-(-)(void-)-)-converts-to-incompatible-function-type elapsed time: 734m configs tested: 148 configs skipped: 9 tested configs: alpha allyesconfig gcc alpha defconfig gcc alpha randconfig-r002-20230704 gcc alpha randconfig-r003-20230704 gcc alpha randconfig-r004-20230704 gcc alpha randconfig-r023-20230703 gcc alpha...

...what was the > > original issue preventing BUG_ON from being used. > > > > Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. > > How much does this bloat the kernel? It seems to add 8 bytes to each {wr,rd}msr() call (4 extra instructions: test, jmp, ud2, jmp). allyesconfig, paravirt enabled, before: text data bss dec hex filename 108368312 23500872 55705600 187574784 b2e2a00 vmlinux allyesconfig, paravirt enabled, after: text data bss dec hex filename 108384438 23500904 55717888 18760...

...what was the > > original issue preventing BUG_ON from being used. > > > > Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. > > How much does this bloat the kernel? It seems to add 8 bytes to each {wr,rd}msr() call (4 extra instructions: test, jmp, ud2, jmp). allyesconfig, paravirt enabled, before: text data bss dec hex filename 108368312 23500872 55705600 187574784 b2e2a00 vmlinux allyesconfig, paravirt enabled, after: text data bss dec hex filename 108384438 23500904 55717888 18760...

...ng ids grouped by kconfigs: gcc_recent_errors |-- alpha-allnoconfig | |-- mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node | `-- mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node |-- alpha-allyesconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | |-- drivers-gpu-drm-nouveau-nouveau_backlight.c:error:d-directive-output-may-be-truncated-writing-between-and-bytes-into-a-region-of-size | |-- mm-mempool.c...

...t ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrmsr(0x410, 0xfffffffffffffbff) during MCE initialization) --- arch/x86/include/asm/paravirt.h | 11 +++++++---- 1 file changed, 7 insertion...

...t ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used. Change rdmsr(), wrmsr(), and rdmsrl() to BUG_ON() on errors. Signed-off-by: Eduardo Habkost <ehabkost at redhat.com> --- * Build-tested using allyesconfig, with no build errors. * Tested by being able to detect the following host bug: https://bugzilla.redhat.com/show_bug.cgi?id=1025868 (#GP exception on wrmsr(0x410, 0xfffffffffffffbff) during MCE initialization) --- arch/x86/include/asm/paravirt.h | 11 +++++++---- 1 file changed, 7 insertion...

...t;> >> 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 allyesconfig builds, but I don't see other option for now. > > Was there an bug reported for this? It would be good to CC the maintainers > of Xen on that sort of thing. > There was no report for this. I just looked at Xen code because of this Luis's mail and I don't see how it could...

...t;> >> 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 allyesconfig builds, but I don't see other option for now. > > Was there an bug reported for this? It would be good to CC the maintainers > of Xen on that sort of thing. > There was no report for this. I just looked at Xen code because of this Luis's mail and I don't see how it could...

...t;> corresponding *_create_handle() function is removed from each driver. >> >> In many cases this change eliminates a struct *_framebuffer object, >> as the only need for the derived struct is the addition of the gem >> object pointer. >> >> TESTED: compiled: allyesconfig ARCH=x86,arm platforms:i915, rockchip >> >> Signed-off-by: Joe Kniss <djmk at google.com> >> --- > > > Hi Joe, > > I'm also looking into adding gem objs to drm_framebuffer in this patch: > [PATCH v2 01/22] drm: Add GEM backed framebuffer library > ht...

...t;> corresponding *_create_handle() function is removed from each driver. >> >> In many cases this change eliminates a struct *_framebuffer object, >> as the only need for the derived struct is the addition of the gem >> object pointer. >> >> TESTED: compiled: allyesconfig ARCH=x86,arm platforms:i915, rockchip >> >> Signed-off-by: Joe Kniss <djmk at google.com> >> --- > > > Hi Joe, > > I'm also looking into adding gem objs to drm_framebuffer in this patch: > [PATCH v2 01/22] drm: Add GEM backed framebuffer library > ht...

...t;> corresponding *_create_handle() function is removed from each driver. >> >> In many cases this change eliminates a struct *_framebuffer object, >> as the only need for the derived struct is the addition of the gem >> object pointer. >> >> TESTED: compiled: allyesconfig ARCH=x86,arm platforms:i915, rockchip >> >> Signed-off-by: Joe Kniss <djmk at google.com> >> --- > > > Hi Joe, > > I'm also looking into adding gem objs to drm_framebuffer in this patch: > [PATCH v2 01/22] drm: Add GEM backed framebuffer library > ht...

...2020 at 14:03, Dave Airlie <airlied at gmail.com> wrote: > > On Fri, 7 Aug 2020 at 11:13, Rodrigo Vivi <rodrigo.vivi at intel.com> wrote: > > > > From: Rodrigo Vivi <rodrigo.vivi at gmail.com> > > > > These are missed cases that I just identified with allyesconfig build. > > > > Is this against drm-tip? it's a merge problem, that I thought I'd > already addressed, but tip seems to have lost it. I think I've fixed drm-tip rebuilds now. Dave.

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? Tengo problemas con el kernel compilado:...

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? Tengo problemas con el kernel compilado:...

...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 allyesconfig builds, but I don't see other option for now. > from someone on xen-devel though. Here's the thing though -- if true > -- I'd like to do it *properly*, where *properly* means addressing a > bit of architecture. A simple Kconfig slap seems rather reactive. I'd > like to...

...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 allyesconfig builds, but I don't see other option for now. > from someone on xen-devel though. Here's the thing though -- if true > -- I'd like to do it *properly*, where *properly* means addressing a > bit of architecture. A simple Kconfig slap seems rather reactive. I'd > like to...