From: kbuild test robot <lkp@intel.com>
To: Chao Yu <chao2.yu@samsung.com>
Cc: kbuild-all@01.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] f2fs: enhance foreground GC
Date: Fri, 22 Jan 2016 18:12:20 +0800 [thread overview]
Message-ID: <201601221856.kIf9q6Kq%fengguang.wu@intel.com> (raw)
In-Reply-To: <00b701d154f9$639564e0$2ac02ea0$@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Hi Chao,
[auto build test WARNING on f2fs/dev]
[also build test WARNING on v4.4 next-20160121]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Chao-Yu/f2fs-correct-search-area-in-get_new_segment/20160122-174633
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs dev
config: i386-randconfig-s0-201603 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
fs/f2fs/gc.c: In function 'do_garbage_collect':
>> fs/f2fs/gc.c:807:6: warning: 'type' may be used uninitialized in this function [-Wmaybe-uninitialized]
if (type == SUM_TYPE_NODE) {
^
vim +/type +807 fs/f2fs/gc.c
791 * - lock_page(sum_page)
792 */
793
794 if (type == SUM_TYPE_NODE)
795 gc_node_segment(sbi, sum->entries, segno, gc_type);
796 else
797 gc_data_segment(sbi, sum->entries, gc_list, segno,
798 gc_type);
799
800 stat_inc_seg_count(sbi, type, gc_type);
801 stat_inc_call_count(sbi->stat_info);
802
803 f2fs_put_page(sum_page, 0);
804 }
805
806 if (gc_type == FG_GC) {
> 807 if (type == SUM_TYPE_NODE) {
808 struct writeback_control wbc = {
809 .sync_mode = WB_SYNC_ALL,
810 .nr_to_write = LONG_MAX,
811 .for_reclaim = 0,
812 };
813 sync_node_pages(sbi, 0, &wbc);
814 } else {
815 f2fs_submit_merged_bio(sbi, DATA, WRITE);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 28879 bytes --]
prev parent reply other threads:[~2016-01-22 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 9:43 Chao Yu
2016-01-22 10:12 ` 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=201601221856.kIf9q6Kq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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®