linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: trondmy@kernel.org, Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: kbuild-all@lists.01.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] NFSv4: Use the net namespace uniquifier if it is set
Date: Thu, 8 Oct 2020 06:40:55 +0800	[thread overview]
Message-ID: <202010080658.utCvACPj-lkp@intel.com> (raw)
In-Reply-To: <20201007210720.537880-3-trondmy@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]

Hi,

I love your patch! Perhaps something to improve:

[auto build test WARNING on nfs/linux-next]
[also build test WARNING on v5.9-rc8 next-20201007]
[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]

url:    https://github.com/0day-ci/linux/commits/trondmy-kernel-org/Give-containers-a-unique-client-id/20201008-050958
base:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
config: s390-randconfig-s032-20201008 (attached as .config)
compiler: s390-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.2-218-gc0e96d6d-dirty
        # https://github.com/0day-ci/linux/commit/440cb74f8b835271bd5e1f6574dc9cb002cec5be
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review trondmy-kernel-org/Give-containers-a-unique-client-id/20201008-050958
        git checkout 440cb74f8b835271bd5e1f6574dc9cb002cec5be
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=s390 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

echo
echo "sparse warnings: (new ones prefixed by >>)"
echo
>> fs/nfs/nfs4proc.c:6022:22: sparse: sparse: incompatible types in comparison expression (different address spaces):
>> fs/nfs/nfs4proc.c:6022:22: sparse:    char const [noderef] __rcu *
>> fs/nfs/nfs4proc.c:6022:22: sparse:    char const *

vim +6022 fs/nfs/nfs4proc.c

  6009	
  6010	static size_t
  6011	nfs4_get_uniquifier(struct nfs_client *clp, char *buf, size_t buflen)
  6012	{
  6013		struct nfs_net *nn = net_generic(clp->cl_net, nfs_net_id);
  6014		struct nfs_netns_client *nn_clp = nn->nfs_client;
  6015		const char *id;
  6016		size_t len;
  6017	
  6018		buf[0] = '\0';
  6019	
  6020		if (nn_clp) {
  6021			rcu_read_lock();
> 6022			id = rcu_dereference(nn_clp->identifier);
  6023			if (id && *id != '\0')
  6024				len = strlcpy(buf, id, buflen);
  6025			rcu_read_unlock();
  6026			if (len)
  6027				return len;
  6028		}
  6029	
  6030		if (nfs4_client_id_uniquifier[0] != '\0')
  6031			return strlcpy(buf, nfs4_client_id_uniquifier, buflen);
  6032		return 0;
  6033	}
  6034	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 20942 bytes --]

      parent reply	other threads:[~2020-10-07 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 21:07 [PATCH 0/2] Give containers a unique client id trondmy
2020-10-07 21:07 ` [PATCH 1/2] NFSv4: Clean up initialisation of uniquified client id strings trondmy
2020-10-07 21:07   ` [PATCH 2/2] NFSv4: Use the net namespace uniquifier if it is set trondmy
2020-10-07 21:25     ` J. Bruce Fields
2020-10-07 21:34       ` Trond Myklebust
2020-10-07 21:45         ` bfields
2020-10-07 22:02     ` Dai Ngo
2020-10-07 22:28       ` Trond Myklebust
2020-10-07 22:40     ` 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=202010080658.utCvACPj-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-nfs@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).