From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.10 0/1] fs/fuse/dev.c:213: warning: Function parameter or member 'sync' not described in 'fuse_dev_wake_and_unlock'
Date: Sat, 04 Jul 2026 13:32:57 +0800 [thread overview]
Message-ID: <202607041301.VRf0LRtn-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-5.10
head: a00af2707c1d0a67daa8f91db74300f65d84db3b
commit: 05a8f2c4d2f5b0664b97f3c426783cc26a946b3b [0/1] FROMLIST: fuse: give wakeup hints to the scheduler
config: i386-randconfig-012-20260702 (https://download.01.org/0day-ci/archive/20260704/202607041301.VRf0LRtn-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260704/202607041301.VRf0LRtn-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/202607041301.VRf0LRtn-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/fuse/dev.c:213: warning: Function parameter or member 'fiq' not described in 'fuse_dev_wake_and_unlock'
>> fs/fuse/dev.c:213: warning: Function parameter or member 'sync' not described in 'fuse_dev_wake_and_unlock'
vim +213 fs/fuse/dev.c
be2ff42c5d6ebc Kirill Tkhai 2018-09-11 207
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 208 /**
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 209 * A new request is available, wake fiq->waitq
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 210 */
05a8f2c4d2f5b0 Pradeep P V K 2021-12-06 211 static void fuse_dev_wake_and_unlock(struct fuse_iqueue *fiq, bool sync)
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 212 __releases(fiq->lock)
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 @213 {
05a8f2c4d2f5b0 Pradeep P V K 2021-12-06 214 if (sync)
05a8f2c4d2f5b0 Pradeep P V K 2021-12-06 215 wake_up_sync(&fiq->waitq);
05a8f2c4d2f5b0 Pradeep P V K 2021-12-06 216 else
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 217 wake_up(&fiq->waitq);
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 218 kill_fasync(&fiq->fasync, SIGIO, POLL_IN);
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 219 spin_unlock(&fiq->lock);
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 220 }
ae3aad77f46fbb Stefan Hajnoczi 2018-06-18 221
:::::: The code at line 213 was first introduced by commit
:::::: ae3aad77f46fbba56eff7141b2fc49870b60827e fuse: add fuse_iqueue_ops callbacks
:::::: TO: Stefan Hajnoczi <stefanha@redhat.com>
:::::: CC: Miklos Szeredi <mszeredi@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-04 5:34 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=202607041301.VRf0LRtn-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.