From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: lucas.dimarchi@intel.com, linux-kernel@vger.kernel.org,
intel-xe@lists.freedesktop.org
Subject: Re: [BUG] allmodconfig build error in next-20240108
Date: Tue, 9 Jan 2024 09:57:57 +1100 [thread overview]
Message-ID: <20240109095757.1313b2d9@canb.auug.org.au> (raw)
In-Reply-To: <45ad1d0f-a10f-483e-848a-76a30252edbe@paulmck-laptop>
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
Hi Paul,
On Mon, 8 Jan 2024 13:33:36 -0800 "Paul E. McKenney" <paulmck@kernel.org> wrote:
>
> Recent -next trees get the following build error for allmodconfig builds:
>
> ------------------------------------------------------------------------
>
> drivers/gpu/drm/xe/xe_gt_pagefault.c: In function ‘xe_guc_pagefault_handler’:
> ./include/linux/fortify-string.h:57:33: error: writing 16 bytes into a region of size 0 [-Werror=stringop-overflow=]
> 57 | #define __underlying_memcpy __builtin_memcpy
> | ^
> ./include/linux/fortify-string.h:644:9: note: in expansion of macro ‘__underlying_memcpy’
> 644 | __underlying_##op(p, q, __fortify_size); \
> | ^~~~~~~~~~~~~
> ./include/linux/fortify-string.h:689:26: note: in expansion of macro ‘__fortify_memcpy_chk’
> 689 | #define memcpy(p, q, s) __fortify_memcpy_chk(p, q, s, \
> | ^~~~~~~~~~~~~~~~~~~~
> drivers/gpu/drm/xe/xe_gt_pagefault.c:340:17: note: in expansion of macro ‘memcpy’
> 340 | memcpy(pf_queue->data + pf_queue->tail, msg, len * sizeof(u32));
> | ^~~~~~
> In file included from drivers/gpu/drm/xe/xe_device_types.h:17,
> from drivers/gpu/drm/xe/xe_vm_types.h:16,
> from drivers/gpu/drm/xe/xe_bo.h:13,
> from drivers/gpu/drm/xe/xe_gt_pagefault.c:16:
> drivers/gpu/drm/xe/xe_gt_types.h:102:25: note: at offset [1144, 265324] into destination object ‘tile’ of size 8
> 102 | struct xe_tile *tile;
> |
Which architecture? What compiler and version? Anything special in your build
setup? I do x86_64 allmodconfig builds all day with gcc v13.2 and I don't see
this failure.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-08 22:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 21:33 [BUG] allmodconfig build error in next-20240108 Paul E. McKenney
2024-01-08 22:57 ` Stephen Rothwell [this message]
2024-01-08 23:15 ` Paul E. McKenney
2024-01-09 16:58 ` Lucas De Marchi
2024-01-09 21:11 ` Stephen Rothwell
2024-01-09 22:45 ` Paul E. McKenney
2024-01-09 22:58 ` Stephen Rothwell
2024-01-10 1:09 ` Lucas De Marchi
2024-01-10 3:46 ` Paul E. McKenney
2024-01-10 5:03 ` Stephen Rothwell
2024-01-10 10:26 ` Paul E. McKenney
2024-01-10 15:00 ` Lucas De Marchi
2024-01-10 15:18 ` Jani Nikula
2024-01-10 15:21 ` Lucas De Marchi
2024-01-10 16:00 ` Paul E. McKenney
2024-01-09 18:08 ` ✗ CI.Patch_applied: failure for " Patchwork
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=20240109095757.1313b2d9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.dimarchi@intel.com \
--cc=paulmck@kernel.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