On Thu, 2023-01-12 at 12:21 -0500, Paul Moore wrote: > On Tue, Jan 10, 2023 at 3:56 AM Roberto Sassu > <roberto.sassu@xxxxxxxxxxxxxxx> wrote: > > On Thu, 2022-12-01 at 11:41 +0100, Roberto Sassu wrote: > > > From: Roberto Sassu <roberto.sassu@xxxxxxxxxx> > > > > > > In preparation for removing security_old_inode_init_security(), switch to > > > security_inode_init_security(). > > > > > > Extend the existing ocfs2_initxattrs() to take the > > > ocfs2_security_xattr_info structure from fs_info, and populate the > > > name/value/len triple with the first xattr provided by LSMs. > > > > Hi Mark, Joel, Joseph > > > > some time ago I sent this patch set to switch to the newer > > function security_inode_init_security(). Almost all the other parts of > > this patch set have been reviewed, and the patch set itself should be > > ready to be merged. > > > > I kindly ask if you could have a look at this patch and give your > > Reviewed-by, so that Paul could take the patch set. > > I've been pushing to clean up some of the LSM interfaces to try and > simplify things and remove as many special cases as possible, > Roberto's work in this patchset is part of that. I would really > appreciate it if the vfs/ocfs2 folks could give patch 2/6 a quick look > to make sure you are okay with the changes. > > I realize that the various end-of-year holidays tend to slow things > down a bit, but this patchset has been on the lists for over a month > now; if I don't hear anything in the next week or two I'll assume you > folks are okay with these patches ... Hi Paul is this patch set going to land in 6.3? Thanks Roberto
