From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v4] fs: Fix page_mkwrite off-by-one errors
Date: Fri, 10 Jan 2020 21:54:23 +0800 [thread overview]
Message-ID: <202001102143.nz0QSedd%lkp@intel.com> (raw)
In-Reply-To: <20200108131528.4279-1-agruenba@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
Hi Andreas,
I love your patch! Yet something to improve:
[auto build test ERROR on ceph-client/for-linus]
[also build test ERROR on ext4/dev xfs-linux/for-next linus/master v5.5-rc5]
[cannot apply to f2fs/dev-test rw-ubifs/next btrfs/next next-20200109]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Andreas-Gruenbacher/fs-Fix-page_mkwrite-off-by-one-errors/20200110-033920
base: https://github.com/ceph/ceph-client.git for-linus
config: sh-rsk7269_defconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 7.5.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
GCC_VERSION=7.5.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
fs/buffer.o: In function `block_page_mkwrite':
buffer.c:(.text+0x2bd0): undefined reference to `page_mkwrite_check_truncate'
fs/iomap/buffered-io.o: In function `iomap_page_mkwrite':
>> buffered-io.c:(.text+0x2460): undefined reference to `page_mkwrite_check_truncate'
fs/ext4/inode.o: In function `ext4_page_mkwrite':
>> inode.c:(.text+0x7478): undefined reference to `page_mkwrite_check_truncate'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 11699 bytes --]
prev parent reply other threads:[~2020-01-10 13:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 13:15 [PATCH v4] fs: Fix page_mkwrite off-by-one errors Andreas Gruenbacher
2020-01-08 13:15 ` Andreas Gruenbacher
2020-01-08 13:15 ` [f2fs-dev] " Andreas Gruenbacher
2020-01-08 13:15 ` Andreas Gruenbacher
2020-01-08 16:57 ` Christoph Hellwig
2020-01-08 16:57 ` Christoph Hellwig
2020-01-08 16:57 ` [f2fs-dev] " Christoph Hellwig
2020-01-08 16:57 ` Christoph Hellwig
2020-01-15 17:10 ` Darrick J. Wong
2020-01-15 17:10 ` Darrick J. Wong
2020-01-15 17:10 ` [f2fs-dev] " Darrick J. Wong
2020-01-15 17:10 ` Darrick J. Wong
2020-01-08 22:42 ` Jaegeuk Kim
2020-01-08 22:42 ` Jaegeuk Kim
2020-01-08 22:42 ` [f2fs-dev] " Jaegeuk Kim
2020-01-08 22:42 ` Jaegeuk Kim
2020-01-09 13:34 ` Jeff Layton
2020-01-09 13:34 ` Jeff Layton
2020-01-09 13:34 ` [f2fs-dev] " Jeff Layton
2020-01-09 13:34 ` Jeff Layton
2020-01-10 13:07 ` kbuild test robot
2020-01-10 13:54 ` 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=202001102143.nz0QSedd%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.