All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: oe-kbuild-all@lists.linux.dev, Chuck Lever <cel@kernel.org>
Subject: [cel:nfsd-testing 166/231] include/linux/rcupdate.h:525:36: error: dereferencing pointer to incomplete type 'struct nfsd_file'
Date: Wed, 24 Jun 2026 07:11:57 +0800	[thread overview]
Message-ID: <202606240755.8PVHHD1Q-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux nfsd-testing
head:   2bb83225da8ee0383d17783b5c903589696faf90
commit: f2be51ec3aba541721c2baa65d272553d0fe961c [166/231] NFS/localio: fix ref leak on nfs_uuid_add_file failure
config: sparc-randconfig-002-20260624 (https://download.01.org/0day-ci/archive/20260624/202606240755.8PVHHD1Q-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260624/202606240755.8PVHHD1Q-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/202606240755.8PVHHD1Q-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/rbtree.h:24,
                    from include/linux/mm_types.h:11,
                    from include/linux/mmzone.h:22,
                    from include/linux/gfp.h:7,
                    from include/linux/umh.h:4,
                    from include/linux/kmod.h:9,
                    from include/linux/module.h:18,
                    from fs/nfs_common/nfslocalio.c:7:
   fs/nfs_common/nfslocalio.c: In function 'nfs_open_local_fh':
>> include/linux/rcupdate.h:525:36: error: dereferencing pointer to incomplete type 'struct nfsd_file'
    #define RCU_INITIALIZER(v) (typeof(*(v)) __force __rcu *)(v)
                                       ^~~~
   fs/nfs_common/nfslocalio.c:305:33: note: in expansion of macro 'RCU_INITIALIZER'
      struct nfsd_file __rcu *tmp = RCU_INITIALIZER(localio);
                                    ^~~~~~~~~~~~~~~


vim +525 include/linux/rcupdate.h

ca5ecddfa8fcbd Paul E. McKenney 2010-04-28  520  
462225ae47d717 Paul E. McKenney 2013-11-11  521  /**
462225ae47d717 Paul E. McKenney 2013-11-11  522   * RCU_INITIALIZER() - statically initialize an RCU-protected global variable
462225ae47d717 Paul E. McKenney 2013-11-11  523   * @v: The value to statically initialize with.
462225ae47d717 Paul E. McKenney 2013-11-11  524   */
462225ae47d717 Paul E. McKenney 2013-11-11 @525  #define RCU_INITIALIZER(v) (typeof(*(v)) __force __rcu *)(v)
462225ae47d717 Paul E. McKenney 2013-11-11  526  

:::::: The code at line 525 was first introduced by commit
:::::: 462225ae47d7175f886281d8a91708550cd5178c rcu: Add an RCU_INITIALIZER for global RCU-protected pointers

:::::: TO: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
:::::: CC: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-06-23 23:12 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=202606240755.8PVHHD1Q-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cel@kernel.org \
    --cc=chris.mason@fusionio.com \
    --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 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.