All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: "Fabiano Rosas" <farosas@suse.de>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	devel@lists.libvirt.org, "Laurent Vivier" <lvivier@redhat.com>
Subject: Re: [PULL 25/32] crypto: fix lifecycle handling of gnutls credentials objects
Date: Thu, 23 Apr 2026 14:45:48 +0100	[thread overview]
Message-ID: <aeoijCiAfbgGewXE@redhat.com> (raw)
In-Reply-To: <6ffa975c-9d13-4569-bd50-59df75c89b9c@maciej.szmigiero.name>

On Fri, Apr 17, 2026 at 03:31:02PM +0200, Maciej S. Szmigiero wrote:
> On 3.04.2026 20:25, Maciej S. Szmigiero wrote:
> > On 3.11.2025 14:37, Daniel P. Berrangé wrote:
> > > As described in the previous commit, the gnutls credentials need to
> > > be kept alive for as long as the gnutls session object exists. Convert
> > > the QCryptoTLSCreds objects to use QCryptoTLSCredsBox and holding the
> > > gnutls credential objects. When loading the credentials into a gnutls
> > > session, store a reference to the box into the QCryptoTLSSession object.
> > > 
> > > This has the useful side effect that the QCryptoTLSSession code no
> > > longer needs to know about all the different credential types, it can
> > > use the generic pointer stored in the box.
> > > 
> > > Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > > ---
> > (..)
> > > diff --git a/crypto/tlscredsanon.c b/crypto/tlscredsanon.c
> > > index 5c55b07b2f..0a728ccbf6 100644
> > > --- a/crypto/tlscredsanon.c
> > > +++ b/crypto/tlscredsanon.c
> > > @@ -36,6 +36,7 @@ static int
> > >   qcrypto_tls_creds_anon_load(QCryptoTLSCredsAnon *creds,
> > >                               Error **errp)
> > >   {
> > > +    g_autoptr(QCryptoTLSCredsBox) box = NULL;
> > >       g_autofree char *dhparams = NULL;
> > >       int ret;
> > > @@ -43,6 +44,8 @@ qcrypto_tls_creds_anon_load(QCryptoTLSCredsAnon *creds,
> > >               creds->parent_obj.dir ? creds->parent_obj.dir : "<nodir>");
> > >       if (creds->parent_obj.endpoint == QCRYPTO_TLS_CREDS_ENDPOINT_SERVER) {
> > > +        box = qcrypto_tls_creds_box_new_server(GNUTLS_CRD_ANON);
> > > +
> > >           if (creds->parent_obj.dir &&
> > >               qcrypto_tls_creds_get_path(&creds->parent_obj,
> > >                                          QCRYPTO_TLS_CREDS_DH_PARAMS,
> > > @@ -50,7 +53,7 @@ qcrypto_tls_creds_anon_load(QCryptoTLSCredsAnon *creds,
> > >               return -1;
> > >           }
> > > -        ret = gnutls_anon_allocate_server_credentials(&creds->data.server);
> > > +        ret = gnutls_anon_allocate_server_credentials(&box->data.anonserver);
> > >           if (ret < 0) {
> > >               error_setg(errp, "Cannot allocate credentials: %s",
> > >                          gnutls_strerror(ret));
> > > @@ -58,42 +61,26 @@ qcrypto_tls_creds_anon_load(QCryptoTLSCredsAnon *creds,
> > >           }
> > >           if (qcrypto_tls_creds_get_dh_params_file(&creds->parent_obj, dhparams,
> > > -                                                 &creds->parent_obj.dh_params,
> > > -                                                 errp) < 0) {
> > > +                                                 &box->dh_params, errp) < 0) {
> > >               return -1;
> > >           }
> > > -        gnutls_anon_set_server_dh_params(creds->data.server,
> > > -                                         creds->parent_obj.dh_params);
> > > +        gnutls_anon_set_server_dh_params(box->data.anonserver,
> > > +                                         box->dh_params);
> > >       } else {
> > > -        ret = gnutls_anon_allocate_client_credentials(&creds->data.client);
> > > +        ret = gnutls_anon_allocate_client_credentials(&box->data.anonclient);
> > 
> > Pointed question - where's the object pointed to by "box" allocated in this case
> > of an anonymous TLS client being loaded? :)
> 
> To be clear, that was supposed to be a humorous report of a regression introduced
> by the above commit - sorry if it wasn't communicated well.

No problem. I understood your message, I simply forget to
reply to it :-(

> Reproducer:
> > $ qemu-system-x86_64 -object tls-creds-anon,endpoint=client,id=test
> > Segmentation fault
> 
> The above code branch really needs something like
> "box = qcrypto_tls_creds_box_new_client(GNUTLS_CRD_ANON)".

Yep, and even more importantly we needed a test case in test-crypto-tlssession
to validate this works !

I've CC'd you on the proposal fix



  reply	other threads:[~2026-04-23 13:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 13:36 [PULL 00/32] Next pr patches Daniel P. Berrangé
2025-11-03 13:36 ` [PULL 01/32] Implement -run-with exit-with-parent=on Daniel P. Berrangé
2025-11-03 13:36 ` [PULL 02/32] tests/qtest: Use exit-with-parent=on in qtest invocations Daniel P. Berrangé
2025-11-03 13:36 ` [PULL 03/32] crypto/hash: Have hashing functions take void * buffer argument Daniel P. Berrangé
2025-11-03 13:36 ` [PULL 04/32] io/channel: Have read/write " Daniel P. Berrangé
2025-11-03 13:36 ` [PULL 05/32] io: add a "blocking" field to QIOChannelSocket Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 06/32] io: flush zerocopy socket error queue on sendmsg failure due to ENOBUF Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 07/32] crypto: bump min gnutls to 3.7.5 Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 08/32] crypto: unconditionally enable gnutls XTS support Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 09/32] crypto: bump min libgcrypt to 1.9.4 Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 10/32] crypto: bump min nettle to 3.7.3 Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 11/32] crypto: drop in-tree XTS cipher mode impl Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 12/32] crypto: remove redundant parameter checking CA certs Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 13/32] crypto: add missing free of certs array Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 14/32] crypto: replace stat() with access() for credential checks Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 15/32] crypto: remove redundant access() checks before loading certs Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 16/32] crypto: move check for TLS creds 'dir' property Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 17/32] crypto: use g_autofree when loading x509 credentials Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 18/32] crypto: remove needless indirection via parent_obj field Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 19/32] crypto: move release of DH parameters into TLS creds parent Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 20/32] crypto: shorten the endpoint == server check in TLS creds Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 21/32] crypto: remove duplication loading x509 CA cert Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 22/32] crypto: reduce duplication in handling TLS priority strings Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 23/32] crypto: introduce method for reloading TLS creds Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 24/32] crypto: introduce a wrapper around gnutls credentials Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 25/32] crypto: fix lifecycle handling of gnutls credentials objects Daniel P. Berrangé
2026-04-03 18:25   ` Maciej S. Szmigiero
2026-04-17 13:31     ` Maciej S. Szmigiero
2026-04-23 13:45       ` Daniel P. Berrange [this message]
2026-04-23 19:07         ` Maciej S. Szmigiero
2025-11-03 13:37 ` [PULL 26/32] crypto: make TLS credentials structs private Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 27/32] crypto: deprecate use of external dh-params.pem file Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 28/32] crypto: avoid loading the CA certs twice Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 29/32] crypto: avoid loading the identity " Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 30/32] crypto: expand logic to cope with multiple certificate identities Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 31/32] crypto: support upto 5 parallel " Daniel P. Berrangé
2025-11-03 13:37 ` [PULL 32/32] docs: creation of x509 certs compliant with post-quantum crypto Daniel P. Berrangé
2025-11-04 15:19 ` [PULL 00/32] Next pr patches Richard Henderson

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=aeoijCiAfbgGewXE@redhat.com \
    --to=berrange@redhat.com \
    --cc=devel@lists.libvirt.org \
    --cc=farosas@suse.de \
    --cc=lvivier@redhat.com \
    --cc=mail@maciej.szmigiero.name \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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 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.