From: kernel test robot <lkp@intel.com>
To: Ajay Kaher <akaher@vmware.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [linux-next:master 4907/10848] fs/tracefs/event_inode.c:58: warning: Function parameter or member 'del_list' not described in 'eventfs_file'
Date: Fri, 18 Aug 2023 11:26:04 +0800 [thread overview]
Message-ID: <202308181108.C2BQ6D3n-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 47762f08697484cf0c2f2904b8c52375ed26c8cb
commit: 63940449555e799d387f316993ad824476c16953 [4907/10848] eventfs: Implement eventfs lookup, read, open functions
config: microblaze-randconfig-r032-20230817 (https://download.01.org/0day-ci/archive/20230818/202308181108.C2BQ6D3n-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230818/202308181108.C2BQ6D3n-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/202308181108.C2BQ6D3n-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/tracefs/event_inode.c:58: warning: Function parameter or member 'del_list' not described in 'eventfs_file'
>> fs/tracefs/event_inode.c:58: warning: Function parameter or member 'rcu' not described in 'eventfs_file'
>> fs/tracefs/event_inode.c:58: warning: Function parameter or member 'is_freed' not described in 'eventfs_file'
vim +58 fs/tracefs/event_inode.c
c1504e51023847 Ajay Kaher 2023-07-28 29
c1504e51023847 Ajay Kaher 2023-07-28 30 /**
c1504e51023847 Ajay Kaher 2023-07-28 31 * struct eventfs_file - hold the properties of the eventfs files and
c1504e51023847 Ajay Kaher 2023-07-28 32 * directories.
c1504e51023847 Ajay Kaher 2023-07-28 33 * @name: the name of the file or directory to create
63940449555e79 Ajay Kaher 2023-07-28 34 * @d_parent: holds parent's dentry
63940449555e79 Ajay Kaher 2023-07-28 35 * @dentry: once accessed holds dentry
c1504e51023847 Ajay Kaher 2023-07-28 36 * @list: file or directory to be added to parent directory
c1504e51023847 Ajay Kaher 2023-07-28 37 * @ei: list of files and directories within directory
c1504e51023847 Ajay Kaher 2023-07-28 38 * @fop: file_operations for file or directory
c1504e51023847 Ajay Kaher 2023-07-28 39 * @iop: inode_operations for file or directory
c1504e51023847 Ajay Kaher 2023-07-28 40 * @data: something that the caller will want to get to later on
c1504e51023847 Ajay Kaher 2023-07-28 41 * @mode: the permission that the file or directory should have
c1504e51023847 Ajay Kaher 2023-07-28 42 */
c1504e51023847 Ajay Kaher 2023-07-28 43 struct eventfs_file {
c1504e51023847 Ajay Kaher 2023-07-28 44 const char *name;
63940449555e79 Ajay Kaher 2023-07-28 45 struct dentry *d_parent;
63940449555e79 Ajay Kaher 2023-07-28 46 struct dentry *dentry;
c1504e51023847 Ajay Kaher 2023-07-28 47 struct list_head list;
c1504e51023847 Ajay Kaher 2023-07-28 48 struct eventfs_inode *ei;
c1504e51023847 Ajay Kaher 2023-07-28 49 const struct file_operations *fop;
c1504e51023847 Ajay Kaher 2023-07-28 50 const struct inode_operations *iop;
63940449555e79 Ajay Kaher 2023-07-28 51 union {
63940449555e79 Ajay Kaher 2023-07-28 52 struct list_head del_list; /* list of eventfs_file to delete */
63940449555e79 Ajay Kaher 2023-07-28 53 struct rcu_head rcu; /* eventfs_file to delete */
63940449555e79 Ajay Kaher 2023-07-28 54 unsigned long is_freed; /* Freed if one of the above is set */
63940449555e79 Ajay Kaher 2023-07-28 55 };
c1504e51023847 Ajay Kaher 2023-07-28 56 void *data;
c1504e51023847 Ajay Kaher 2023-07-28 57 umode_t mode;
c1504e51023847 Ajay Kaher 2023-07-28 @58 };
c1504e51023847 Ajay Kaher 2023-07-28 59
:::::: The code at line 58 was first introduced by commit
:::::: c1504e5102384762bd06b068e9928b624a8a88c6 eventfs: Implement eventfs dir creation functions
:::::: TO: Ajay Kaher <akaher@vmware.com>
:::::: CC: Steven Rostedt (Google) <rostedt@goodmis.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-18 3:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202308181108.C2BQ6D3n-lkp@intel.com \
--to=lkp@intel.com \
--cc=akaher@vmware.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox