mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Shaohua Li <shli@kernel.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, tj@kernel.org,
	gregkh@linuxfoundation.org, hch@lst.de, axboe@fb.com,
	rostedt@goodmis.org, lizefan@huawei.com, Kernel-team@fb.com,
	Shaohua Li <shli@fb.com>
Subject: Re: [PATCH 11/11] block: use standard blktrace API to output cgroup info for debug notes
Date: Sat, 3 Jun 2017 10:00:06 +0800	[thread overview]
Message-ID: <201706030929.WDb2sklG%fengguang.wu@intel.com> (raw)
In-Reply-To: <326d853e83cbaf6ba200c72a7b1801792cbc3886.1496432591.git.shli@fb.com>

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

Hi Shaohua,

[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v4.12-rc3 next-20170602]
[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/Shaohua-Li/kernfs-implement-i_generation/20170603-083132
config: x86_64-randconfig-x015-201722 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All error/warnings (new ones prefixed by >>):

   block/blk-throttle.c: In function 'throtl_schedule_pending_timer':
>> block/blk-throttle.c:355:3: error: implicit declaration of function 'blk_add_cgroup_trace_msg' [-Werror=implicit-function-declaration]
      blk_add_cgroup_trace_msg(__td->queue,   \
      ^
>> block/blk-throttle.c:697:2: note: in expansion of macro 'throtl_log'
     throtl_log(sq, "schedule timer. delay=%lu jiffies=%lu",
     ^~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/blk_add_cgroup_trace_msg +355 block/blk-throttle.c

   349		struct throtl_data *__td = sq_to_td((sq));			\
   350										\
   351		(void)__td;							\
   352		if (likely(!blk_trace_note_message_enabled(__td->queue)))	\
   353			break;							\
   354		if ((__tg)) {							\
 > 355			blk_add_cgroup_trace_msg(__td->queue,			\
   356				tg_to_blkg(__tg)->blkcg, "throtl " fmt, ##args);\
   357		} else {							\
   358			blk_add_trace_msg(__td->queue, "throtl " fmt, ##args);	\

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

      parent reply	other threads:[~2017-06-03  2:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 21:53 [PATCH 00/11]blktrace: output cgroup info Shaohua Li
2017-06-02 21:53 ` [PATCH 01/11] kernfs: implement i_generation Shaohua Li
2017-06-02 21:53 ` [PATCH 02/11] kernfs: use idr instead of ida to manage inode number Shaohua Li
2017-06-12 18:14   ` Tejun Heo
2017-06-02 21:53 ` [PATCH 03/11] kernfs: add an API to get kernfs node from " Shaohua Li
2017-06-02 22:03   ` Eduardo Valentin
2017-06-02 23:36     ` Shaohua Li
2017-06-12 18:20   ` Tejun Heo
2017-06-12 18:37     ` Tejun Heo
2017-06-02 21:53 ` [PATCH 04/11] kernfs: don't set dentry->d_fsdata Shaohua Li
2017-06-12 18:29   ` Tejun Heo
2017-06-02 21:53 ` [PATCH 05/11] kernfs: add exportfs operations Shaohua Li
2017-06-02 21:53 ` [PATCH 06/11] cgroup: export fhandle info for a cgroup Shaohua Li
2017-06-12 18:44   ` Tejun Heo
2017-06-02 21:54 ` [PATCH 07/11] blktrace: export cgroup info in trace Shaohua Li
2017-06-03  5:35   ` kbuild test robot
2017-06-02 21:54 ` [PATCH 08/11] block: always attach cgroup info into bio Shaohua Li
2017-06-12 18:49   ` Tejun Heo
2017-06-02 21:54 ` [PATCH 09/11] block: call __bio_free in bio_endio Shaohua Li
2017-06-02 21:54 ` [PATCH 10/11] blktrace: add an option to allow displying cgroup path Shaohua Li
2017-06-02 21:54 ` [PATCH 11/11] block: use standard blktrace API to output cgroup info for debug notes Shaohua Li
2017-06-03  1:09   ` kbuild test robot
2017-06-03  2:00   ` 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=201706030929.WDb2sklG%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Kernel-team@fb.com \
    --cc=axboe@fb.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=kbuild-all@01.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=rostedt@goodmis.org \
    --cc=shli@fb.com \
    --cc=shli@kernel.org \
    --cc=tj@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

all inboxes | Powered by JetHome®