From: Amir Goldstein <amir73il@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Miklos Szeredi <miklos@szeredi.hu>,
Vivek Goyal <vgoyal@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 04/11] ovl: store file handle of lower inode on copy up
Date: Mon, 24 Apr 2017 16:57:13 +0300 [thread overview]
Message-ID: <CAOQ4uxi98NobOt3wck2_ona-dsS6OMJSHr+iDANVHi0vkge=oQ@mail.gmail.com> (raw)
In-Reply-To: <201704242153.XQhZVb57%fengguang.wu@intel.com>
On Mon, Apr 24, 2017 at 4:32 PM, kbuild test robot <lkp@intel.com> wrote:
> Hi Amir,
>
> [auto build test WARNING on miklos-vfs/overlayfs-next]
> [also build test WARNING on v4.11-rc8 next-20170424]
> [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/Amir-Goldstein/overlayfs-constant-inode-numbers/20170424-175555
> base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
>
>
> coccinelle warnings: (new ones prefixed by >>)
>
>>> fs/overlayfs/copy_up.c:309:7-14: ERROR: PTR_ERR applied after initialization to constant on line 299
Why is this wrong?
The pointer tested is not const - it's referenced data is.
Anyway, this pointed out another thing worth a warning:
The static variable null_fh was meant to be const.
I wonder if coccinelle has a way to figure out this pattern?
I guess not.
> > 289 static struct ovl_fh null_fh = {
> 290 .version = OVL_FH_VERSION,
> 291 .magic = OVL_FH_MAGIC,
> 292 .type = FILEID_INVALID,
>
> vim +309 fs/overlayfs/copy_up.c
>
> 293 .len = sizeof(struct ovl_fh),
> 294 };
> 295
> 296 static int ovl_set_lower_fh(struct dentry *dentry, struct dentry *upper)
> 297 {
> 298 int err;
> > 299 const struct ovl_fh *fh = NULL;
> 300
> 301 if (ovl_redirect_fh(dentry->d_sb))
> 302 fh = ovl_get_fh(ovl_dentry_lower(dentry));
> 303 /*
> 304 * On failure to encode lower fh, store an invalid 'null' fh, so
> 305 * we can always use the overlay.fh xattr to distignuish between
> 306 * a copy up and a pure upper inode. If lower fs does not support
> 307 * encoding fh, don't try to encode again.
> 308 */
> > 309 err = PTR_ERR(fh);
> 310 if (IS_ERR_OR_NULL(fh)) {
> 311 if (err == -EOPNOTSUPP) {
> 312 pr_warn("overlay: file handle not supported by lower - turning off redirect_fh\n");
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-04-24 13:57 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 9:14 [PATCH v2 00/11] overlayfs constant inode numbers Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 01/11] ovl: store path type in dentry Amir Goldstein
2017-04-24 12:59 ` Vivek Goyal
2017-04-24 13:10 ` Amir Goldstein
2017-04-24 13:36 ` Vivek Goyal
2017-04-24 13:41 ` Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 02/11] ovl: cram opaque boolean into type flags Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 03/11] ovl: check if all layers are on the same fs Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 04/11] ovl: store file handle of lower inode on copy up Amir Goldstein
2017-04-24 13:32 ` kbuild test robot
2017-04-24 13:57 ` Amir Goldstein [this message]
2017-04-25 14:53 ` Miklos Szeredi
2017-04-26 5:47 ` Amir Goldstein
2017-04-26 9:21 ` Miklos Szeredi
2017-04-26 9:27 ` Amir Goldstein
2017-04-26 9:35 ` Miklos Szeredi
2017-04-26 9:39 ` Miklos Szeredi
2017-04-26 9:53 ` Amir Goldstein
2017-04-26 9:57 ` Miklos Szeredi
2017-04-24 9:14 ` [PATCH v2 05/11] ovl: lookup redirect by file handle Amir Goldstein
2017-04-25 8:10 ` Amir Goldstein
2017-04-25 15:13 ` Miklos Szeredi
2017-04-25 17:41 ` Amir Goldstein
2017-04-25 19:11 ` Amir Goldstein
2017-04-26 9:06 ` Miklos Szeredi
2017-04-26 9:40 ` Amir Goldstein
2017-04-26 9:55 ` Miklos Szeredi
2017-04-26 10:17 ` Amir Goldstein
2017-04-26 12:15 ` Miklos Szeredi
2017-04-26 14:51 ` Amir Goldstein
2017-04-27 6:27 ` Amir Goldstein
2017-04-27 7:48 ` Miklos Szeredi
2017-04-27 9:22 ` Amir Goldstein
2017-04-27 9:26 ` Miklos Szeredi
[not found] ` <CAOQ4uxiweaqzR3eT-StgtDFAHBuYhGRvAJE6v=XpH33MevpmoA@mail.gmail.com>
[not found] ` <CAJfpegtTJmcLVrLOeQbhu4Q6sM0Mi_FRgr+vStF0k95QsWm5uQ@mail.gmail.com>
2017-04-27 13:53 ` Amir Goldstein
2017-04-27 14:46 ` Miklos Szeredi
2017-04-27 16:08 ` Amir Goldstein
2017-04-28 7:25 ` Amir Goldstein
2017-04-28 7:55 ` Miklos Szeredi
2017-04-28 8:15 ` Amir Goldstein
2017-04-28 9:37 ` Miklos Szeredi
2017-04-28 9:57 ` Amir Goldstein
2017-04-28 10:05 ` Miklos Szeredi
2017-04-28 10:45 ` Amir Goldstein
2017-04-27 7:40 ` Miklos Szeredi
2017-04-24 9:14 ` [PATCH v2 06/11] ovl: lookup non-dir inode copy up origin Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 07/11] ovl: set the COPYUP type flag for non-dirs Amir Goldstein
2017-04-26 14:40 ` Miklos Szeredi
2017-04-26 14:53 ` Miklos Szeredi
2017-04-26 15:02 ` Amir Goldstein
2017-04-26 18:51 ` Amir Goldstein
2017-04-27 9:32 ` Miklos Szeredi
2017-04-26 14:57 ` Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 08/11] ovl: redirect non-dir by path on rename Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 09/11] ovl: constant st_ino/st_dev across copy up Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 10/11] ovl: persistent and constant inode number for directories Amir Goldstein
2017-04-24 9:14 ` [PATCH v2 11/11] ovl: fix du --one-file-system on overlay mount Amir Goldstein
2017-04-24 18:40 ` [PATCH v2 12/12] ovl: persistent inode numbers for hardlinks Amir Goldstein
2017-04-24 18:51 ` [PATCH v2 00/11] overlayfs constant inode numbers Amir Goldstein
2017-04-25 11:52 ` Vivek Goyal
2017-04-25 12:05 ` Amir Goldstein
2017-04-25 12:16 ` Vivek Goyal
2017-04-25 12:41 ` Amir Goldstein
2017-04-25 12:52 ` Vivek Goyal
2017-04-25 13:23 ` Amir Goldstein
2017-04-25 13:29 ` Vivek Goyal
2017-04-25 13:49 ` Amir Goldstein
2017-04-25 13:53 ` Vivek Goyal
2017-04-25 14:20 ` Amir Goldstein
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='CAOQ4uxi98NobOt3wck2_ona-dsS6OMJSHr+iDANVHi0vkge=oQ@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.