Home
last modified time | relevance | path

Searched refs:read (Results 1 – 25 of 25) sorted by relevance

/security/smack/
Dsmackfs.c674 .read = seq_read,
937 .read = seq_read,
1011 .read = seq_read,
1276 .read = seq_read,
1533 .read = seq_read,
1601 .read = smk_read_doi,
1679 .read = smk_read_direct,
1757 .read = smk_read_mapped,
1843 .read = smk_read_ambient,
2021 .read = seq_read,
[all …]
/security/loadpin/
DKconfig6 Any files read through the kernel file reading interface
11 have a root filesystem backed by a read-only device such as
/security/integrity/ima/
Dima_fs.c60 .read = ima_show_htable_violations,
73 .read = ima_show_measurements_count,
204 .read = seq_read,
270 .read = seq_read,
447 .read = seq_read,
DKconfig21 as they are read or executed. If an attacker manages
142 It is often useful to be able to read back the IMA policy. It is
/security/selinux/
Dselinuxfs.c194 .read = sel_read_enforce,
216 .read = sel_read_handle_unknown,
269 .read = sel_read_handle_status,
338 .read = sel_read_policyvers,
364 .read = sel_read_mls,
499 .read = sel_read_policy,
676 .read = sel_read_checkreqprot,
801 .read = simple_transaction_read,
1261 .read = sel_read_bool,
1511 .read = sel_read_sidtab_hash_stats,
[all …]
DKconfig78 kernel (including any implied execute for read-implies-exec) for
/security/tomoyo/
Dsecurityfs_if.c121 .read = tomoyo_read_self,
208 .read = tomoyo_read,
Dcommon.c2429 head->read = tomoyo_read_domain; in tomoyo_open_control()
2434 head->read = tomoyo_read_exception; in tomoyo_open_control()
2439 head->read = tomoyo_read_log; in tomoyo_open_control()
2444 head->read = tomoyo_read_pid; in tomoyo_open_control()
2448 head->read = tomoyo_read_version; in tomoyo_open_control()
2454 head->read = tomoyo_read_stat; in tomoyo_open_control()
2460 head->read = tomoyo_read_profile; in tomoyo_open_control()
2465 head->read = tomoyo_read_query; in tomoyo_open_control()
2470 head->read = tomoyo_read_manager; in tomoyo_open_control()
2478 head->read = NULL; in tomoyo_open_control()
[all …]
DKconfig39 You can read the log via /sys/kernel/security/tomoyo/audit.
Dcommon.h794 void (*read)(struct tomoyo_io_buffer *head); member
/security/integrity/evm/
Devm_secfs.c113 .read = evm_read_key,
263 .read = evm_read_xattrs,
/security/lockdown/
DKconfig44 code to read confidential material held inside the kernel are
Dlockdown.c170 .read = lockdown_read,
/security/keys/
Duser_defined.c32 .read = user_read,
Drequest_key_auth.c39 .read = request_key_auth_read,
Dbig_key.c77 .read = big_key_read,
Dkeyctl.c848 if (key->type->read) { in keyctl_read_key()
855 ret = key->type->read(key, buffer, buflen); in keyctl_read_key()
Drequest_key.c386 if (ctx->index_key.type->read) in construct_alloc_key()
Dkey.c915 if (index_key.type->read) in key_create_or_update()
Dtrusted.c1190 .read = trusted_read,
Dkeyring.c93 .read = keyring_read,
/security/apparmor/
Dapparmorfs.c604 .read = ns_revision_read,
981 .read = multi_transaction_read,
1019 .read = seq_read,
1038 .read = seq_read, \
1140 .read = seq_read, \
1216 .read = seq_read, \
1317 .read = rawdata_read,
2196 .read = seq_read,
/security/
Dinode.c326 .read = lsm_read,
/security/safesetid/
Dsecurityfs.c229 .read = safesetid_file_read,
/security/keys/encrypted-keys/
Dencrypted.c986 .read = encrypted_read,