From: John Meneghini <jmeneghi@redhat.com>
To: Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>,
Chris Leech <cleech@redhat.com>
Cc: linux-nvme@lists.infradead.org,
Prashanth Nayak <prashanth.nayak@netapp.com>
Subject: Re: [PATCH 1/1] libnvme: TLS PSK derivation fixes
Date: Tue, 26 Aug 2025 10:09:25 -0400 [thread overview]
Message-ID: <fddfda33-e149-4e0f-914c-c20dde754031@redhat.com> (raw)
In-Reply-To: <61da6ec7-500e-4e33-a51a-d2f6ec9e08b6@suse.de>
On 8/20/25 4:22 AM, Hannes Reinecke wrote:
> On 8/20/25 10:10, Daniel Wagner wrote:
>> On Mon, Aug 11, 2025 at 09:33:06PM -0700, Chris Leech wrote:
>>> If we don't have a resolution by then, maybe this is something we can
>>> resolve at ALPSS.
>>>
>>> [1] Side note; with nvme_fabrics_cfg _not_ being allocated through
>>> libnvme, I don't see how the various additions there can be ABI safe. It
>>> looks to me like this struct alone broke ABI in libnvme 1.4, 1.8, 1.9,
>>> and 1.11.
>>
>> I know and I was hopping it wouldn't cause troubles... nvme_fabrics_cfg
>> is a bit of a problem. I was planing to address this for v2.
>
> In a similar vein: shouldn't we have a session at ALPSS around
> libnvme v2?
Yes, both Chris and I have proposed a talk to discuss NVMe/TLS at ALPSS.
> Or, if not a session, maybe a beer topic?
Sure, you can drink a beer when we talk about it. ;-)
/John
> Cheers,
>
> Hannes
next prev parent reply other threads:[~2025-08-26 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 2:17 [PATCH 0/1] NVMe/TLS connection issues to SPDK Chris Leech
2025-07-21 2:17 ` [PATCH 1/1] libnvme: TLS PSK derivation fixes Chris Leech
2025-07-21 6:36 ` Hannes Reinecke
2025-07-21 15:31 ` Chris Leech
2025-07-25 9:36 ` Hannes Reinecke
2025-07-25 18:08 ` Chris Leech
2025-07-28 7:12 ` Hannes Reinecke
2025-08-08 16:18 ` John Meneghini
2025-08-12 4:33 ` Chris Leech
2025-08-18 9:42 ` Hannes Reinecke
2025-08-20 8:10 ` Daniel Wagner
2025-08-20 8:22 ` Hannes Reinecke
2025-08-26 14:09 ` John Meneghini [this message]
2025-07-21 7:11 ` [PATCH 0/1] NVMe/TLS connection issues to SPDK Hannes Reinecke
2025-07-21 15:44 ` Chris Leech
2025-07-22 6:27 ` Hannes Reinecke
2025-07-24 14:35 ` Daniel Wagner
2025-07-24 15:07 ` Chris Leech
2025-07-24 15:37 ` Daniel Wagner
2025-08-12 22:05 ` Chris Leech
2025-08-12 22:11 ` [RFC PATCH 1/2] crypto: hkdf: add hkdf_expand_label() Chris Leech
2025-08-18 9:44 ` Hannes Reinecke
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=fddfda33-e149-4e0f-914c-c20dde754031@redhat.com \
--to=jmeneghi@redhat.com \
--cc=cleech@redhat.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=prashanth.nayak@netapp.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 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.