From: "Luís Henriques" <lhenriques@suse.de>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Xiubo Li <xiubli@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph updates for 6.4-rc1
Date: Fri, 05 May 2023 12:42:45 +0100 [thread overview]
Message-ID: <87wn1nm2bu.fsf@brahms.olymp> (raw)
In-Reply-To: <20230504182810.165185-1-idryomov@gmail.com> (Ilya Dryomov's message of "Thu, 4 May 2023 20:28:10 +0200")
[re-arranged CC list]
Ilya Dryomov <idryomov@gmail.com> writes:
> Hi Linus,
>
> The following changes since commit 457391b0380335d5e9a5babdec90ac53928b23b4:
>
> Linux 6.3 (2023-04-23 12:02:52 -0700)
>
> are available in the Git repository at:
>
> https://github.com/ceph/ceph-client.git tags/ceph-for-6.4-rc1
>
> for you to fetch changes up to db2993a423e3fd0e4878f4d3ac66fe717f5f072e:
>
> ceph: reorder fields in 'struct ceph_snapid_map' (2023-04-30 12:37:28 +0200)
>
> ----------------------------------------------------------------
> A few filesystem improvements, with a rather nasty use-after-free fix
> from Xiubo intended for stable.
Thank you, Ilya. It's unfortunate that fscrypt support misses yet another
merge window, but I guess there are still a few loose ends.
Is there a public list of issues (kernel or ceph proper) still to be
sorted out before this feature gets merged? Or is this just a lack of
confidence on the implementation stability?
Cheers
--
Luís
next prev parent reply other threads:[~2023-05-05 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 18:28 [GIT PULL] Ceph updates for 6.4-rc1 Ilya Dryomov
2023-05-04 21:50 ` pr-tracker-bot
2023-05-05 11:42 ` Luís Henriques [this message]
2023-05-05 18:59 ` Ilya Dryomov
2023-05-08 8:50 ` Luís Henriques
2023-05-09 7:32 ` Xiubo Li
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=87wn1nm2bu.fsf@brahms.olymp \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=xiubli@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 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.