From: kbuild test robot <lkp@intel.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: kbuild-all@lists.01.org, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 05/16] fsnotify: simplify arguments passing to fsnotify_parent()
Date: Wed, 19 Feb 2020 18:50:02 +0800 [thread overview]
Message-ID: <202002191836.KJ7wwO0T%lkp@intel.com> (raw)
In-Reply-To: <20200217131455.31107-6-amir73il@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6241 bytes --]
Hi Amir,
I love your patch! Yet something to improve:
[auto build test ERROR on 11a48a5a18c63fd7621bb050228cebf13566e4d8]
url: https://github.com/0day-ci/linux/commits/Amir-Goldstein/Fanotify-event-with-name-info/20200219-160517
base: 11a48a5a18c63fd7621bb050228cebf13566e4d8
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from fs///attr.c:15:0:
include/linux/fsnotify.h: In function 'fsnotify_dentry':
>> include/linux/fsnotify.h:52:18: warning: passing argument 1 of 'fsnotify_parent' makes integer from pointer without a cast [-Wint-conversion]
fsnotify_parent(dentry, mask, inode, FSNOTIFY_EVENT_INODE);
^~~~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: expected '__u32 {aka unsigned int}' but argument is of type 'struct dentry *'
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
>> include/linux/fsnotify.h:52:26: warning: passing argument 2 of 'fsnotify_parent' makes pointer from integer without a cast [-Wint-conversion]
fsnotify_parent(dentry, mask, inode, FSNOTIFY_EVENT_INODE);
^~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: expected 'const void *' but argument is of type '__u32 {aka unsigned int}'
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
include/linux/fsnotify.h:52:32: warning: passing argument 3 of 'fsnotify_parent' makes integer from pointer without a cast [-Wint-conversion]
fsnotify_parent(dentry, mask, inode, FSNOTIFY_EVENT_INODE);
^~~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: expected 'int' but argument is of type 'struct inode *'
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
>> include/linux/fsnotify.h:52:2: error: too many arguments to function 'fsnotify_parent'
fsnotify_parent(dentry, mask, inode, FSNOTIFY_EVENT_INODE);
^~~~~~~~~~~~~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: declared here
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
include/linux/fsnotify.h: In function 'fsnotify_file':
include/linux/fsnotify.h:68:24: warning: passing argument 1 of 'fsnotify_parent' makes integer from pointer without a cast [-Wint-conversion]
ret = fsnotify_parent(path->dentry, mask, path, FSNOTIFY_EVENT_PATH);
^~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: expected '__u32 {aka unsigned int}' but argument is of type 'struct dentry * const'
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
include/linux/fsnotify.h:68:38: warning: passing argument 2 of 'fsnotify_parent' makes pointer from integer without a cast [-Wint-conversion]
ret = fsnotify_parent(path->dentry, mask, path, FSNOTIFY_EVENT_PATH);
^~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: expected 'const void *' but argument is of type '__u32 {aka unsigned int}'
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
include/linux/fsnotify.h:68:44: warning: passing argument 3 of 'fsnotify_parent' makes integer from pointer without a cast [-Wint-conversion]
ret = fsnotify_parent(path->dentry, mask, path, FSNOTIFY_EVENT_PATH);
^~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: expected 'int' but argument is of type 'const struct path *'
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
In file included from fs///attr.c:15:0:
include/linux/fsnotify.h:68:8: error: too many arguments to function 'fsnotify_parent'
ret = fsnotify_parent(path->dentry, mask, path, FSNOTIFY_EVENT_PATH);
^~~~~~~~~~~~~~~
In file included from include/linux/fsnotify.h:15:0,
from fs///attr.c:15:
include/linux/fsnotify_backend.h:543:19: note: declared here
static inline int fsnotify_parent(__u32 mask, const void *data, int data_type)
^~~~~~~~~~~~~~~
vim +/fsnotify_parent +52 include/linux/fsnotify.h
40
41 /*
42 * Simple wrappers to consolidate calls fsnotify_parent()/fsnotify() when
43 * an event is on a file/dentry.
44 */
45 static inline void fsnotify_dentry(struct dentry *dentry, __u32 mask)
46 {
47 struct inode *inode = d_inode(dentry);
48
49 if (S_ISDIR(inode->i_mode))
50 mask |= FS_ISDIR;
51
> 52 fsnotify_parent(dentry, mask, inode, FSNOTIFY_EVENT_INODE);
53 fsnotify(inode, mask, inode, FSNOTIFY_EVENT_INODE, NULL, 0);
54 }
55
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 7238 bytes --]
next prev parent reply other threads:[~2020-02-19 10:50 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:14 [PATCH v2 00/16] Fanotify event with name info Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 01/16] fsnotify: tidy up FS_ and FAN_ constants Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 02/16] fsnotify: factor helpers fsnotify_dentry() and fsnotify_file() Amir Goldstein
2020-02-25 13:46 ` Jan Kara
2020-02-25 14:27 ` Amir Goldstein
2020-02-26 13:59 ` Jan Kara
2020-02-17 13:14 ` [PATCH v2 03/16] fsnotify: funnel all dirent events through fsnotify_name() Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 04/16] fsnotify: use helpers to access data by data_type Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 05/16] fsnotify: simplify arguments passing to fsnotify_parent() Amir Goldstein
2020-02-19 10:50 ` kbuild test robot [this message]
2020-02-19 11:11 ` Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 06/16] fsnotify: pass dentry instead of inode for events possible on child Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 07/16] fsnotify: replace inode pointer with tag Amir Goldstein
2020-02-26 8:20 ` Jan Kara
2020-02-26 9:34 ` Amir Goldstein
2020-02-26 8:52 ` Jan Kara
2020-02-17 13:14 ` [PATCH v2 08/16] fanotify: merge duplicate events on parent and child Amir Goldstein
2020-02-26 9:18 ` Jan Kara
2020-02-26 12:14 ` Amir Goldstein
2020-02-26 14:38 ` Jan Kara
2021-01-22 13:59 ` fanotify_merge improvements Amir Goldstein
2021-01-23 13:30 ` Amir Goldstein
2021-01-25 13:01 ` Jan Kara
2021-01-26 16:21 ` Amir Goldstein
2021-01-27 11:24 ` Jan Kara
2021-01-27 12:57 ` Amir Goldstein
2021-01-27 15:15 ` Jan Kara
2021-01-27 18:03 ` Amir Goldstein
2021-01-28 10:27 ` Jan Kara
2021-01-28 18:50 ` Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 09/16] fanotify: fix merging marks masks with FAN_ONDIR Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 10/16] fanotify: send FAN_DIR_MODIFY event flavor with dir inode and name Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 11/16] fanotify: prepare to encode both parent and child fid's Amir Goldstein
2020-02-26 10:23 ` Jan Kara
2020-02-26 11:53 ` Amir Goldstein
2020-02-26 17:07 ` Jan Kara
2020-02-26 17:50 ` Amir Goldstein
2020-02-27 9:06 ` Amir Goldstein
2020-02-27 11:27 ` Jan Kara
2020-02-27 12:12 ` Amir Goldstein
2020-02-27 13:30 ` Jan Kara
2020-02-27 14:06 ` Amir Goldstein
2020-03-01 16:26 ` Amir Goldstein
2020-03-05 15:49 ` Jan Kara
2020-03-06 11:19 ` Amir Goldstein
2020-03-08 7:29 ` Amir Goldstein
2020-03-18 17:51 ` Jan Kara
2020-03-18 18:50 ` Amir Goldstein
2020-03-19 9:30 ` Jan Kara
2020-03-19 10:07 ` Amir Goldstein
2020-03-30 19:29 ` Amir Goldstein
2020-02-27 11:01 ` Jan Kara
2020-02-17 13:14 ` [PATCH v2 12/16] fanotify: record name info for FAN_DIR_MODIFY event Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 13/16] fanotify: report " Amir Goldstein
2020-02-19 9:43 ` kbuild test robot
2020-02-19 10:17 ` kbuild test robot
2020-02-19 11:22 ` Amir Goldstein
2020-04-16 12:16 ` Michael Kerrisk (man-pages)
2020-04-20 15:53 ` Jan Kara
2020-04-20 18:45 ` Amir Goldstein
2020-04-20 18:47 ` Michael Kerrisk (man-pages)
2020-02-17 13:14 ` [PATCH v2 14/16] fanotify: report parent fid + name with FAN_REPORT_NAME Amir Goldstein
2020-02-17 13:14 ` [PATCH v2 15/16] fanotify: refine rules for when name is reported Amir Goldstein
2020-02-17 13:14 ` [BONUS][PATCH v2 16/16] fanotify: support limited functionality for unprivileged users Amir Goldstein
2020-02-20 22:10 ` [PATCH v2 00/16] Fanotify event with name info Matthew Bobrowski
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=202002191836.KJ7wwO0T%lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=kbuild-all@lists.01.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).