mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@01.org, Emese Revfy <re.emese@gmail.com>,
	Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] initify_plugin: one more warning workaround
Date: Fri, 31 Mar 2017 18:33:31 +0800	[thread overview]
Message-ID: <201703311857.cUqdeG2a%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170329211434.2655137-1-arnd@arndb.de>

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

Hi Arnd,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.11-rc4 next-20170330]
[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/Arnd-Bergmann/initify_plugin-one-more-warning-workaround/20170331-161135
reproduce: make htmldocs

All warnings (new ones prefixed by >>):

>> lib/vsprintf.c:2407: warning: No description found for parameter '3'
>> lib/vsprintf.c:2407: warning: Excess function parameter 'buf' description in '__unverified_nocapture'
>> lib/vsprintf.c:2407: warning: Excess function parameter 'size' description in '__unverified_nocapture'
>> lib/vsprintf.c:2407: warning: Excess function parameter 'fmt' description in '__unverified_nocapture'
>> lib/vsprintf.c:2407: warning: Excess function parameter 'bin_buf' description in '__unverified_nocapture'
   lib/crc32.c:148: warning: No description found for parameter 'tab)[256]'
   lib/crc32.c:148: warning: Excess function parameter 'tab' description in 'crc32_le_generic'
   lib/crc32.c:293: warning: No description found for parameter 'tab)[256]'
   lib/crc32.c:293: warning: Excess function parameter 'tab' description in 'crc32_be_generic'
   lib/crc32.c:1: warning: no structured comments found

vim +/3 +2407 lib/vsprintf.c

4370aa4a Lai Jiangshan       2009-03-06  2391   * This function like C99 vsnprintf, but the difference is that vsnprintf gets
4370aa4a Lai Jiangshan       2009-03-06  2392   * arguments from stack, and bstr_printf gets arguments from @bin_buf which is
4370aa4a Lai Jiangshan       2009-03-06  2393   * a binary buffer that generated by vbin_printf.
4370aa4a Lai Jiangshan       2009-03-06  2394   *
4370aa4a Lai Jiangshan       2009-03-06  2395   * The format follows C99 vsnprintf, but has some extensions:
0efb4d20 Steven Rostedt      2009-09-17  2396   *  see vsnprintf comment for details.
4370aa4a Lai Jiangshan       2009-03-06  2397   *
4370aa4a Lai Jiangshan       2009-03-06  2398   * The return value is the number of characters which would
4370aa4a Lai Jiangshan       2009-03-06  2399   * be generated for the given input, excluding the trailing
4370aa4a Lai Jiangshan       2009-03-06  2400   * '\0', as per ISO C99. If you want to have the exact
4370aa4a Lai Jiangshan       2009-03-06  2401   * number of characters written into @buf as return value
4370aa4a Lai Jiangshan       2009-03-06  2402   * (not including the trailing '\0'), use vscnprintf(). If the
4370aa4a Lai Jiangshan       2009-03-06  2403   * return is greater than or equal to @size, the resulting
4370aa4a Lai Jiangshan       2009-03-06  2404   * string is truncated.
4370aa4a Lai Jiangshan       2009-03-06  2405   */
85dcce6c Arnd Bergmann       2017-03-29  2406  __unverified_nocapture(3) int bstr_printf(char *buf, size_t size, const char *fmt, const u32 *bin_buf)
4370aa4a Lai Jiangshan       2009-03-06 @2407  {
fef20d9c Frederic Weisbecker 2009-03-06  2408  	struct printf_spec spec = {0};
d4be151b André Goddard Rosa  2009-12-14  2409  	char *str, *end;
d4be151b André Goddard Rosa  2009-12-14  2410  	const char *args = (const char *)bin_buf;
4370aa4a Lai Jiangshan       2009-03-06  2411  
762abb51 Rasmus Villemoes    2015-11-06  2412  	if (WARN_ON_ONCE(size > INT_MAX))
4370aa4a Lai Jiangshan       2009-03-06  2413  		return 0;
4370aa4a Lai Jiangshan       2009-03-06  2414  
4370aa4a Lai Jiangshan       2009-03-06  2415  	str = buf;

:::::: The code at line 2407 was first introduced by commit
:::::: 4370aa4aa75391a5e2e06bccb0919109f725ed8e vsprintf: add binary printf

:::::: TO: Lai Jiangshan <laijs@cn.fujitsu.com>
:::::: CC: Ingo Molnar <mingo@elte.hu>

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

  reply	other threads:[~2017-03-31 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 21:14 Arnd Bergmann
2017-03-31 10:33 ` kbuild test robot [this message]
2017-03-31 11:20   ` Arnd Bergmann
2017-03-31 11:29     ` [kbuild-all] " Fengguang Wu

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=201703311857.cUqdeG2a%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=re.emese@gmail.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®