KEYS: for-next-keys-7.2-rc6

The following changes since commit 248951ddc14de84de3910f9b13f51491a8cd91df:

Merge tag 'hwmon-for-v7.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (2026-07-21 08:34:39 -0700)

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-rc6

for you to fetch changes up to a82c8a05e86f3f84e09698f65b4515b5d04633f6:

assoc_array: trim the final shortcut word using the current chunk end (2026-07-23 18:23:45 +0300)

----------------------------------------------------------------
Hi

This pull request contains bug fixes discussed in [1] and two fixes (in one commit) from Fabrice for DCP trusted keys backend..

BR, Jarkko

[1] https://lore.kernel.org/keyrings/[email protected]/

----------------------------------------------------------------
Fabrice Derepas (1):
KEYS: trusted: dcp: fix key_len validation and calc_blob_len() return type

Michael Bommarito (3):
keys: fix out-of-bounds read in keyring_get_key_chunk()
keys: make keyring key-chunk byte order agree with keyring_diff_objects()
assoc_array: trim the final shortcut word using the current chunk end

 lib/assoc_array.c                        |  3 ++-
 security/keys/keyring.c                  | 14 ++++++++------
 security/keys/trusted-keys/trusted_dcp.c | 15 +++++++++++----
 3 files changed, 21 insertions(+), 11 deletions(-)

Please don't explain commits with links. The commit log is supposed to be legible without a network connection. Links are ok as supplements and background information, but not as a "this is explained by link".

And the pull request is supposed to have what I can useas that commit log (either in the email or in the tag). Yes, I edit things for clarity and consistency, but I don't want to follow links and try to figure out what some discussion was all about.

So please give me an explanation for what you are asking me to pull. Both so that I see what I'm pulling, and so that I'll have a merge message explaining things for later.

I've done this myself this time, but please make your pull requests legible in the future. The patch series you merged even had a cover letter, please keep track of these things and don't make people search for them.

Linus

I'll keep this is mind and yeah, get the frustration with this.

BR, Jarkko

Right, and thanks for still merging it.

BR, Jarkko