From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [axboe:nowait/fsnotify 1/2] fs/notify/inotify/inotify_user.c:698:9: error: member reference type 'const struct fd_prepare *const' is a pointer; did you mean to use '->'?
Date: Fri, 30 Oct 2026 03:41:25 +0100 [thread overview]
Message-ID: <202610300357.n7Os1pXZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git nowait/fsnotify
head: 0257f0c419d8ac11d8401ca3125b3712ccd706b4
commit: e226d04bfaf89cd0024a132fd9bafc3de182894d [1/2] inotify: convert read to read_iter
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20261030/202610300357.n7Os1pXZ-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261030/202610300357.n7Os1pXZ-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/202610300357.n7Os1pXZ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/notify/inotify/inotify_user.c:698:9: error: member reference type 'const struct fd_prepare *const' is a pointer; did you mean to use '->'?
698 | if (fdf.err) {
| ~~~^
| ->
>> fs/notify/inotify/inotify_user.c:698:10: error: no member named 'err' in 'struct fd_prepare'
698 | if (fdf.err) {
| ~~~ ^
fs/notify/inotify/inotify_user.c:700:13: error: member reference type 'const struct fd_prepare *const' is a pointer; did you mean to use '->'?
700 | return fdf.err;
| ~~~^
| ->
fs/notify/inotify/inotify_user.c:700:14: error: no member named 'err' in 'struct fd_prepare'
700 | return fdf.err;
| ~~~ ^
4 errors generated.
vim +698 fs/notify/inotify/inotify_user.c
676
677
678 /* inotify syscalls */
679 static int do_inotify_init(int flags)
680 {
681 struct fsnotify_group *group;
682
683 /* Check the IN_* constants for consistency. */
684 BUILD_BUG_ON(IN_CLOEXEC != O_CLOEXEC);
685 BUILD_BUG_ON(IN_NONBLOCK != O_NONBLOCK);
686
687 if (flags & ~(IN_CLOEXEC | IN_NONBLOCK))
688 return -EINVAL;
689
690 /* fsnotify_obtain_group took a reference to group, we put this when we kill the file in the end */
691 group = inotify_new_group(inotify_max_queued_events);
692 if (IS_ERR(group))
693 return PTR_ERR(group);
694
695 FD_PREPARE(fdf, O_RDONLY | flags,
696 anon_inode_getfile_fmode("inotify", &inotify_fops, group,
697 O_RDONLY | flags, FMODE_NOWAIT));
> 698 if (fdf.err) {
699 fsnotify_destroy_group(group);
700 return fdf.err;
701 }
702
703 return fd_publish(fdf);
704 }
705
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-30 2:42 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=202610300357.n7Os1pXZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox