From: kernel test robot <lkp@intel.com>
To: Li Wang <liwang@kylinos.cn>, Miklos Szeredi <miklos@szeredi.hu>,
Bernd Schubert <bernd@bsbernd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Li Wang <liwang@kylinos.cn>
Subject: Re: [PATCH v2] fuse: Send FORGET over io_uring when ring is ready
Date: Wed, 8 Apr 2026 07:06:04 +0200 [thread overview]
Message-ID: <202604080703.edi7Btyb-lkp@intel.com> (raw)
In-Reply-To: <20260403035752.20206-1-liwang@kylinos.cn>
Hi Li,
kernel test robot noticed the following build errors:
[auto build test ERROR on v7.0-rc7]
[also build test ERROR on linus/master]
[cannot apply to mszeredi-fuse/for-next next-20260407]
[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/Li-Wang/fuse-Send-FORGET-over-io_uring-when-ring-is-ready/20260408-015226
base: v7.0-rc7
patch link: https://lore.kernel.org/r/20260403035752.20206-1-liwang%40kylinos.cn
patch subject: [PATCH v2] fuse: Send FORGET over io_uring when ring is ready
config: x86_64-rhel-9.4-ltp (https://download.01.org/0day-ci/archive/20260408/202604080703.edi7Btyb-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260408/202604080703.edi7Btyb-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/202604080703.edi7Btyb-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/fuse/dev_uring.c: In function 'fuse_io_uring_send_forget':
>> fs/fuse/dev_uring.c:1433:21: error: 'struct fuse_args' has no member named 'abort_on_kill'
1433 | if (!d->args.abort_on_kill)
| ^
vim +1433 fs/fuse/dev_uring.c
1378
1379 /*
1380 * Send FUSE_FORGET through the io-uring ring when active; same payload as
1381 * fuse_read_single_forget(), with userspace committing like any other request.
1382 * Called from fuse_dev_queue_forget() when fuse_uring_ready().
1383 */
1384 void fuse_io_uring_send_forget(struct fuse_iqueue *fiq,
1385 struct fuse_forget_link *forget)
1386 {
1387 struct fuse_conn *fc = container_of(fiq, struct fuse_conn, iq);
1388 struct fuse_mount *fm;
1389 struct fuse_req *req;
1390 struct fuse_forget_uring_data *d;
1391
1392 if (!fuse_uring_ready(fc)) {
1393 fuse_dev_queue_forget_list(fiq, forget);
1394 return;
1395 }
1396
1397 down_read(&fc->killsb);
1398 if (list_empty(&fc->mounts)) {
1399 up_read(&fc->killsb);
1400 fuse_dev_queue_forget_list(fiq, forget);
1401 return;
1402 }
1403 fm = list_first_entry(&fc->mounts, struct fuse_mount, fc_entry);
1404 up_read(&fc->killsb);
1405
1406 d = kmalloc(sizeof(*d), GFP_KERNEL);
1407 if (!d)
1408 goto fallback;
1409
1410 atomic_inc(&fc->num_waiting);
1411 req = fuse_request_alloc(fm, GFP_KERNEL);
1412 if (!req) {
1413 kfree(d);
1414 fuse_drop_waiting(fc);
1415 goto fallback;
1416 }
1417
1418 memset(&d->args, 0, sizeof(d->args));
1419 d->inarg.nlookup = forget->forget_one.nlookup;
1420 d->args.opcode = FUSE_FORGET;
1421 d->args.nodeid = forget->forget_one.nodeid;
1422 d->args.in_numargs = 1;
1423 d->args.in_args[0].size = sizeof(d->inarg);
1424 d->args.in_args[0].value = &d->inarg;
1425 d->args.force = true;
1426 d->args.noreply = true;
1427 d->args.end = fuse_forget_uring_free;
1428
1429 kfree(forget);
1430
1431 fuse_force_creds(req);
1432 __set_bit(FR_WAITING, &req->flags);
> 1433 if (!d->args.abort_on_kill)
1434 __set_bit(FR_FORCE, &req->flags);
1435 fuse_adjust_compat(fc, &d->args);
1436 fuse_args_to_req(req, &d->args);
1437 req->in.h.len = sizeof(struct fuse_in_header) +
1438 fuse_len_args(req->args->in_numargs,
1439 (struct fuse_arg *)req->args->in_args);
1440
1441 fuse_uring_queue_fuse_req(fiq, req);
1442 return;
1443
1444 fallback:
1445 fuse_dev_queue_forget_list(fiq, forget);
1446 }
1447
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-08 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 3:57 [PATCH v2] fuse: Send FORGET over io_uring when ring is ready Li Wang
2026-04-03 19:00 ` Joanne Koong
2026-04-08 1:08 ` kernel test robot
2026-04-08 5:03 ` kernel test robot
2026-04-08 5:06 ` kernel test robot
2026-04-08 5:06 ` 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=202604080703.edi7Btyb-lkp@intel.com \
--to=lkp@intel.com \
--cc=bernd@bsbernd.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwang@kylinos.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox