mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: kbuild-all@01.org,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Jeff Layton <jlayton@poochiereds.net>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stanislav Kinsbursky <skinsbursky@virtuozzo.com>,
	Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: Re: [PATCH] lockd: get rid of reference-counted NSM RPC clients
Date: Wed, 7 Oct 2015 19:31:23 +0800	[thread overview]
Message-ID: <201510071938.9dWoRRtf%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444215808-5995-1-git-send-email-aryabinin@virtuozzo.com>

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

Hi Andrey,

[auto build test WARNING on next-20151007 -- if it's inappropriate base, please ignore]

config: xtensa-allyesconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All warnings (new ones prefixed by >>):

   fs/lockd/mon.c: In function 'nsm_mon_unmon':
>> fs/lockd/mon.c:111:3: warning: format '%d' expects argument of type 'int', but argument 2 has type 'long int' [-Wformat=]
      dprintk("lockd: failed to create NSM upcall transport, "
      ^

vim +111 fs/lockd/mon.c

    95			.priv		= &nsm->sm_priv,
    96			.prog		= NLM_PROGRAM,
    97			.vers		= 3,
    98			.proc		= NLMPROC_NSM_NOTIFY,
    99			.mon_name	= nsm->sm_mon_name,
   100			.nodename	= host->nodename,
   101		};
   102		struct rpc_message msg = {
   103			.rpc_argp	= &args,
   104			.rpc_resp	= res,
   105		};
   106	
   107		memset(res, 0, sizeof(*res));
   108	
   109		clnt = nsm_create(host->net, host->nodename);
   110		if (IS_ERR(clnt)) {
 > 111			dprintk("lockd: failed to create NSM upcall transport, "
   112				"status=%d, net=%p\n", PTR_ERR(clnt), host->net);
   113			return PTR_ERR(clnt);
   114		}
   115	
   116		msg.rpc_proc = &clnt->cl_procinfo[proc];
   117		status = rpc_call_sync(clnt, &msg, RPC_TASK_SOFTCONN);
   118		if (status == -ECONNREFUSED) {
   119			dprintk("lockd:	NSM upcall RPC failed, status=%d, forcing rebind\n",

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 42875 bytes --]

      parent reply	other threads:[~2015-10-07 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 11:03 Andrey Ryabinin
2015-10-07 11:28 ` kbuild test robot
2015-10-07 11:39   ` [PATCH v2] " Andrey Ryabinin
2015-10-07 20:41     ` J. Bruce Fields
2015-10-07 21:45     ` Trond Myklebust
2015-10-08 12:16       ` J. Bruce Fields
2015-10-07 11:31 ` kbuild 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=201510071938.9dWoRRtf%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=anna.schumaker@netapp.com \
    --cc=aryabinin@virtuozzo.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@poochiereds.net \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@virtuozzo.com \
    --cc=trond.myklebust@primarydata.com \
    /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

all inboxes | Powered by JetHome®