From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>,
"Ilya Dryomov" <idryomov@gmail.com>,
"Alex Markuze" <amarkuze@redhat.com>,
"Xiubo Li" <xiubo.li@clyso.com>,
"Viacheslav Dubeyko" <slava@dubeyko.com>,
ceph-devel@vger.kernel.org,
"Jordan DESNOËS" <jordan.desnoes@francetv.fr>,
"Jordan DESNOËS via B4 Relay"
<devnull+jordan.desnoes.francetv.fr@kernel.org>
Subject: Re: [PATCH 6.18.y 0/4] libceph: add CEPH_CRYPTO_AES256KRB5 support
Date: Thu, 19 Nov 2026 11:08:16 -0500 [thread overview]
Message-ID: <2026-11-19-1-daily-reply-0014@kernel.org> (raw)
In-Reply-To: <20261119-aes256k-6-18-y-v1-0-bd5db87da2f5@francetv.fr>
> Backport of the libceph aes256k series from v7.0, as discussed in [1].
> Ilya is fine with it going to 6.18.y.
Ugh, this really looks like a brand new feature... Is it not?
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-19 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 8:57 [PATCH 6.18.y 0/4] libceph: add CEPH_CRYPTO_AES256KRB5 support Jordan DESNOËS via B4 Relay
2026-11-19 8:57 ` Jordan DESNOËS
2026-11-19 8:57 ` [PATCH 6.18.y 1/4] libceph: generalize ceph_x_encrypt_offset() and ceph_x_encrypt_buflen() Jordan DESNOËS via B4 Relay
2026-11-19 8:57 ` Jordan DESNOËS
2026-11-19 8:57 ` [PATCH 6.18.y 2/4] libceph: introduce ceph_crypto_key_prepare() Jordan DESNOËS via B4 Relay
2026-11-19 8:57 ` Jordan DESNOËS
2026-11-19 8:57 ` [PATCH 6.18.y 3/4] libceph: add support for CEPH_CRYPTO_AES256KRB5 Jordan DESNOËS via B4 Relay
2026-11-19 8:57 ` Jordan DESNOËS
2026-11-19 8:57 ` [PATCH 6.18.y 4/4] libceph: adapt ceph_x_challenge_blob hashing and msgr1 message signing Jordan DESNOËS via B4 Relay
2026-11-19 8:57 ` Jordan DESNOËS
2026-11-19 16:08 ` Sasha Levin [this message]
2026-11-19 17:29 ` [PATCH 6.18.y 0/4] libceph: add CEPH_CRYPTO_AES256KRB5 support DESNOËS Jordan
2026-11-20 20:38 ` Sasha Levin
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=2026-11-19-1-daily-reply-0014@kernel.org \
--to=sashal@kernel.org \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=devnull+jordan.desnoes.francetv.fr@kernel.org \
--cc=idryomov@gmail.com \
--cc=jordan.desnoes@francetv.fr \
--cc=slava@dubeyko.com \
--cc=stable@vger.kernel.org \
--cc=xiubo.li@clyso.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.