public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: trondmy@kernel.org, linux-nfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] NFS/pnfs: Fix the error path in pnfs_layoutreturn_retry_later_locked()
Date: Mon, 12 May 2025 04:59:27 +0800	[thread overview]
Message-ID: <202505120404.RyxNoBfS-lkp@intel.com> (raw)
In-Reply-To: <7a4abcb32bb29ad463638bf1d2d0600a3d9e357c.1746970073.git.trond.myklebust@hammerspace.com>

Hi,

kernel test robot noticed the following build errors:

[auto build test ERROR on trondmy-nfs/linux-next]
[also build test ERROR on linus/master v6.15-rc5 next-20250509]
[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/trondmy-kernel-org/NFS-pnfs-Fix-the-error-path-in-pnfs_layoutreturn_retry_later_locked/20250511-212905
base:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link:    https://lore.kernel.org/r/7a4abcb32bb29ad463638bf1d2d0600a3d9e357c.1746970073.git.trond.myklebust%40hammerspace.com
patch subject: [PATCH] NFS/pnfs: Fix the error path in pnfs_layoutreturn_retry_later_locked()
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20250512/202505120404.RyxNoBfS-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250512/202505120404.RyxNoBfS-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/202505120404.RyxNoBfS-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/nfs/pnfs.c: In function 'pnfs_layoutreturn_retry_later_locked':
>> fs/nfs/pnfs.c:1254:17: error: implicit declaration of function 'pnfs_reset_return_info'; did you mean 'pnfs_set_plh_return_info'? [-Wimplicit-function-declaration]
    1254 |                 pnfs_reset_return_info(lo);
         |                 ^~~~~~~~~~~~~~~~~~~~~~
         |                 pnfs_set_plh_return_info


vim +1254 fs/nfs/pnfs.c

  1245	
  1246	static void
  1247	pnfs_layoutreturn_retry_later_locked(struct pnfs_layout_hdr *lo,
  1248					     const nfs4_stateid *arg_stateid,
  1249					     const struct pnfs_layout_range *range,
  1250					     struct list_head *freeme)
  1251	{
  1252		if (pnfs_layout_is_valid(lo) &&
  1253		    nfs4_stateid_match_other(&lo->plh_stateid, arg_stateid))
> 1254			pnfs_reset_return_info(lo);
  1255		else
  1256			pnfs_mark_layout_stateid_invalid(lo, freeme);
  1257		pnfs_clear_layoutreturn_waitbit(lo);
  1258	}
  1259	

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

      reply	other threads:[~2025-05-11 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-11 13:28 [PATCH] NFS/pnfs: Fix the error path in pnfs_layoutreturn_retry_later_locked() trondmy
2025-05-11 20:59 ` kernel test robot [this message]

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=202505120404.RyxNoBfS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=trondmy@kernel.org \
    /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