From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [rgushchin:cgwb.6 3/7] fs/fs-writeback.c:270:6: warning: no previous prototype for 'inode_cgwb_move_to_attached'
Date: Fri, 28 May 2021 08:40:53 +0800 [thread overview]
Message-ID: <202105280846.Mmo0dEWP-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3446 bytes --]
tree: https://github.com/rgushchin/linux.git cgwb.6
head: 5f789741798a3b19bd28a558def7cbe6bde9842a
commit: 9ef2177a5d2b49dedf1fa2dda32f8235b6939880 [3/7] fix for 1
config: openrisc-randconfig-r015-20210526 (attached as .config)
compiler: or1k-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/rgushchin/linux/commit/9ef2177a5d2b49dedf1fa2dda32f8235b6939880
git remote add rgushchin https://github.com/rgushchin/linux.git
git fetch --no-tags rgushchin cgwb.6
git checkout 9ef2177a5d2b49dedf1fa2dda32f8235b6939880
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=openrisc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> fs/fs-writeback.c:270:6: warning: no previous prototype for 'inode_cgwb_move_to_attached' [-Wmissing-prototypes]
270 | void inode_cgwb_move_to_attached(struct inode *inode, struct bdi_writeback *wb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/inode_cgwb_move_to_attached +270 fs/fs-writeback.c
21c6321fbb3a378 Tejun Heo 2015-05-28 261
3f28da6584d53a3 Roman Gushchin 2021-05-25 262 /**
3f28da6584d53a3 Roman Gushchin 2021-05-25 263 * inode_cgwb_move_to_attached - put the inode onto wb->b_attached list
3f28da6584d53a3 Roman Gushchin 2021-05-25 264 * @inode: inode of interest with i_lock held
3f28da6584d53a3 Roman Gushchin 2021-05-25 265 * @wb: target bdi_writeback
3f28da6584d53a3 Roman Gushchin 2021-05-25 266 *
3f28da6584d53a3 Roman Gushchin 2021-05-25 267 * Remove the inode from wb's io lists and if necessarily put onto b_attached
3f28da6584d53a3 Roman Gushchin 2021-05-25 268 * list. Only inodes attached to cgwb's are kept on this list.
3f28da6584d53a3 Roman Gushchin 2021-05-25 269 */
3f28da6584d53a3 Roman Gushchin 2021-05-25 @270 void inode_cgwb_move_to_attached(struct inode *inode, struct bdi_writeback *wb)
3f28da6584d53a3 Roman Gushchin 2021-05-25 271 {
3f28da6584d53a3 Roman Gushchin 2021-05-25 272 assert_spin_locked(&wb->list_lock);
3f28da6584d53a3 Roman Gushchin 2021-05-25 273 assert_spin_locked(&inode->i_lock);
3f28da6584d53a3 Roman Gushchin 2021-05-25 274
9ef2177a5d2b49d Roman Gushchin 2021-05-27 275 inode->i_state &= ~I_SYNC_QUEUED;
3f28da6584d53a3 Roman Gushchin 2021-05-25 276 if (wb != &wb->bdi->wb)
3f28da6584d53a3 Roman Gushchin 2021-05-25 277 list_move(&inode->i_io_list, &wb->b_attached);
3f28da6584d53a3 Roman Gushchin 2021-05-25 278 else
3f28da6584d53a3 Roman Gushchin 2021-05-25 279 list_del_init(&inode->i_io_list);
9ef2177a5d2b49d Roman Gushchin 2021-05-27 280 wb_io_lists_depopulated(wb);
3f28da6584d53a3 Roman Gushchin 2021-05-25 281 }
3f28da6584d53a3 Roman Gushchin 2021-05-25 282
:::::: The code at line 270 was first introduced by commit
:::::: 3f28da6584d53a3d8e9bb4ec76ef4ad06593425b writeback, cgroup: keep list of inodes attached to bdi_writeback
:::::: TO: Roman Gushchin <guro@fb.com>
:::::: CC: Roman Gushchin <guro@fb.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 27910 bytes --]
reply other threads:[~2021-05-28 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202105280846.Mmo0dEWP-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.