From: Jiri Pirko <jiri@resnulli.us>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, x86@kernel.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, jgg@ziepe.ca,
david.quigley@intel.com, lukas@wunner.de, ksinyuk@kernel.org,
rodrigo.vivi@intel.com, cedric.xing@intel.com, sameo@meta.com,
drdeeglaze@gmail.com, James.Bottomley@hansenpartnership.com,
aik@amd.com, jpiotrowski@nvidia.com, qinkun@google.com,
pgonda@google.com, alistair.francis@wdc.com, ankita@nvidia.com,
suzuki.poulose@arm.com, kas@kernel.org,
rick.p.edgecombe@intel.com, elena.reshetova@intel.com,
dave.hansen@linux.intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
peter.fang@intel.com
Subject: Re: [PATCH RFC 12/20] ctlv: Add device and operation dispatch
Date: Thu, 22 Oct 2026 11:05:41 +0200 [thread overview]
Message-ID: <atnRsQHieSNzE51D@FV6GYCPJ69> (raw)
In-Reply-To: <20261021022505.6fe1b1bb@jic23-hlaptop>
Wed, Oct 21, 2026 at 03:25:05AM +0200, jic23@kernel.org wrote:
>On Thu, 15 Oct 2026 16:50:45 +0200
>Jiri Pirko <jiri@resnulli.us> wrote:
>
>> From: Jiri Pirko <jiri@nvidia.com>
>>
>> Register CTLV devices, resolve family chains and dispatch operations
>> through validated messages. Wire CONFIG_CTLV and the generated root family
>> after all module objects are present.
>>
>> Assisted-by: Cursor: GPT-5.6 Sol
>> Assisted-by: Cursor: Claude Opus 5.5
>> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
>> ---
>> drivers/Kconfig | 2 +
>> drivers/Makefile | 1 +
>> drivers/ctlv/Makefile | 4 +-
>> drivers/ctlv/core.c | 1517 +++++++++++++++++++++++++++++++++++
>Normally I'd push back hard on too big to read, but it is an rfc
>and other patches in the series are much large.
>
>I'm out of time for today and not sure when I'll get back to this,
>so just a few quick comments inline on the bit I did look at.
>
>> drivers/ctlv/device.h | 17 +
>> include/linux/ctlv.h | 55 ++
>> include/linux/ctlv_family.h | 22 +
>> 7 files changed, 1616 insertions(+), 2 deletions(-)
>> create mode 100644 drivers/ctlv/core.c
>
>> diff --git a/drivers/ctlv/core.c b/drivers/ctlv/core.c
>> new file mode 100644
>> index 000000000000..aeab29fe2fdd
>> --- /dev/null
>> +++ b/drivers/ctlv/core.c
>
>...
>
>> +static int ctlv_file_open(struct inode *inode, struct file *filp)
>> +{
>> + struct ctlv_device *ctlvdev = container_of(inode->i_cdev, struct ctlv_device, cdev);
>> + struct ctlv_file *cfile;
>> + int ret;
>> +
>> + /*
>> + * A failed create can withdraw the cdev while an open is waiting for
>> + * the lifecycle lock, so admission itself first pins core storage.
>> + */
>> + get_device(&ctlvdev->dev);
>> + ctlv_file_open_pinned(ctlvdev);
>> + scoped_guard(rwsem_read, &ctlvdev->registration_lock) {
>> + if (!ctlv_file_open_allowed(ctlvdev)) {
>> + ret = -ENODEV;
>> + break;
>Personally I still dislike the hidden for loop in scoped_guard()
>and using break with that enough I'd do a
> do {
> guard(rwsem_read)(&ctlvdev->registration_lock);
>
>
> } while (0);
>
>Just so it is obvious what those breaks are from.
Agreed, easier to read. Will fix.
>
>Maybe I just need to get this one into my code review head...
>> + }
>> + if (!(filp->f_mode & FMODE_READ)) {
>> + ret = -EACCES;
>> + break;
>> + }
>> +
>> + cfile = kzalloc_obj(*cfile, GFP_KERNEL_ACCOUNT);
>> + if (!cfile) {
>> + ret = -ENOMEM;
>> + break;
>> + }
>> + cfile->ctlvdev = ctlvdev;
>> + /*
>> + * Commits this description to the device. An open that failed
>> + * after this would have to take it back.
>> + */
>> + ret = ctlv_event_file_init(cfile);
>> + if (ret) {
>> + kfree(cfile);
>> + break;
>> + }
>> + /* This description keeps the reference taken on entry. */
>> + filp->private_data = cfile;
>> + return 0;
>> + }
>> +
>> + put_device(&ctlvdev->dev);
>> + return ret;
>> +}
>
>> +struct ctlv_device *ctlv_create(struct device *parent_dev, const struct ctlv_family *family,
>> + const void *init_info)
>> +{
>> + struct ctlv_device *ctlvdev;
>> + int devnum, ret;
>> +
>> + if (!parent_dev || !family)
>> + return ERR_PTR(-EINVAL);
>> +
>> + ctlvdev = kzalloc_obj(*ctlvdev, GFP_KERNEL);
>> + if (!ctlvdev)
>> + return ERR_PTR(-ENOMEM);
>> + ctlvdev->family = family;
>> + init_rwsem(&ctlvdev->registration_lock);
>> + spin_lock_init(&ctlvdev->transition_lock);
>> + ctlv_event_device_init(ctlvdev);
>> +
>> + /* Before anything reads the schema through this device. */
>> + ret = ctlv_op_resolution_init(ctlvdev, family);
>> + if (ret)
>> + goto err_free;
>> + /* What this family's events need of every queue opened on it. */
>> + ret = ctlv_event_sizes(ctlvdev);
>> + if (ret)
>> + goto err_free;
>> + /* Before a minor is spent on a device that could not be announced. */
>> + ret = ctlv_device_uevent_check(family);
>> + if (ret)
>> + goto err_free;
>> + if (ctlvdev->dynamic_ops_count) {
>> + ctlvdev->disabled = bitmap_zalloc(ctlvdev->dynamic_ops_count, GFP_KERNEL);
>> + if (!ctlvdev->disabled) {
>> + ret = -ENOMEM;
>> + goto err_free;
>> + }
>> + }
>> + devnum = ida_alloc_max(&ctlv_device_ids, CTLV_MAX_DEVICES - 1, GFP_KERNEL);
>> + if (devnum < 0) {
>> + ret = devnum;
>> + goto err_free;
>> + }
>> +
>> + ctlvdev->dev.devt = ctlv_device_number + devnum;
>> + ctlvdev->dev.class = &ctlv_device_class;
>> + ctlvdev->dev.parent = parent_dev;
>> + device_initialize(&ctlvdev->dev);
>> + /*
>> + * The core owns the file operations, so an open holds the core module
>> + * and not the family's, which may unload while readers remain.
>> + */
>> + cdev_init(&ctlvdev->cdev, &ctlv_file_operations);
>> + ctlvdev->cdev.owner = THIS_MODULE;
>> +
>> + ret = dev_set_name(&ctlvdev->dev, "ctlv%d", devnum);
>> + if (ret)
>> + goto err_put;
>> + ret = ctlv_family_claim_add(family->schema);
>> + if (ret)
>> + goto err_put;
>> + ret = ctlv_family_privs_pre_init(ctlvdev, init_info);
>> + if (ret)
>> + goto err_put;
>> + ret = ctlv_family_privs_init(ctlvdev);
>> + if (ret)
>> + goto err_put;
>> + ctlv_op_publish_all(ctlvdev);
>> + ctlv_event_contexts_start(ctlvdev);
>> + ret = ctlv_family_privs_post_init(ctlvdev);
>> + if (ret)
>> + goto err_fini;
>> + scoped_guard(rwsem_write, &ctlvdev->registration_lock) {
>> + ret = ctlv_device_add(ctlvdev);
>> + if (!ret)
>> + ctlvdev->registered = true;
>> + }
>> + if (ret)
>> + goto err_fini;
>> + return ctlvdev;
>> +
>> +err_fini:
>> + ctlv_device_fini(ctlvdev);
>> +err_put:
>> + put_device(&ctlvdev->dev);
>> + return ERR_PTR(ret);
>
>Jason did some nice handling in the fwctl stuff for
>device alloc and hand over after device_initialize()
>(I've copied it into a few places recently :)
>
>I'd like to see something similar here as it made
>it easier to follow lifetimes etc.
Will do.
>
>> +err_free:
>> + bitmap_free(ctlvdev->disabled);
>> + ctlv_family_privs_free(ctlvdev);
>> + kfree(ctlvdev->ops);
>> + kfree(ctlvdev);
>> + return ERR_PTR(ret);
>> +}
>> +EXPORT_SYMBOL_NS_GPL(ctlv_create, "CTLV");
>
Thanks!
next prev parent reply other threads:[~2026-10-22 9:05 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:50 [PATCH RFC 00/20] attestation: Add a common subsystem and TDX support Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 01/20] ctlv: Add the schema language and generator Jiri Pirko
2026-10-20 22:31 ` Jonathan Cameron
2026-10-21 13:23 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 02/20] ctlv: Add the UAPI wire format and family API Jiri Pirko
2026-10-19 23:29 ` Jason Gunthorpe
2026-10-20 12:26 ` Jiri Pirko
2026-10-20 23:00 ` Jonathan Cameron
2026-10-20 23:39 ` Jonathan Cameron
2026-10-21 13:54 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 03/20] ctlv: Add the root family specification and generated files Jiri Pirko
2026-10-19 23:29 ` Jason Gunthorpe
2026-10-20 12:28 ` Jiri Pirko
2026-10-20 12:55 ` Jason Gunthorpe
2026-10-20 14:07 ` Jiri Pirko
2026-10-20 23:30 ` Jonathan Cameron
2026-10-21 16:25 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 04/20] Documentation: ctlv: Add userspace ABI Jiri Pirko
2026-10-19 23:29 ` Jason Gunthorpe
2026-10-20 14:06 ` Jiri Pirko
2026-10-21 0:11 ` Jonathan Cameron
2026-10-22 9:01 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 05/20] ctlv: Prepare message input handling Jiri Pirko
2026-10-21 0:43 ` Jonathan Cameron
2026-10-22 8:27 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 06/20] ctlv: Prepare blob descriptor validation Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 07/20] ctlv: Prepare schema validation Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 08/20] ctlv: Prepare message output handling Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 09/20] ctlv: Prepare VA blob handling Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 10/20] ctlv: Prepare event queue support Jiri Pirko
2026-10-21 1:12 ` Jonathan Cameron
2026-10-22 9:04 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 11/20] ctlv: Prepare runtime introspection Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 12/20] ctlv: Add device and operation dispatch Jiri Pirko
2026-10-21 1:25 ` Jonathan Cameron
2026-10-22 9:05 ` Jiri Pirko [this message]
2026-10-15 14:50 ` [PATCH RFC 13/20] Documentation: ctlv: Describe how to write a family Jiri Pirko
2026-10-19 23:29 ` Jason Gunthorpe
2026-10-21 14:23 ` Jiri Pirko
2026-10-21 14:49 ` Jason Gunthorpe
2026-10-21 16:24 ` Jiri Pirko
2026-10-21 16:48 ` Jason Gunthorpe
2026-10-22 8:22 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 14/20] attestation: Add the base family specification and generated files Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 15/20] attestation: Prepare provider and instance core Jiri Pirko
2026-10-19 23:29 ` Jason Gunthorpe
2026-10-21 13:04 ` Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 16/20] attestation: Prepare measurement register journal Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 17/20] attestation: Add CTLV operation handling Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 18/20] tdx-guest: Expose the native attestation service API Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 19/20] attestation: Add the TDX family specification and generated files Jiri Pirko
2026-10-15 14:50 ` [PATCH RFC 20/20] attestation: Add the TDX family implementation Jiri Pirko
2026-10-16 23:43 ` [PATCH RFC 00/20] attestation: Add a common subsystem and TDX support Jason Gunthorpe
2026-10-17 18:16 ` Dionna Glaze
2026-10-17 19:06 ` Jarkko Sakkinen
2026-10-17 19:08 ` Jarkko Sakkinen
2026-10-17 19:22 ` Jarkko Sakkinen
2026-10-17 20:55 ` Jason Gunthorpe
2026-10-17 21:14 ` Jarkko Sakkinen
2026-10-17 20:34 ` Jason Gunthorpe
2026-10-17 20:55 ` Jarkko Sakkinen
2026-10-17 23:10 ` Jason Gunthorpe
2026-10-18 23:53 ` Dionna Glaze
2026-10-19 12:08 ` Jiri Pirko
2026-10-19 16:10 ` Dionna Glaze
2026-10-19 22:56 ` Jason Gunthorpe
2026-10-21 8:33 ` Jiri Pirko
2026-10-21 14:12 ` Mimi Zohar
2026-10-21 14:35 ` Jason Gunthorpe
2026-10-21 19:05 ` Mimi Zohar
2026-10-20 9:26 ` Jiri Pirko
2026-10-20 13:45 ` Mimi Zohar
2026-10-20 14:06 ` Jason Gunthorpe
2026-10-20 15:22 ` Mimi Zohar
2026-10-20 16:11 ` Yeoreum Yun
2026-10-20 16:52 ` Jason Gunthorpe
2026-10-21 12:23 ` Mimi Zohar
2026-10-21 13:18 ` Jarkko Sakkinen
2026-10-21 13:50 ` Yeoreum Yun
2026-10-21 13:51 ` Jason Gunthorpe
2026-10-21 14:31 ` Mimi Zohar
2026-10-21 14:39 ` Jason Gunthorpe
2026-10-21 12:48 ` James Bottomley
2026-10-21 13:55 ` Jason Gunthorpe
2026-10-19 12:40 ` Jarkko Sakkinen
2026-10-19 23:11 ` Jason Gunthorpe
2026-10-20 12:49 ` James Bottomley
2026-10-20 13:13 ` Jason Gunthorpe
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=atnRsQHieSNzE51D@FV6GYCPJ69 \
--to=jiri@resnulli.us \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aik@amd.com \
--cc=alistair.francis@wdc.com \
--cc=ankita@nvidia.com \
--cc=cedric.xing@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david.quigley@intel.com \
--cc=drdeeglaze@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=jgg@ziepe.ca \
--cc=jic23@kernel.org \
--cc=jpiotrowski@nvidia.com \
--cc=kas@kernel.org \
--cc=ksinyuk@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=peter.fang@intel.com \
--cc=pgonda@google.com \
--cc=qinkun@google.com \
--cc=rick.p.edgecombe@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sameo@meta.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=suzuki.poulose@arm.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®