From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ajay Kaher <akaher@vmware.com>,
Zheng Yejian <zhengyejian1@huawei.com>
Subject: Re: [PATCH] tracefs/eventfs: Use dput to free the toplevel events directory
Date: Wed, 6 Sep 2023 10:52:03 +0800 [thread overview]
Message-ID: <202309061055.V08YOtla-lkp@intel.com> (raw)
In-Reply-To: <20230905183332.628d7cc0@gandalf.local.home>
Hi Steven,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on next-20230905]
[cannot apply to v6.5]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/tracefs-eventfs-Use-dput-to-free-the-toplevel-events-directory/20230906-063414
base: linus/master
patch link: https://lore.kernel.org/r/20230905183332.628d7cc0%40gandalf.local.home
patch subject: [PATCH] tracefs/eventfs: Use dput to free the toplevel events directory
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230906/202309061055.V08YOtla-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230906/202309061055.V08YOtla-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/202309061055.V08YOtla-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/tracefs/event_inode.c: In function 'eventfs_remove_events_dir':
>> fs/tracefs/event_inode.c:804:31: warning: variable 'ei' set but not used [-Wunused-but-set-variable]
804 | struct eventfs_inode *ei;
| ^~
vim +/ei +804 fs/tracefs/event_inode.c
5bdcd5f5331a276 Ajay Kaher 2023-07-28 794
5bdcd5f5331a276 Ajay Kaher 2023-07-28 795 /**
5bdcd5f5331a276 Ajay Kaher 2023-07-28 796 * eventfs_remove_events_dir - remove eventfs dir or file from list
5bdcd5f5331a276 Ajay Kaher 2023-07-28 797 * @dentry: events's dentry to be removed.
5bdcd5f5331a276 Ajay Kaher 2023-07-28 798 *
5bdcd5f5331a276 Ajay Kaher 2023-07-28 799 * This function remove events main directory
5bdcd5f5331a276 Ajay Kaher 2023-07-28 800 */
5bdcd5f5331a276 Ajay Kaher 2023-07-28 801 void eventfs_remove_events_dir(struct dentry *dentry)
5bdcd5f5331a276 Ajay Kaher 2023-07-28 802 {
5bdcd5f5331a276 Ajay Kaher 2023-07-28 803 struct tracefs_inode *ti;
5bdcd5f5331a276 Ajay Kaher 2023-07-28 @804 struct eventfs_inode *ei;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-06 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 22:33 [PATCH] tracefs/eventfs: Use dput to free the toplevel events directory Steven Rostedt
2023-09-06 2:52 ` 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=202309061055.V08YOtla-lkp@intel.com \
--to=lkp@intel.com \
--cc=akaher@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=zhengyejian1@huawei.com \
/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