linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sean Fu <fxinrong@gmail.com>
Cc: kbuild-all@01.org, viro@zeniv.linux.org.uk, shli@kernel.org,
	anton@tuxera.com, jack@suse.cz, axboe@fb.com,
	ebiggers@google.com, rpeterso@redhat.com, bmarzins@redhat.com,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net,
	Sean Fu <fxinrong@gmail.com>
Subject: Re: [PATCH] fs: buffer: Modify alloc_page_buffers.
Date: Tue, 20 Jun 2017 02:20:13 +0800	[thread overview]
Message-ID: <201706200227.7hQW8rSk%fengguang.wu@intel.com> (raw)
In-Reply-To: <1497877296-22441-1-git-send-email-fxinrong@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]

Hi Sean,

[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc6 next-20170619]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Sean-Fu/fs-buffer-Modify-alloc_page_buffers/20170620-012328
config: x86_64-randconfig-x015-201725 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

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/buffer.c: In function 'alloc_page_buffers':
>> fs/buffer.c:895:21: warning: 'tail' may be used uninitialized in this function [-Wmaybe-uninitialized]
      tail->b_this_page = head;
      ~~~~~~~~~~~~~~~~~~^~~~~~

vim +/tail +895 fs/buffer.c

   879	
   880			bh->b_this_page = head;
   881			bh->b_blocknr = -1;
   882	
   883			if (head == NULL)
   884				tail = bh;
   885	
   886			head = bh;
   887			bh->b_state = b_state;
   888			bh->b_size = size;
   889	
   890			/* Link the buffer to its page */
   891			set_bh_page(bh, page, offset);
   892		}
   893	
   894		if (circular)
 > 895			tail->b_this_page = head;
   896	
   897		return head;
   898	/*
   899	 * In case anything failed, we just free everything we got.
   900	 */
   901	no_grow:
   902		if (head) {
   903			do {

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28003 bytes --]

      parent reply	other threads:[~2017-06-19 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 13:01 [PATCH] fs: buffer: Modify alloc_page_buffers Sean Fu
2017-06-19 13:21 ` Jan Kara
2017-06-19 16:03 ` Al Viro
2017-06-21 17:07   ` Sean Fu
2017-06-23  8:26   ` Sean Fu
2017-06-19 18:20 ` 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=201706200227.7hQW8rSk%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=anton@tuxera.com \
    --cc=axboe@fb.com \
    --cc=bmarzins@redhat.com \
    --cc=ebiggers@google.com \
    --cc=fxinrong@gmail.com \
    --cc=jack@suse.cz \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=rpeterso@redhat.com \
    --cc=shli@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).