From: kbuild test robot <lkp@intel.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [gfs2:gfs2-iopen 15/15] fs/gfs2/glock.c:687:6: sparse: sparse: symbol '__gfs2_inode_remember_delete' was not declared. Should it be static?
Date: Sat, 25 Jan 2020 08:17:39 +0800 [thread overview]
Message-ID: <202001250859.Hrvdf2d0%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git gfs2-iopen
head: 90a0918fc357b78974088d4dc80de1448d8f135a
commit: 90a0918fc357b78974088d4dc80de1448d8f135a [15/15] DEBUG
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-153-g47b6dfef-dirty
git checkout 90a0918fc357b78974088d4dc80de1448d8f135a
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/gfs2/glock.c:687:6: sparse: sparse: symbol '__gfs2_inode_remember_delete' was not declared. Should it be static?
fs/gfs2/glock.h:172:36: sparse: sparse: context imbalance in '__gfs2_glock_put' - unexpected unlock
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
arch/x86/include/asm/bitops.h:77:37: sparse: sparse: cast truncates bits from constant value (ffffff7f becomes 7f)
fs/gfs2/glock.c:834:13: sparse: sparse: context imbalance in 'glock_work_func' - different lock contexts for basic block
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all at lists.01.org Intel Corporation
next reply other threads:[~2020-01-25 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 0:17 kbuild test robot [this message]
2020-01-25 0:17 ` [Cluster-devel] [RFC PATCH gfs2] __gfs2_inode_remember_delete() can be static kbuild test robot
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=202001250859.Hrvdf2d0%lkp@intel.com \
--to=lkp@intel.com \
/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).