| /linux/mm/kasan/ |
| H A D | kasan_test_c.c | 733 static void kasan_atomics_helper(struct kunit *test, void *unsafe, void *safe) in kasan_atomics_helper() argument
735 int *i_unsafe = unsafe; in kasan_atomics_helper()
742 KUNIT_EXPECT_KASAN_FAIL(test, atomic_read(unsafe)); in kasan_atomics_helper()
743 KUNIT_EXPECT_KASAN_FAIL(test, atomic_set(unsafe, 42)); in kasan_atomics_helper()
744 KUNIT_EXPECT_KASAN_FAIL(test, atomic_add(42, unsafe)); in kasan_atomics_helper()
745 KUNIT_EXPECT_KASAN_FAIL(test, atomic_sub(42, unsafe)); in kasan_atomics_helper()
746 KUNIT_EXPECT_KASAN_FAIL(test, atomic_inc(unsafe)); in kasan_atomics_helper()
747 KUNIT_EXPECT_KASAN_FAIL(test, atomic_dec(unsafe)); in kasan_atomics_helper()
748 KUNIT_EXPECT_KASAN_FAIL(test, atomic_and(42, unsafe)); in kasan_atomics_helper()
749 KUNIT_EXPECT_KASAN_FAIL(test, atomic_andnot(42, unsafe)); in kasan_atomics_helper()
[all …]
|
| /linux/Documentation/translations/zh_CN/rust/ |
| H A D | coding-guidelines.rst | 80 一种特殊的注释是 ``// SAFETY:`` 注释。这些注释必须出现在每个 ``unsafe`` 块之前，它们
86 unsafe { *p = 0; }
121 /// assert_eq!(unsafe { x.unwrap_unchecked() }, "air");
123 pub unsafe fn unwrap_unchecked(self) -> T {
128 None => unsafe { hint::unreachable_unchecked() },
150 - 任何 ``unsafe`` 的代码块都必须在前面加上一个 ``// SAFETY:`` 的注释，描述里面
|
| /linux/arch/x86/boot/ |
| H A D | video-mode.c | 31 void probe_cards(int unsafe) in probe_cards() argument
36 if (probed[unsafe]) in probe_cards()
39 probed[unsafe] = 1; in probe_cards()
42 if (card->unsafe == unsafe) { in probe_cards()
|
| H A D | video.h | 76 int unsafe; /* Probing is unsafe, only do after "scan" */ member
|
| H A D | video-bios.c | 123 .unsafe = 1,
|
| /linux/kernel/printk/ |
| H A D | nbcon.c | 258 if (cur->unsafe) in nbcon_context_try_acquire_direct()
270 new.unsafe = cur->unsafe_takeover; in nbcon_context_try_acquire_direct()
361 WARN_ON_ONCE(cur->unsafe); in nbcon_context_try_acquire_requested()
366 new.unsafe = cur->unsafe_takeover; in nbcon_context_try_acquire_requested()
432 WARN_ON_ONCE(!cur->unsafe); in nbcon_context_try_acquire_handover()
543 WARN_ON_ONCE(cur->unsafe != true); in nbcon_context_try_acquire_hostile()
549 new.unsafe |= cur->unsafe_takeover; in nbcon_context_try_acquire_hostile()
550 new.unsafe_takeover |= cur->unsafe; in nbcon_context_try_acquire_hostile()
671 new.unsafe |= cur.unsafe_takeover; in nbcon_context_release()
722 if (cur->unsafe) in nbcon_context_can_proceed()
[all …]
|
| /linux/drivers/ntb/test/ |
| H A D | ntb_pingpong.c | 91 static unsigned int unsafe; variable
92 module_param(unsafe, uint, 0644);
93 MODULE_PARM_DESC(unsafe, "Run even though ntb operations may be unsafe");
248 if (!unsafe) in pp_check_ntb()
254 if (!unsafe) in pp_check_ntb()
|
| /linux/tools/testing/selftests/ |
| H A D | lib.mk | 132 …rsync -aq --copy-unsafe-links $(TEST_PROGS) $(TEST_PROGS_EXTENDED) $(TEST_FILES) $(TEST_GEN_MODS_D…
153 $(if $(INSTALL_LIST),rsync -a --copy-unsafe-links $(INSTALL_LIST) $(INSTALL_PATH)/)
158 …$(if $(INSTALL_LIST),rsync -a --copy-unsafe-links $(INSTALL_LIST)/*.ko $(INSTALL_PATH)/$(INSTALL_L…
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 118 is irq-unsafe means it was ever acquired with irq enabled.
120 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
124 <hardirq-safe> or <hardirq-unsafe>
125 <softirq-safe> or <softirq-unsafe>
128 cannot be ever acquired with irq enabled (irq-unsafe). Otherwise, a
159 <hardirq-safe> -> <hardirq-unsafe>
160 <softirq-safe> -> <softirq-unsafe>
163 taken by a hardirq context, interrupting a hardirq-unsafe lock - and
165 lock could be taken by an softirq context, interrupting a softirq-unsafe
176 took any hardirq-unsafe lock in the past.
[all …]
|
| H A D | preempt-locking.rst | 92 But keep in mind that 'irqs disabled' is a fundamentally unsafe way of
|
| /linux/Documentation/rust/ |
| H A D | general-information.rst | 110 #. Any ``unsafe`` blocks respect the safety contract necessary to call the
111 operations inside the block. Similarly, any ``unsafe impl``\ s respect the
131 are located in ``rust/kernel/`` and their role is to encapsulate the unsafe
|
| /linux/include/linux/ |
| H A D | binfmts.h | 57 int unsafe; /* how unsafe this exec is (mask of LSM_UNSAFE_*) */ member
|
| H A D | console.h | 225 unsigned int unsafe : 1; member
|
| /linux/drivers/memstick/core/ |
| H A D | Kconfig | 9 bool "Allow unsafe resume (DANGEROUS)"
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| H A D | cpufreq-st.txt | 40 Example [unsafe]
|
| /linux/lib/ |
| H A D | Kconfig.kgdb | 28 bool "KGDB: use kprobe blocklist to prohibit unsafe breakpoints"
35 identify symbols where it is unsafe to set breakpoints.
|
| H A D | Kconfig.kasan | 152 bool "Stack instrumentation (unsafe)" if CC_IS_CLANG && !COMPILE_TEST
162 with Clang, this option is deemed unsafe.
|
| /linux/tools/testing/selftests/coredump/ |
| H A D | README.rst | 20 While a thread is active, the stack pointer is unsafe to read and therefore the `kstkesp` field
|
| /linux/tools/perf/Documentation/ |
| H A D | Makefile | 48 ASCIIDOC_EXTRA += --unsafe -f asciidoc.conf
|
| /linux/Documentation/i2c/ |
| H A D | dma-considerations.rst | 28 using an unsafe DMA buffer. To improve this situation, using I2C_M_DMA_SAFE in
|
| /linux/Documentation/translations/it_IT/locking/ |
| H A D | lockdep-design.rst | 114 (*irq-unsafe*) significa che è sempre stato acquisito con le interruzioni
121 <hardirq-safe> o <hardirq-unsafe>
122 <softirq-safe> o <softirq-unsafe>
156 <hardirq-safe> -> <hardirq-unsafe>
157 <softirq-safe> -> <softirq-unsafe>
|
| /linux/Documentation/driver-api/ |
| H A D | ntb.rst | 150 * unsafe - Some hardware has known issues with scratchpad and doorbell
153 unsafe=1.
|
| /linux/security/ |
| H A D | commoncap.c | 946 ((bprm->unsafe & ~LSM_UNSAFE_PTRACE) || in cap_bprm_creds_from_file()
950 (bprm->unsafe & LSM_UNSAFE_NO_NEW_PRIVS)) { in cap_bprm_creds_from_file()
|
| /linux/Documentation/trace/ |
| H A D | debugging.rst | 48 ** unsafe for production use. **
|
| /linux/drivers/mtd/ |
| H A D | Kconfig | 54 this is very unsafe, but could be useful for file systems which are
|