From: kernel test robot <lkp@intel.com>
To: Yangtao Li <frank.li@vivo.com>,
slava@dubeyko.com, glaubitz@physik.fu-berlin.de
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfs: export dbg_flags in debugfs
Date: Thu, 8 May 2025 21:26:18 +0800 [thread overview]
Message-ID: <202505082102.YBG1Di7L-lkp@intel.com> (raw)
In-Reply-To: <20250507145550.425303-1-frank.li@vivo.com>
Hi Yangtao,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on linus/master v6.15-rc5 next-20250508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yangtao-Li/hfs-export-dbg_flags-in-debugfs/20250507-224016
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20250507145550.425303-1-frank.li%40vivo.com
patch subject: [PATCH] hfs: export dbg_flags in debugfs
config: m68k-defconfig (https://download.01.org/0day-ci/archive/20250508/202505082102.YBG1Di7L-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505082102.YBG1Di7L-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/202505082102.YBG1Di7L-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/hfs/bnode.c: In function 'hfs_bnode_dump':
>> fs/hfs/bnode.c:176:29: warning: variable 'tmp' set but not used [-Wunused-but-set-variable]
176 | int tmp;
| ^~~
At top level:
cc1: note: unrecognized command-line option '-Wno-unterminated-string-initialization' may have been intended to silence earlier diagnostics
vim +/tmp +176 fs/hfs/bnode.c
^1da177e4c3f415 Linus Torvalds 2005-04-16 147
^1da177e4c3f415 Linus Torvalds 2005-04-16 148 void hfs_bnode_dump(struct hfs_bnode *node)
^1da177e4c3f415 Linus Torvalds 2005-04-16 149 {
^1da177e4c3f415 Linus Torvalds 2005-04-16 150 struct hfs_bnode_desc desc;
^1da177e4c3f415 Linus Torvalds 2005-04-16 151 __be32 cnid;
^1da177e4c3f415 Linus Torvalds 2005-04-16 152 int i, off, key_off;
^1da177e4c3f415 Linus Torvalds 2005-04-16 153
c2b3e1f76e5c902 Joe Perches 2013-04-30 154 hfs_dbg(BNODE_MOD, "bnode: %d\n", node->this);
^1da177e4c3f415 Linus Torvalds 2005-04-16 155 hfs_bnode_read(node, &desc, 0, sizeof(desc));
c2b3e1f76e5c902 Joe Perches 2013-04-30 156 hfs_dbg(BNODE_MOD, "%d, %d, %d, %d, %d\n",
^1da177e4c3f415 Linus Torvalds 2005-04-16 157 be32_to_cpu(desc.next), be32_to_cpu(desc.prev),
^1da177e4c3f415 Linus Torvalds 2005-04-16 158 desc.type, desc.height, be16_to_cpu(desc.num_recs));
^1da177e4c3f415 Linus Torvalds 2005-04-16 159
^1da177e4c3f415 Linus Torvalds 2005-04-16 160 off = node->tree->node_size - 2;
^1da177e4c3f415 Linus Torvalds 2005-04-16 161 for (i = be16_to_cpu(desc.num_recs); i >= 0; off -= 2, i--) {
^1da177e4c3f415 Linus Torvalds 2005-04-16 162 key_off = hfs_bnode_read_u16(node, off);
c2b3e1f76e5c902 Joe Perches 2013-04-30 163 hfs_dbg_cont(BNODE_MOD, " %d", key_off);
^1da177e4c3f415 Linus Torvalds 2005-04-16 164 if (i && node->type == HFS_NODE_INDEX) {
^1da177e4c3f415 Linus Torvalds 2005-04-16 165 int tmp;
^1da177e4c3f415 Linus Torvalds 2005-04-16 166
^1da177e4c3f415 Linus Torvalds 2005-04-16 167 if (node->tree->attributes & HFS_TREE_VARIDXKEYS)
^1da177e4c3f415 Linus Torvalds 2005-04-16 168 tmp = (hfs_bnode_read_u8(node, key_off) | 1) + 1;
^1da177e4c3f415 Linus Torvalds 2005-04-16 169 else
^1da177e4c3f415 Linus Torvalds 2005-04-16 170 tmp = node->tree->max_key_len + 1;
c2b3e1f76e5c902 Joe Perches 2013-04-30 171 hfs_dbg_cont(BNODE_MOD, " (%d,%d",
c2b3e1f76e5c902 Joe Perches 2013-04-30 172 tmp, hfs_bnode_read_u8(node, key_off));
^1da177e4c3f415 Linus Torvalds 2005-04-16 173 hfs_bnode_read(node, &cnid, key_off + tmp, 4);
c2b3e1f76e5c902 Joe Perches 2013-04-30 174 hfs_dbg_cont(BNODE_MOD, ",%d)", be32_to_cpu(cnid));
^1da177e4c3f415 Linus Torvalds 2005-04-16 175 } else if (i && node->type == HFS_NODE_LEAF) {
^1da177e4c3f415 Linus Torvalds 2005-04-16 @176 int tmp;
^1da177e4c3f415 Linus Torvalds 2005-04-16 177
^1da177e4c3f415 Linus Torvalds 2005-04-16 178 tmp = hfs_bnode_read_u8(node, key_off);
c2b3e1f76e5c902 Joe Perches 2013-04-30 179 hfs_dbg_cont(BNODE_MOD, " (%d)", tmp);
^1da177e4c3f415 Linus Torvalds 2005-04-16 180 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 181 }
c2b3e1f76e5c902 Joe Perches 2013-04-30 182 hfs_dbg_cont(BNODE_MOD, "\n");
^1da177e4c3f415 Linus Torvalds 2005-04-16 183 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 184
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-08 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 14:55 [PATCH] hfs: export dbg_flags in debugfs Yangtao Li
2025-05-08 13:26 ` kernel test robot [this message]
2025-05-09 17:39 ` Viacheslav Dubeyko
2025-05-11 10:45 ` 回复: " 李扬韬
2025-05-15 1:22 ` Viacheslav Dubeyko
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=202505082102.YBG1Di7L-lkp@intel.com \
--to=lkp@intel.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=slava@dubeyko.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).