From: kbuild test robot <lkp-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Nikhilesh Reddy <reddyn-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>,
fuse-devel
<fuse-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Greg KH
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>,
Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
jack-AlSwsSmVLrQ@public.gmane.org,
Antonio SJ Musumeci
<trapexit-wGTF+nt6ur047o9RxwvyTQ@public.gmane.org>,
sven.utcke-Mmb7MZpHnFY@public.gmane.org,
Nikolaus Rath <nikolaus-BTH8mxji4b0@public.gmane.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-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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 --]
prev parent reply other threads:[~2016-01-14 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 19:01 [PATCH v2 fixed line wrap mangling] fuse: Add support for fuse stacked I/O Nikhilesh Reddy
[not found] ` <5697F092.9070003-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
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-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=fuse-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=jack-AlSwsSmVLrQ@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org \
--cc=nikolaus-BTH8mxji4b0@public.gmane.org \
--cc=reddyn-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=richard-/L3Ra7n9ekc@public.gmane.org \
--cc=sven.utcke-Mmb7MZpHnFY@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=trapexit-wGTF+nt6ur047o9RxwvyTQ@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.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;
as well as URLs for NNTP newsgroup(s).