mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PROBLEM linux-next] make randconfig: kernel/kallsyms.c:492:17: error: ‘strcpy’ source argument is the same as destination [-Werror=restrict]
Date: Thu, 27 Jun 2024 20:50:00 +0200	[thread overview]
Message-ID: <a40298f8-fedd-46bd-97c9-9c2775bda17a@gmail.com> (raw)

Hi all,

On vanilla linux-next 20240627 tree, there appears to be something od with this KCONFIG_SEED=0x6C165C4C.

This construct should prevent the kernel/kallsyms.c:492:17: error: ‘strcpy’ source argument is the same as destination
error, so I am perplexed?

491         if (name != buffer)
492                 strcpy(buffer, name);



$ time nice make -j 36 bindeb-pkg |& tee ../err-6.10-rc5-next-20240627-02.log; date
  GEN     debian
dpkg-buildpackage --build=binary --no-pre-clean --unsigned-changes -R'make -f debian/rules' -j1 -a$(cat debian/arch)
dpkg-buildpackage: info: source package linux-upstream
dpkg-buildpackage: info: source version 6.10.0-rc5-3
dpkg-buildpackage: info: source distribution jammy
dpkg-buildpackage: info: source changed by marvin <marvin@defiant>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 make -f debian/rules binary
#
# No change to .config
#
mkdir -p /home/marvin/linux/kernel/linux-next/tools/objtool && make O=/home/marvin/linux/kernel/linux-next subdir=tools/objtool --no-print-directory -C objtool 
  INSTALL libsubcmd_headers
  CALL    scripts/checksyscalls.sh
  UPD     init/utsversion-tmp.h
  CC      init/version.o
  AR      init/built-in.a
  CC      kernel/kallsyms.o
  CC      kernel/kallsyms_selftest.o
  CC      kernel/vmcore_info.o
  CC      kernel/elfcorehdr.o
  CC      kernel/crash_reserve.o
  CC      kernel/kexec_core.o
  CC      kernel/crash_core.o
  CC      kernel/kexec_file.o
  UPD     kernel/config_data
  CC      kernel/kprobes.o
  CC      kernel/hung_task.o
  CC      kernel/seccomp.o
  CC      kernel/tracepoint.o
  CC      kernel/irq_work.o
  CC      kernel/static_call.o
  CC      kernel/static_call_inline.o
  CC      kernel/context_tracking.o
  CC      kernel/torture.o
  CC      kernel/iomem.o
  CC      kernel/rseq.o
  CC      kernel/watch_queue.o
  GZIP    kernel/config_data.gz
  CC      kernel/configs.o
kernel/kallsyms.c: In function ‘__sprint_symbol.constprop’:
kernel/kallsyms.c:492:17: error: ‘strcpy’ source argument is the same as destination [-Werror=restrict]
  492 |                 strcpy(buffer, name);
      |                 ^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[6]: *** [scripts/Makefile.build:244: kernel/kallsyms.o] Error 1
make[6]: *** Waiting for unfinished jobs....
make[5]: *** [scripts/Makefile.build:485: kernel] Error 2
make[4]: *** [Makefile:1934: .] Error 2
make[3]: *** [debian/rules:74: build-arch] Error 2
dpkg-buildpackage: error: make -f debian/rules binary subprocess returned exit status 2
make[2]: *** [scripts/Makefile.package:121: bindeb-pkg] Error 2
make[1]: *** [/home/marvin/linux/kernel/linux-next/Makefile:1555: bindeb-pkg] Error 2
make: *** [Makefile:240: __sub-make] Error 2

real	0m2.962s
user	0m12.970s
sys	0m5.293s
Thu Jun 27 20:42:38 CEST 2024
$ 

Hope this helps.

Best regards,
Mirsad Todorovac

                 reply	other threads:[~2024-06-27 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a40298f8-fedd-46bd-97c9-9c2775bda17a@gmail.com \
    --to=mtodorovac69@gmail.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®