Displaying 7 results from an estimated 7 matches for "evm_xattr".
2011 May 16
0
[PATCH v5 12/21] evm: add evm_inode_post_init call in btrfs
..."
#include "btrfs_inode.h"
#include "transaction.h"
@@ -367,31 +368,49 @@ int btrfs_xattr_security_init(struct btrfs_trans_handle *trans,
const struct qstr *qstr)
{
int err;
- size_t len;
- void *value;
- char *suffix;
+ struct xattr lsm_xattr;
+ struct xattr evm_xattr;
char *name;
- err = security_inode_init_security(inode, dir, qstr, &suffix, &value,
- &len);
+ err = security_inode_init_security(inode, dir, qstr, &lsm_xattr.name,
+ &lsm_xattr.value,
+ &lsm_xattr.value_len);
if (err) {
if (err == -EOPNOTSUPP)...
2011 Jun 02
0
[PATCH v6 11/20] evm: add evm_inode_post_init call in btrfs
..."
#include "btrfs_inode.h"
#include "transaction.h"
@@ -367,31 +368,49 @@ int btrfs_xattr_security_init(struct btrfs_trans_handle *trans,
const struct qstr *qstr)
{
int err;
- size_t len;
- void *value;
- char *suffix;
+ struct xattr lsm_xattr;
+ struct xattr evm_xattr;
char *name;
- err = security_inode_init_security(inode, dir, qstr, &suffix, &value,
- &len);
+ err = security_inode_init_security(inode, dir, qstr, &lsm_xattr.name,
+ &lsm_xattr.value,
+ &lsm_xattr.value_len);
if (err) {
if (err == -EOPNOTSUPP)...
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 24
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
...y(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
...e, 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 *xatt...
2023 Mar 24
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
...y_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 ret = -EOPNOTSUPP, n...