All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 2/2] fs: srvfs: new pseudo-fs for publishing opened fd's in the filesystem
Date: Wed, 30 Jun 2021 07:39:24 +0800	[thread overview]
Message-ID: <202106300744.P3865dbT-lkp@intel.com> (raw)
In-Reply-To: <20210629144341.14313-3-info@metux.net>

[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]

Hi "Enrico,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linux/master]
[also build test WARNING on kees/for-next/pstore linus/master v5.13 next-20210629]
[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/Enrico-Weigelt-metux-IT-consult/fs-allow-filesystems-to-directly-pass-an-existing-struct-file/20210629-234355
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git c54b245d011855ea91c5beff07f1db74143ce614
config: arc-allyesconfig (attached as .config)
compiler: arceb-elf-gcc (GCC) 9.3.0
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/0day-ci/linux/commit/b27203409c71484eb143ea4bb70e7634c9c68e5e
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Enrico-Weigelt-metux-IT-consult/fs-allow-filesystems-to-directly-pass-an-existing-struct-file/20210629-234355
        git checkout b27203409c71484eb143ea4bb70e7634c9c68e5e
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arc 

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 >>):

>> fs/srvfs/super.c:96:16: warning: no previous prototype for 'srvfs_mount' [-Wmissing-prototypes]
      96 | struct dentry *srvfs_mount(struct file_system_type *fs_type,
         |                ^~~~~~~~~~~
--
>> fs/srvfs/fileref.c:25:6: warning: no previous prototype for 'srvfs_fileref_destroy' [-Wmissing-prototypes]
      25 | void srvfs_fileref_destroy(struct kref *ref)
         |      ^~~~~~~~~~~~~~~~~~~~~


vim +/srvfs_mount +96 fs/srvfs/super.c

    95	
  > 96	struct dentry *srvfs_mount(struct file_system_type *fs_type,
    97				   int flags, const char *dev_name, void *data)
    98	{
    99		return mount_nodev(fs_type, flags, data, srvfs_fill_super);
   100	}
   101	

---
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: 68223 bytes --]

      reply	other threads:[~2021-06-29 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 14:43 RFC: allow recording and passing of open file descriptors Enrico Weigelt, metux IT consult
2021-06-29 14:43 ` [RFC PATCH 1/2] fs: allow filesystems to directly pass an existing struct file Enrico Weigelt, metux IT consult
2021-06-29 14:43 ` [RFC PATCH 2/2] fs: srvfs: new pseudo-fs for publishing opened fd's in the filesystem Enrico Weigelt, metux IT consult
2021-06-29 23:39   ` kernel test robot [this message]

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=202106300744.P3865dbT-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.