From: kernel test robot <lkp@intel.com>
To: Fullway Wang <fullwaywang@outlook.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>,
Christian Brauner <brauner@kernel.org>
Subject: [brauner-vfs:vfs.misc 9/10] fs/romfs/storage.c:243:22: error: use of undeclared identifier 'buflen'
Date: Sat, 20 Jan 2024 12:52:38 +0800 [thread overview]
Message-ID: <202401201224.8iFVwFru-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.misc
head: 31081ab305a184c2685e701ee1a8ca33b76bf7eb
commit: 530041d36e377a71958148b25b98ac217ff50419 [9/10] fs: romfs: Fix potential uninitialized memory leak
config: i386-buildonly-randconfig-003-20240120 (https://download.01.org/0day-ci/archive/20240120/202401201224.8iFVwFru-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240120/202401201224.8iFVwFru-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/202401201224.8iFVwFru-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/romfs/storage.c:243:22: error: use of undeclared identifier 'buflen'
243 | if (pos >= limit || buflen > limit - pos)
| ^
1 error generated.
vim +/buflen +243 fs/romfs/storage.c
233
234 /*
235 * determine the length of a string in romfs
236 */
237 ssize_t romfs_dev_strnlen(struct super_block *sb,
238 unsigned long pos, size_t maxlen)
239 {
240 size_t limit;
241
242 limit = romfs_maxsize(sb);
> 243 if (pos >= limit || buflen > limit - pos)
244 return -EIO;
245
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-20 4:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202401201224.8iFVwFru-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=fullwaywang@outlook.com \
--cc=llvm@lists.linux.dev \
--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