From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 7/8] btrfs: Convert to fs_context
Date: Thu, 13 Aug 2020 18:22:59 +0800 [thread overview]
Message-ID: <202008131848.Cms6XlMi%lkp@intel.com> (raw)
In-Reply-To: <20200812163654.17080-8-marcos@mpdesouza.com>
[-- Attachment #1: Type: text/plain, Size: 4584 bytes --]
Hi Marcos,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on kdave/for-next]
[also build test WARNING on next-20200812]
[cannot apply to v5.8]
[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]
url: https://github.com/0day-ci/linux/commits/Marcos-Paulo-de-Souza/btrfs-convert-to-fscontext/20200813-012641
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
config: mips-randconfig-r031-20200813 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 62ef1cb2079123b86878e4bfed3c14db448f1373)
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
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from fs/btrfs/super.c:31:
In file included from fs/btrfs/delayed-inode.h:17:
fs/btrfs/ctree.h:2292:8: warning: 'const' type qualifier on return type has no effect [-Wignored-qualifiers]
size_t __const btrfs_get_num_csums(void);
^~~~~~~~
In file included from fs/btrfs/super.c:47:
fs/btrfs/sysfs.h:16:14: warning: 'const' type qualifier on return type has no effect [-Wignored-qualifiers]
const char * const btrfs_feature_set_name(enum btrfs_feature_set set);
^~~~~~
>> fs/btrfs/super.c:2420:5: warning: no previous prototype for function 'btrfs_mount_root_fc' [-Wmissing-prototypes]
int btrfs_mount_root_fc(struct fs_context *fc, unsigned int rdonly)
^
fs/btrfs/super.c:2420:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int btrfs_mount_root_fc(struct fs_context *fc, unsigned int rdonly)
^
static
fs/btrfs/super.c:3086:32: warning: unused variable 'btrfs_root_fs_type' [-Wunused-variable]
static struct file_system_type btrfs_root_fs_type = {
^
fs/btrfs/super.c:1508:12: warning: unused function 'btrfs_parse_device_options' [-Wunused-function]
static int btrfs_parse_device_options(const char *options, fmode_t flags,
^
fs/btrfs/super.c:1563:12: warning: unused function 'btrfs_parse_subvol_options' [-Wunused-function]
static int btrfs_parse_subvol_options(const char *options, char **subvol_name,
^
fs/btrfs/super.c:2219:12: warning: unused function 'btrfs_set_super' [-Wunused-function]
static int btrfs_set_super(struct super_block *s, void *data)
^
7 warnings generated.
vim +/btrfs_mount_root_fc +2420 fs/btrfs/super.c
2414
2415 /*
2416 * Duplicate the current fc and prepare for mounting the root.
2417 * btrfs_get_tree will be called recursively, but then will check for the
2418 * ctx->root being set and call btrfs_root_get_tree.
2419 */
> 2420 int btrfs_mount_root_fc(struct fs_context *fc, unsigned int rdonly)
2421 {
2422 struct btrfs_fs_context *ctx, *root_ctx;
2423 struct fs_context *root_fc;
2424 struct vfsmount *root_mnt;
2425 int ret;
2426
2427 root_fc = vfs_dup_fs_context(fc);
2428 if (IS_ERR(root_fc))
2429 return PTR_ERR(root_fc);
2430
2431 root_fc->sb_flags &= ~SB_RDONLY;
2432 root_fc->sb_flags |= rdonly | SB_NOSEC;
2433 root_ctx = root_fc->fs_private;
2434 root_ctx->root_mnt = NULL;
2435 root_ctx->root = true;
2436
2437 /*
2438 * fc_mount will call btrfs_get_tree again, and by checking ctx->root
2439 * being true it'll call btrfs_root_get_tree to avoid infinite recursion.
2440 */
2441 root_mnt = fc_mount(root_fc);
2442 if (IS_ERR(root_mnt)) {
2443 ret = PTR_ERR(root_mnt);
2444 goto error_fc;
2445 }
2446
2447 ctx = fc->fs_private;
2448 ctx->root_mnt = root_mnt;
2449 ret = 0;
2450
2451 error_fc:
2452 put_fs_context(root_fc);
2453 return ret;
2454 }
2455
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30112 bytes --]
next prev parent reply other threads:[~2020-08-13 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 16:36 [RFC PATCH 0/8] btrfs: convert to fscontext Marcos Paulo de Souza
2020-08-12 16:36 ` [RFC PATCH 1/8] btrfs: fs_context: Add initial fscontext parameters Marcos Paulo de Souza
2020-08-12 16:36 ` [RFC PATCH 2/8] btrfs: super: Introduce fs_context ops, init and free functions Marcos Paulo de Souza
2020-08-17 12:50 ` David Sterba
2020-08-12 16:36 ` [RFC PATCH 3/8] btrfs: super: Introduce btrfs_fc_parse_param and btrfs_apply_configuration Marcos Paulo de Souza
2020-08-17 13:09 ` David Sterba
2020-08-12 16:36 ` [RFC PATCH 4/8] btrfs: super: Introduce btrfs_fc_validate Marcos Paulo de Souza
2020-08-12 16:36 ` [RFC PATCH 5/8] btrfs: super: Introduce btrfs_dup_fc Marcos Paulo de Souza
2020-08-12 16:36 ` [RFC PATCH 6/8] btrfs: super: Introduce btrfs_mount_root_fc Marcos Paulo de Souza
2020-08-17 13:14 ` David Sterba
2020-08-12 16:36 ` [RFC PATCH 7/8] btrfs: Convert to fs_context Marcos Paulo de Souza
2020-08-13 10:22 ` kernel test robot [this message]
2020-08-17 13:26 ` David Sterba
2020-08-12 16:36 ` [RFC PATCH 8/8] btrfs: Remove leftover code from fscontext conversion Marcos Paulo de Souza
2020-08-17 12:44 ` [RFC PATCH 0/8] btrfs: convert to fscontext David Sterba
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=202008131848.Cms6XlMi%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.