From: kbuild test robot <lkp@intel.com>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: kbuild-all@lists.01.org, linux-fsdevel@vger.kernel.org,
hch@lst.de, darrick.wong@oracle.com, sandeen@sandeen.net
Subject: Re: [PATCH 4/5] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap
Date: Sun, 24 Nov 2019 22:52:42 +0800 [thread overview]
Message-ID: <201911242203.bV0i78w8%lkp@intel.com> (raw)
In-Reply-To: <20191122085320.124560-5-cmaiolino@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4177 bytes --]
Hi Carlos,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on hch-configfs/for-next]
[also build test ERROR on v5.4-rc8 next-20191122]
[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/Carlos-Maiolino/Refactor-ioctl_fibmap-internal-interface/20191124-165458
base: git://git.infradead.org/users/hch/configfs.git for-next
config: riscv-allnoconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.4.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.4.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from fs/inode.c:7:0:
include/linux/fs.h: In function 'bmap':
include/linux/fs.h:2869:31: error: parameter name omitted
static inline int bmap(struct inode *, sector_t *)
^~~~~
include/linux/fs.h:2869:31: error: parameter name omitted
fs/inode.c: At top level:
>> fs/inode.c:1608:5: error: redefinition of 'bmap'
int bmap(struct inode *inode, sector_t *block)
^~~~
In file included from fs/inode.c:7:0:
include/linux/fs.h:2869:19: note: previous definition of 'bmap' was here
static inline int bmap(struct inode *, sector_t *)
^~~~
vim +/bmap +1608 fs/inode.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 1593
^1da177e4c3f41 Linus Torvalds 2005-04-16 1594 /**
^1da177e4c3f41 Linus Torvalds 2005-04-16 1595 * bmap - find a block number in a file
1dc338a4af8188 Carlos Maiolino 2019-11-22 1596 * @inode: inode owning the block number being requested
1dc338a4af8188 Carlos Maiolino 2019-11-22 1597 * @block: pointer containing the block to find
^1da177e4c3f41 Linus Torvalds 2005-04-16 1598 *
1dc338a4af8188 Carlos Maiolino 2019-11-22 1599 * Replaces the value in *block with the block number on the device holding
1dc338a4af8188 Carlos Maiolino 2019-11-22 1600 * corresponding to the requested block number in the file.
1dc338a4af8188 Carlos Maiolino 2019-11-22 1601 * That is, asked for block 4 of inode 1 the function will replace the
1dc338a4af8188 Carlos Maiolino 2019-11-22 1602 * 4 in *block, with disk block relative to the disk start that holds that
1dc338a4af8188 Carlos Maiolino 2019-11-22 1603 * block of the file.
1dc338a4af8188 Carlos Maiolino 2019-11-22 1604 *
1dc338a4af8188 Carlos Maiolino 2019-11-22 1605 * Returns -EINVAL in case of error, 0 otherwise. If mapping falls into a
1dc338a4af8188 Carlos Maiolino 2019-11-22 1606 * hole, returns 0 and *block is also set to 0.
^1da177e4c3f41 Linus Torvalds 2005-04-16 1607 */
1dc338a4af8188 Carlos Maiolino 2019-11-22 @1608 int bmap(struct inode *inode, sector_t *block)
^1da177e4c3f41 Linus Torvalds 2005-04-16 1609 {
1dc338a4af8188 Carlos Maiolino 2019-11-22 1610 if (!inode->i_mapping->a_ops->bmap)
1dc338a4af8188 Carlos Maiolino 2019-11-22 1611 return -EINVAL;
1dc338a4af8188 Carlos Maiolino 2019-11-22 1612
1dc338a4af8188 Carlos Maiolino 2019-11-22 1613 *block = inode->i_mapping->a_ops->bmap(inode->i_mapping, *block);
1dc338a4af8188 Carlos Maiolino 2019-11-22 1614 return 0;
^1da177e4c3f41 Linus Torvalds 2005-04-16 1615 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 1616 EXPORT_SYMBOL(bmap);
^1da177e4c3f41 Linus Torvalds 2005-04-16 1617
:::::: The code at line 1608 was first introduced by commit
:::::: 1dc338a4af818855d7878307b8026c6af9e6304a fs: Enable bmap() function to properly return errors
:::::: TO: Carlos Maiolino <cmaiolino@redhat.com>
:::::: CC: 0day robot <lkp@intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 5379 bytes --]
next prev parent reply other threads:[~2019-11-24 14:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:53 [PATCH 0/5] Refactor ioctl_fibmap() internal interface Carlos Maiolino
2019-11-22 8:53 ` [PATCH 1/5] fs: Enable bmap() function to properly return errors Carlos Maiolino
2019-11-22 13:37 ` Christoph Hellwig
2019-11-22 14:02 ` Carlos Maiolino
2019-11-22 14:07 ` Christoph Hellwig
2019-11-22 8:53 ` [PATCH 2/5] cachefiles: drop direct usage of ->bmap method Carlos Maiolino
2019-11-22 13:37 ` Christoph Hellwig
2019-11-22 14:04 ` Carlos Maiolino
2019-11-22 8:53 ` [PATCH 3/5] ecryptfs: drop direct calls to ->bmap Carlos Maiolino
2019-11-22 8:53 ` [PATCH 4/5] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
2019-11-22 13:38 ` Christoph Hellwig
2019-11-24 9:56 ` kbuild test robot
2019-11-24 14:52 ` kbuild test robot [this message]
2019-11-22 8:53 ` [PATCH 5/5] fibmap: Reject negative block numbers Carlos Maiolino
2019-11-22 13:38 ` Christoph Hellwig
2019-12-10 15:03 [PATCH 0/5] Refactor ioctl_fibmap() internal interface Carlos Maiolino
2019-12-10 15:03 ` [PATCH 4/5] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
2020-01-09 13:30 [PATCH V8 0/5] Refactor ioctl_fibmap() internal interface Carlos Maiolino
2020-01-09 13:30 ` [PATCH 4/5] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
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=201911242203.bV0i78w8%lkp@intel.com \
--to=lkp@intel.com \
--cc=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).