From: Doug Anderson <dianders@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 6492/7272] kernel/watchdog.c:111:12: warning: 'hardlockup_all_cpu_backtrace_proc_handler' defined but not used
Date: Fri, 4 Aug 2023 07:09:14 -0700 [thread overview]
Message-ID: <CAD=FV=UjeDqVd6gCwk68WWdLXw8p2cBk9Q9RqCtdmcC3NCJhGQ@mail.gmail.com> (raw)
In-Reply-To: <202308041501.2T8kM1gb-lkp@intel.com>
Hi,
On Fri, Aug 4, 2023 at 12:19 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: bdffb18b5dd8071cd25685b966f380a30b1fadaa
> commit: 838b3b76220d5b1bc53e4186d8936c5ec6810bf0 [6492/7272] watchdog/hardlockup: avoid large stack frames in watchdog_hardlockup_check()
> config: x86_64-randconfig-x012-20230731 (https://download.01.org/0day-ci/archive/20230804/202308041501.2T8kM1gb-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce: (https://download.01.org/0day-ci/archive/20230804/202308041501.2T8kM1gb-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202308041501.2T8kM1gb-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> kernel/watchdog.c:111:12: warning: 'hardlockup_all_cpu_backtrace_proc_handler' defined but not used [-Wunused-function]
> 111 | static int hardlockup_all_cpu_backtrace_proc_handler(struct ctl_table *table, int write,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> vim +/hardlockup_all_cpu_backtrace_proc_handler +111 kernel/watchdog.c
>
> 110
> > 111 static int hardlockup_all_cpu_backtrace_proc_handler(struct ctl_table *table, int write,
Leaving breadcrumbs here. The expected plan to fix this is to replace
the v2 patch with v4:
https://lore.kernel.org/r/20230804065935.v4.2.I501ab68cb926ee33a7c87e063d207abf09b9943c@changeid/
-Doug
prev parent reply other threads:[~2023-08-04 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 7:18 kernel test robot
2023-08-04 14:09 ` Doug Anderson [this message]
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='CAD=FV=UjeDqVd6gCwk68WWdLXw8p2cBk9Q9RqCtdmcC3NCJhGQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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