mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: kbuild-all@01.org, Jeff Layton <jlayton@poochiereds.net>,
	bfields@fieldses.org, Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] fs/locks: Remove fl_nspid
Date: Thu, 8 Jun 2017 14:50:41 +0800	[thread overview]
Message-ID: <201706081429.wGkVsweB%fengguang.wu@intel.com> (raw)
In-Reply-To: <cffd6e4ae6b537a405e5692010606e5df8a08156.1496769145.git.bcodding@redhat.com>

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

Hi Benjamin,

[auto build test WARNING on jlayton/linux-next]
[also build test WARNING on next-20170607]
[cannot apply to linus/master linux/master v4.12-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Benjamin-Coddington/fs-locks-Use-allocation-rather-than-the-stack-in-fcntl_getlk/20170608-015328
base:   git://git.samba.org/jlayton/linux linux-next
reproduce: make htmldocs

All warnings (new ones prefixed by >>):

   fs/inode.c:1664: warning: No description found for parameter 'rcu'
>> fs/locks.c:2052: warning: No description found for parameter 'init_nr'
>> fs/locks.c:2052: warning: Excess function parameter 'nr' description in 'locks_translate_pid'
>> fs/locks.c:2052: warning: No description found for parameter 'init_nr'
>> fs/locks.c:2052: warning: Excess function parameter 'nr' description in 'locks_translate_pid'
   include/linux/jbd2.h:442: warning: No description found for parameter 'i_transaction'
   include/linux/jbd2.h:442: warning: No description found for parameter 'i_next_transaction'
   include/linux/jbd2.h:442: warning: No description found for parameter 'i_list'
   include/linux/jbd2.h:442: warning: No description found for parameter 'i_vfs_inode'
   include/linux/jbd2.h:442: warning: No description found for parameter 'i_flags'
   include/linux/jbd2.h:496: warning: No description found for parameter 'h_rsv_handle'
   include/linux/jbd2.h:496: warning: No description found for parameter 'h_reserved'
   include/linux/jbd2.h:496: warning: No description found for parameter 'h_type'
   include/linux/jbd2.h:496: warning: No description found for parameter 'h_line_no'
   include/linux/jbd2.h:496: warning: No description found for parameter 'h_start_jiffies'
   include/linux/jbd2.h:496: warning: No description found for parameter 'h_requested_credits'
   include/linux/jbd2.h:496: warning: No description found for parameter 'saved_alloc_context'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_chkpt_bhs'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_devname'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_average_commit_time'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_min_batch_time'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_max_batch_time'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_commit_callback'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_failed_commit'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_chksum_driver'
   include/linux/jbd2.h:1049: warning: No description found for parameter 'j_csum_seed'
   fs/jbd2/transaction.c:434: warning: No description found for parameter 'rsv_blocks'
   fs/jbd2/transaction.c:434: warning: No description found for parameter 'gfp_mask'
   fs/jbd2/transaction.c:434: warning: No description found for parameter 'type'
   fs/jbd2/transaction.c:434: warning: No description found for parameter 'line_no'
   fs/jbd2/transaction.c:511: warning: No description found for parameter 'type'
   fs/jbd2/transaction.c:511: warning: No description found for parameter 'line_no'
   fs/jbd2/transaction.c:641: warning: No description found for parameter 'gfp_mask'

vim +/init_nr +2052 fs/locks.c

  2036	{
  2037		if (filp->f_op->lock && is_remote_lock(filp))
  2038			return filp->f_op->lock(filp, F_GETLK, fl);
  2039		posix_test_lock(filp, fl);
  2040		return 0;
  2041	}
  2042	EXPORT_SYMBOL_GPL(vfs_test_lock);
  2043	
  2044	/**
  2045	 * locks_translate_pid - translate a pid number into a namespace
  2046	 * @nr: The pid number in the init_pid_ns
  2047	 * @ns: The namespace into which the pid should be translated
  2048	 *
  2049	 * Used to tranlate a fl_pid into a namespace virtual pid number
  2050	 */
  2051	static pid_t locks_translate_pid(int init_nr, struct pid_namespace *ns)
> 2052	{
  2053		pid_t vnr = 0;
  2054		struct task_struct *task;
  2055	
  2056		rcu_read_lock();
  2057		task = find_task_by_pid_ns(init_nr, &init_pid_ns);
  2058		if (task)
  2059			get_task_struct(task);
  2060		rcu_read_unlock();

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

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

  parent reply	other threads:[~2017-06-08  6:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 17:19 [PATCH 0/3 v3] Fixups for l_pid Benjamin Coddington
2017-06-06 17:19 ` [PATCH 1/3] fs/locks: Use allocation rather than the stack in fcntl_getlk() Benjamin Coddington
2017-06-06 17:19 ` [PATCH 2/3] fs/locks: Remove fl_nspid Benjamin Coddington
2017-06-06 18:00   ` Jeff Layton
2017-06-06 18:25     ` Jeff Layton
2017-06-06 18:57       ` Benjamin Coddington
2017-06-06 20:41         ` Benjamin Coddington
2017-06-06 23:05         ` Jeff Layton
2017-06-08  6:50   ` kbuild test robot [this message]
2017-06-06 17:19 ` [PATCH 3/3] fs/locks: Use fs-specific l_pid for remote locks Benjamin Coddington
2017-06-06 20:45 [PATCH 0/3 v4] Fixups for l_pid Benjamin Coddington
2017-06-06 20:45 ` [PATCH 2/3] fs/locks: Remove fl_nspid Benjamin Coddington

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=201706081429.wGkVsweB%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bcodding@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@poochiereds.net \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®