mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Mikulas Patocka <mpatocka@redhat.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 3/3] pipe: add proc_dopipe_max_size() to safely assign pipe_max_size
Date: Fri, 29 Sep 2017 23:19:44 +0800	[thread overview]
Message-ID: <201709292356.BJTYzH5G%fengguang.wu@intel.com> (raw)
In-Reply-To: <1506435684-3163-4-git-send-email-joe.lawrence@redhat.com>

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

Hi Joe,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc2 next-20170929]
[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/Joe-Lawrence/A-few-round_pipe_size-and-pipe-max-size-fixups/20170929-205234
config: h8300-h8300h-sim_defconfig (attached as .config)
compiler: h8300-linux-gcc (GCC) 6.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=h8300 

All errors (new ones prefixed by >>):

   fs/pipe.o: In function `pipe_proc_fn':
>> fs/pipe.c:1133: undefined reference to `proc_dopipe_max_size'

vim +1133 fs/pipe.c

  1125	
  1126	/*
  1127	 * This should work even if CONFIG_PROC_FS isn't set, as proc_dointvec_minmax
  1128	 * will return an error.
  1129	 */
  1130	int pipe_proc_fn(struct ctl_table *table, int write, void __user *buf,
  1131			 size_t *lenp, loff_t *ppos)
  1132	{
> 1133		return proc_dopipe_max_size(table, write, buf, lenp, ppos);
  1134	}
  1135	

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

  parent reply	other threads:[~2017-09-29 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 14:21 [PATCH 0/3] A few round_pipe_size() and pipe-max-size fixups Joe Lawrence
2017-09-26 14:21 ` [PATCH 1/3] pipe: match pipe_max_size data type with procfs Joe Lawrence
2017-09-26 14:21 ` [PATCH 2/3] pipe: avoid round_pipe_size() nr_pages overflow on 32-bit Joe Lawrence
2017-09-26 14:21 ` [PATCH 3/3] pipe: add proc_dopipe_max_size() to safely assign pipe_max_size Joe Lawrence
2017-09-29 13:50   ` kbuild test robot
2017-09-29 15:19   ` kbuild test robot [this message]
2017-10-02 18:45   ` [PATCH v2 " Joe Lawrence

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=201709292356.BJTYzH5G%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=joe.lawrence@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=mtk.manpages@gmail.com \
    --cc=rdunlap@infradead.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®