public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/101941] [12 Regression] Linux kernel build failure due to retaining fnsplit fragment with __attribute__((__error__)) Date: Thu, 13 Jan 2022 14:23:16 +0000 [thread overview] Message-ID: <bug-101941-4-Xdky76I3Cd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101941-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101941 --- Comment #26 from Martin Liška <marxin at gcc dot gnu.org> --- I've just rebuilt kernel-default package from openSUSE:Factory with the following config: https://gist.githubusercontent.com/marxin/d5373a0dd6ab35233a47a25337e73dc5/raw/d2c810d2d32104619b57b6f1d118d052302c519f/.config and there's one more compilation error for fs/lockd/svclock.c: gcc fs_lockd_svclock.i -c -O2 In file included from ./include/linux/string.h:253, from ./include/linux/bitmap.h:10, from ./include/linux/cpumask.h:12, from ./arch/x86/include/asm/cpumask.h:5, from ./arch/x86/include/asm/msr.h:11, from ./arch/x86/include/asm/processor.h:22, from ./arch/x86/include/asm/cpufeature.h:5, from ./arch/x86/include/asm/thread_info.h:53, from ./include/linux/thread_info.h:60, from ./arch/x86/include/asm/preempt.h:7, from ./include/linux/preempt.h:78, from ./include/linux/spinlock.h:55, from ./include/linux/mmzone.h:8, from ./include/linux/gfp.h:6, from ./include/linux/slab.h:15, from fs/lockd/svclock.c:25: In function ‘strcpy’, inlined from ‘nlmdbg_cookie2a’ at fs/lockd/svclock.c:74:4, inlined from ‘nlmsvc_lookup_block’ at fs/lockd/svclock.c:157:721: ./include/linux/fortify-string.h:319:17: error: call to ‘__write_overflow’ declared with attribute error: detected write beyond size of object (1st parameter) 319 | __write_overflow(); | ^~~~~~~~~~~~~~~~~~ In function ‘strcpy’, inlined from ‘nlmdbg_cookie2a’ at fs/lockd/svclock.c:74:4, inlined from ‘nlmsvc_find_block’ at fs/lockd/svclock.c:196:672, inlined from ‘nlmsvc_grant_reply’ at fs/lockd/svclock.c:963:16: ./include/linux/fortify-string.h:319:17: error: call to ‘__write_overflow’ declared with attribute error: detected write beyond size of object (1st parameter) 319 | __write_overflow(); | ^~~~~~~~~~~~~~~~~~ that started with r12-6030-g422f9eb7011b76c1.
next prev parent reply other threads:[~2022-01-13 14:23 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-16 22:36 [Bug ipa/101941] New: " dmalcolm at gcc dot gnu.org 2021-08-16 22:36 ` [Bug ipa/101941] " dmalcolm at gcc dot gnu.org 2021-08-16 22:50 ` pinskia at gcc dot gnu.org 2021-08-16 23:02 ` [Bug ipa/101941] [12 Regression] " dmalcolm at gcc dot gnu.org 2021-08-17 7:56 ` rguenth at gcc dot gnu.org 2021-08-18 13:47 ` dmalcolm at gcc dot gnu.org 2021-09-16 23:00 ` pinskia at gcc dot gnu.org 2021-09-17 8:47 ` jakub at gcc dot gnu.org 2021-09-17 8:53 ` jakub at gcc dot gnu.org 2021-09-20 8:18 ` dac324 at yahoo dot de 2021-11-15 9:37 ` pinskia at gcc dot gnu.org 2021-11-15 9:43 ` aldyh at gcc dot gnu.org 2021-11-15 10:00 ` pinskia at gcc dot gnu.org 2021-11-15 14:38 ` jakub at gcc dot gnu.org 2021-11-16 4:24 ` pinskia at gcc dot gnu.org 2021-11-16 5:07 ` pinskia at gcc dot gnu.org 2021-11-16 5:59 ` pinskia at gcc dot gnu.org 2021-11-16 6:14 ` pinskia at gcc dot gnu.org 2021-11-16 6:24 ` pinskia at gcc dot gnu.org 2021-11-16 10:04 ` hubicka at kam dot mff.cuni.cz 2021-11-16 10:23 ` jakub at gcc dot gnu.org 2021-11-16 10:41 ` hubicka at gcc dot gnu.org 2021-11-17 1:12 ` pinskia at gcc dot gnu.org 2021-11-17 3:10 ` pinskia at gcc dot gnu.org 2021-11-17 6:27 ` pinskia at gcc dot gnu.org 2022-01-12 14:17 ` dmalcolm at gcc dot gnu.org 2022-01-13 14:23 ` marxin at gcc dot gnu.org [this message] 2022-01-13 14:24 ` marxin at gcc dot gnu.org 2022-01-13 14:29 ` pinskia at gcc dot gnu.org 2022-01-13 15:01 ` siddhesh at gcc dot gnu.org 2022-01-18 10:36 ` cvs-commit at gcc dot gnu.org 2022-01-18 10:36 ` pinskia at gcc dot gnu.org
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=bug-101941-4-Xdky76I3Cd@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).