linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: kbuild-all@01.org, viro@zeniv.linux.org.uk, tytso@mit.edu,
	adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	arnd@arndb.de, y2038@lists.linaro.org
Subject: Re: [PATCH v3 4/5] vfs: Add timestamp_truncate() api
Date: Sun, 19 Feb 2017 14:26:05 +0800	[thread overview]
Message-ID: <201702191425.I1Iniitc%fengguang.wu@intel.com> (raw)
In-Reply-To: <1487460608-15697-5-git-send-email-deepa.kernel@gmail.com>

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

Hi Deepa,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.10-rc8 next-20170217]
[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/Deepa-Dinamani/vfs-Add-timestamp-range-check-support/20170219-073734
reproduce: make htmldocs

All warnings (new ones prefixed by >>):

   fs/inode.c:1679: warning: No description found for parameter 'rcu'
   fs/inode.c:2125: warning: No description found for parameter 'inode'
>> fs/inode.c:2125: warning: Excess function parameter 'gran' description in 'timestamp_truncate'
   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:494: warning: No description found for parameter 'h_rsv_handle'
   include/linux/jbd2.h:494: warning: No description found for parameter 'h_reserved'
   include/linux/jbd2.h:494: warning: No description found for parameter 'h_type'
   include/linux/jbd2.h:494: warning: No description found for parameter 'h_line_no'
   include/linux/jbd2.h:494: warning: No description found for parameter 'h_start_jiffies'
   include/linux/jbd2.h:494: warning: No description found for parameter 'h_requested_credits'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_chkpt_bhs[JBD2_NR_BATCH]'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_devname[BDEVNAME_SIZE+24]'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_average_commit_time'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_min_batch_time'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_max_batch_time'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_commit_callback'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_failed_commit'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_chksum_driver'
   include/linux/jbd2.h:1047: warning: No description found for parameter 'j_csum_seed'
   fs/jbd2/transaction.c:428: warning: No description found for parameter 'rsv_blocks'
   fs/jbd2/transaction.c:428: warning: No description found for parameter 'gfp_mask'
   fs/jbd2/transaction.c:428: warning: No description found for parameter 'type'
   fs/jbd2/transaction.c:428: warning: No description found for parameter 'line_no'
   fs/jbd2/transaction.c:504: warning: No description found for parameter 'type'
   fs/jbd2/transaction.c:504: warning: No description found for parameter 'line_no'
   fs/jbd2/transaction.c:634: warning: No description found for parameter 'gfp_mask'

vim +2125 fs/inode.c

  2109	
  2110	void inode_nohighmem(struct inode *inode)
  2111	{
  2112		mapping_set_gfp_mask(inode->i_mapping, GFP_USER);
  2113	}
  2114	EXPORT_SYMBOL(inode_nohighmem);
  2115	
  2116	/**
  2117	 * fs_timespec_trunc - Truncate timespec to a granularity
  2118	 * @t: Timespec
  2119	 * @gran: Granularity in ns.
  2120	 *
  2121	 * Truncate a timespec to a granularity. Always rounds down. gran must
  2122	 * not be 0 nor greater than a second (NSEC_PER_SEC, or 10^9 ns).
  2123	 */
  2124	struct timespec timestamp_truncate(struct timespec t, struct inode *inode)
> 2125	{
  2126		struct super_block *sb = inode->i_sb;
  2127		unsigned int gran = sb->s_time_gran;
  2128	
  2129		t.tv_sec = clamp_t(time64_t, t.tv_sec, sb->s_time_min, sb->s_time_max);
  2130	
  2131		/* Avoid division in the common cases 1 ns and 1 s. */
  2132		if (gran == 1) {
  2133			/* nothing */

---
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: 6457 bytes --]

  reply	other threads:[~2017-02-19  6:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18 23:30 [PATCH v3 0/5] vfs: Add timestamp range check support Deepa Dinamani
2017-02-18 23:30 ` [PATCH v3 1/5] vfs: Add file timestamp range support Deepa Dinamani
2017-02-19  1:56   ` Al Viro
2017-02-19 19:23     ` Deepa Dinamani
2017-02-18 23:30 ` [PATCH v3 2/5] vfs: Add checks for filesystem timestamp limits Deepa Dinamani
2017-02-18 23:30 ` [PATCH v3 3/5] ext4: Initialize timestamps limits Deepa Dinamani
2017-02-18 23:30 ` [PATCH v3 4/5] vfs: Add timestamp_truncate() api Deepa Dinamani
2017-02-19  6:26   ` kbuild test robot [this message]
2017-02-21 18:18     ` Deepa Dinamani
2017-02-18 23:30 ` [PATCH v3 5/5] utimes: Clamp the timestamps before update Deepa Dinamani

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=201702191425.I1Iniitc%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=arnd@arndb.de \
    --cc=deepa.kernel@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=y2038@lists.linaro.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).