On Tue, Dec 27, 2022 at 10:34 AM Geert Uytterhoeven
<ge...@linux-m68k.org> wrote:
>
> On Tue, 27 Dec 2022, Geert Uytterhoeven wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v6.2-rc1[1] compared to v6.1[2].
> >
> > Summarized:
> > - build errors: +11/-13
>
> amd-...@lists.freedesktop.org
> linux-arm-ker...@lists.infradead.org
> linux-me...@vger.kernel.org
> linux-wirel...@vger.kernel.org
> linux-m...@vger.kernel.org
> linux...@vger.kernel.org
> linux-f2fs-de...@lists.sourceforge.net
> linuxppc-dev@lists.ozlabs.org
> kasan-...@googlegroups.com
> linux-xte...@linux-xtensa.org
>
> +
> /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn31/display_mode_vba_31.c:
> error: the frame size of 2224 bytes is larger than 2048 bytes
> [-Werror=frame-larger-than=]: => 7082:1
> +
> /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn314/display_mode_vba_314.c:
> error: the frame size of 2208 bytes is larger than 2048 bytes
> [-Werror=frame-larger-than=]: => 7127:1
>
@Siqueira, Rodrigo @Mahfooz, Hamza
Can you take a look at fixing the DML stack size here up?
Alex
> arm64-gcc5/arm64-allmodconfig
>
> + /kisskb/src/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c: error: array
> subscript 2 is above array bounds of 'u32[2]' {aka 'unsigned int[2]'}
> [-Werror=array-bounds]: => 641:28
> + /kisskb/src/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c: error: array
> subscript 3 is above array bounds of 'u32[2]' {aka 'unsigned int[2]'}
> [-Werror=array-bounds]: => 641:28
>
> m68k-gcc8/m68k-allmodconfig
> See also
> https://lore.kernel.org/all/camuhmdwppx2mpqfewjjbjsqvdbqoxyjjdpknqu9qurauvzx...@mail.gmail.com
>
> + /kisskb/src/include/linux/bitfield.h: error: call to '__field_overflow'
> declared with attribute error: value doesn't fit into mask: => 151:3
>
> In function 'u32_encode_bits',
> inlined from 'ieee80211_mlo_multicast_tx' at
> /kisskb/src/net/mac80211/tx.c:4435:17,
> inlined from 'ieee80211_subif_start_xmit' at
> /kisskb/src/net/mac80211/tx.c:4483:3:
>
> mipsel-gcc5/mips-allmodconfig
>
> + /kisskb/src/include/linux/compiler_types.h: error: call to
> '__compiletime_assert_262' declared with attribute error: Unsupported access
> size for {READ,WRITE}_ONCE().: => 358:45
> + /kisskb/src/include/linux/compiler_types.h: error: call to
> '__compiletime_assert_263' declared with attribute error: Unsupported access
> size for {READ,WRITE}_ONCE().: => 358:45
>
> In function 'follow_pmd_mask',
> inlined from 'follow_pud_mask' at /kisskb/src/mm/gup.c:735:9,
> inlined from 'follow_p4d_mask' at /kisskb/src/mm/gup.c:752:9,
> inlined from 'follow_page_mask' at /kisskb/src/mm/gup.c:809:9:
>
> sh4-gcc11/sh-defconfig (Günter wondered if pmd_t should use union)
>
> + /kisskb/src/include/linux/fortify-string.h: error: '__builtin_memcpy'
> offset [0, 127] is out of the bounds [0, 0] [-Werror=array-bounds]: => 57:33
>
> /kisskb/src/arch/s390/kernel/setup.c: In function 'setup_lowcore_dat_on':
> s390x-gcc11/s390-all{mod,yes}config
>
> + /kisskb/src/include/linux/fortify-string.h: error: '__builtin_memset'
> pointer overflow between offset [28, 898293814] and size [-898293787, -1]
> [-Werror=array-bounds]: => 59:33
>
> /kisskb/src/fs/f2fs/inline.c: In function 'f2fs_move_inline_dirents':
>
> powerpc-gcc11/ppc64_book3e_allmodconfig
> powerpc-gcc11/powerpc-all{mod,yes}config
>
> + /kisskb/src/kernel/kcsan/kcsan_test.c: error: the frame size of 1680
> bytes is larger than 1536 bytes [-Werror=frame-larger-than=]: => 257:1
>
> xtensa-gcc11/xtensa-allmodconfig (patch available)
>
> + {standard input}: Error: unknown pseudo-op: `.cfi_def_c': => 1718
>
> sh4-gcc11/sh-allmodconfig (ICE = internal compiler error)
>
> > [1]
> > http://kisskb.ellerman.id.au/kisskb/branch/linus/head/1b929c02afd37871d5afb9d498426f83432e71c2/
> > (all 152 configs)
> > [2]
> > http://kisskb.ellerman.id.au/kisskb/branch/linus/head/830b3c68c1fb1e9176028d02ef86f3cf76aa2476/
> > (all 152 configs)
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> ge...@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
