From: kernel test robot <lkp@intel.com>
To: Wen Yang <wen.yang@linux.dev>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: oe-kbuild-all@lists.linux.dev, Wen Yang <wen.yang@linux.dev>,
Jens Axboe <axboe@kernel.dk>, Dylan Yudaken <dylany@fb.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Paolo Bonzini <pbonzini@redhat.com>,
Dave Young <dyoung@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] eventfd: introduce configurable maximum value for eventfd
Date: Sun, 9 Mar 2025 22:31:38 +0800 [thread overview]
Message-ID: <202503092223.G4FJDVsM-lkp@intel.com> (raw)
In-Reply-To: <20250309055003.32194-1-wen.yang@linux.dev>
Hi Wen,
kernel test robot noticed the following build errors:
[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on linus/master v6.14-rc5 next-20250307]
[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/Wen-Yang/eventfd-introduce-configurable-maximum-value-for-eventfd/20250309-135152
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20250309055003.32194-1-wen.yang%40linux.dev
patch subject: [PATCH v3] eventfd: introduce configurable maximum value for eventfd
config: i386-buildonly-randconfig-003-20250309 (https://download.01.org/0day-ci/archive/20250309/202503092223.G4FJDVsM-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250309/202503092223.G4FJDVsM-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/202503092223.G4FJDVsM-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
fs/eventfd.c: In function 'eventfd_is_writable':
>> fs/eventfd.c:251:76: error: 'ucnt' undeclared (first use in this function); did you mean 'uint'?
251 | return (ctx->maximum > ctx->count) && (ctx->maximum - ctx->count > ucnt);
| ^~~~
| uint
fs/eventfd.c:251:76: note: each undeclared identifier is reported only once for each function it appears in
>> fs/eventfd.c:252:1: warning: control reaches end of non-void function [-Wreturn-type]
252 | }
| ^
vim +251 fs/eventfd.c
248
249 static inline bool eventfd_is_writable(const struct eventfd_ctx *ctx)
250 {
> 251 return (ctx->maximum > ctx->count) && (ctx->maximum - ctx->count > ucnt);
> 252 }
253
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-03-09 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 5:50 [PATCH v3] eventfd: introduce configurable maximum value for eventfd Wen Yang
2025-03-09 14:31 ` kernel test robot
2025-03-09 14:31 ` 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=202503092223.G4FJDVsM-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=dylany@fb.com \
--cc=dyoung@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wen.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox