From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 5/5] fs: allow to mount beneath top mount
Date: Wed, 29 Mar 2023 06:42:19 +0800 [thread overview]
Message-ID: <202303290629.d046fvuG-lkp@intel.com> (raw)
In-Reply-To: <20230202-fs-move-mount-replace-v2-5-f53cd31d6392@kernel.org>
Hi Christian,
I love your patch! Perhaps something to improve:
[auto build test WARNING on 197b6b60ae7bc51dd0814953c562833143b292aa]
url: https://github.com/intel-lab-lkp/linux/commits/Christian-Brauner/fs-add-path_mounted/20230329-001618
base: 197b6b60ae7bc51dd0814953c562833143b292aa
patch link: https://lore.kernel.org/r/20230202-fs-move-mount-replace-v2-5-f53cd31d6392%40kernel.org
patch subject: [PATCH v2 5/5] fs: allow to mount beneath top mount
config: x86_64-randconfig-a014-20230327 (https://download.01.org/0day-ci/archive/20230329/202303290629.d046fvuG-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/13451428e46188ad86767587daa736968e4cc62c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Christian-Brauner/fs-add-path_mounted/20230329-001618
git checkout 13451428e46188ad86767587daa736968e4cc62c
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303290629.d046fvuG-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/namespace.c:990: warning: expecting prototype for mnt_beneath(). Prototype was for attach_mnt_beneath() instead
vim +990 fs/namespace.c
969
970 /**
971 * mnt_beneath - mount a mount beneath another one, attach to
972 * @mount_hashtable and parent's list of child mounts
973 *
974 * @new_parent: the source mount
975 * @top_mnt: the mount beneath which @new_parent is mounted
976 * @new_mp: the new mountpoint of @top_mnt on @new_parent
977 *
978 * Remove @top_mnt from its current parent and mountpoint and mount it
979 * on @new_mp on @new_parent, and mount @new_parent on the old parent
980 * and old mountpoint of @top_mnt. Finally, attach @new_parent mount to
981 * @mnt_hashtable and @new_parent->mnt_parent->mnt_mounts.
982 *
983 * Note, when we call __attach_mnt() we've already mounted @new_parent
984 * on top of @top_mnt's old parent so @new_parent->mnt_parent will point
985 * to the correct parent.
986 */
987 static void attach_mnt_beneath(struct mount *new_parent,
988 struct mount *top_mnt,
989 struct mountpoint *new_mp)
> 990 {
991 mnt_set_mountpoint_beneath(new_parent, top_mnt, new_mp);
992 __attach_mnt(new_parent, new_parent->mnt_parent);
993 }
994
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-03-28 22:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:13 [PATCH v2 0/5] fs: allow to mount beneath top mount Christian Brauner
2023-03-28 16:13 ` [PATCH v2 1/5] fs: add path_mounted() Christian Brauner
2023-04-05 19:29 ` Seth Forshee
2023-03-28 16:13 ` [PATCH v2 2/5] pnode: pass mountpoint directly Christian Brauner
2023-04-05 19:30 ` Seth Forshee
2023-04-06 13:01 ` Christian Brauner
2023-03-28 16:13 ` [PATCH v2 3/5] fs: fix __lookup_mnt() documentation Christian Brauner
2023-04-05 19:32 ` Seth Forshee
2023-03-28 16:13 ` [PATCH v2 4/5] fs: use a for loop when locking a mount Christian Brauner
2023-04-05 19:34 ` Seth Forshee
2023-03-28 16:13 ` [PATCH v2 5/5] fs: allow to mount beneath top mount Christian Brauner
2023-03-28 22:42 ` kernel test robot [this message]
2023-04-05 19:34 ` Seth Forshee
2023-04-06 13:56 ` Christian Brauner
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=202303290629.d046fvuG-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.