All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: <kernel-tls-handshake@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 0/5] Kick off ktls-utils 1.2 development
Date: Tue, 10 Jun 2025 09:25:45 -0400	[thread overview]
Message-ID: <20250610132550.39715-1-cel@kernel.org> (raw)

From: Chuck Lever <chuck.lever@oracle.com>

This is a small series collects a few recently discussed code
changes and other clean-ups. These have been pushed to
oracle/ktls-utils in a ktls-utils-1.2-dev branch.

By the way, I recently enabled CodeQL on chucklever/ktls-utils and
that's where patch 3/5 comes from. If anyone knows of sensible
static analysis that can be easily enabled via GitHub Action, let me
know and I can try to set that up.

Chuck Lever (5):
  tlshd: Fix a minor race
  tlshd: Remove unneeded variable "error"
  workflows: Limit permission of the makefile.yml action
  tlshd: Add default keyrings for NFS
  tlshd: Relocate TLSHD_ALLPERMS

 .github/workflows/makefile.yml |  1 +
 src/tlshd/config.c             | 93 +++++++++++++---------------------
 src/tlshd/tlshd.conf.man       |  8 ++-
 3 files changed, 42 insertions(+), 60 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-06-10 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 13:25 Chuck Lever [this message]
2025-06-10 13:25 ` [PATCH 1/5] tlshd: Fix a minor race Chuck Lever
2025-06-10 13:25 ` [PATCH 2/5] tlshd: Remove unneeded variable "error" Chuck Lever
2025-06-10 13:25 ` [PATCH 3/5] workflows: Limit permission of the makefile.yml action Chuck Lever
2025-06-10 13:25 ` [PATCH 4/5] tlshd: Add default keyrings for NFS Chuck Lever
2025-06-10 13:25 ` [PATCH 5/5] tlshd: Relocate TLSHD_ALLPERMS Chuck Lever

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=20250610132550.39715-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    /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.