From: kernel test robot <lkp@intel.com>
To: Sagi Grimberg <sagi@grimberg.me>, Chuck Lever <chuck.lever@oracle.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Dai Ngo <dai.ngo@oracle.com>, Olga Kornievskaia <aglo@umich.edu>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 3/3] nfsd: resolve possible conflicts of reads using special stateids and write delegations
Date: Mon, 29 Jul 2024 08:35:56 +0800 [thread overview]
Message-ID: <202407290814.7REsmaH7-lkp@intel.com> (raw)
In-Reply-To: <20240728204104.519041-4-sagi@grimberg.me>
Hi Sagi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.11-rc1 next-20240726]
[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/Sagi-Grimberg/nfsd-don-t-assume-copy-notify-when-preprocessing-the-stateid/20240729-044834
base: linus/master
patch link: https://lore.kernel.org/r/20240728204104.519041-4-sagi%40grimberg.me
patch subject: [PATCH v2 3/3] nfsd: resolve possible conflicts of reads using special stateids and write delegations
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240729/202407290814.7REsmaH7-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240729/202407290814.7REsmaH7-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/202407290814.7REsmaH7-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/nfsd/nfs4state.c:8826: warning: Excess function parameter 'inode' description in 'nfsd4_deleg_read_conflict'
>> fs/nfsd/nfs4state.c:8826: warning: Excess function parameter 'modified' description in 'nfsd4_deleg_read_conflict'
>> fs/nfsd/nfs4state.c:8826: warning: Excess function parameter 'size' description in 'nfsd4_deleg_read_conflict'
vim +8826 fs/nfsd/nfs4state.c
8805
8806 /**
8807 * nfsd4_deleg_read_conflict - Recall if read causes conflict
8808 * @rqstp: RPC transaction context
8809 * @clp: nfs client
8810 * @fhp: nfs file handle
8811 * @inode: file to be checked for a conflict
8812 * @modified: return true if file was modified
8813 * @size: new size of file if modified is true
8814 *
8815 * This function is called when there is a conflict between a write
8816 * delegation and a read that is using a special stateid where the
8817 * we cannot derive the client stateid exsistence. The server
8818 * must recall a conflicting delegation before allowing the read
8819 * to continue.
8820 *
8821 * Returns 0 if there is no conflict; otherwise an nfs_stat
8822 * code is returned.
8823 */
8824 __be32 nfsd4_deleg_read_conflict(struct svc_rqst *rqstp,
8825 struct nfs4_client *clp, struct svc_fh *fhp)
> 8826 {
8827 struct nfs4_file *fp;
8828 __be32 status = 0;
8829
8830 fp = nfsd4_file_hash_lookup(fhp);
8831 if (!fp)
8832 return nfs_ok;
8833
8834 spin_lock(&state_lock);
8835 spin_lock(&fp->fi_lock);
8836 if (!list_empty(&fp->fi_delegations) &&
8837 !nfs4_delegation_exists(clp, fp)) {
8838 /* conflict, recall deleg */
8839 status = nfserrno(nfsd_open_break_lease(fp->fi_inode,
8840 NFSD_MAY_READ));
8841 if (status)
8842 goto out;
8843 if (!nfsd_wait_for_delegreturn(rqstp, fp->fi_inode))
8844 status = nfserr_jukebox;
8845 }
8846 out:
8847 spin_unlock(&fp->fi_lock);
8848 spin_unlock(&state_lock);
8849 return status;
8850 }
8851
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-29 0:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 20:41 [PATCH v2 0/3] Offer write delegations for O_WRONLY opens Sagi Grimberg
2024-07-28 20:41 ` [PATCH v2 1/3] nfsd: don't assume copy notify when preprocessing the stateid Sagi Grimberg
2024-07-28 20:41 ` [PATCH v2 2/3] nfsd: Offer write delegations for o_wronly opens Sagi Grimberg
2024-07-29 12:10 ` Jeff Layton
2024-07-29 12:58 ` Sagi Grimberg
2024-07-29 13:10 ` Jeff Layton
2024-07-29 13:39 ` Sagi Grimberg
2024-07-29 13:52 ` Chuck Lever
2024-07-29 14:05 ` Sagi Grimberg
2024-07-29 14:10 ` Chuck Lever
2024-07-29 14:21 ` Jeff Layton
2024-07-29 14:12 ` Jeff Layton
2024-07-29 16:12 ` Dai Ngo
2024-07-30 18:45 ` Chuck Lever
2024-07-29 12:26 ` Jeff Layton
2024-07-29 12:59 ` Sagi Grimberg
2024-07-29 13:17 ` Jeff Layton
2024-07-29 13:37 ` Sagi Grimberg
2024-07-29 22:41 ` kernel test robot
2024-07-28 20:41 ` [PATCH v2 3/3] nfsd: resolve possible conflicts of reads using special stateids and write delegations Sagi Grimberg
2024-07-29 0:35 ` kernel test robot [this message]
2024-07-29 6:22 ` Sagi Grimberg
2024-07-29 7:55 ` Miguel Ojeda
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=202407290814.7REsmaH7-lkp@intel.com \
--to=lkp@intel.com \
--cc=aglo@umich.edu \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sagi@grimberg.me \
/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