linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
	keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] keys: Add tracepoints
Date: Wed, 21 Aug 2024 13:36:08 +0100	[thread overview]
Message-ID: <20240821123616.60401-1-dhowells@redhat.com> (raw)

Hi Jarkko,

Here's a patch to add some tracepoints to keyrings to make it easier to
debug what's going on, plus a bunch of preliminary patches to move things
about a bit to make that easier.

The patches can also be found here:

	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-next

Thanks,
David

David Howells (7):
  keys: Out of line key_is_dead() so it can have tracepoints added in
  keys: Extract struct key_user to its own header for tracing purposes
  keys: Move key_get() out of line so a tracepoint can be added
  keys: Add a key_ref_get() wrapper
  keys: Use key_get() instead of __key_get()
  keys: Provide a key_try_get() function and use it
  keys: Add tracepoints for the keyrings facility

 Documentation/security/keys/core.rst |   1 -
 crypto/asymmetric_keys/restrict.c    |   6 +-
 include/keys/key_user.h              |  35 +++
 include/linux/key.h                  |  16 +-
 include/trace/events/key.h           | 401 +++++++++++++++++++++++++++
 security/keys/gc.c                   |   4 +
 security/keys/internal.h             |  41 +--
 security/keys/key.c                  |  70 ++++-
 security/keys/keyctl.c               |   2 +
 security/keys/keyring.c              |  45 ++-
 security/keys/process_keys.c         |  15 +-
 11 files changed, 566 insertions(+), 70 deletions(-)
 create mode 100644 include/keys/key_user.h
 create mode 100644 include/trace/events/key.h


             reply	other threads:[~2024-08-21 12:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 12:36 David Howells [this message]
2024-08-21 12:36 ` [PATCH 1/7] keys: Out of line key_is_dead() so it can have tracepoints added in David Howells
2024-08-27 18:22   ` Jarkko Sakkinen
2024-08-21 12:36 ` [PATCH 2/7] keys: Extract struct key_user to its own header for tracing purposes David Howells
2024-08-27 18:23   ` Jarkko Sakkinen
2024-08-21 12:36 ` [PATCH 3/7] keys: Move key_get() out of line so a tracepoint can be added David Howells
2024-08-27 18:23   ` Jarkko Sakkinen
2024-08-21 12:36 ` [PATCH 4/7] keys: Add a key_ref_get() wrapper David Howells
2024-08-27 18:23   ` Jarkko Sakkinen
2024-08-21 12:36 ` [PATCH 5/7] keys: Use key_get() instead of __key_get() David Howells
2024-08-27 18:24   ` Jarkko Sakkinen
2024-08-21 12:36 ` [PATCH 6/7] keys: Provide a key_try_get() function and use it David Howells
2024-08-27 18:24   ` Jarkko Sakkinen
2024-08-21 12:36 ` [PATCH 7/7] keys: Add tracepoints for the keyrings facility David Howells
2024-08-27 18:27   ` Jarkko Sakkinen
2024-09-28  2:03   ` Justin Stitt

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=20240821123616.60401-1-dhowells@redhat.com \
    --to=dhowells@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.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;
as well as URLs for NNTP newsgroup(s).