On Fri, May 5, 2023 at 1:42 PM Luís Henriques <lhenriques@xxxxxxx> wrote: > > > [re-arranged CC list] > > Ilya Dryomov <idryomov@xxxxxxxxx> 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? Hi Luís, When fscrypt work got supposedly finalized it was already pretty late in the cycle and it just didn't help that upon pulling it I encountered a subtly broken patch which was NACKed before ("libceph: defer removing the req from osdc just after req->r_callback") and also that "optionally bypass content encryption" leftover. It got addressed but too late for such a large change to be staged for 6.4 merge window. I would encourage everyone to make another pass over the entire series to make sure that there is nothing eyebrows-raising left there and that it really feels solid. Thanks, Ilya
