Displaying 6 results from an estimated 6 matches for "new_xattr".
Did you mean:
new_xattrs
2023 Mar 24
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
..._inode_init_security(struct inode *inode, struct inode *dir,
> > > > const struct qstr *qstr,
> > > > const initxattrs initxattrs, void *fs_data)
> > > > {
> > > > - struct xattr new_xattrs[MAX_LSM_EVM_XATTR + 1];
> > > > - struct xattr *lsm_xattr, *evm_xattr, *xattr;
> > > > - int ret;
> > > > + struct security_hook_list *P;
> > > > + struct xattr *new_xattrs;
> > > > + struct xattr *xattr;
>...
2023 Mar 27
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
...(struct inode *inode, struct inode *dir,
> > > > > const struct qstr *qstr,
> > > > > const initxattrs initxattrs, void *fs_data)
> > > > > {
> > > > > - struct xattr new_xattrs[MAX_LSM_EVM_XATTR + 1];
> > > > > - struct xattr *lsm_xattr, *evm_xattr, *xattr;
> > > > > - int ret;
> > > > > + struct security_hook_list *P;
> > > > > + struct xattr *new_xattrs;
> > > > > +...
2023 Mar 24
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
...4,66 @@ int security_inode_init_security(struct inode *inode, struct inode *dir,
> > > const struct qstr *qstr,
> > > const initxattrs initxattrs, void *fs_data)
> > > {
> > > - struct xattr new_xattrs[MAX_LSM_EVM_XATTR + 1];
> > > - struct xattr *lsm_xattr, *evm_xattr, *xattr;
> > > - int ret;
> > > + struct security_hook_list *P;
> > > + struct xattr *new_xattrs;
> > > + struct xattr *xattr;
> > > + int r...
2022 Dec 01
8
[PATCH v7 0/6] evm: Do HMAC of multiple per LSM xattrs for new inodes
From: Roberto Sassu <roberto.sassu at huawei.com>
One of the major goals of LSM stacking is to run multiple LSMs side by side
without interfering with each other. The ultimate decision will depend on
individual LSM decision.
Several changes need to be made to the LSM infrastructure to be able to
support that. This patch set tackles one of them: gives to each LSM the
ability to specify one
2023 Mar 14
7
[PATCH v8 0/6] evm: Do HMAC of multiple per LSM xattrs for new inodes
From: Roberto Sassu <roberto.sassu at huawei.com>
One of the major goals of LSM stacking is to run multiple LSMs side by side
without interfering with each other. The ultimate decision will depend on
individual LSM decision.
Several changes need to be made to the LSM infrastructure to be able to
support that. This patch set tackles one of them: gives to each LSM the
ability to specify one
2023 Mar 28
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
...t, but
> > I'm not yet convinced that we can't make some minor changes to the
> > LSMs to avoid the compaction step.
>
> I liked more the idea that LSMs do what they are most familiar with,
> get an offset in a security blob or, in this case, a starting slot in
> the new_xattrs array, and write there.
>
> v3 had the lsm_find_xattr_slot() helper, to get the starting slot, but
> somehow I find it less intuitive.
>
> Ok, if you prefer to avoid the compaction stage, I will rewrite this
> patch.
My concern is having to look through the xattr array after eac...