| /linux-4.1.27/security/integrity/ima/ |
| D | ima_api.c | 92 int violation, struct inode *inode, in ima_store_template() argument
104 if (!violation) { in ima_store_template()
120 result = ima_add_template_entry(entry, violation, op, inode, filename); in ima_store_template()
136 int violation = 1; in ima_add_violation() local
148 result = ima_store_template(entry, violation, inode, filename); in ima_add_violation()
270 int violation = 0; in ima_store_measurement() local
283 result = ima_store_template(entry, violation, inode, filename); in ima_store_measurement()
|
| D | ima_queue.c | 108 int ima_add_template_entry(struct ima_template_entry *entry, int violation, in ima_add_template_entry() argument
119 if (!violation) { in ima_add_template_entry()
135 if (violation) /* invalidate pcr */ in ima_add_template_entry()
|
| D | ima_init.c | 59 int violation = 0; in ima_add_boot_aggregate() local
86 result = ima_store_template(entry, violation, NULL, in ima_add_boot_aggregate()
|
| D | ima.h | 97 int ima_add_template_entry(struct ima_template_entry *entry, int violation,
147 int ima_store_template(struct ima_template_entry *entry, int violation,
|
| /linux-4.1.27/Documentation/x86/ |
| D | intel_mpx.txt | 58 information about the violation in the 'struct siginfo'.
96 * bounds violation caused by MPX instructions.
166 If a #BR is generated due to a bounds violation caused by MPX.
167 We need to decode MPX instructions to get violation address and
185 The '_addr' field refers to violation address, and new '_addr_and'
189 can get violation address and bounds when bounds violations occur.
|
| /linux-4.1.27/drivers/memory/ |
| D | Kconfig | 80 represents a coherency violation.
|
| /linux-4.1.27/arch/m68k/ifpsp060/ |
| D | CHANGES | 58 ADDR should cause a "segmentation violation", the memory read
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | sysfs-bus-usb | 103 Note that some devices, in violation of the USB spec, have a
|
| /linux-4.1.27/arch/frv/kernel/ |
| D | break.S | 439 # to get a BREAK fault not an access violation should the return be to userspace
|
| /linux-4.1.27/Documentation/ |
| D | clk.txt | 249 violation.
|
| D | DMA-API.txt | 582 do not violate those constraints. In the worst case such a violation can
|
| D | DMA-API-HOWTO.txt | 508 kernel logs when the DMA controller hardware detects violation of the
|
| D | SubmittingPatches | 252 looks better with a violation then its probably best left alone.
|
| /linux-4.1.27/Documentation/usb/ |
| D | URB.txt | 174 memory-access violation. The driver is responsible for avoiding this,
|
| /linux-4.1.27/Documentation/block/ |
| D | data-integrity.txt | 98 concept of an end-to-end protection scheme is a layering violation.
|
| /linux-4.1.27/drivers/base/ |
| D | Kconfig | 136 then it may be a violation of the GPL to distribute the resulting
|
| /linux-4.1.27/Documentation/locking/ |
| D | lockdep-design.txt | 108 any rule violation between the new lock and any of the held locks.
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 1.Intro | 202 a result, their distribution is a violation of the GNU General Public
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | mmu.txt | 268 - guest page fault (or npt page fault, or ept violation)
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 442 protected by the receiving host or if acceptance may result in violation of
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic7xxx.reg | 879 mask PROTO_VIOLATION 0x20|SEQINT /* SCSI protocol violation */
|
| /linux-4.1.27/net/netfilter/ |
| D | Kconfig | 285 in PNS->PAC direction. This is a violation of RFC2637.
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 171 (helps with certain sharing violation cases when server such as
|