Searched full:lose (Results 1 – 25 of 450) sorted by relevance
12345678910>>...18
| /Linux-v6.1/Documentation/power/ |
| D | swsusp.rst | 29 they won't be accessible after resume and you may lose data, as though
403 anything, not even read-only mount, or you are going to lose your
443 I suspend to disk, I can lose data unless the filesystem has been mounted
447 That's right ... if you disconnect that device, you may lose data.
448 In fact, even with "-o sync" you can lose data if your programs have
|
| /Linux-v6.1/include/linux/ |
| D | list_bl.h | 98 /* pprev may be `first`, so be careful not to lose the lock bit */ in hlist_bl_add_before()
122 /* pprev may be `first`, so be careful not to lose the lock bit */ in __hlist_bl_del()
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | ocfs2.rst | 79 This means that if you lose your power, you will lose
|
| /Linux-v6.1/tools/testing/selftests/tc-testing/tc-tests/actions/ |
| D | xt.json | 132 "$TC action add action xt -j LOG --log-prefix LOSE index 1003"
159 "$TC action add action xt -j LOG --log-prefix LOSE index 1003"
|
| /Linux-v6.1/arch/m68k/include/asm/ |
| D | current.h | 14 * current and lose _current_task.
|
| /Linux-v6.1/include/trace/events/ |
| D | rxrpc.h | 762 rxrpc_serial_t serial, u8 flags, bool retrans, bool lose),
764 TP_ARGS(call, seq, serial, flags, retrans, lose),
774 __field(bool, lose )
785 __entry->lose = lose;
796 __entry->lose ? " *LOSE*" : "")
1023 TP_printk("%08x:%08x:%08x:%04x %08x %08x %02x %02x %s *LOSE*",
|
| /Linux-v6.1/tools/testing/selftests/bpf/progs/ |
| D | linked_vars2.c | 18 /* these two weak variables should lose */
|
| D | linked_maps2.c | 26 /* this definition will lose, but it has to exactly match the winner */
|
| D | linked_funcs2.c | 45 /* this weak instance should lose, because it will be processed second */
|
| /Linux-v6.1/arch/sparc/include/asm/ |
| D | asmmacro.h | 11 * lose. It makes sure the kernel has a proper window so that
|
| /Linux-v6.1/arch/mips/kernel/ |
| D | signal-common.h | 30 /* Make sure we will not lose FPU ownership */
|
| /Linux-v6.1/drivers/gpu/drm/i915/gt/ |
| D | intel_gt_irq.h | 60 * and not lose any. in intel_engine_set_irq_handler()
|
| /Linux-v6.1/include/asm-generic/ |
| D | mshyperv.h | 126 * to lose it. We can still lose a message of the same type but in vmbus_signal_eom()
|
| /Linux-v6.1/Documentation/userspace-api/media/dvb/ |
| D | fe-set-tone.rst | 43 setting a tone may interfere on other devices, as they may lose the
|
| D | fe-set-voltage.rst | 46 setting a voltage level may interfere on other devices, as they may lose
|
| /Linux-v6.1/arch/powerpc/lib/ |
| D | vmx-helper.c | 21 * thus make us lose the VMX context. So on page faults, we just in enter_vmx_usercopy()
|
| /Linux-v6.1/arch/x86/include/uapi/asm/ |
| D | ucontext.h | 47 * the signal was raised.. Old kernels would lose track of the
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 36 there is still a scenario when we can lose soft dirty bits -- a task
|
| /Linux-v6.1/include/uapi/linux/ |
| D | securebits.h | 27 set*uid to gain/lose privilege, transitions to/from uid 0 cause
|
| D | resource.h | 17 * structure will lose. This reduces the chances of that happening.
|
| /Linux-v6.1/include/linux/platform_data/ |
| D | pm33xx.h | 22 * needed when MPU will lose context.
|
| /Linux-v6.1/arch/x86/kernel/ |
| D | nmi.c | 131 * of them concurrently, you can lose some because only one in nmi_handle()
317 * NMI, otherwise we may lose it, because the CPU-specific in default_do_nmi()
426 * NMIs can page fault or hit breakpoints which will cause it to lose
|
| /Linux-v6.1/arch/powerpc/kernel/ |
| D | idle_64e.S | 29 * since we may otherwise lose it (doorbells etc...).
|
| /Linux-v6.1/tools/testing/selftests/powerpc/pmu/ebb/ |
| D | lost_exception_test.c | 18 * lose the exception.
|
| /Linux-v6.1/Documentation/devicetree/bindings/gpio/ |
| D | ti,omap-gpio.yaml | 54 Indicates if a GPIO bank is always powered and will never lose its logic state.
|
12345678910>>...18
