Searched refs:dangerous (Results 1 – 25 of 33) sorted by relevance
12
| /Linux-v5.4/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-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 5 Since the force_remove is inherently broken and dangerous to
|
| /Linux-v5.4/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-v5.4/arch/x86/platform/olpc/ |
| D | xo1-wakeup.S | 19 # Clear any dangerous flags
|
| /Linux-v5.4/arch/x86/kernel/ |
| D | verify_cpu.S | 36 push $0 # Kill any dangerous flags
|
| /Linux-v5.4/drivers/pnp/pnpbios/ |
| D | Kconfig | 33 interface is potentially dangerous because the PNPBIOS driver will
|
| /Linux-v5.4/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 167 bool "Enable broken and dangerous selftests"
172 This option enables the execution of selftests that are "dangerous"
|
| /Linux-v5.4/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 64 In the ideal world, upper layers should already mark dangerous contexts
|
| /Linux-v5.4/Documentation/livepatch/ |
| D | cumulative-patches.rst | 83 As a result, it might be dangerous to replace newer cumulative patches by
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | dawr-power9.rst | 68 This is a dangerous setting, USE AT YOUR OWN RISK.
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-piix4.rst | 65 updates first, for example), and backup first! An even more dangerous
|
| /Linux-v5.4/Documentation/gpu/ |
| D | introduction.rst | 49 names are "Notes" with information for dangerous or tricky corner cases,
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-nice-design.rst | 109 and forcing audio apps to run under the more dangerous SCHED_FIFO
|
| /Linux-v5.4/drivers/mtd/ |
| D | Kconfig | 190 data listed in multiple partitions was dangerous; however, SCSI does
|
| /Linux-v5.4/Documentation/ia64/ |
| D | aliasing.rst | 152 any control over the access size, so this would be dangerous.
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | persist.rst | 138 WARNING: USB-persist can be dangerous!!
|
| /Linux-v5.4/drivers/cpufreq/ |
| D | Kconfig.x86 | 280 and is thus considered dangerous. Please use the regular ACPI cpufreq
|
| /Linux-v5.4/arch/powerpc/ |
| D | Kconfig.debug | 149 bool "Early debugging (dangerous)"
|
| /Linux-v5.4/drivers/gpu/drm/ |
| D | Kconfig | 369 Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
|
| /Linux-v5.4/Documentation/s390/ |
| D | s390dbf.rst | 314 Using "%s" in sprintf event functions is dangerous. You can only
|
| /Linux-v5.4/Documentation/process/ |
| D | management-style.rst | 72 you cannot escape. A cornered rat may be dangerous - a cornered manager
|
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 314 is dangerous and can ruin the proper labeling of your system.
860 is logged. This feature is dangerous, as files and directories may
|
| /Linux-v5.4/drivers/block/ |
| D | Kconfig | 372 this option is dangerous unless the CD-RW media is known good, as we
|
| /Linux-v5.4/Documentation/input/joydev/ |
| D | joystick.rst | 190 dangerous, but not simple either.
|
| /Linux-v5.4/Documentation/networking/device_drivers/cirrus/ |
| D | cs89x0.txt | 251 identify the card. This could be dangerous if you are
|
12
