From: Kees Cook <keescook@chromium.org>
To: kbuild-all@lists.01.org
Subject: Re: [kees:for-next/pstore 8/35] fs//pstore/inode.c:288:16: warning: no previous prototype for function 'psinfo_lock_root'
Date: Sat, 30 May 2020 10:34:47 -0700 [thread overview]
Message-ID: <202005301034.C76C7F9@keescook> (raw)
In-Reply-To: <202005301645.xhmuTeZu%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2448 bytes --]
On Sat, May 30, 2020 at 04:38:48PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore
> head: 3e01c33ced486b6ba180486f828b2b317c0fda01
> commit: 6bcaa233a90ba3be98a6093cf346ac51eb05258f [8/35] pstore: Add locking around superblock changes
> config: x86_64-randconfig-a015-20200529 (attached as .config)
> compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2d068e534f1671459e1b135852c1b3c10502e929)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install x86_64 cross compiling tool for clang build
> # apt-get install binutils-x86-64-linux-gnu
> git checkout 6bcaa233a90ba3be98a6093cf346ac51eb05258f
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
>
> >> fs//pstore/inode.c:288:16: warning: no previous prototype for function 'psinfo_lock_root' [-Wmissing-prototypes]
> struct dentry *psinfo_lock_root(void)
> ^
> fs//pstore/inode.c:288:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
> struct dentry *psinfo_lock_root(void)
> ^
> static
> 1 warning generated.
>
> vim +/psinfo_lock_root +288 fs//pstore/inode.c
>
> 287
> > 288 struct dentry *psinfo_lock_root(void)
Thanks! Yes, this should be static. Fixed now.
-Kees
> 289 {
> 290 struct dentry *root;
> 291
> 292 mutex_lock(&pstore_sb_lock);
> 293 /*
> 294 * Having no backend is fine -- no records appear.
> 295 * Not being mounted is fine -- nothing to do.
> 296 */
> 297 if (!psinfo || !pstore_sb) {
> 298 mutex_unlock(&pstore_sb_lock);
> 299 return NULL;
> 300 }
> 301
> 302 root = pstore_sb->s_root;
> 303 inode_lock(d_inode(root));
> 304 mutex_unlock(&pstore_sb_lock);
> 305
> 306 return root;
> 307 }
> 308
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
--
Kees Cook
prev parent reply other threads:[~2020-05-30 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 8:38 [kees:for-next/pstore 8/35] fs//pstore/inode.c:288:16: warning: no previous prototype for function 'psinfo_lock_root' kbuild test robot
2020-05-30 17:34 ` 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=202005301034.C76C7F9@keescook \
--to=keescook@chromium.org \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.