From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaegeuk Kim Subject: Re: linux-next: build warning after merge of the block tree Date: Wed, 17 Apr 2019 07:03:05 -0700 Message-ID: <20190417140305.GB23731@jaegeuk-macbookpro.roam.corp.google.com> References: <20190417123125.3de22f73@canb.auug.org.au> <0879e11b-c84c-65b8-581f-bf7adcb5e231@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <0879e11b-c84c-65b8-581f-bf7adcb5e231@huawei.com> Sender: linux-kernel-owner@vger.kernel.org To: Chao Yu Cc: Stephen Rothwell , Jens Axboe , Linux Next Mailing List , Linux Kernel Mailing List , Christoph Hellwig List-Id: linux-next.vger.kernel.org On 04/17, Chao Yu wrote: > Hi Jaegeuk, > > On 2019/4/17 10:31, Stephen Rothwell wrote: > > Hi all, > > > > After merging the block tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > > > fs/f2fs/node.c: In function 'f2fs_remove_inode_page': > > fs/f2fs/node.c:1193:47: warning: format '%zu' expects argument of type 'size_t', but argument 5 has type 'blkcnt_t' {aka 'long long unsigned int'} [-Wformat=] > > "Inconsistent i_blocks, ino:%lu, iblocks:%zu", > > ~~^ > > %llu > > inode->i_ino, inode->i_blocks); > > ~~~~~~~~~~~~~~~ > > Could you please help to fix that as below in your dev branch directly? > > "Inconsistent i_blocks, ino:%lu, iblocks:%llu", We can just use "%lu"? > inode->i_ino, (unsigned long long)inode->i_blocks) > > > It looks that we need to fix below commits as well: > > f2fs: fix to avoid panic in dec_valid_block_count() > f2fs: fix to avoid panic in dec_valid_node_count() > > Thanks, > > > > > Introduced by commit > > > > 90ae238d9dac ("f2fs: fix to avoid panic in f2fs_remove_inode_page()") > > > > from the f2fs tree interacting with commit > > > > 72deb455b5ec ("block: remove CONFIG_LBDAF") > >