linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [vfs:T3 63/82] fs/fs_context.c:737:12: error: 'struct fs_context' has no member named 'subtype'; did you mean 'fs_type'?
@ 2019-05-13 18:52 kbuild test robot
  0 siblings, 0 replies; only message in thread
From: kbuild test robot @ 2019-05-13 18:52 UTC (permalink / raw)
  To: David Howells; +Cc: kbuild-all, linux-fsdevel, Al Viro

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git T3
head:   8bb72026a69d4b951665d8628a61a8049fb3eb8d
commit: b9cbde9478868ca74055e4be2c86409dd4369d07 [63/82] vfs: Move the subtype parameter into fuse
config: x86_64-lkp (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        git checkout b9cbde9478868ca74055e4be2c86409dd4369d07
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs/fs_context.c: In function 'vfs_clean_context':
>> fs/fs_context.c:737:12: error: 'struct fs_context' has no member named 'subtype'; did you mean 'fs_type'?
     kfree(fc->subtype);
               ^~~~~~~
               fs_type
   fs/fs_context.c:738:6: error: 'struct fs_context' has no member named 'subtype'; did you mean 'fs_type'?
     fc->subtype = NULL;
         ^~~~~~~
         fs_type

vim +737 fs/fs_context.c

ecdab150f David Howells 2018-11-01  714  
ecdab150f David Howells 2018-11-01  715  /*
ecdab150f David Howells 2018-11-01  716   * Clean up a context after performing an action on it and put it into a state
ecdab150f David Howells 2018-11-01  717   * from where it can be used to reconfigure a superblock.
ecdab150f David Howells 2018-11-01  718   *
ecdab150f David Howells 2018-11-01  719   * Note that here we do only the parts that can't fail; the rest is in
ecdab150f David Howells 2018-11-01  720   * finish_clean_context() below and in between those fs_context is marked
ecdab150f David Howells 2018-11-01  721   * FS_CONTEXT_AWAITING_RECONF.  The reason for splitup is that after
ecdab150f David Howells 2018-11-01  722   * successful mount or remount we need to report success to userland.
ecdab150f David Howells 2018-11-01  723   * Trying to do full reinit (for the sake of possible subsequent remount)
ecdab150f David Howells 2018-11-01  724   * and failing to allocate memory would've put us into a nasty situation.
ecdab150f David Howells 2018-11-01  725   * So here we only discard the old state and reinitialization is left
ecdab150f David Howells 2018-11-01  726   * until we actually try to reconfigure.
ecdab150f David Howells 2018-11-01  727   */
ecdab150f David Howells 2018-11-01  728  void vfs_clean_context(struct fs_context *fc)
ecdab150f David Howells 2018-11-01  729  {
ecdab150f David Howells 2018-11-01  730  	if (fc->need_free && fc->ops && fc->ops->free)
ecdab150f David Howells 2018-11-01  731  		fc->ops->free(fc);
ecdab150f David Howells 2018-11-01  732  	fc->need_free = false;
ecdab150f David Howells 2018-11-01  733  	fc->fs_private = NULL;
ecdab150f David Howells 2018-11-01  734  	fc->s_fs_info = NULL;
ecdab150f David Howells 2018-11-01  735  	fc->sb_flags = 0;
ecdab150f David Howells 2018-11-01  736  	security_free_mnt_opts(&fc->security);
ecdab150f David Howells 2018-11-01 @737  	kfree(fc->subtype);
ecdab150f David Howells 2018-11-01  738  	fc->subtype = NULL;
ecdab150f David Howells 2018-11-01  739  	kfree(fc->source);
ecdab150f David Howells 2018-11-01  740  	fc->source = NULL;
ecdab150f David Howells 2018-11-01  741  
ecdab150f David Howells 2018-11-01  742  	fc->purpose = FS_CONTEXT_FOR_RECONFIGURE;
ecdab150f David Howells 2018-11-01  743  	fc->phase = FS_CONTEXT_AWAITING_RECONF;
ecdab150f David Howells 2018-11-01  744  }
ecdab150f David Howells 2018-11-01  745  

:::::: The code at line 737 was first introduced by commit
:::::: ecdab150fddb42fe6a739335257949220033b782 vfs: syscall: Add fsconfig() for configuring and managing a context

:::::: TO: David Howells <dhowells@redhat.com>
:::::: CC: Al Viro <viro@zeniv.linux.org.uk>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26679 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-05-13 18:53 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-13 18:52 [vfs:T3 63/82] fs/fs_context.c:737:12: error: 'struct fs_context' has no member named 'subtype'; did you mean 'fs_type'? kbuild test robot

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