Searched refs:dangerous (Results 1 – 25 of 45) sorted by relevance
12
77 int opt, dangerous = 0; in main() local84 dangerous = 1; in main()116 if (is32bits() && !dangerous) in main()
12 Note: This driver is doing some dangerous hack. Please only enable
5 Since the force_remove is inherently broken and dangerous to
2 may be dangerous. These will be removed eventually and should not be
59 In the future, other potentially dangerous kernel features could become63 dangerous than chroot by itself.
19 # Clear any dangerous flags
8 /// an initializer. Using warning-silencing tricks is dangerous as it
43 This is dangerous, do not enable unless running
36 push $0 # Kill any dangerous flags
33 interface is potentially dangerous because the PNPBIOS driver will
150 * potentially dangerous if used on baseboard
210 bool "Enable broken and dangerous selftests"215 This option enables the execution of selftests that are "dangerous"
64 In the ideal world, upper layers should already mark dangerous contexts
130 This might be really dangerous especially for larger orders.
83 As a result, it might be dangerous to replace newer cumulative patches by
76 This is a dangerous setting, USE AT YOUR OWN RISK.
65 updates first, for example), and backup first! An even more dangerous
109 and forcing audio apps to run under the more dangerous SCHED_FIFO
185 dangerous output signals to be set.
16 into a number of buffer overflow issues and dangerous security bugs and user
203 data listed in multiple partitions was dangerous; however, SCSI does
111 Why is late loading dangerous?
138 WARNING: USB-persist can be dangerous!!
137 - x86/x86_64: Microcode late loading is dangerous and will result in
322 and is thus considered dangerous. Please use the regular ACPI cpufreq