From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Brian Norris <briannorris@chromium.org>,
Grant Grundler <grundler@chromium.org>
Subject: [jsarha:topic/cros-sof-v4.14 8447/9354] kernel/panic.c:591:6: warning: no previous declaration for '__warn_printk'
Date: Fri, 17 Jun 2022 23:55:20 +0800 [thread overview]
Message-ID: <202206172352.f6AzDAj9-lkp@intel.com> (raw)
tree: https://github.com/jsarha/linux topic/cros-sof-v4.14
head: 6f750b16c322c9191168a3a97c427c90581d9144
commit: c4256ec7a28ebcf4371230422dceae6befc40836 [8447/9354] UPSTREAM: bug: fix "cut here" location for __WARN_TAINT architectures
config: i386-tinyconfig (https://download.01.org/0day-ci/archive/20220617/202206172352.f6AzDAj9-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
# https://github.com/jsarha/linux/commit/c4256ec7a28ebcf4371230422dceae6befc40836
git remote add jsarha https://github.com/jsarha/linux
git fetch --no-tags jsarha topic/cros-sof-v4.14
git checkout c4256ec7a28ebcf4371230422dceae6befc40836
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
kernel/panic.c:61:13: warning: no previous declaration for 'panic_smp_self_stop' [-Wmissing-declarations]
void __weak panic_smp_self_stop(void)
^~~~~~~~~~~~~~~~~~~
kernel/panic.c:71:13: warning: no previous declaration for 'nmi_panic_self_stop' [-Wmissing-declarations]
void __weak nmi_panic_self_stop(struct pt_regs *regs)
^~~~~~~~~~~~~~~~~~~
kernel/panic.c:82:13: warning: no previous declaration for 'crash_smp_send_stop' [-Wmissing-declarations]
void __weak crash_smp_send_stop(void)
^~~~~~~~~~~~~~~~~~~
kernel/panic.c:516:6: warning: no previous declaration for '__warn' [-Wmissing-declarations]
void __warn(const char *file, int line, void *caller, unsigned taint,
^~~~~~
kernel/panic.c: In function '__warn':
kernel/panic.c:533:3: warning: function '__warn' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
vprintk(args->fmt, args->args);
^~~~~~~
kernel/panic.c: At top level:
>> kernel/panic.c:591:6: warning: no previous declaration for '__warn_printk' [-Wmissing-declarations]
void __warn_printk(const char *fmt, ...)
^~~~~~~~~~~~~
kernel/panic.c: In function '__warn_printk':
kernel/panic.c:598:2: warning: function '__warn_printk' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
vprintk(fmt, args);
^~~~~~~
vim +/__warn_printk +591 kernel/panic.c
583
584 void warn_slowpath_null(const char *file, int line)
585 {
586 pr_warn(CUT_HERE);
587 __warn(file, line, __builtin_return_address(0), TAINT_WARN, NULL, NULL);
588 }
589 EXPORT_SYMBOL(warn_slowpath_null);
590 #else
> 591 void __warn_printk(const char *fmt, ...)
592 {
593 va_list args;
594
595 pr_warn(CUT_HERE);
596
597 va_start(args, fmt);
598 vprintk(fmt, args);
599 va_end(args);
600 }
601 EXPORT_SYMBOL(__warn_printk);
602 #endif
603
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-17 17:34 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=202206172352.f6AzDAj9-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=briannorris@chromium.org \
--cc=grundler@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).