From: Kees Cook <keescook@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: Allen Pais <apais@linux.microsoft.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Vijay Nag <nagvijay@microsoft.com>
Subject: Re: [linux-next:master 11772/12060] fs/coredump.c:67:27: warning: unused variable 'core_file_note_size_min'
Date: Wed, 8 May 2024 09:53:34 -0700 [thread overview]
Message-ID: <202405080953.5E9B78A9CA@keescook> (raw)
In-Reply-To: <202405081838.tuETPvPf-lkp@intel.com>
On Wed, May 08, 2024 at 06:30:25PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: e7b4ef8fffaca247809337bb78daceb406659f2d
> commit: 13513eafc3ea08cdb70aebe56a7e43083302a809 [11772/12060] fs/coredump: Enable dynamic configuration of max file note size
> config: i386-buildonly-randconfig-005-20240508 (https://download.01.org/0day-ci/archive/20240508/202405081838.tuETPvPf-lkp@intel.com/config)
> compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240508/202405081838.tuETPvPf-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/202405081838.tuETPvPf-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> fs/coredump.c:67:27: warning: unused variable 'core_file_note_size_min' [-Wunused-const-variable]
> 67 | static const unsigned int core_file_note_size_min = CORE_FILE_NOTE_SIZE_DEFAULT;
> | ^~~~~~~~~~~~~~~~~~~~~~~
> fs/coredump.c:68:27: warning: unused variable 'core_file_note_size_max' [-Wunused-const-variable]
> 68 | static const unsigned int core_file_note_size_max = CORE_FILE_NOTE_SIZE_MAX;
> | ^~~~~~~~~~~~~~~~~~~~~~~
> 2 warnings generated.
Thanks. I folded in a fix to move these under CONFIG_SYSCTL.
-Kees
--
Kees Cook
prev parent reply other threads:[~2024-05-08 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 10:30 [linux-next:master 11772/12060] fs/coredump.c:67:27: warning: unused variable 'core_file_note_size_min' kernel test robot
2024-05-08 16:53 ` Kees Cook [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=202405080953.5E9B78A9CA@keescook \
--to=keescook@chromium.org \
--cc=apais@linux.microsoft.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nagvijay@microsoft.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).