| /linux/Documentation/crypto/ |
| H A D | devel-algos.rst | 72 other part of the kernel. Note that the .cia_setkey() call might happen
73 before or after any of these schematics happen, but must not happen
172 other part of the kernel. Note that the .setkey() call might happen
173 before or after any of these schematics happen, but must not happen
210 ----------- other transformations happen here -----------
|
| /linux/arch/arm/mach-omap2/ |
| H A D | powerdomain-common.c | 61 WARN_ON(1); /* should never happen */ in omap2_pwrdm_get_mem_bank_onstate_mask()
81 WARN_ON(1); /* should never happen */ in omap2_pwrdm_get_mem_bank_retst_mask()
101 WARN_ON(1); /* should never happen */ in omap2_pwrdm_get_mem_bank_stst_mask()
|
| /linux/arch/riscv/include/asm/ |
| H A D | kvm_vmid.h | 13 * Writes to vmid_version and vmid happen with vmid_lock held
14 * whereas reads happen without any lock held.
|
| /linux/Documentation/bpf/ |
| H A D | cpumasks.rst | 235 /* Should never happen. */
240 /* Should never happen. */
309 /* Should never happen. */
314 /* Should never happen. */
318 /* Should never happen. */
324 /* Should never happen. */
|
| /linux/tools/testing/selftests/kvm/x86/ |
| H A D | xen_shinfo_test.c | 716 "Expected event channel IRQ but it didn't happen"); in main()
729 "Expected event channel IRQ but it didn't happen"); in main()
749 "Expected event channel IRQ but it didn't happen"); in main()
760 "Expected event channel IRQ but it didn't happen"); in main()
773 "Expected event channel IRQ but it didn't happen"); in main()
784 "Expected event channel IRQ but it didn't happen"); in main()
807 "Expected event channel IRQ but it didn't happen"); in main()
821 "Expected event channel IRQ but it didn't happen"); in main()
874 "Expected event channel IRQ but it didn't happen"); in main()
891 "Expected event channel IRQ but it didn't happen"); in main()
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | unaligned-memory-access.rst | 28 The above may seem a little vague, as memory access can happen in different
62 happen. The exception handler is able to correct the unaligned access,
65 happen, but the exceptions do not contain enough information for the
72 memory accesses to happen, your code will not work correctly on certain
172 Think about what would happen if addr1 was an odd address such as 0x10003.
|
| /linux/drivers/md/ |
| H A D | dm-builtin.c | 19 * happen:
38 * being scheduled long enough, this bug may really happen.
|
| /linux/include/linux/sched/ |
| H A D | wake_q.h | 19 * already in a wake queue, the wakeup will happen soon and the second
31 * NOTE that there is no guarantee the wakeup will happen any later than the
|
| /linux/kernel/locking/ |
| H A D | spinlock_debug.c | 131 * Must not happen on UP: in do_raw_spin_trylock()
171 * Must not happen on UP: in do_raw_read_trylock()
223 * Must not happen on UP: in do_raw_write_trylock()
|
| /linux/drivers/mtd/parsers/ |
| H A D | Kconfig | 37 for your particular device. It won't happen automatically. The
118 for your particular device. It won't happen automatically. The
167 for your particular device. It won't happen automatically. The
|
| /linux/include/uapi/linux/ |
| H A D | virtio_mem.h | 70 * There are no guarantees what will happen if unplugged memory is
76 * It can happen that the device cannot process a request, because it is
81 * scenarios (if the device is busy) it can happen that the device still
|
| /linux/Documentation/networking/devlink/ |
| H A D | mlxsw.rst | 97 routed from a disabled router interface (RIF). This can happen during
103 routed through a disabled router interface (RIF). This can happen during
|
| /linux/arch/sh/drivers/pci/ |
| H A D | ops-dreamcast.c | 21 * The !gapspci_config_access case really shouldn't happen, ever, unless
34 * likely to happen anytime soon.
|
| /linux/tools/testing/selftests/ptrace/ |
| H A D | get_syscall_info.c | 90 /* cannot happen */ in TEST()
128 /* cannot happen */ in TEST()
142 /* cannot happen */ in TEST()
|
| /linux/drivers/scsi/elx/libefc/ |
| H A D | efc_domain.c | 443 /* Should not happen */ in __efc_domain_wait_alloc()
502 /* Should not happen */ in __efc_domain_allocated()
503 efc_log_err(efc, "%s: evt: %d should not happen\n", in __efc_domain_allocated()
598 /* Should not happen */ in __efc_domain_wait_attach()
599 efc_log_err(efc, "%s: evt: %d should not happen\n", in __efc_domain_wait_attach()
667 /* Should not happen */ in __efc_domain_ready()
668 efc_log_err(efc, "%s: evt: %d should not happen\n", in __efc_domain_ready()
673 /* can happen during p2p */ in __efc_domain_ready()
|
| /linux/arch/um/os-Linux/ |
| H A D | signal.c | 291 * happen in this order, so have the barrier here. in unblock_signals()
380 * that could happen in the middle, losing the in mark_sigio_pending()
387 * timer signal (SIGALRM) cannot happen. in mark_sigio_pending()
450 * that the signal handler will either happen before or after in unblock_signals_hard()
|
| /linux/arch/riscv/lib/ |
| H A D | delay.c | 65 * won't happen.
105 * This doesn't bother checking for overflow, as it won't happen (it's in ndelay()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-rpmsg | 28 wasn't assigned (can happen if no driver exists for this
46 wasn't assigned (can happen if the kernel driver that
|
| /linux/Documentation/arch/x86/ |
| H A D | sgx.rst | 81 handle an EPCM fault at any time. In practice, this can happen on events like
234 When EPC page leaks happen, a WARNING like this is shown in dmesg:
285 ``EREMOVE`` happen concurrently for pages that refer to the same
286 "SECS" metadata pages. This can happen if there are concurrent
|
| /linux/kernel/trace/ |
| H A D | pid_list.c | 27 * If a refill needs to happen, it can not happen here in get_lower_chunk()
51 * If a refill needs to happen, it can not happen here in get_upper_chunk()
|
| /linux/net/x25/ |
| H A D | x25_forward.c | 31 /* This shouldn't happen, if it occurs somehow in x25_forward_call()
45 * established LCI? It shouldn't happen, just in case.. in x25_forward_call()
|
| /linux/kernel/module/ |
| H A D | stats.c | 121 * happen due to the initial kernel_read_file_from_fd(). kernel_read_file_from_fd()
122 * uses vmalloc(). These should typically not happen unless your system is
126 * These typically should not happen unless your system is under memory
131 * failures can happen if we had a check in between a successful kernel_read_file_from_fd()
178 * These really should not happen unless your compression / decompression
|
| /linux/arch/um/kernel/skas/ |
| H A D | mmu.c | 66 * 1 cases, since they shouldn't happen either. in destroy_context()
68 * Negative cases happen if the child died unexpectedly. in destroy_context()
|
| /linux/Documentation/userspace-api/ |
| H A D | mseal.rst | 12 the memory has to be marked with X bit, or else an exception will happen.
62 memory range could happen. However, those cases should be rare.
120 - mprotect, pkey_mprotect, madvise: partial update might happen, e.g.
|
| /linux/drivers/net/ethernet/chelsio/cxgb3/ |
| H A D | l2t.c | 51 * whole plus a spinlock per L2T entry. Entry lookups and allocations happen
52 * under the protection of the table lock, individual entry changes happen
55 * no other lookups can happen while allocating new entries. Entry updates
58 * and therefore can happen in parallel with entry allocation but no entry
|