From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] TPM DEVICE DRIVER: for-next-keys-7.2-rc1
Date: Fri, 19 Jun 2026 03:49:12 +0300 [thread overview]
Message-ID: <ajSSCDRWgINwlDT1@kernel.org> (raw)
OOPS please ignore I'll resend this!
Wrong template apologies.
BR, Jarkko
On Fri, Jun 19, 2026 at 12:47:08AM +0000, jarkko@kernel.org wrote:
> The following changes since commit 0e0611827f3349d0a2ac121c023a6d3260dcecdb:
>
> Merge tag 'pull-fixes' of gitolite.kernel.org:pub/scm/linux/kernel/git/viro/vfs (2026-06-15 15:53:57 +0530)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/for-next-keys-7.2-rc1
>
> for you to fetch changes up to 1b9524250996b1f2f49833a1b2ae21c34e486f85:
>
> keys: keyctl_pkey: replace BUG with return -EOPNOTSUPP (2026-06-15 15:19:13 +0300)
>
> ----------------------------------------------------------------
> Hi
>
> Please, pull. This pull request contains only fixes.
>
> BR, Jarkko
>
> ----------------------------------------------------------------
> David Laight (1):
> keys: Replace strcpy(derived_buf, "AUTH_KEY") with strscpy(..., HASH_SIZE)
>
> Eric Biggers (1):
> KEYS: encrypted: Remove unnecessary selection of CRYPTO_RNG
>
> Gui-Dong Han (1):
> KEYS: Use acquire when reading state in keyring search
>
> Jarkko Sakkinen (2):
> KEYS: fix overflow in keyctl_pkey_params_get_2()
> KEYS: trusted: Debugging as a feature
>
> Len Bao (1):
> keys/trusted_keys: mark 'migratable' as __ro_after_init
>
> Mohammed EL Kadiri (3):
> keys: prevent slab cache merging for key_jar
> keys: request_key: replace BUG with return -EINVAL
> keys: keyctl_pkey: replace BUG with return -EOPNOTSUPP
>
> Shaomin Chen (1):
> keys: Pin request_key_auth payload in instantiate paths
>
> Thorsten Blum (1):
> keys: use kmalloc_flex in user_preparse
>
> Documentation/admin-guide/kernel-parameters.txt | 16 +++++++++
> include/keys/request_key_auth-type.h | 2 ++
> include/keys/trusted-type.h | 21 +++++++-----
> security/keys/Kconfig | 1 -
> security/keys/encrypted-keys/encrypted.c | 4 +--
> security/keys/internal.h | 2 ++
> security/keys/key.c | 2 +-
> security/keys/keyctl.c | 24 ++++++++++----
> security/keys/keyctl_pkey.c | 14 ++++++--
> security/keys/keyring.c | 2 +-
> security/keys/request_key.c | 2 +-
> security/keys/request_key_auth.c | 33 +++++++++++++++++--
> security/keys/trusted-keys/Kconfig | 23 +++++++++++++
> security/keys/trusted-keys/trusted_caam.c | 7 ++--
> security/keys/trusted-keys/trusted_core.c | 8 ++++-
> security/keys/trusted-keys/trusted_tpm1.c | 44 ++++++++++++++-----------
> security/keys/user_defined.c | 2 +-
> 17 files changed, 158 insertions(+), 49 deletions(-)
next reply other threads:[~2026-06-19 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 0:49 Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-19 0:48 Jarkko Sakkinen
2026-06-19 19:24 ` pr-tracker-bot
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=ajSSCDRWgINwlDT1@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome