From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>, linux-fsdevel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
Karel Zak <kzak@redhat.com>,
Lennart Poettering <lennart@poettering.net>,
Ian Kent <raven@themaw.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v2] fanotify: notify on mount attach and detach
Date: Mon, 9 Dec 2024 12:10:51 +0800 [thread overview]
Message-ID: <202412071410.oxkaXcVR-lkp@intel.com> (raw)
In-Reply-To: <20241206151154.60538-1-mszeredi@redhat.com>
Hi Miklos,
kernel test robot noticed the following build errors:
[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on linus/master v6.13-rc1]
[cannot apply to jack-fs/fsnotify pcmoore-selinux/next next-20241206]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Miklos-Szeredi/fanotify-notify-on-mount-attach-and-detach/20241206-231407
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20241206151154.60538-1-mszeredi%40redhat.com
patch subject: [PATCH v2] fanotify: notify on mount attach and detach
config: hexagon-randconfig-001-20241207 (https://download.01.org/0day-ci/archive/20241207/202412071410.oxkaXcVR-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241207/202412071410.oxkaXcVR-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412071410.oxkaXcVR-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/coredump.c:36:
include/linux/fsnotify.h:258:20: error: redefinition of 'fsnotify_mntns_delete'
static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
^
include/linux/fsnotify_backend.h:914:20: note: previous definition is here
static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
^
In file included from fs/coredump.c:36:
>> include/linux/fsnotify.h:260:2: error: implicit declaration of function '__fsnotify_mntns_delete' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__fsnotify_mntns_delete(mntns);
^
include/linux/fsnotify.h:260:2: note: did you mean 'fsnotify_mntns_delete'?
include/linux/fsnotify.h:258:20: note: 'fsnotify_mntns_delete' declared here
static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
^
2 errors generated.
--
In file included from fs/namespace.c:22:
include/linux/fsnotify.h:258:20: error: redefinition of 'fsnotify_mntns_delete'
static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
^
include/linux/fsnotify_backend.h:914:20: note: previous definition is here
static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
^
In file included from fs/namespace.c:22:
>> include/linux/fsnotify.h:260:2: error: implicit declaration of function '__fsnotify_mntns_delete' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
__fsnotify_mntns_delete(mntns);
^
include/linux/fsnotify.h:260:2: note: did you mean 'fsnotify_mntns_delete'?
include/linux/fsnotify.h:258:20: note: 'fsnotify_mntns_delete' declared here
static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
^
>> fs/namespace.c:1126:10: error: no member named 'n_fsnotify_marks' in 'struct mnt_namespace'
if (ns->n_fsnotify_marks)
~~ ^
3 errors generated.
vim +/__fsnotify_mntns_delete +260 include/linux/fsnotify.h
257
> 258 static inline void fsnotify_mntns_delete(struct mnt_namespace *mntns)
259 {
> 260 __fsnotify_mntns_delete(mntns);
261 }
262
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-09 4:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 15:11 [PATCH v2] fanotify: notify on mount attach and detach Miklos Szeredi
2024-12-06 16:00 ` Christian Brauner
2024-12-07 21:17 ` Christian Brauner
2024-12-10 15:10 ` Miklos Szeredi
2024-12-11 10:00 ` Christian Brauner
2024-12-11 10:21 ` Miklos Szeredi
2024-12-11 10:34 ` Christian Brauner
2024-12-11 10:55 ` Miklos Szeredi
2024-12-11 11:24 ` Christian Brauner
2024-12-11 12:03 ` Christian Brauner
2024-12-06 18:29 ` Amir Goldstein
2024-12-10 16:11 ` Miklos Szeredi
2024-12-11 10:07 ` Christian Brauner
2024-12-08 21:26 ` Christian Brauner
2024-12-09 17:02 ` Miklos Szeredi
2024-12-10 9:48 ` Christian Brauner
2024-12-09 4:06 ` kernel test robot
2024-12-09 4:10 ` kernel test robot [this message]
2024-12-09 4:49 ` kernel test robot
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=202412071410.oxkaXcVR-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kzak@redhat.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mszeredi@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raven@themaw.net \
--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