Home
last modified time | relevance | path

Searched refs:failure (Results 1 – 200 of 212) sorted by relevance

12

/linux-4.4.14/Documentation/mic/mpssd/
Dmpss57 failure
67 failure
98 [ $RETVAL -ne 0 ] && failure || success
136 [ $RETVAL -ne 0 ] && failure || success
174 [ $RETVAL -ne 0 ] && failure || success
/linux-4.4.14/arch/m68k/ifpsp060/
Dos.S84 | d1 - 0 = success, !0 = failure
115 | d1 - 0 = success, !0 = failure
147 | d1 - 0 = success, !0 = failure
170 | d1 - 0 = success, !0 = failure
181 | d1 - 0 = success, !0 = failure
206 | d1 - 0 = success, !0 = failure
217 | d1 - 0 = success, !0 = failure
241 | d1 - 0 = success, !0 = failure
263 | d1 - 0 = success, !0 = failure
287 | d1 - 0 = success, !0 = failure
Diskeleton.S195 | d0 = 0 -> success; non-zero -> failure
/linux-4.4.14/Documentation/driver-model/
Ddevres.txt27 sufficient bugs in ->remove and ->probe failure path. Well, yes,
35 initialization failure don't happen often enough to be noticeable.
36 Init failure path is worse because it's much less travelled while
40 and having half broken failure path implementation in ->probe() which
41 would leak resources or even cause oops when failure occurs. iomap
132 to better maintained higher layer. Also, as init failure path is
142 resources on failure. For example,
163 As resource acquisition failure usually means probe failure, constructs
165 layer) where interface function shouldn't have side effect on failure.
/linux-4.4.14/drivers/gpu/drm/amd/amdkfd/
Dkfd_events.c917 memory_exception_data.failure.NotPresent = 1; in kfd_signal_iommu_event()
918 memory_exception_data.failure.NoExecute = 0; in kfd_signal_iommu_event()
919 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event()
922 memory_exception_data.failure.NotPresent = 1; in kfd_signal_iommu_event()
923 memory_exception_data.failure.NoExecute = 0; in kfd_signal_iommu_event()
924 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event()
926 memory_exception_data.failure.NotPresent = 0; in kfd_signal_iommu_event()
928 memory_exception_data.failure.ReadOnly = 1; in kfd_signal_iommu_event()
930 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event()
932 memory_exception_data.failure.NoExecute = 1; in kfd_signal_iommu_event()
[all …]
/linux-4.4.14/Documentation/fault-injection/
Dfault-injection.txt43 likelihood of failure injection, in percent.
46 Note that one-failure-per-hundred is a very high error rate
72 specifies the verbosity of the messages when failure is
74 log line per failure; '2' will print a call trace too -- useful
123 default is 'N', setting it to 'Y' will disable failure injections
173 Upon should_fail() returning true, client code should inject a failure.
264 allocation failure.
275 Same as above except to inject page allocation failure instead of slab
276 allocation failure.
/linux-4.4.14/drivers/dma/
Dste_dma40.c3163 goto failure; in d40_hw_detect_init()
3169 goto failure; in d40_hw_detect_init()
3175 goto failure; in d40_hw_detect_init()
3179 goto failure; in d40_hw_detect_init()
3183 goto failure; in d40_hw_detect_init()
3195 goto failure; in d40_hw_detect_init()
3201 goto failure; in d40_hw_detect_init()
3215 goto failure; in d40_hw_detect_init()
3242 goto failure; in d40_hw_detect_init()
3291 goto failure; in d40_hw_detect_init()
[all …]
/linux-4.4.14/drivers/net/can/sja1000/
Dkvaser_pci.c277 goto failure; in kvaser_pci_add_chan()
285 failure: in kvaser_pci_add_chan()
308 goto failure; in kvaser_pci_init_one()
374 failure: in kvaser_pci_init_one()
/linux-4.4.14/drivers/macintosh/
Dwindfarm_fcu_controls.c172 unsigned char failure; in wf_fcu_fan_get_rpm() local
176 rc = wf_fcu_read_reg(pv, 0xb, &failure, 1); in wf_fcu_fan_get_rpm()
179 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_rpm()
228 unsigned char failure; in wf_fcu_fan_get_pwm() local
233 rc = wf_fcu_read_reg(pv, 0x2b, &failure, 1); in wf_fcu_fan_get_pwm()
236 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_pwm()
Dsmu.c986 goto failure; in smu_create_sdb_partition()
993 goto failure; in smu_create_sdb_partition()
998 goto failure; in smu_create_sdb_partition()
1002 failure: in smu_create_sdb_partition()
/linux-4.4.14/arch/arm/nwfpe/
Dentry.S79 mov r4, lr @ save the failure-return addresses
95 reteq r4 @ no, return failure
/linux-4.4.14/arch/x86/mm/
Dpat_rbtree.c137 goto failure; in memtype_rb_check_conflict()
151 goto failure; in memtype_rb_check_conflict()
162 failure: in memtype_rb_check_conflict()
/linux-4.4.14/Documentation/
Dinit.txt6 Some high-level reasons for failure (listed roughly in order of execution)
39 Please extend this explanation whenever you find new failure causes
44 which can then store the kernel_execve() result value and on failure
Drpmsg.txt76 Returns 0 on success and an appropriate error value on failure.
93 Returns 0 on success and an appropriate error value on failure.
111 Returns 0 on success and an appropriate error value on failure.
123 Returns 0 on success and an appropriate error value on failure.
137 Returns 0 on success and an appropriate error value on failure.
152 Returns 0 on success and an appropriate error value on failure.
203 Returns 0 on success, and an appropriate error value on failure.
Dpercpu-rw-semaphore.txt19 -ENOMEM on allocation failure.
Dremoteproc.txt56 handle on success, and NULL on failure. This function increments
101 On success, the new rproc is returned, and on failure, NULL.
170 On success, 0 should be returned, and on failure, an appropriate error code.
173 On success, 0 is returned, and on failure, an appropriate error code.
Dhwspinlock.txt63 appropriate error code on failure (e.g. -EINVAL if the hwspinlock
246 Returns 0 on success, or appropriate error code on failure.
310 return 0 on failure and 1 on success. This callback may _not_ sleep.
DCodingStyle779 (-Exxx = failure, 0 = success) or a "succeeded" boolean (0 = failure,
793 for success or -EBUSY for failure. In the same way, "PCI device present" is
803 this rule. Generally they indicate failure by returning some out-of-range
805 NULL or the ERR_PTR mechanism to report failure.
Dpnp.txt118 - returns zero for success or a negative error number for failure; count
DDMA-API-HOWTO.txt200 This means that in the failure case, you have three options:
635 of sg entries it mapped them to. On failure 0 is returned.
774 failure can be determined by:
864 the failure case.
Dmd.txt230 by a user-space program. Any device failure or other event that
369 blocked - device has failed, and the failure hasn't been
386 Writing "faulty" simulates a failure on the device.
Diostats.txt131 or failure of the read cannot be attributed to the partition. In other
Drobust-futex-ABI.txt31 probably causing deadlock or other such failure of the other threads
Dunshare.txt159 On success, zero returned. On failure, -1 is returned and errno is
Dvme_api.txt77 failure. For all successful matches, the probe routine of the corresponding
DDMA-API.txt322 mapped them to. On failure 0, is returned.
531 failure.
DManagementStyle123 That may sound like a failure, but it's usually a sign that there was
Dcpu-hotplug.txt224 seen any poweroff/reboot failure so far after CPU0 is offline on a few tested
DSubmittingPatches691 have led to this patch. Including symptoms of the failure which the
694 looking for the applicable patch. If a patch fixes a compile failure,
Ddma-buf-sharing.txt61 buffer, so it can be exported. On failure to allocate the dma_buf object,
/linux-4.4.14/Documentation/powerpc/
Dtransactional_memory.txt60 abort handler can check the cause of the failure, and retry.
78 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
85 effects will be persistent, independent of transaction success or failure. No
92 failure before entering the kernel (which may produce different failure codes).
195 presented). The transaction cannot then be continued and will take the failure
Deeh-pci-error-recovery.txt36 EEH was originally designed to guard against hardware failure, such
154 allow any interested parties to find out about the failure. Device
Dcxlflash.txt305 check if the device is operating normally. If a failure is returned
/linux-4.4.14/tools/testing/selftests/rcutorture/bin/
Dparse-console.sh42 print_warning Assertion failure in $file $title
/linux-4.4.14/net/ipv4/
Dfib_semantics.c1033 goto failure; in fib_create_info()
1038 goto failure; in fib_create_info()
1043 goto failure; in fib_create_info()
1060 goto failure; in fib_create_info()
1065 goto failure; in fib_create_info()
1071 goto failure; in fib_create_info()
1098 goto failure; in fib_create_info()
1145 goto failure; in fib_create_info()
1152 goto failure; in fib_create_info()
1206 failure: in fib_create_info()
Dipmr.c430 goto failure; in ipmr_new_tunnel()
437 goto failure; in ipmr_new_tunnel()
443 failure: in ipmr_new_tunnel()
523 goto failure; in ipmr_reg_vif()
532 goto failure; in ipmr_reg_vif()
538 failure: in ipmr_reg_vif()
Dtcp_ipv4.c223 goto failure; in tcp_v4_connect()
232 goto failure; in tcp_v4_connect()
250 goto failure; in tcp_v4_connect()
254 failure: in tcp_v4_connect()
/linux-4.4.14/drivers/net/ethernet/micrel/
Dks8695net.c1386 goto failure; in ks8695_probe()
1396 goto failure; in ks8695_probe()
1404 goto failure; in ks8695_probe()
1417 goto failure; in ks8695_probe()
1427 goto failure; in ks8695_probe()
1469 goto failure; in ks8695_probe()
1528 goto failure; in ks8695_probe()
1535 failure: in ks8695_probe()
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dsbs_sbs-battery.txt9 IO failure.
/linux-4.4.14/tools/testing/selftests/futex/
DREADME32 o Tests return 0 for success and < 0 for failure.
45 FAIL: Reason for test failure
/linux-4.4.14/net/sched/
Dact_police.c169 goto failure; in tcf_act_police_locate()
175 goto failure; in tcf_act_police_locate()
247 failure: in tcf_act_police_locate()
Dsch_htb.c1344 goto failure; in htb_change_class()
1348 goto failure; in htb_change_class()
1352 goto failure; in htb_change_class()
1358 goto failure; in htb_change_class()
1388 goto failure; in htb_change_class()
1393 goto failure; in htb_change_class()
1398 goto failure; in htb_change_class()
1407 goto failure; in htb_change_class()
1519 failure: in htb_change_class()
Dcls_route.c140 goto failure; in route4_classify()
156 goto failure; in route4_classify()
195 failure: in route4_classify()
Dsch_cbq.c1819 goto failure; in cbq_change_class()
1832 goto failure; in cbq_change_class()
1841 goto failure; in cbq_change_class()
1847 goto failure; in cbq_change_class()
1855 goto failure; in cbq_change_class()
1903 failure: in cbq_change_class()
/linux-4.4.14/arch/ia64/kernel/
Dunaligned.c1372 goto failure; in ia64_handle_unaligned()
1427 goto failure; in ia64_handle_unaligned()
1455 goto failure; in ia64_handle_unaligned()
1471 goto failure; in ia64_handle_unaligned()
1501 goto failure; in ia64_handle_unaligned()
1505 goto failure; in ia64_handle_unaligned()
1521 failure: in ia64_handle_unaligned()
/linux-4.4.14/fs/btrfs/
Dsysfs.c760 goto failure; in btrfs_sysfs_add_mounted()
764 goto failure; in btrfs_sysfs_add_mounted()
770 goto failure; in btrfs_sysfs_add_mounted()
775 goto failure; in btrfs_sysfs_add_mounted()
778 failure: in btrfs_sysfs_add_mounted()
/linux-4.4.14/net/decnet/
Ddn_fib.c284 goto failure; in dn_fib_create_info()
315 goto failure; in dn_fib_create_info()
365 goto failure; in dn_fib_create_info()
369 goto failure; in dn_fib_create_info()
402 failure: in dn_fib_create_info()
/linux-4.4.14/drivers/target/iscsi/
Discsi_target_erl1.c1175 goto failure; in iscsit_handle_dataout_timeout()
1182 goto failure; in iscsit_handle_dataout_timeout()
1205 goto failure; in iscsit_handle_dataout_timeout()
1210 goto failure; in iscsit_handle_dataout_timeout()
1218 goto failure; in iscsit_handle_dataout_timeout()
1226 failure: in iscsit_handle_dataout_timeout()
/linux-4.4.14/sound/isa/wavefront/
Dwavefront_synth.c1965 goto failure; in wavefront_download_firmware()
1972 goto failure; in wavefront_download_firmware()
1977 goto failure; in wavefront_download_firmware()
1981 goto failure; in wavefront_download_firmware()
1989 goto failure; in wavefront_download_firmware()
1997 goto failure; in wavefront_download_firmware()
2006 failure: in wavefront_download_firmware()
/linux-4.4.14/arch/arm/vfp/
Dentry.S45 @ failure to the VFP initialisation code.
/linux-4.4.14/sound/core/oss/
Dpcm_oss.c862 goto failure; in snd_pcm_oss_change_params()
885 goto failure; in snd_pcm_oss_change_params()
910 goto failure; in snd_pcm_oss_change_params()
915 goto failure; in snd_pcm_oss_change_params()
951 goto failure; in snd_pcm_oss_change_params()
959 goto failure; in snd_pcm_oss_change_params()
968 goto failure; in snd_pcm_oss_change_params()
976 goto failure; in snd_pcm_oss_change_params()
981 goto failure; in snd_pcm_oss_change_params()
986 goto failure; in snd_pcm_oss_change_params()
[all …]
/linux-4.4.14/scripts/coccinelle/null/
Deno.cocci47 msg = "ERROR: allocation function on line %s returns NULL not ERR_PTR on failure" % (p1[0].line)
/linux-4.4.14/Documentation/filesystems/
Defivarfs.txt22 but it does prevent this kind of failure from being accomplished
Dpath-lookup.txt195 failure.
315 a better errno) to signal an rcu-walk failure.
342 drop rcu that fail due to d_seq failure and requiring the entire path lookup
368 dentry not existing (which can be common) is not necessarily a failure of
Dceph.txt11 * High availability and reliability. No single point of failure.
Dvfs.txt159 superblock must be locked. On failure it should return ERR_PTR(error).
678 Returns 0 on success; < 0 on failure (which is the error code), in
689 Returns < 0 on failure, otherwise the number of bytes (<= 'copied')
723 indicate failure with a 0 return value.
753 that is signalling imminent failure) it will pass a new page
777 is ok for this address space. Used for memory failure handling.
1038 the case of failure. The vfsmount should be returned with 2 refs on
Dxfs-self-describing-metadata.txt124 events that lead to the eventual failure, and even whether there are corruptions
DLocking282 Note, failure to run either redirty_page_for_writepage() or the combination of
Dcoda.txt692 indicates success or failure.
855 relevant. It indicates success or the type of failure.
/linux-4.4.14/arch/x86/kernel/acpi/
Dwakeup_32.S81 # In case of S3 failure, we'll emerge here. Jump
/linux-4.4.14/Documentation/hwmon/
Dmax3179025 monitoring and control of fan RPM as well as detection of fan failure.
Dg76235 fan1_fault: reports fan failure, i.e. no transition on fan gear pin for
Dhwmon-kernel-api.txt43 or PTR_ERR for failure. If this registration function is used, hardware
/linux-4.4.14/fs/reiserfs/
Dinode.c734 goto failure; in reiserfs_get_block()
743 goto failure; in reiserfs_get_block()
775 goto failure; in reiserfs_get_block()
787 goto failure; in reiserfs_get_block()
884 goto failure; in reiserfs_get_block()
924 goto failure; in reiserfs_get_block()
951 goto failure; in reiserfs_get_block()
962 goto failure; in reiserfs_get_block()
1086 goto failure; in reiserfs_get_block()
1114 goto failure; in reiserfs_get_block()
[all …]
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt13 * failure.
36 The code consists of a the high level handler in mm/memory-failure.c,
51 There are two (actually three) modi memory failure recovery can be in:
Dzsmalloc.txt21 uncompressed form). For allocation requests larger than this size, failure
Dnuma139 itself on allocation failure. The kernel profiling subsystem is an example of
Dtranshuge.txt45 the same vma without any failure or significant delay and without
150 allocation failure to throttle the next allocation attempt.
Dcleancache.txt42 a negative return value indicates failure. A "put_page" will copy a
Dfrontswap.txt38 If a store returns failure, transcendent memory has rejected the data, and the
Dhugetlbpage.txt99 The success or failure of huge page allocation depends on the amount of
Dunevictable-lru.txt448 page on failure - will be freed when the reference count held by the migration
/linux-4.4.14/Documentation/power/
Dbasic-pm-debugging.txt143 A failure of any of the "platform", "processors" or "core" tests may cause your
144 system to hang or become unstable, so please beware. Such a failure usually
175 information about the reasons of the suspend (resume) failure. Alternatively,
227 the failure number. Others are the failure number of different steps of suspend
Ds2ram.txt83 quickly after the resume failure. The trace option does not use the seconds
Dfreezing-of-tasks.txt191 at this point. So, seemingly, the failure is due to the freezing of tasks.
218 leading to freezing failure.
Dsuspend-and-cpuhotplug.txt274 As a result of this task freezing failure, the suspend operation gets
Druntime_pm.txt312 error code on failure, where -EINPROGRESS means that ->runtime_idle() is
319 error code on failure, where -EAGAIN or -EBUSY means it is safe to attempt
332 error code on failure, where -EAGAIN means it may be safe to attempt to
Dswsusp.txt120 seconds to failure. What do you do? Suspend to disk.
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-kernel-api.txt33 This routine returns zero on success and a negative errno code for failure.
132 parameter. It returns zero on success or a negative errno code for failure.
135 parameter. It returns zero on success or a negative errno code for failure.
147 parameter. It returns zero on success or a negative errno code for failure.
233 This routine returns zero on success and a negative errno code for failure.
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-fcoe51 lesb/link_fail: Link Error Status Block (LESB) link failure count.
54 failure count.
/linux-4.4.14/drivers/ras/
DKconfig8 failure.
/linux-4.4.14/arch/arm/boot/dts/
Dimx28-duckbill.dts116 failure {
/linux-4.4.14/drivers/md/
DKconfig86 of each other. In the event of a mirror failure, the RAID driver
90 of a single drive, and the set protects against a failure of (N - 1)
133 the capacity of C * (N - 1) MB, and protects against a failure
142 against a failure of any two drives. For a given sector
368 the capacity of C * (N - 1) MB, and protects against a failure
377 against a failure of any two drives. For a given sector
/linux-4.4.14/fs/minix/
Ditree_common.c47 goto failure; in get_branch()
63 failure: in get_branch()
/linux-4.4.14/net/dccp/
Dipv4.c108 goto failure; in dccp_v4_connect()
115 goto failure; in dccp_v4_connect()
129 goto failure; in dccp_v4_connect()
132 failure: in dccp_v4_connect()
Dipv6.c851 goto failure; in dccp_v6_connect()
874 goto failure; in dccp_v6_connect()
912 failure: in dccp_v6_connect()
/linux-4.4.14/Documentation/cgroups/
Dhugetlb.txt33 hugetlb.<hugepagesize>.failcnt # show the number of allocation failure due to HugeTLB limit
Dmemory.txt474 kernel pages will still be seen. This is not considered a failure and the
553 This failcnt(== failure count) shows the number of times that a usage counter
Dcgroups.txt382 Note that specifying 'release_agent' more than once will return failure.
/linux-4.4.14/drivers/net/ethernet/xircom/
Dxirc2ps_cs.c706 goto failure; in xirc2ps_config()
729 goto failure; in xirc2ps_config()
735 goto failure; in xirc2ps_config()
761 goto failure; in xirc2ps_config()
923 failure: in xirc2ps_config()
/linux-4.4.14/Documentation/thermal/
Dpower_allocator.txt189 success, -E* on failure. This is currently used by the power
202 on failure. This is currently used by thermal core to calculate the
213 -E* on failure. This is currently used by the thermal core to convert
/linux-4.4.14/drivers/infiniband/ulp/iser/
Discsi_iser.c821 goto failure; in iscsi_iser_ep_connect()
830 goto failure; in iscsi_iser_ep_connect()
833 failure: in iscsi_iser_ep_connect()
Diser_verbs.c841 goto failure; in iser_route_handler()
858 goto failure; in iser_route_handler()
862 failure: in iser_route_handler()
/linux-4.4.14/fs/squashfs/
Dfile.c193 goto failure; in read_indexes()
206 failure: in read_indexes()
/linux-4.4.14/fs/jffs2/
DTODO37 case of failure? scan() does not clean everything. Fix.
/linux-4.4.14/include/uapi/linux/
Dkfd_ioctl.h209 struct kfd_memory_exception_failure failure; member
Daudit.h415 __u32 failure; /* Failure-to-log action */ member
/linux-4.4.14/Documentation/scsi/
DChangeLog.sym53c8xx_231 - Check against memory allocation failure for SCRIPTZ and add the
48 - Cleanup a bit the PPR failure recovery code.
Dscsi_eh.txt216 cannot recover some of failed scmds. Also, note that failure of the
217 highest-severity action means EH failure and results in offlining of
240 either retry or error-finish (notify upper layer of failure) recovered
274 layer of failure.
422 layer of failure of the scmds.
DChangeLog.ips59 4.20.13 - Fix some failure cases / reset code
Dscsi_mid_low_api.txt422 * Returns 0 on success, negative errno of failure (e.g. -ENOMEM)
463 * Returns pointer to partition table, or NULL for failure
498 * Returns pointer to new Scsi_Host instance or NULL on failure
558 * Returns 0 on success, -1 on failure
576 * Returns pointer to new Scsi_Host instance or NULL on failure
614 * Returns value: 0 on success, 1 on failure (e.g. LLD busy ??)
1011 * If there's a failure, return either:
Dscsi_fc_transport.txt332 - The link may be down. It is not a failure if it is. It simply
341 failure cases for quicker resolution.
DChangeLog.megaraid_sas152 1. Fix some failure gotos from megasas_probe_one(), etc.
DChangeLog.megaraid6 1. Changes in Initialization to fix kdump failure.
DChangeLog.ncr53c8xx384 interrupt code in case of negotiation failure.
DChangeLog.lpfc522 * Zero out seg_cnt in prep_io failure path to prevent double sg
967 * Removed LPFC_DEV_RPTLUN node failure bit because we don't issue
1390 * Detect failure return from pci_map_sg call in lpfc_os_prep_io
/linux-4.4.14/drivers/net/wireless/libertas_tf/
Dif_usb.c685 u8 failure; in if_usb_receive() local
689 failure = (tmp & 0xff00) >> 8; in if_usb_receive()
690 lbtf_send_tx_feedback(priv, retrycnt, failure); in if_usb_receive()
/linux-4.4.14/drivers/gpu/drm/msm/hdmi/
Dhdmi_hdcp.c293 u32 reg_val, failure, nack0; in reset_hdcp_ddc_failures() local
298 failure = reg_val & HDMI_HDCP_DDC_STATUS_FAILED; in reset_hdcp_ddc_failures()
301 reg_val, failure, nack0); in reset_hdcp_ddc_failures()
303 if (failure) { in reset_hdcp_ddc_failures()
/linux-4.4.14/tools/testing/fault-injection/
Dfailcmd.sh25 likelihood of failure injection, in percent.
/linux-4.4.14/drivers/net/wireless/zd1211rw/
Dzd_mac.h154 u8 failure; member
Dzd_mac.c456 success = !tx_status->failure; in zd_mac_tx_status()
507 int success = !tx_status->failure; in zd_mac_tx_failed()
527 if (tx_status->failure && mac->ack_pending && in zd_mac_tx_failed()
/linux-4.4.14/mm/
DMakefile66 obj-$(CONFIG_MEMORY_FAILURE) += memory-failure.o
/linux-4.4.14/fs/ext4/
Dindirect.c161 goto failure; in ext4_get_branch()
167 goto failure; in ext4_get_branch()
172 goto failure; in ext4_get_branch()
183 failure: in ext4_get_branch()
/linux-4.4.14/Documentation/device-mapper/
Ddm-uevent.txt67 1.) Path failure.
Dera.txt100 crash such as power failure.
Ddm-io.txt65 indicate success or failure on each individual region.
Dpersistent-data.txt49 On power failure your metadata will be as it was when last committed.
Dlog-writes.txt35 cases where a power failure at a particular point in time would create an
Ddm-raid.txt58 resyncing after a failure is likely to take longer.
/linux-4.4.14/arch/frv/mm/
Dtlb-miss.S43 # handle a lookup failure of one sort or another in a kernel TLB handler
88 # handle a lookup failure of one sort or another in a user TLB handler
/linux-4.4.14/fs/sysv/
Ditree.c105 goto failure; in get_branch()
118 failure: in get_branch()
/linux-4.4.14/Documentation/networking/
Dcxacru.txt91 "poll" (used to resume status polling if it was disabled due to failure)
Dxfrm_sync.txt137 or failure.
Dlapb-module.txt72 is the maximum number of tries on the link before it is declared a failure.
Dbonding.txt239 802.3ad aggregations when partial failure of the active aggregator
364 the active slave failure, it doesn't really guarantee that the
419 a slave after a link failure has been detected. This option
746 when failure of the active slave or recovery of the primary slave
762 failure or 2
2037 use_carrier=0 to see if that improves the failure detection time. If
2119 the active slave changes (e.g., due to a link failure), the
2204 thus detecting that failure without switch support.
2208 end connectivity failures (which may be caused by the failure of any
2506 failure). If you find this to be a problem, specify an appropriate
Darcnet.txt31 If you don't e-mail me about your success/failure soon, I may be forced to
/linux-4.4.14/Documentation/video4linux/
Dcafe_ccic25 perhaps decreases the chances of an allocation failure later on.
Dvideobuf176 are void functions which, evidently, are immune to failure.
/linux-4.4.14/arch/powerpc/kernel/
Diommu.c486 goto failure; in ppc_iommu_map_sg()
502 goto failure; in ppc_iommu_map_sg()
556 failure: in ppc_iommu_map_sg()
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt223 Same as above. Total failure, no recovery even after
303 A driver can still return a critical failure for this function if
308 will typically report a "permanent failure" in such a case. The
355 A "permanent failure" has occurred, and the platform cannot recover
366 permanent failure in some way. If the device is hotplug-capable,
Dpcieaer-howto.txt96 failure.
/linux-4.4.14/drivers/net/wireless/libertas/
DREADME142 Value field specifies the consecutive failure count threshold which
144 generated, the consecutive failure count is reset to 0.
/linux-4.4.14/drivers/staging/media/omap4iss/
Diss.c583 int failure = 0; in iss_pipeline_disable() local
611 failure = -ETIMEDOUT; in iss_pipeline_disable()
615 return failure; in iss_pipeline_disable()
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-floppy.1996-200226 * Compromise by not reporting a failure to get this
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES107 Fix premature write failure on congested networks (we would give up
137 cached files. Fix setxattr failure to certain Samba versions. Fix mount
155 connect fails (e.g. due to signing negotiation failure) fix
470 network failure) fix tcp session reconnect code so we do not try first
581 to the kernel log). Fix intermittent failure in connectathon
654 Fix unload_nls oops in a mount failure path. Serialize writes to same socket
671 Fix unsafe global variable usage and password hash failure on gcc 3.3.1
673 failure. Fix invalid dentry - race in mkdir when directory gets created
684 Fix errors in reconnecting after TCP session failure. Fix module unloading
728 during auto reconnection to server after server recovered from failure.
[all …]
/linux-4.4.14/Documentation/sound/alsa/
Dhdspm.txt206 has a failure, there is a takeover to the working one, with no
207 sample failure. Its only useful if you use the second as a
/linux-4.4.14/Documentation/isdn/
DREADME.hysdn106 2 -> card is in an error state due to a previous boot failure
131 1006 Second boot stage failure
/linux-4.4.14/Documentation/blockdev/
DREADME.DAC96086 disks the device names will not change in the event of a disk drive failure.
451 1:1 is now disconnected, simulating a drive failure. The failure is noted by
466 from /proc/rd also reflects the drive failure. The status message in
623 1:2 is now disconnected, simulating a drive failure. The failure is noted by
642 reflects the drive failure and automatic rebuild. The status message in
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt37 emitted. After that only test failure messages are reported until the test
/linux-4.4.14/arch/sparc/kernel/
Detrap_32.S273 bne trap_setup_user_stack_is_bolixed ! failure
/linux-4.4.14/scripts/
Dspelling.txt420 failue||failure
421 failuer||failure
423 faliure||failure
/linux-4.4.14/Documentation/frv/
Datomic-ops.txt101 It simultaneously records the success or failure of the store in ICC3.Z.
/linux-4.4.14/Documentation/devicetree/bindings/c6x/
Ddscr.txt32 failure.
/linux-4.4.14/Documentation/DocBook/
D80211.xml.db66 API-cfg80211-michael-mic-failure
/linux-4.4.14/arch/mips/kernel/
Dr4k_fpu.S363 fault: li v0, -EFAULT # failure
/linux-4.4.14/drivers/net/ethernet/ibm/
Dibmveth.c252 goto failure; in ibmveth_replenish_buffer_pool()
274 goto failure; in ibmveth_replenish_buffer_pool()
285 failure: in ibmveth_replenish_buffer_pool()
/linux-4.4.14/Documentation/usb/
Derror-codes.txt108 error, a failure to respond (often caused by
Dpower-management.txt406 idle. This is perfectly normal. If the reason for failure was that
411 Autoresume attempts also can fail, although failure would mean that
/linux-4.4.14/net/core/
Dsock.c1853 goto failure; in sock_alloc_send_pskb()
1857 goto failure; in sock_alloc_send_pskb()
1866 goto failure; in sock_alloc_send_pskb()
1879 failure: in sock_alloc_send_pskb()
Dskbuff.c4508 goto failure; in alloc_skb_with_frags()
4518 failure: in alloc_skb_with_frags()
/linux-4.4.14/drivers/media/platform/omap3isp/
Disp.c976 int failure = 0; in isp_pipeline_disable() local
1032 failure = -ETIMEDOUT; in isp_pipeline_disable()
1036 return failure; in isp_pipeline_disable()
/linux-4.4.14/drivers/s390/char/
Draw3270.c1174 goto failure; in raw3270_set_online()
1182 failure: in raw3270_set_online()
/linux-4.4.14/drivers/usb/gadget/
DKconfig57 either create new failure modes or remove the one you're
71 either create new failure modes or remove the one you're
/linux-4.4.14/Documentation/development-process/
D6.Followthrough15 standards. A failure to participate in this process is quite likely to
158 having a patch pulled as the result of a failure to fix a regression could
D1.Intro253 the licensing of the kernel is doomed to almost certain failure. There are
D4.Coding270 fact of the matter, though, is that the resulting failure recovery paths
/linux-4.4.14/Documentation/hid/
Dhid-transport.txt68 device failures. Once transport drivers detect unplug or failure events, they
83 retransmission on failure, etc. in a blocking manner. If such functionality is
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME.FPE144 is caused by a failure to alias fp_current to the kernel variable
/linux-4.4.14/Documentation/laptops/
Dasus-laptop.txt243 I appreciate any success or failure
/linux-4.4.14/net/ipv6/
Dtcp_ipv6.c220 goto failure; in tcp_v6_connect()
246 goto failure; in tcp_v6_connect()
297 failure: in tcp_v6_connect()
Dip6mr.c762 goto failure; in ip6mr_reg_vif()
767 failure: in ip6mr_reg_vif()
/linux-4.4.14/Documentation/power/regulator/
Dconsumer.txt170 consumers under regulator stress or failure conditions.
/linux-4.4.14/Documentation/fb/
Dsstfb.txt16 Please read the Bug section, and report any success or failure to me
/linux-4.4.14/fs/ext2/
Dinode.c249 goto failure; in ext2_get_branch()
265 failure: in ext2_get_branch()
/linux-4.4.14/net/netlink/
Daf_netlink.c1989 int failure; member
2024 if (p->failure) { in do_one_broadcast()
2045 p->failure = 1; in do_one_broadcast()
2091 info.failure = 0; in netlink_broadcast_filtered()
/linux-4.4.14/
DREPORTING-BUGS88 If the failure includes an "OOPS:", take a picture of the screen, capture
/linux-4.4.14/drivers/net/wireless/mwifiex/
DREADME152 num_cmd_assoc_fail = <number of associate commands with failure return>
/linux-4.4.14/kernel/
Daudit.c846 s.failure = audit_failure; in audit_receive_msg()
868 err = audit_set_failure(s.failure); in audit_receive_msg()
/linux-4.4.14/Documentation/sysctl/
Dvm.txt391 still having a valid copy on disk) the kernel will handle the failure
416 Enable memory failure recovery (when supported by the platform)
420 0: Always panic on a memory failure.
/linux-4.4.14/Documentation/i2c/
Ddev-interface160 All these transactions return -1 on failure; you can read errno to see
Dwriting-clients387 All these transactions return a negative errno value on failure. The 'write'
/linux-4.4.14/fs/affs/
DChanges12 apparently not causing the failure, as directory
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt229 IT knows when a platform crashes even when there is a hard failure on the host.
/linux-4.4.14/Documentation/input/
Dinput-programming.txt167 in case of failure. The close() callback (which is void) must always succeed.
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt284 successful, -EFAULT on failure. Our original code did not test this
/linux-4.4.14/arch/powerpc/
DKconfig.debug13 Only enable this if you are hitting a build failure in the
/linux-4.4.14/Documentation/filesystems/caching/
Dobject.txt180 failure for whatever reason, and should call fscache_obtained_object() to
Dfscache.txt286 rej=N Number of async ops rejected due to object lookup/create failure
/linux-4.4.14/tools/perf/util/
Dmachine.c833 goto failure; in machines__create_guest_kernel_maps()
837 failure: in machines__create_guest_kernel_maps()
/linux-4.4.14/drivers/net/wireless/
Dmac80211_hwsim.c3120 goto failure; in hwsim_init_netlink()
3125 goto failure; in hwsim_init_netlink()
3130 failure: in hwsim_init_netlink()
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt15 progress, and we experience a power failure, the block will contain a mix of old
Dnvdimm.txt51 performance benefit of interleaving, but enables DIMM-bounded failure
/linux-4.4.14/Documentation/x86/x86_64/
Dboot-options.txt60 threshold to 1. Enabling this may make memory predictive failure
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt29 of failure.
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dat91-clock.txt157 18 (AT91_PMC_CFDEV) -> clock failure detected
/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt235 normally results from lock-class leakage or failure to properly
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt93 * Have simple testcases for every input validation failure case in your ioctl.
/linux-4.4.14/Documentation/nfc/
Dnfc-hci.txt138 success, negative for failure).
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-encoder-api.txt698 8=enable scene change detection (seems to be a failure)
/linux-4.4.14/Documentation/RCU/
Dstallwarn.txt245 o A hardware failure. This is quite unlikely, but has occurred
/linux-4.4.14/Documentation/serial/
Ddriver289 returns, and it should return -EBUSY on failure.
/linux-4.4.14/drivers/media/radio/
DKconfig362 in case of automatic probing failure, ie. as a fallback.
/linux-4.4.14/firmware/keyspan_pda/
Dkeyspan_pda.S679 setb c ; c=1: failure
Dxircom_pgs.S717 setb c ; c=1: failure
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt359 this is a void function and cannot return failure. The subsystem is
/linux-4.4.14/drivers/staging/lustre/
Dsysfs-fs-lustre20 an internal assertion failure
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex767 failure. The structure $<device>_info$ should have a pointer to the
786 success, and non-zero upon failure.
/linux-4.4.14/Documentation/virtual/kvm/
Dapi.txt404 Returns: 0 on success, negative on failure.
1860 Returns: 0 on success, negative value on failure
2112 Returns: 0 on success, negative value on failure
/linux-4.4.14/scripts/genksyms/
Dparse.tab.c_shipped2252 /* Return failure if at end of input. */
/linux-4.4.14/drivers/block/
DDAC960.c6139 goto failure; in DAC960_V1_ExecuteUserCommand()
6158 failure: in DAC960_V1_ExecuteUserCommand()

12