/linux-6.1.9/samples/bpf/ |
D | test_lwt_bpf.sh | 134 function failure { function 144 failure "test_ctx xmit: packets are dropped" 160 failure "test_ctx out: packets are dropped" 176 failure "test_ctx out: packets are dropped" 200 failure "test_data ${1}: packets are dropped" 213 failure "test_data in: packets are dropped" 231 failure "test_cb ${1}: packets are dropped" 247 failure "test_cb in: packets are dropped" 271 failure "test_drop_all ${1}: Unexpected success of ping" 284 failure "test_drop_all in: Unexpected success of ping" [all …]
|
/linux-6.1.9/arch/x86/kernel/cpu/ |
D | rdrand.c | 27 bool failure = false; in x86_init_rdrand() local 35 failure = true; in x86_init_rdrand() 42 failure = true; in x86_init_rdrand() 44 if (failure) { in x86_init_rdrand()
|
/linux-6.1.9/tools/perf/tests/ |
D | mem.c | 14 char failure[100]; in check() local 21 scnprintf(failure, sizeof failure, "unexpected %s", out); in check() 22 TEST_ASSERT_VAL(failure, !strcmp(string, out)); in check()
|
/linux-6.1.9/drivers/media/platform/mediatek/mdp/ |
D | mtk_mdp_vpu.c | 38 vpu->failure = msg->status; in mtk_mdp_vpu_ipi_handler() 39 if (!vpu->failure) { in mtk_mdp_vpu_ipi_handler() 57 msg_id, vpu->failure); in mtk_mdp_vpu_ipi_handler() 106 if (!err && vpu->failure) in mtk_mdp_vpu_send_ap_ipi() 124 if (!err && vpu->failure) in mtk_mdp_vpu_init()
|
/linux-6.1.9/drivers/gpu/drm/amd/amdgpu/ |
D | amdgpu_acp.c | 273 goto failure; in acp_hw_init() 279 goto failure; in acp_hw_init() 285 goto failure; in acp_hw_init() 323 goto failure; in acp_hw_init() 327 goto failure; in acp_hw_init() 336 goto failure; in acp_hw_init() 342 goto failure; in acp_hw_init() 348 goto failure; in acp_hw_init() 444 goto failure; in acp_hw_init() 449 goto failure; in acp_hw_init() [all …]
|
/linux-6.1.9/arch/m68k/ifpsp060/ |
D | os.S | 84 | 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
|
/linux-6.1.9/drivers/media/platform/mediatek/vcodec/ |
D | venc_vpu_if.c | 33 vpu->failure = 1; in handle_enc_init_msg() 57 vpu->failure = (msg->status != VENC_IPI_MSG_STATUS_OK); in vpu_enc_ipi_handler() 58 if (vpu->failure) in vpu_enc_ipi_handler() 59 goto failure; in vpu_enc_ipi_handler() 77 failure: in vpu_enc_ipi_handler() 100 if (vpu->failure) in vpu_enc_send_msg() 117 vpu->failure = 0; in vpu_enc_init()
|
D | vdec_vpu_if.c | 53 vpu->failure = 1; in handle_init_ack_msg() 73 vpu->failure = 1; in handle_get_param_msg_ack() 101 vpu->failure = msg->status; in vpu_dec_ipi_handler() 137 vpu->failure = 0; in vcodec_vpu_send_msg() 158 return vpu->failure; in vcodec_vpu_send_msg()
|
/linux-6.1.9/drivers/gpu/drm/amd/amdkfd/ |
D | kfd_events.c | 1172 memory_exception_data.failure.NotPresent = 1; in kfd_signal_iommu_event() 1173 memory_exception_data.failure.NoExecute = 0; in kfd_signal_iommu_event() 1174 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event() 1176 memory_exception_data.failure.NotPresent = 0; in kfd_signal_iommu_event() 1179 memory_exception_data.failure.ReadOnly = 1; in kfd_signal_iommu_event() 1181 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event() 1184 memory_exception_data.failure.NoExecute = 1; in kfd_signal_iommu_event() 1186 memory_exception_data.failure.NoExecute = 0; in kfd_signal_iommu_event() 1193 memory_exception_data.failure.NotPresent, in kfd_signal_iommu_event() 1194 memory_exception_data.failure.NoExecute, in kfd_signal_iommu_event() [all …]
|
D | kfd_int_process_v11.c | 310 exception_data.failure.NotPresent = info.prot_valid ? 1 : 0; in event_interrupt_wq_v11() 311 exception_data.failure.NoExecute = info.prot_exec ? 1 : 0; in event_interrupt_wq_v11() 312 exception_data.failure.ReadOnly = info.prot_write ? 1 : 0; in event_interrupt_wq_v11() 313 exception_data.failure.imprecise = 0; in event_interrupt_wq_v11()
|
/linux-6.1.9/drivers/hid/ |
D | hid-uclogic-core.c | 201 goto failure; in uclogic_probe() 211 goto failure; in uclogic_probe() 219 goto failure; in uclogic_probe() 230 goto failure; in uclogic_probe() 236 goto failure; in uclogic_probe() 242 goto failure; in uclogic_probe() 246 failure: in uclogic_probe()
|
/linux-6.1.9/Documentation/driver-api/driver-model/ |
D | devres.rst | 29 sufficient bugs in ->remove and ->probe failure path. Well, yes, 37 initialization failure don't happen often enough to be noticeable. 38 Init failure path is worse because it's much less travelled while 42 and having half broken failure path implementation in ->probe() which 43 would leak resources or even cause oops when failure occurs. iomap 134 to better maintained higher layer. Also, as init failure path is 151 resources on failure. For example:: 172 As resource acquisition failure usually means probe failure, constructs 174 layer) where interface function shouldn't have side effect on failure.
|
/linux-6.1.9/net/sched/ |
D | act_police.c | 102 goto failure; in tcf_police_init() 108 goto failure; in tcf_police_init() 119 goto failure; in tcf_police_init() 124 goto failure; in tcf_police_init() 133 goto failure; in tcf_police_init() 142 goto failure; in tcf_police_init() 149 goto failure; in tcf_police_init() 155 goto failure; in tcf_police_init() 221 failure: in tcf_police_init()
|
/linux-6.1.9/tools/testing/selftests/lkdtm/ |
D | tests.txt | 7 #EXHAUST_STACK Corrupts memory on failure 22 #WRITE_AFTER_FREE Corrupts memory on failure 24 #WRITE_BUDDY_AFTER_FREE Corrupts memory on failure
|
/linux-6.1.9/scripts/ |
D | Kconfig.include | 22 # $(failure,<command>) 24 failure = $(if-success,$(1),n,y) variable 39 $(error-if,$(failure,command -v $(CC)),C compiler '$(CC)' not found) 40 $(error-if,$(failure,command -v $(LD)),linker '$(LD)' not found)
|
/linux-6.1.9/arch/x86/mm/pat/ |
D | memtype_interval.c | 90 goto failure; in memtype_check_conflict() 98 goto failure; in memtype_check_conflict() 108 failure: in memtype_check_conflict()
|
/linux-6.1.9/drivers/net/ethernet/intel/i40e/ |
D | i40e_xsk.c | 327 bool *failure) in i40e_handle_xdp_result_zc() argument 338 *failure = true; in i40e_handle_xdp_result_zc() 391 bool failure = false; in i40e_clean_rx_irq_zc() local 437 &rx_bytes, size, xdp_res, &failure); in i40e_clean_rx_irq_zc() 438 if (failure) in i40e_clean_rx_irq_zc() 450 failure |= !i40e_alloc_rx_buffers_zc(rx_ring, cleaned_count); in i40e_clean_rx_irq_zc() 456 if (failure || next_to_clean == rx_ring->next_to_use) in i40e_clean_rx_irq_zc() 463 return failure ? budget : (int)total_rx_packets; in i40e_clean_rx_irq_zc()
|
/linux-6.1.9/drivers/macintosh/ |
D | windfarm_fcu_controls.c | 171 unsigned char failure; in wf_fcu_fan_get_rpm() local 175 rc = wf_fcu_read_reg(pv, 0xb, &failure, 1); in wf_fcu_fan_get_rpm() 178 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_rpm() 227 unsigned char failure; in wf_fcu_fan_get_pwm() local 232 rc = wf_fcu_read_reg(pv, 0x2b, &failure, 1); in wf_fcu_fan_get_pwm() 235 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_pwm()
|
/linux-6.1.9/drivers/net/can/sja1000/ |
D | kvaser_pci.c | 265 goto failure; in kvaser_pci_add_chan() 273 failure: in kvaser_pci_add_chan() 296 goto failure; in kvaser_pci_init_one() 362 failure: in kvaser_pci_init_one()
|
/linux-6.1.9/drivers/net/ethernet/intel/ixgbe/ |
D | ixgbe_xsk.c | 256 bool failure = false; in ixgbe_clean_rx_irq_zc() local 266 failure = failure || in ixgbe_clean_rx_irq_zc() 313 failure = true; in ixgbe_clean_rx_irq_zc() 370 if (failure || rx_ring->next_to_clean == rx_ring->next_to_use) in ixgbe_clean_rx_irq_zc() 377 return failure ? budget : (int)total_rx_packets; in ixgbe_clean_rx_irq_zc()
|
/linux-6.1.9/Documentation/admin-guide/ |
D | init.rst | 6 This document provides some high-level reasons for failure 38 Please extend this explanation whenever you find new failure causes 44 which can then store the ``kernel_execve()`` result value and on failure
|
/linux-6.1.9/arch/arm/nwfpe/ |
D | entry.S | 67 mov r4, lr @ save the failure-return addresses 83 reteq r4 @ no, return failure
|
/linux-6.1.9/drivers/staging/ks7010/ |
D | ks_hostif.c | 379 mic_failure->failure = 0; in hostif_data_indication_wpa() 382 if (mic_failure->failure == 0) { in hostif_data_indication_wpa() 383 mic_failure->failure = 1; in hostif_data_indication_wpa() 385 } else if (mic_failure->failure == 1) { in hostif_data_indication_wpa() 386 mic_failure->failure = 2; in hostif_data_indication_wpa() 450 priv->wpa.mic_failure.failure == 2) { in hostif_data_indication() 960 priv->wpa.mic_failure.failure); in hostif_mic_failure_confirm() 1148 priv->wpa.mic_failure.failure > 0) { in hostif_data_request() 1203 priv->wpa.mic_failure.failure > 0) { in hostif_data_request() 1210 if (priv->wpa.mic_failure.failure == 2) in hostif_data_request() [all …]
|
/linux-6.1.9/tools/testing/selftests/powerpc/tm/ |
D | tm-trap.c | 219 : : : : failure, success); in ping() 221 failure: in ping()
|
/linux-6.1.9/Documentation/fault-injection/ |
D | fault-injection.rst | 67 likelihood of failure injection, in percent. 71 Note that one-failure-per-hundred is a very high error rate 98 specifies the verbosity of the messages when failure is 100 log line per failure; '2' will print a call trace too -- useful 153 default is 'N', setting it to 'Y' will disable failure injections 270 Upon should_fail() returning true, client code should inject a failure: 400 allocation failure:: 411 Same as above except to inject page allocation failure instead of slab 412 allocation failure::
|