/linux-6.12.1/drivers/target/iscsi/ |
D | iscsi_target_datain_values.c | 76 * For Normal and Recovery DataSequenceInOrder=Yes and DataPDUInOrder=Yes. 90 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_yes_and_yes() 98 next_burst_len = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes() 100 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes() 136 datain->data_sn = (!dr->recovery) ? cmd->data_sn++ : dr->data_sn++; in iscsit_set_datain_values_yes_and_yes() 139 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes() 147 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes() 157 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes() 164 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes() 174 * For Normal and Recovery DataSequenceInOrder=No and DataPDUInOrder=Yes. [all …]
|
/linux-6.12.1/drivers/remoteproc/ |
D | remoteproc_sysfs.c | 22 * By writing to the 'recovery' sysfs entry, we control the behavior of the 23 * recovery mechanism dynamically. The default value of this entry is "enabled". 25 * The 'recovery' sysfs entry supports these commands: 29 * processor crashes while recovery is disabled, it will 30 * be automatically recovered too as soon as recovery is enabled. 36 * recover: This function will trigger an immediate recovery if the 38 * or checking the recovery state (enabled/disabled). 40 * additional crashes to happen after enabling recovery. In this 41 * case, enabling recovery will make it hard to debug subsequent 42 * crashes, so it's recommended to keep recovery disabled, and [all …]
|
D | remoteproc_debugfs.c | 61 * disabled: By default coredump collection is disabled. Recovery will 68 * recovery process will have to wait until data is read by 174 /* expose recovery flag via debugfs */ 185 * By writing to the 'recovery' debugfs entry, we control the behavior of the 186 * recovery mechanism dynamically. The default value of this entry is "enabled". 188 * The 'recovery' debugfs entry supports these commands: 192 * processor crashes while recovery is disabled, it will 193 * be automatically recovered too as soon as recovery is enabled. 199 * recover: This function will trigger an immediate recovery if the 201 * or checking the recovery state (enabled/disabled). [all …]
|
/linux-6.12.1/fs/ocfs2/dlm/ |
D | dlmrecovery.c | 5 * recovery stuff 127 /* Worker function used during recovery. */ 164 * RECOVERY THREAD 169 /* wake the recovery thread in dlm_kick_recovery_thread() 171 * 1) sleeping with no recovery happening in dlm_kick_recovery_thread() 172 * 2) sleeping with recovery mastered elsewhere in dlm_kick_recovery_thread() 173 * 3) recovery mastered here, waiting on reco data */ in dlm_kick_recovery_thread() 178 /* Launch the recovery thread */ 181 mlog(0, "starting dlm recovery thread...\n"); in dlm_launch_recovery_thread() 197 mlog(0, "waiting for dlm recovery thread to exit\n"); in dlm_complete_recovery_thread() [all …]
|
/linux-6.12.1/drivers/s390/scsi/ |
D | zfcp_dbf.h | 28 * struct zfcp_dbf_rec_trigger - trace record for triggered recovery action 29 * @ready: number of ready recovery actions 30 * @running: number of running recovery actions 31 * @want: wanted recovery action 32 * @need: needed recovery action 42 * struct zfcp_dbf_rec_running - trace record for running recovery 45 * @rec_step: current step of the recovery action 58 * enum zfcp_dbf_rec_id - recovery trace record id 59 * @ZFCP_DBF_REC_TRIG: triggered recovery identifier 60 * @ZFCP_DBF_REC_RUN: running recovery identifier [all …]
|
D | zfcp_def.h | 94 * @ZFCP_ERP_ACTION_REOPEN_LUN: LUN recovery. 95 * @ZFCP_ERP_ACTION_REOPEN_PORT: Port recovery. 96 * @ZFCP_ERP_ACTION_REOPEN_PORT_FORCED: Forced port recovery. 97 * @ZFCP_ERP_ACTION_REOPEN_ADAPTER: Adapter recovery. 130 u32 status; /* recovery status */ 176 struct list_head erp_ready_head; /* error recovery for this 182 struct zfcp_erp_action erp_action; /* pending error recovery */ 219 struct zfcp_erp_action erp_action; /* pending error recovery */ 261 * running I/O and recovery is in struct zfcp_scsi_dev.
|
/linux-6.12.1/Documentation/PCI/ |
D | pci-error-recovery.rst | 4 PCI Error Recovery 26 of a bus disconnection, and then performing error recovery. 29 Reporting and recovery is performed in several steps. First, when 38 Next, recovery is performed in several stages. Most of the complexity 57 through a large number of contortions to complete recovery. Almost all 61 device drivers already handle very similar recovery procedures; 72 The error recovery API support is exposed to the driver in the form of 75 and the actual recovery steps taken are platform dependent. The 111 is assumed that the driver is not doing any direct recovery and requires 160 particular, if the platform doesn't isolate slots), and recovery [all …]
|
D | pcieaer-howto.rst | 43 - Performs error recovery actions. 98 To enable error recovery, a software driver must provide callbacks. 152 PCI error-recovery callbacks 157 when performing error recovery actions. 162 pci-error-recovery.rst except PCIe-specific parts (e.g. 163 reset_link). Please refer to pci-error-recovery.rst for detailed 174 require any recovery actions. The AER driver clears the device's 200 function. If reset_link is not NULL, recovery function will use it 210 error recovery handler (pci_driver->err_handler is equal to NULL)? 222 Fatal error recovery will fail if the errors are reported by the [all …]
|
/linux-6.12.1/drivers/md/dm-vdo/ |
D | recovery-journal.c | 6 #include "recovery-journal.h" 30 * The number of reserved blocks must be large enough to prevent a new recovery journal 40 * A lock_counter is intended to keep all of the locks for the blocks in the recovery journal. The 49 * Lock sets are laid out with the set for recovery journal first, followed by the logical zones, 61 * @journal: The recovery journal. 78 * @journal: The recovery journal. 109 * @journal: The recovery journal. 128 * vdo_release_recovery_journal_block_reference() - Release a reference to a recovery journal 130 * @journal: The recovery journal. 214 * is_block_dirty() - Check whether a recovery block is dirty. [all …]
|
D | repair.c | 21 #include "recovery-journal.h" 40 * The absolute position of an entry in the recovery journal, including the sector number and the 70 /* The sequence number of the first valid block for block map recovery */ 77 * The highest sequence number of the journal. During recovery (vs read-only rebuild), not 88 /* The entry data for the block map recovery */ 109 /* These fields are only used during recovery. */ 112 /* The location of the next recovery journal entry to apply */ 274 /* FIXME: shouldn't this say either "recovery" or "repair"? */ in finish_repair() 297 vdo_log_warning("Recovery aborted"); in abort_repair() 674 * advance_points() - Advance the current recovery and journal points. [all …]
|
/linux-6.12.1/fs/gfs2/ |
D | lock_dlm.c | 20 #include "recovery.h" 365 * dlm/gfs2 recovery coordination using dlm_recover callbacks 371 * 4. dlm_controld starts and finishes its own user level recovery 372 * 5. dlm_controld starts dlm-kernel dlm_recoverd to do kernel recovery 374 * 7. dlm_recoverd does its own lock recovery 380 * 13. gfs2_recover provides recovery results to gfs2_control (recovery_result) 384 * - failures during recovery 411 * - parallel recovery steps across all nodes 426 * and missing a journal recovery? 437 * require recovery, because the mount in step 4 could not have [all …]
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-class-remoteproc | 83 copy the dump. Also recovery process will not proceed until 86 What: /sys/class/remoteproc/.../recovery 89 Description: Remote processor recovery mechanism 91 Reports the recovery mechanism of the remote processor, 99 processor crashes while recovery is disabled, it will 100 be automatically recovered too as soon as recovery is enabled.
|
/linux-6.12.1/Documentation/networking/devlink/ |
D | devlink-health.rst | 23 attributes of the health reporting and recovery procedures. 33 * Recovery procedures 50 * Auto recovery attempt is being done. Depends on: 52 - Auto-recovery configuration 80 * Configure reporter's generic parameters (like: disable/enable auto recovery) 81 * Invoke recovery procedure 95 - Triggers reporter's recovery procedure. 98 event in terms of recovery flow should follow closely that of a real
|
/linux-6.12.1/include/linux/ |
D | dm-region-hash.h | 87 * Region recovery control. 90 /* Prepare some regions for recovery by starting to quiesce them. */ 93 /* Try fetching a quiesced region for recovery. */ 96 /* Report recovery end on a region. */ 99 /* Returns number of regions with recovery work outstanding. */ 102 /* Start/stop recovery. */
|
/linux-6.12.1/fs/ocfs2/ |
D | journal.c | 81 * offline slots during recovery and mount 206 /* disable any new recovery threads and wait for any currently in ocfs2_recovery_exit() 213 /* At this point, we know that no more recovery threads can be in ocfs2_recovery_exit() 214 * launched, so wait for any recovery completion work to in ocfs2_recovery_exit() 220 * Now that recovery is shut down, and the osb is about to be in ocfs2_recovery_exit() 924 /* Skip recovery waits here - journal inode metadata never in ocfs2_journal_init() 1289 /* Does the second half of the recovery process. By this point, the 1291 * hence it's no longer in the recovery map, but there's still some 1292 * cleanup we can do which shouldn't happen within the recovery thread 1296 * NOTE: This function can and will sleep on recovery of other nodes [all …]
|
/linux-6.12.1/Documentation/i2c/ |
D | gpio-fault-injection.rst | 36 master under test should detect this condition and trigger a bus recovery (see 38 core (see 'struct bus_recovery_info'). However, the bus recovery will not 47 device. Bus recovery should be able to fix these situations. But please note: 51 and will init a bus recovery on its own. If you want to implement bus recovery 64 recovery. This time, however, it should succeed and the device should release 82 This is why bus recovery (up to 9 clock pulses) must either check SDA or send
|
/linux-6.12.1/net/ipv4/ |
D | tcp_recovery.c | 11 * the recovery or starting the recovery by DUPACK threshold. in tcp_rack_reo_wnd() 131 * the aRTT term is bounded by the fast recovery or timeout, in tcp_rack_advance() 172 * triggering fast recovery, increment reo_wnd by min_rtt/4 (upper bounded 178 * recovery undo). After that, reset it to default (min_rtt/4). 212 /* RFC6582 NewReno recovery for non-SACK connection. It simply retransmits 214 * a) three or more DUPACKs to start the fast recovery 215 * b) an ACK acknowledging new data during the fast recovery.
|
/linux-6.12.1/include/linux/qed/ |
D | qede_rdma.h | 53 int qede_rdma_dev_add(struct qede_dev *dev, bool recovery); 56 void qede_rdma_dev_remove(struct qede_dev *dev, bool recovery); 62 bool recovery) in qede_rdma_dev_add() argument 70 bool recovery) {} in qede_rdma_dev_remove() argument
|
/linux-6.12.1/drivers/md/ |
D | md.c | 518 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in __mddev_resume() 1413 /* active but not in sync implies recovery up to in super_90_validate() 1997 &mddev->recovery)) in super_1_validate() 2460 /* May as well allow recovery to be retried once */ in bind_rdev_to_array() 2656 * curr_resync_completed can only be used during recovery. in md_update_sb() 2663 test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) && in md_update_sb() 2664 test_bit(MD_RECOVERY_RECOVER, &mddev->recovery) && in md_update_sb() 2665 !test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in md_update_sb() 2713 * then a recovery will happen and soon that array won't in md_update_sb() 2794 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) in md_update_sb() [all …]
|
D | raid1.h | 32 * 2/ when resync/recovery is known to be happening - i.e. in code that is 33 * called as part of performing resync/recovery. 79 * whether to retry a read, writeout a resync or recovery 93 * We don't allow both normal IO and resync/recovery IO at 94 * the same time - resync/recovery can only happen when there 113 * recovery to be attempted as we expect a read error.
|
/linux-6.12.1/Documentation/devicetree/bindings/sound/ |
D | st,sta32x.txt | 44 If present, thermal warning recovery is enabled. 46 - st,fault-detect-recovery: 47 If present, fault detect recovery is enabled. 52 - st,fault-detect-recovery: 53 If present, then fault recovery will be enabled.
|
/linux-6.12.1/drivers/pci/pcie/ |
D | err.c | 3 * This file implements the error recovery as a core part of PCIe error 5 * collected and printed to console, then, an error recovery procedure 6 * will be executed by following the PCI error recovery rules. 202 * or RCiEP, recovery runs on the device itself. For Ports, that in pcie_do_recovery() 205 * If it was detected by another device (Endpoint, etc), recovery in pcie_do_recovery() 266 pci_info(bridge, "device recovery successful\n"); in pcie_do_recovery() 275 pci_info(bridge, "device recovery failed\n"); in pcie_do_recovery()
|
/linux-6.12.1/arch/powerpc/platforms/powernv/ |
D | opal-hmi.c | 47 "Core checkstop during recovery" }, in print_core_checkstop_reason() 54 "Recovery in maintenance mode" }, in print_core_checkstop_reason() 64 "Hang Recovery Failed (core check stop)" }, in print_core_checkstop_reason() 203 "Processor Recovery done", in print_hmi_event_info() 204 "Processor recovery occurred again", in print_hmi_event_info() 205 "Processor recovery occurred for masked error", in print_hmi_event_info() 211 "SCOM has set a reserved FIR bit to cause recovery", in print_hmi_event_info() 212 "Debug trigger has set a reserved FIR bit to cause recovery", in print_hmi_event_info() 214 "CAPP recovery process is in progress", in print_hmi_event_info()
|
/linux-6.12.1/arch/s390/pci/ |
D | pci_event.c | 94 pr_info("%s: Automatic recovery failed after initial reporting\n", pci_name(pdev)); in zpci_event_notify_error_detected() 119 pr_info("%s: Automatic recovery failed after MMIO re-enable\n", in zpci_event_do_error_state_clear() 154 pr_info("%s: Automatic recovery failed after slot reset\n", pci_name(pdev)); in zpci_event_do_reset() 164 * We follow the scheme outlined in Documentation/PCI/pci-error-recovery.rst. 165 * With the simplification that recovery always happens per function 177 * configuration space while we perform recovery. in zpci_event_attempt_error_recovery() 198 pr_info("%s: The %s driver bound to the device does not support error recovery\n", in zpci_event_attempt_error_recovery() 218 pr_err("%s: Automatic recovery failed; operator intervention is required\n", in zpci_event_attempt_error_recovery() 287 case 0x0040: /* Service Action or Error Recovery Failed */ in __zpci_event_error()
|
/linux-6.12.1/drivers/net/ethernet/mellanox/mlx5/core/en/xsk/ |
D | setup.c | 193 /* ICOSQ recovery deactivates RQs. Suspend the recovery to avoid in mlx5e_activate_xsk() 194 * activating XSKRQ in the middle of recovery. in mlx5e_activate_xsk() 205 /* ICOSQ recovery may reactivate XSKRQ if clear_bit is called in the in mlx5e_deactivate_xsk() 206 * middle of recovery. Suspend the recovery to avoid it. in mlx5e_deactivate_xsk()
|