Searched refs:dangerous (Results 1 – 25 of 40) sorted by relevance
12
| /linux-5.19.10/tools/testing/selftests/timers/ |
| D | set-2038.c | 77 int opt, dangerous = 0; in main() local
84 dangerous = 1; in main()
116 if (is32bits() && !dangerous) in main()
|
| /linux-5.19.10/arch/mips/loongson64/ |
| D | Kconfig | 12 Note: This driver is doing some dangerous hack. Please only enable
|
| /linux-5.19.10/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 5 Since the force_remove is inherently broken and dangerous to
|
| D | sysfs-driver-intel_pmc_bxt | 2 may be dangerous. These will be removed eventually and should not be
|
| /linux-5.19.10/Documentation/userspace-api/ |
| D | no_new_privs.rst | 59 In the future, other potentially dangerous kernel features could become
63 dangerous than chroot by itself.
|
| /linux-5.19.10/arch/x86/platform/olpc/ |
| D | xo1-wakeup.S | 19 # Clear any dangerous flags
|
| /linux-5.19.10/scripts/coccinelle/misc/ |
| D | uninitialized_var.cocci | 8 /// an initializer. Using warning-silencing tricks is dangerous as it
|
| /linux-5.19.10/drivers/pnp/pnpbios/ |
| D | Kconfig | 33 interface is potentially dangerous because the PNPBIOS driver will
|
| /linux-5.19.10/arch/x86/kernel/ |
| D | verify_cpu.S | 36 push $0 # Kill any dangerous flags
|
| /linux-5.19.10/arch/arm/boot/dts/ |
| D | imx6ul-tqma6ul-common.dtsi | 150 * potentially dangerous if used on baseboard
|
| /linux-5.19.10/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 188 bool "Enable broken and dangerous selftests"
193 This option enables the execution of selftests that are "dangerous"
|
| /linux-5.19.10/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 64 In the ideal world, upper layers should already mark dangerous contexts
|
| D | memory-allocation.rst | 129 This might be really dangerous especially for larger orders.
|
| /linux-5.19.10/Documentation/powerpc/ |
| D | dawr-power9.rst | 76 This is a dangerous setting, USE AT YOUR OWN RISK.
|
| /linux-5.19.10/Documentation/livepatch/ |
| D | cumulative-patches.rst | 83 As a result, it might be dangerous to replace newer cumulative patches by
|
| /linux-5.19.10/Documentation/i2c/busses/ |
| D | i2c-piix4.rst | 65 updates first, for example), and backup first! An even more dangerous
|
| /linux-5.19.10/Documentation/scheduler/ |
| D | sched-nice-design.rst | 109 and forcing audio apps to run under the more dangerous SCHED_FIFO
|
| /linux-5.19.10/Documentation/filesystems/cifs/ |
| D | ksmbd.rst | 16 into number of buffer overflow issues and dangerous security bugs and user
|
| /linux-5.19.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 185 dangerous output signals to be set.
|
| /linux-5.19.10/drivers/mtd/ |
| D | Kconfig | 203 data listed in multiple partitions was dangerous; however, SCSI does
|
| /linux-5.19.10/drivers/cpufreq/ |
| D | Kconfig.x86 | 289 and is thus considered dangerous. Please use the regular ACPI cpufreq
|
| /linux-5.19.10/Documentation/gpu/ |
| D | introduction.rst | 49 names are "Notes" with information for dangerous or tricky corner cases,
|
| /linux-5.19.10/Documentation/ia64/ |
| D | aliasing.rst | 152 any control over the access size, so this would be dangerous.
|
| /linux-5.19.10/Documentation/driver-api/usb/ |
| D | persist.rst | 138 WARNING: USB-persist can be dangerous!!
|
| /linux-5.19.10/arch/powerpc/ |
| D | Kconfig.debug | 155 bool "Early debugging (dangerous)"
|
12