From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org
Subject: [GIT PULL] tpmdd changes for v6.9-rc2
Date: Tue, 26 Mar 2024 16:38:38 +0200 [thread overview]
Message-ID: <20240326143838.15076-1-jarkko@kernel.org> (raw)
Merge tag 'gfs2-v6.8-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2024-03-25 10:53:39 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/tpmdd-v6.9-rc2
for you to fetch changes up to 6999f8229e5998e8286e6a960779b6c202d878da:
keys: Fix overwrite of key expiration on instantiation (2024-03-26 16:24:53 +0200)
----------------------------------------------------------------
Hi,
This pull request contains just a couple of unintrusive changes for
v6.9.
Note that "keys: update key quotas in key_put()" makes quotas less racy
by updating qnkeys and qnbytes already in key_put(). It is not exactly a
bug fix but does make overall kerrnel behaviour more stable and
consistent. Just adding this because I try to keep follow-up PR's for
kernel releases bug fix only but I think here it makes sense to make an
exception.
BR, Jarkko
----------------------------------------------------------------
Luis Henriques (1):
keys: update key quotas in key_put()
Silvio Gissi (1):
keys: Fix overwrite of key expiration on instantiation
security/keys/gc.c | 8 --------
security/keys/key.c | 35 ++++++++++++++++++++++++-----------
security/keys/keyctl.c | 11 ++++++-----
3 files changed, 30 insertions(+), 24 deletions(-)
next reply other threads:[~2024-03-26 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 14:38 Jarkko Sakkinen [this message]
2024-03-30 22:32 ` [GIT PULL] tpmdd changes for v6.9-rc2 Linus Torvalds
2024-03-31 5:57 ` Jarkko Sakkinen
2024-03-31 15:36 ` Jarkko Sakkinen
2024-03-31 17:01 ` Linus Torvalds
2024-04-01 13:17 ` Jarkko Sakkinen
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=20240326143838.15076-1-jarkko@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 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.