mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Nikhilesh Reddy <reddyn@codeaurora.org>
Cc: kbuild-all@01.org, Miklos Szeredi <miklos@szeredi.hu>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, Richard Weinberger <richard@nod.at>,
	"Theodore Ts'o" <tytso@mit.edu>,
	jack@suse.cz, Antonio SJ Musumeci <trapexit@spawn.link>,
	sven.utcke@gmx.de, Nikolaus Rath <nikolaus@rath.org>
Subject: Re: [PATCH v2 fixed line wrap mangling] fuse: Add support for fuse stacked I/O
Date: Fri, 15 Jan 2016 03:19:29 +0800	[thread overview]
Message-ID: <201601150357.7KjURjcS%fengguang.wu@intel.com> (raw)
In-Reply-To: <5697F092.9070003@codeaurora.org>

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

Hi Nikhilesh,

[auto build test WARNING on v4.4-rc8]
[also build test WARNING on next-20160114]
[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/Nikhilesh-Reddy/fuse-Add-support-for-fuse-stacked-I-O/20160115-030449
config: i386-randconfig-x005-01140835 (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/fuse/file.c: In function 'fuse_do_open':
>> fs/fuse/file.c:148:22: warning: 'lower_file' may be used uninitialized in this function [-Wmaybe-uninitialized]
       ff->rw_lower_file = lower_file;
                         ^

vim +/lower_file +148 fs/fuse/file.c

   132	
   133		ff = fuse_file_alloc(fc);
   134		if (!ff)
   135			return -ENOMEM;
   136	
   137		ff->fh = 0;
   138		ff->open_flags = FOPEN_KEEP_CACHE; /* Default for no-open */
   139		if (!fc->no_open || isdir) {
   140			struct fuse_open_out outarg;
   141			int err;
   142	
   143			err = fuse_send_open(fc, nodeid, file, opcode, &outarg,
   144					     &(lower_file));
   145			if (!err) {
   146				ff->fh = outarg.fh;
   147				ff->open_flags = outarg.open_flags;
 > 148				ff->rw_lower_file = lower_file;
   149	
   150			} else if (err != -ENOSYS || isdir) {
   151				fuse_file_free(ff);
   152				return err;
   153			} else {
   154				fc->no_open = 1;
   155			}
   156		}

---
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: 28669 bytes --]

      reply	other threads:[~2016-01-14 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 19:01 Nikhilesh Reddy
2016-01-14 19:19 ` 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=201601150357.7KjURjcS%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=kbuild-all@01.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=nikolaus@rath.org \
    --cc=reddyn@codeaurora.org \
    --cc=richard@nod.at \
    --cc=sven.utcke@gmx.de \
    --cc=torvalds@linux-foundation.org \
    --cc=trapexit@spawn.link \
    --cc=tytso@mit.edu \
    --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

all inboxes | Powered by JetHome®