From: Sagi Grimberg <sagi@grimberg.me>
To: Chuck Lever <cel@kernel.org>, Scott Mayhew <smayhew@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
kernel-tls-handshake@lists.linux.dev
Subject: Re: Breakage in ktls-utils with nfs keyring?
Date: Tue, 5 May 2026 11:32:33 +0300 [thread overview]
Message-ID: <f4c22c54-f760-4b60-9acb-dbeb32071285@grimberg.me> (raw)
In-Reply-To: <4797a5a7-ac88-48a5-8707-b9e33a899da6@app.fastmail.com>
On 05/05/2026 11:15, Chuck Lever wrote:
> On Mon, May 4, 2026, at 8:44 AM, Chuck Lever wrote:
>> What you are asking for, then, is a 1.3.0 dot release for this fix. I
>> still don't feel there is a strong requirement for that, given that
>> distributions apply fixes to packages all the time. But I haven't made
>> a final call on that.
> After auditing the commit history between ktls-utils-1.3.0 and 1.4.0,
> there are enough fixes to bundle together and release a 1.3.1 that
> includes the fix for the keyring-based NFS mount failure. I've created
> a branch ktls-utils-1.3-fixes that can be tagged and released once the
> keyring fix is merged into main.
Thanks Chuck.
prev parent reply other threads:[~2026-05-05 8:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 13:32 Breakage in ktls-utils with nfs keyring? Sagi Grimberg
2026-04-30 13:38 ` Chuck Lever
2026-05-01 19:58 ` [PATCH] tlshd: fix keyring cert retrieval Scott Mayhew
2026-05-03 7:30 ` Sagi Grimberg
2026-05-01 20:19 ` Breakage in ktls-utils with nfs keyring? Scott Mayhew
2026-05-02 3:08 ` Chuck Lever
2026-05-03 7:48 ` Sagi Grimberg
2026-05-03 19:11 ` Chuck Lever
2026-05-03 20:37 ` Sagi Grimberg
2026-05-04 6:44 ` Chuck Lever
2026-05-04 8:02 ` Sagi Grimberg
2026-05-04 8:21 ` Hannes Reinecke
2026-05-05 8:15 ` Chuck Lever
2026-05-05 8:32 ` Sagi Grimberg [this message]
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=f4c22c54-f760-4b60-9acb-dbeb32071285@grimberg.me \
--to=sagi@grimberg.me \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).