Home
last modified time | relevance | path

Searched refs:dangerous (Results 1 – 29 of 29) sorted by relevance

/linux-4.1.27/tools/testing/selftests/timers/
Dset-2038.c88 int opt, dangerous = 0; in main() local
95 dangerous = 1; in main()
127 if (is32bits() && !dangerous) in main()
/linux-4.1.27/Documentation/prctl/
Dno_new_privs.txt53 In the future, other potentially dangerous kernel features could become
57 dangerous than chroot by itself.
/linux-4.1.27/arch/x86/platform/olpc/
Dxo1-wakeup.S18 # Clear any dangerous flags
/linux-4.1.27/drivers/pnp/pnpbios/
DKconfig32 interface is potentially dangerous because the PNPBIOS driver will
/linux-4.1.27/arch/x86/kernel/
Dverify_cpu.S38 push $0 # Kill any dangerous flags
/linux-4.1.27/Documentation/i2c/busses/
Di2c-piix461 updates first, for example), and backup first! An even more dangerous
/linux-4.1.27/Documentation/scheduler/
Dsched-nice-design.txt105 and forcing audio apps to run under the more dangerous SCHED_FIFO
/linux-4.1.27/drivers/cpufreq/
DKconfig.x86277 and is thus considered dangerous. Please use the regular ACPI cpufreq
/linux-4.1.27/Documentation/ia64/
Daliasing.txt139 any control over the access size, so this would be dangerous.
/linux-4.1.27/Documentation/usb/
Dpersist.txt133 WARNING: USB-persist can be dangerous!!
/linux-4.1.27/arch/powerpc/
DKconfig.debug126 bool "Early debugging (dangerous)"
/linux-4.1.27/drivers/mtd/
DKconfig319 data listed in multiple partitions was dangerous; however, SCSI does
/linux-4.1.27/Documentation/RCU/
Drcu_dereference.txt62 be dangerous. At this point, the compiler knows that the
/linux-4.1.27/Documentation/security/
DSmack.txt232 is dangerous and can ruin the proper labeling of your system.
716 is logged. This feature is dangerous, as files and directories may
/linux-4.1.27/Documentation/
DManagementStyle67 you cannot escape. A cornered rat may be dangerous - a cornered manager
DCodingStyle571 Seriously dangerous features (such as write support for certain
/linux-4.1.27/Documentation/input/
Djoystick.txt208 dangerous, but not simple either.
/linux-4.1.27/kernel/trace/
DKconfig535 This is a dumb module for testing mmiotrace. It is very dangerous
/linux-4.1.27/Documentation/s390/
Ds390dbf.txt509 IMPORTANT: Using "%s" in sprintf event functions is dangerous. You can only
/linux-4.1.27/drivers/block/
DKconfig454 this option is dangerous unless the CD-RW media is known good, as we
/linux-4.1.27/Documentation/networking/
Dcs89x0.txt251 identify the card. This could be dangerous if you are
/linux-4.1.27/Documentation/cgroups/
Dunified-hierarchy.txt449 details, broken and dangerous implementations of various features.
/linux-4.1.27/drivers/char/
DKconfig88 OTP pages. This is dangerous by nature as you can only program
/linux-4.1.27/Documentation/sysctl/
Dvm.txt286 For some specialised workloads on highmem machines it is dangerous for
/linux-4.1.27/Documentation/virtual/kvm/
Dtimekeeping.txt189 dangerous to allow userspace utilities such as hwclock to have direct RTC
/linux-4.1.27/Documentation/sound/oss/
DREADME.OSS545 of RAM since this is potentially dangerous (you may accidentally run out
1168 dangerous as long as you don't try to use a file called sndscape.cod.
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt734 dangerous actions (like undocking or ejecting a bay device while the
/linux-4.1.27/drivers/video/fbdev/
DKconfig1556 This is dangerous but may provide the only chance to get the
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt484 on the system. However, there are a few parameters that are dangerous