From: kernel test robot <lkp@intel.com>
To: Joanne Koong <joannelkoong@gmail.com>,
miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, josef@toxicpanda.com,
bernd.schubert@fastmail.fm, laoar.shao@gmail.com,
kernel-team@meta.com
Subject: Re: [PATCH v2 2/2] fuse: add default_request_timeout and max_request_timeout sysctls
Date: Tue, 30 Jul 2024 15:49:16 +0800 [thread overview]
Message-ID: <202407301513.fphdIYEE-lkp@intel.com> (raw)
In-Reply-To: <20240730002348.3431931-3-joannelkoong@gmail.com>
Hi Joanne,
kernel test robot noticed the following build errors:
[auto build test ERROR on mszeredi-fuse/for-next]
[also build test ERROR on linus/master v6.11-rc1 next-20240730]
[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/Joanne-Koong/fuse-add-optional-kernel-enforced-timeout-for-requests/20240730-085106
base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
patch link: https://lore.kernel.org/r/20240730002348.3431931-3-joannelkoong%40gmail.com
patch subject: [PATCH v2 2/2] fuse: add default_request_timeout and max_request_timeout sysctls
config: i386-buildonly-randconfig-001-20240730 (https://download.01.org/0day-ci/archive/20240730/202407301513.fphdIYEE-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240730/202407301513.fphdIYEE-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/202407301513.fphdIYEE-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> fs/fuse/sysctl.c:30:30: error: macro "fuse_sysctl_register" passed 1 arguments, but takes just 0
30 | int fuse_sysctl_register(void)
| ^
In file included from fs/fuse/sysctl.c:9:
fs/fuse/fuse_i.h:1501: note: macro "fuse_sysctl_register" defined here
1501 | #define fuse_sysctl_register() (0)
|
>> fs/fuse/sysctl.c:31:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
31 | {
| ^
>> fs/fuse/sysctl.c:38:33: error: macro "fuse_sysctl_unregister" passed 1 arguments, but takes just 0
38 | void fuse_sysctl_unregister(void)
| ^
fs/fuse/fuse_i.h:1502: note: macro "fuse_sysctl_unregister" defined here
1502 | #define fuse_sysctl_unregister() do { } while (0)
|
fs/fuse/sysctl.c:39:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
39 | {
| ^
>> fs/fuse/sysctl.c:13:25: warning: 'fuse_sysctl_table' defined but not used [-Wunused-variable]
13 | static struct ctl_table fuse_sysctl_table[] = {
| ^~~~~~~~~~~~~~~~~
>> fs/fuse/sysctl.c:11:33: warning: 'fuse_table_header' defined but not used [-Wunused-variable]
11 | static struct ctl_table_header *fuse_table_header;
| ^~~~~~~~~~~~~~~~~
vim +/fuse_sysctl_register +30 fs/fuse/sysctl.c
10
> 11 static struct ctl_table_header *fuse_table_header;
12
> 13 static struct ctl_table fuse_sysctl_table[] = {
14 {
15 .procname = "default_request_timeout",
16 .data = &fuse_default_req_timeout,
17 .maxlen = sizeof(fuse_default_req_timeout),
18 .mode = 0644,
19 .proc_handler = proc_douintvec,
20 },
21 {
22 .procname = "max_request_timeout",
23 .data = &fuse_max_req_timeout,
24 .maxlen = sizeof(fuse_max_req_timeout),
25 .mode = 0644,
26 .proc_handler = proc_douintvec,
27 },
28 };
29
> 30 int fuse_sysctl_register(void)
> 31 {
32 fuse_table_header = register_sysctl("fs/fuse", fuse_sysctl_table);
33 if (!fuse_table_header)
34 return -ENOMEM;
35 return 0;
36 }
37
> 38 void fuse_sysctl_unregister(void)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-30 7:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 0:23 [PATCH v2 0/2] fuse: add timeout option for requests Joanne Koong
2024-07-30 0:23 ` [PATCH v2 1/2] fuse: add optional kernel-enforced timeout " Joanne Koong
2024-08-04 22:46 ` Bernd Schubert
2024-08-05 4:45 ` Joanne Koong
2024-08-05 13:05 ` Bernd Schubert
2024-08-05 4:52 ` Joanne Koong
2024-08-05 13:26 ` Bernd Schubert
2024-08-05 22:10 ` Joanne Koong
2024-08-06 15:43 ` Bernd Schubert
2024-08-06 17:08 ` Joanne Koong
2024-08-05 7:32 ` Jingbo Xu
2024-08-05 22:53 ` Joanne Koong
2024-08-06 2:45 ` Jingbo Xu
2024-08-06 16:43 ` Joanne Koong
2024-08-06 15:50 ` Bernd Schubert
2024-07-30 0:23 ` [PATCH v2 2/2] fuse: add default_request_timeout and max_request_timeout sysctls Joanne Koong
2024-07-30 7:49 ` kernel test robot [this message]
2024-07-30 9:14 ` kernel test robot
2024-08-05 7:38 ` Jingbo Xu
2024-08-06 1:26 ` Joanne Koong
2024-07-30 5:59 ` [PATCH v2 0/2] fuse: add timeout option for requests Yafang Shao
2024-07-30 18:16 ` Joanne Koong
2024-07-31 2:13 ` Yafang Shao
2024-07-31 17:52 ` Joanne Koong
2024-07-31 18:46 ` Joanne Koong
2024-08-01 2:47 ` Yafang Shao
2024-08-02 19:05 ` Joanne Koong
2024-08-04 7:46 ` Yafang Shao
2024-08-05 5:05 ` Joanne Koong
2024-08-06 16:23 ` Joanne Koong
2024-08-06 17:11 ` Bernd Schubert
2024-08-06 18:26 ` Joanne Koong
2024-08-06 18:37 ` Joanne Koong
2024-08-06 20:08 ` Bernd Schubert
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=202407301513.fphdIYEE-lkp@intel.com \
--to=lkp@intel.com \
--cc=bernd.schubert@fastmail.fm \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=laoar.shao@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=oe-kbuild-all@lists.linux.dev \
/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.