Searched full:harmful (Results 1 – 25 of 75) sorted by relevance
123
| /freebsd/contrib/netbsd-tests/lib/libc/sys/ |
| H A D | t_socketpair.c | 67 /* This check is harmful since it closes atf's output file */ in run()
74 /* This check is harmful since it requires closing atf's output file */ in run()
131 /* This check is harmful since it closes atf's output file */ in ATF_TC_BODY()
|
| H A D | t_pipe2.c | 57 /* This check is harmful since it closes atf's output file */ in run()
65 /* This check is harmful since it requires closing atf's output file */ in run()
|
| /freebsd/contrib/byacc/ |
| H A D | NOTES | 6 compilers make that effort worthless, perhaps even harmful.
|
| /freebsd/lib/libssp/ |
| H A D | Makefile | 32 # Stack protection on libssp symbols should be considered harmful, as we may
|
| /freebsd/share/man/man4/ |
| H A D | rccgpio.4 | 45 All the GPIO pins are locked in their intended setup to disallow any harmful
|
| H A D | gif.4 | 157 This fragmentation is not harmful though it can degrade the
|
| /freebsd/bin/cat/ |
| H A D | cat.1 | 174 .%T "UNIX Style, or cat -v Considered Harmful"
|
| /freebsd/share/doc/smm/06.nfs/ |
| H A D | ref.t | 64 \fIFragmentation Considered Harmful\fR, Research Report 87/3,
|
| /freebsd/contrib/nvi/regex/ |
| H A D | WHATSNEW | 79 harmful, but technically errors) and some other areas. Debugging
|
| /freebsd/lib/libc/regex/ |
| H A D | WHATSNEW | 78 harmful, but technically errors) and some other areas. Debugging
|
| /freebsd/tools/tools/git/ |
| H A D | HOWTO | 19 was actually written and can actually be harmful. For example, if you
|
| /freebsd/tests/sys/cddl/zfs/bin/ |
| H A D | mkfile.c | 138 * This is fd-leak, but is not harmful in create_file()
|
| /freebsd/sys/sys/ |
| H A D | refcount.h | 45 * destruction of the containing object and instead leads to a less harmful
|
| /freebsd/sys/contrib/device-tree/Bindings/power/supply/ |
| H A D | battery.yaml | 20 different type. This prevents unpredictable, potentially harmful,
|
| /freebsd/share/man/man9/ |
| H A D | fail.9 | 268 to fail consistently is potentially harmful to uptime.
|
| /freebsd/sys/kern/ |
| H A D | kern_mtxpool.c | 178 * harmful. in mtx_pool_alloc()
|
| /freebsd/usr.sbin/arp/ |
| H A D | arp.4 | 128 This is particularly harmful when a shared address is passed between cluster
|
| /freebsd/usr.bin/m4/TEST/ |
| H A D | test.m4 | 161 Other hazards also exist which are potentially harmful. As the roads
|
| /freebsd/contrib/tcsh/ |
| H A D | FAQ | 220 You can read Tom Christiansen's Csh Programming Considered Harmful, a
|
| /freebsd/usr.bin/clang/llvm-profdata/ |
| H A D | llvm-profdata.1 | 211 as being harmful for performance and will be dropped.
|
| /freebsd/stand/common/ |
| H A D | install.c | 309 * loaded and prune the environment from harmful variables. in install()
|
| /freebsd/lib/libutil/ |
| H A D | login_cap.3 | 351 pointer with no harmful side-effects.
|
| /freebsd/sys/powerpc/powermac/ |
| H A D | platform_powermac.c | 206 * management, and is harmful on other machines (it will make OF in powermac_attach()
|
| /freebsd/sys/x86/iommu/ |
| H A D | intel_qi.c | 283 * read. It is more harmful for the parallel DMA operations, in dmar_qi_invalidate_iec()
|
| /freebsd/sys/contrib/openzfs/cmd/zed/agents/ |
| H A D | zfs_agents.c | 211 * layer. Processing multiple FM_RESOURCE_REMOVED events is not harmful. in zfs_agent_post_event()
|
123