From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jlayton:nfs-client-leak 2/8] fs/nfs/pnfs.c:565:30: error: no member named 'pls_tracker' in 'struct pnfs_layout_segment'
Date: Wed, 7 May 2025 17:01:09 +0800 [thread overview]
Message-ID: <202505071627.0GqP7WYb-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git nfs-client-leak
head: 6af305fb6b4bb0b9b5330286b4c66daf076b1145
commit: e805e02639509963455233d10a03edf7cbd38ee9 [2/8] nfs: add refcount tracking to pnfs_layout_segment
config: arm-defconfig (https://download.01.org/0day-ci/archive/20250507/202505071627.0GqP7WYb-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505071627.0GqP7WYb-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/202505071627.0GqP7WYb-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/nfs/pnfs.c:565:30: error: no member named 'pls_tracker' in 'struct pnfs_layout_segment'
565 | ref_tracker_dir_init(&lseg->pls_tracker, 128, "pnfs_layout_segment");
| ~~~~ ^
fs/nfs/pnfs.c:573:31: error: no member named 'pls_tracker' in 'struct pnfs_layout_segment'
573 | ref_tracker_dir_exit(&lseg->pls_tracker);
| ~~~~ ^
fs/nfs/pnfs.c:2599:30: error: no member named 'pls_tracker' in 'struct pnfs_layout_segment'
2599 | ref_tracker_dir_exit(&lseg->pls_tracker);
| ~~~~ ^
3 errors generated.
vim +565 fs/nfs/pnfs.c
551
552 static void
553 pnfs_init_lseg(struct pnfs_layout_hdr *lo, struct pnfs_layout_segment *lseg,
554 const struct pnfs_layout_range *range,
555 const nfs4_stateid *stateid)
556 {
557 INIT_LIST_HEAD(&lseg->pls_list);
558 INIT_LIST_HEAD(&lseg->pls_lc_list);
559 INIT_LIST_HEAD(&lseg->pls_commits);
560 refcount_set(&lseg->pls_refcount, 1);
561 set_bit(NFS_LSEG_VALID, &lseg->pls_flags);
562 lseg->pls_layout = lo;
563 lseg->pls_range = *range;
564 lseg->pls_seq = be32_to_cpu(stateid->seqid);
> 565 ref_tracker_dir_init(&lseg->pls_tracker, 128, "pnfs_layout_segment");
566 }
567
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-07 9:01 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=202505071627.0GqP7WYb-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--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