| /kernel/linux/linux-5.10/security/smack/ |
| D | smack_access.c | 56 * @subject_label: a pointer to the subject's Smack label
60 * This function looks up the subject/object pair in the
103 * smk_access - determine if a subject has a specific access to an object
104 * @subject: a pointer to the subject's Smack label entry
109 * This function looks up the subject/object pair in the
115 int smk_access(struct smack_known *subject, struct smack_known *object, in smk_access() argument
125 * A star subject can't access any object. in smk_access()
127 if (subject == &smack_known_star) { in smk_access()
132 * An internet object can be accessed by any subject. in smk_access()
134 * An internet subject can access any object. in smk_access()
[all …]
|
| /kernel/linux/linux-4.19/security/smack/ |
| D | smack_access.c | 60 * @subject_label: a pointer to the subject's Smack label
64 * This function looks up the subject/object pair in the
108 * smk_access - determine if a subject has a specific access to an object
109 * @subject: a pointer to the subject's Smack label entry
114 * This function looks up the subject/object pair in the
120 int smk_access(struct smack_known *subject, struct smack_known *object, in smk_access() argument
130 * A star subject can't access any object. in smk_access()
132 if (subject == &smack_known_star) { in smk_access()
137 * An internet object can be accessed by any subject. in smk_access()
139 * An internet subject can access any object. in smk_access()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 134 This interface reports whether a subject with the specified
142 This interface reports whether a subject with the specified
159 where the first string is the subject label, the second the
162 "rwxat-". If a rule for a given subject and object exists it will be
223 where the first string is the subject label, the second the
238 where the first string is the subject label, the second the
293 For the ``PTRACE_READ`` a subject needs to have a read access on
298 only allowed when subject's and object's labels are equal.
305 revoke-subject
307 rules with that subject label.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 134 This interface reports whether a subject with the specified
142 This interface reports whether a subject with the specified
159 where the first string is the subject label, the second the
162 "rwxat-". If a rule for a given subject and object exists it will be
223 where the first string is the subject label, the second the
238 where the first string is the subject label, the second the
293 For the ``PTRACE_READ`` a subject needs to have a read access on
298 only allowed when subject's and object's labels are equal.
305 revoke-subject
307 rules with that subject label.
[all …]
|
| /kernel/linux/linux-5.10/crypto/asymmetric_keys/ |
| D | x509_parser.h | 18 char *subject; /* Name of certificate subject */ member
20 struct asymmetric_key_id *skid; /* Subject + subjectKeyId (optional) */
31 const void *raw_subject; /* Raw subject name in ASN.1 */
|
| D | x509_public_key.c | 173 pr_devel("Cert Subject: %s\n", cert->subject); in x509_key_preparse()
199 sulen = strlen(cert->subject); in x509_key_preparse()
212 p = memcpy(desc, cert->subject, sulen); in x509_key_preparse()
|
| /kernel/linux/linux-4.19/crypto/asymmetric_keys/ |
| D | x509_parser.h | 22 char *subject; /* Name of certificate subject */ member
24 struct asymmetric_key_id *skid; /* Subject + subjectKeyId (optional) */
35 const void *raw_subject; /* Raw subject name in ASN.1 */
|
| D | x509_public_key.c | 175 pr_devel("Cert Subject: %s\n", cert->subject); in x509_key_preparse()
201 sulen = strlen(cert->subject); in x509_key_preparse()
214 p = memcpy(desc, cert->subject, sulen); in x509_key_preparse()
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/mscc/ |
| D | ocelot.h | 78 * ENTRYTYPE_NORMAL is subject to aging.
79 * ENTRYTYPE_LOCKED is not subject to aging.
80 * ENTRYTYPE_MACv4 is not subject to aging. For IPv4 multicast.
81 * ENTRYTYPE_MACv6 is not subject to aging. For IPv6 multicast.
|
| /kernel/linux/linux-5.10/ |
| D | README | 52 4. Mark "v1, v2, v3 ..." in your patch subject if you have multiple versions
55 Use --subject-prefix="PATCH v2" option to add v2 tag for patchset.
56 git format-patch --subject-prefix="PATCH v2" -1
58 Subject examples:
59 Subject: [PATCH v2 01/27] fork: fix some -Wmissing-prototypes warnings
60 Subject: [PATCH v3] ext2: improve scalability of bitmap searching
|
| /kernel/linux/linux-4.19/ |
| D | README | 52 4. Mark "v1, v2, v3 ..." in your patch subject if you have multiple versions
55 Use --subject-prefix="PATCH v2" option to add v2 tag for patchset.
56 git format-patch --subject-prefix="PATCH v2" -1
58 Subject examples:
59 Subject: [PATCH v2 01/27] fork: fix some -Wmissing-prototypes warnings
60 Subject: [PATCH v3] ext2: improve scalability of bitmap searching
|
| /kernel/linux/linux-4.19/Documentation/security/ |
| D | credentials.rst | 52 A subject is an object that is acting upon another object.
65 A subject has an additional interpretation of its credentials. A subset
68 subject acts.
77 Linux has a number of actions available that a subject may perform upon an
78 object. The set of actions available depends on the nature of the subject
86 When a subject acts upon an object, a security calculation is made. This
88 action, and searching one or more sets of rules to see whether the subject
101 is an abbreviated ACL with three fixed classes of subject ('user',
118 subject label, the object label and the action and look for a rule
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | credentials.rst | 52 A subject is an object that is acting upon another object.
65 A subject has an additional interpretation of its credentials. A subset
68 subject acts.
77 Linux has a number of actions available that a subject may perform upon an
78 object. The set of actions available depends on the nature of the subject
86 When a subject acts upon an object, a security calculation is made. This
88 action, and searching one or more sets of rules to see whether the subject
101 is an abbreviated ACL with three fixed classes of subject ('user',
118 subject label, the object label and the action and look for a rule
|
| /kernel/linux/linux-4.19/include/uapi/drm/ |
| D | vgem_drm.h | 10 * permit persons to whom the Software is furnished to do so, subject to
37 * subject to backwards-compatibility constraints.
|
| /kernel/linux/linux-5.10/include/uapi/drm/ |
| D | vgem_drm.h | 10 * permit persons to whom the Software is furnished to do so, subject to
37 * subject to backwards-compatibility constraints.
|
| /kernel/linux/linux-4.19/include/xen/ |
| D | xenbus_dev.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /kernel/linux/linux-5.10/include/xen/ |
| D | xenbus_dev.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | submitting-patches.rst | 406 10) Include PATCH in the subject
410 convention to prefix your subject line with [PATCH]. This lets Linus
491 message (just after the subject line) to facilitate tracking. For instance,
597 understand the subject area and to perform thorough reviews, will normally
624 The canonical patch subject line is::
626 Subject: [PATCH 001/123] subsystem: summary phrase
647 The Subject line format makes it very easy to sort the emails
648 alphabetically by subject line - pretty much any email reader will
652 The ``subsystem`` in the email's Subject should identify which
655 The ``summary phrase`` in the email's Subject should concisely
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/xen/ |
| D | grant-table.c | 11 * software packages, subject to the following license:
17 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/xen/ |
| D | hypervisor.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /kernel/linux/linux-4.19/arch/x86/include/asm/xen/ |
| D | hypervisor.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /kernel/linux/linux-4.19/arch/arm/xen/ |
| D | grant-table.c | 11 * software packages, subject to the following license:
17 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | submitting-patches.rst | 345 Include PATCH in the subject
349 convention to prefix your subject line with [PATCH]. This lets Linus
522 understand the subject area and to perform thorough reviews, will normally
556 The canonical patch subject line is::
558 Subject: [PATCH 001/123] subsystem: summary phrase
579 The Subject line format makes it very easy to sort the emails
580 alphabetically by subject line - pretty much any email reader will
584 The ``subsystem`` in the email's Subject should identify which
587 The ``summary phrase`` in the email's Subject should concisely
610 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
[all …]
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 114 following subject lines (``yyyy-mm-dd`` is the date of the pull
124 so please read up on it. The subject line must indicate whether the
128 For fixes eventually landing in bpf -> net tree, the subject must
131 git format-patch --subject-prefix='PATCH bpf' start..finish
134 bpf-next -> net-next, the subject must look like::
136 git format-patch --subject-prefix='PATCH bpf-next' start..finish
140 problem either if the subject line says net or net-next as target.
150 version number (``v2``, ``v3``, ...) into the subject prefix::
152 git format-patch --subject-prefix='PATCH bpf-next v2' start..finish
233 be subject to change.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 119 following subject lines (``yyyy-mm-dd`` is the date of the pull
129 so please read up on it. The subject line must indicate whether the
133 For fixes eventually landing in bpf -> net tree, the subject must
136 git format-patch --subject-prefix='PATCH bpf' start..finish
139 bpf-next -> net-next, the subject must look like::
141 git format-patch --subject-prefix='PATCH bpf-next' start..finish
145 problem either if the subject line says net or net-next as target.
155 version number (``v2``, ``v3``, ...) into the subject prefix::
157 git format-patch --subject-prefix='PATCH net-next v2' start..finish
238 be subject to change.
[all …]
|