Re: staging in the fscrypt patches

[Jeff Layton <jlayton@kernel.org>]

On Sat, 2022-05-28 at 07:18 +0800, Xiubo Li wrote:
> On 5/28/22 12:34 AM, Jeff Layton wrote:
> > Once the Ceph PR for this merge window has gone through, I'd like to
> > start merging in some of the preliminary fscrypt patches. In particular,
> > I'd like to merge these two patches into ceph-client/master so that they
> > go to linux-next:
> > 
> > be2bc0698248 fscrypt: export fscrypt_fname_encrypt and fscrypt_fname_encrypted_size
> > 7feda88977b8 fscrypt: add fscrypt_context_for_new_inode
> > 
> > I'd like to see these in ceph-client/testing, so that they start getting
> > some exposure in teuthology:
> > 
> > 477944c2ed29 libceph: add spinlock around osd->o_requests
> > 355d9572686c libceph: define struct ceph_sparse_extent and add some helpers
> > 229a3e2cf1c7 libceph: add sparse read support to msgr2 crc state machine
> > a0a9795c2a2c libceph: add sparse read support to OSD client
> > 6a16e0951aaf libceph: support sparse reads on msgr2 secure codepath
> > 538b618f8726 libceph: add sparse read support to msgr1
> > 7ef4c2c39f05 ceph: add new mount option to enable sparse reads
> > b609087729f4 ceph: preallocate inode for ops that may create one
> > e66323d65639 ceph: make ceph_msdc_build_path use ref-walk
> > 
> > ...they don't add any new functionality (other than the sparse read
> > stuff), but they do change "normal" operation in some ways that we'll
> > need later, so I'd like to see them start being regularly tested.
> > 
> > If that goes OK, then I'll plan to start merging another tranche a
> > couple of weeks after that.
> > 
> > Does that sound OK?
> 
> Sounds good to me.
> 
> -- Xiubo
> 
> 

Done. I've gone ahead and merged these patches into the two branches.
Please let me know if you encounter any issues from them!

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>