Home
last modified time | relevance | path

Searched full:recovery (Results 1 – 25 of 942) sorted by relevance

12345678910>>...38

/linux/drivers/target/iscsi/
H A Discsi_target_datain_values.c76 * 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 …]
H A Discsi_target_erl2.c3 * This file contains error recovery level two functions used by
47 pr_debug("Incremented connection recovery count to %u for" in iscsit_attach_inactive_connection_recovery_entry()
130 pr_debug("Decremented connection recovery count to %u for" in iscsit_remove_active_connection_recovery_entry()
209 pr_debug("iSCSI connection recovery successful for CID:" in iscsit_discard_cr_cmds_by_expstatsn()
234 " 0x%08x during connection recovery on CID: %hu\n", in iscsit_discard_unacknowledged_ooo_cmdsns_for_conn()
269 * connection's command list for connection recovery. in iscsit_prepare_cmds_for_reallegiance()
281 * Only perform connection recovery on ISCSI_OP_SCSI_CMD or in iscsit_prepare_cmds_for_reallegiance()
348 * Add the struct iscsit_cmd to the connection recovery cmd list in iscsit_prepare_cmds_for_reallegiance()
/linux/drivers/remoteproc/
H A Dremoteproc_debugfs.c61 * 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/Documentation/ABI/testing/
H A Dsysfs-class-remoteproc83 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.
H A Dsysfs-driver-chromeos-acpi9 0 Read only (recovery) firmware.
21 0 Recovery.
37 2 Recovery button was pressed.
38 4 Recovery button was pressed (EC firmware).
76 1 Recovery button.
/linux/include/linux/
H A Ddm-region-hash.h87 * 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/Documentation/PCI/
H A Dpcieaer-howto.rst43 - Performs error recovery actions.
123 To enable error recovery, a software driver must provide callbacks.
165 PCI error-recovery callbacks
170 when performing error recovery actions.
175 pci-error-recovery.rst except PCIe-specific parts (see
176 below). Please refer to pci-error-recovery.rst for detailed
187 require any recovery actions. The AER driver clears the device's
217 or needs a reset for recovery. If all affected drivers agree that they can
225 to indicate that recovery without a reset is possible, the error
238 error recovery handler (pci_driver->err_handler is equal to NULL)?
[all …]
/linux/Documentation/i2c/
H A Dgpio-fault-injection.rst36 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/fs/xfs/
H A Dxfs_buf_item_recover.c33 * recovery.
41 * This structure is used during recovery to record the buf log items which
142 /* log buffer item recovery */
145 * Sort buffer items for log recovery. Most buffer items should end up on the
229 * We can only do post recovery validation on items on CRC enabled in xlog_recover_validate_buf_type()
440 * the buffer. This can occur if log recovery is interrupted at some in xlog_recover_validate_buf_type()
442 * subsequent mount starts recovery from the beginning. in xlog_recover_validate_buf_type()
458 * Perform a 'normal' buffer recovery. Each logged region of the
497 * validate it for real and abort recovery of this buffer rather in xlog_recover_do_reg_buffer()
566 * Perform a dquot buffer recovery.
[all …]
/linux/include/linux/qed/
H A Dqede_rdma.h53 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/drivers/s390/scsi/
H A Dzfcp_def.h94 * @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/tools/testing/selftests/ublk/
H A Dtest_part_02.sh24 echo "Testing partition scan with recovery support..."
27 echo "Testing partition scan without recovery..."
60 # Test 1: Without recovery support - should transition to DEAD
63 # Test 2: With recovery support - should transition to QUIESCED
/linux/drivers/md/
H A Dmd.c540 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in __mddev_resume()
1585 /* active but not in sync implies recovery up to in super_90_validate()
2183 &mddev->recovery)) in super_1_validate()
2831 * curr_resync_completed can only be used during recovery. in md_update_sb()
2838 test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) && in md_update_sb()
2839 test_bit(MD_RECOVERY_RECOVER, &mddev->recovery) && in md_update_sb()
2840 !test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in md_update_sb()
2888 * then a recovery will happen and soon that array won't in md_update_sb()
2969 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) in md_update_sb()
3007 set_bit(MD_RECOVERY_RECOVER, &mddev->recovery); in add_bound_rdev()
[all …]
H A Draid10.c137 * When performing a recovery, we need 2 bios, one for read,
154 if (test_bit(MD_RECOVERY_SYNC, &conf->mddev->recovery) || in r10buf_pool_alloc()
155 test_bit(MD_RECOVERY_RESHAPE, &conf->mddev->recovery)) in r10buf_pool_alloc()
158 nalloc = 2; /* recovery */ in r10buf_pool_alloc()
201 &conf->mddev->recovery)) { in r10buf_pool_alloc()
502 &rdev->mddev->recovery); in raid10_end_write_request()
677 * or recovery, so reshape isn't happening in raid10_find_virt()
918 * either some resync/recovery, or reconfigure the array.
1081 if (!test_bit(MD_RECOVERY_RESHAPE, &rdev->mddev->recovery) || in choose_data_offset()
1131 while (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in regular_request_wait()
[all …]
/linux/arch/powerpc/platforms/powernv/
H A Dopal-hmi.c47 "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/drivers/net/ethernet/qlogic/qede/
H A Dqede_rdma.c28 /* Leftovers from previous error recovery */ in _qede_rdma_dev_add()
86 int qede_rdma_dev_add(struct qede_dev *edev, bool recovery) in qede_rdma_dev_add() argument
94 if (recovery) in qede_rdma_dev_add()
116 void qede_rdma_dev_remove(struct qede_dev *edev, bool recovery) in qede_rdma_dev_remove() argument
122 if (!recovery) { in qede_rdma_dev_remove()
219 /* If device has experienced recovery it was already removed */ in qede_rdma_unregister_driver()
310 /* If a recovery was experienced avoid adding the event */ in qede_rdma_add_event()
/linux/tools/testing/selftests/powerpc/eeh/
H A Deeh-functions.sh72 # The ahci driver doesn't support error recovery. If the ahci device
77 log "$dev, Skipped: ahci doesn't support recovery"
83 # and injecting new errors during the recovery process will probably
84 # result in the recovery failing and the device being marked as
117 # The current record holder for longest recovery time is:
145 # error recovery
/linux/fs/xfs/libxfs/
H A Dxfs_log_recover.h11 * define how recovery should work for that type of log item.
44 * recovery, if provided.
51 * log a new intent-done item; or (c) recovery fails and we have to
146 * Transform a regular reservation into one suitable for recovery of a log
149 * Intent recovery only runs a single step of the transaction chain and defers
/linux/include/uapi/rdma/
H A Dqedr-abi.h141 /* address of SQ doorbell recovery user entry */
144 /* address of RQ doorbell recovery user entry */
166 /* doorbell recovery entry allocated and populated by userspace doorbelling
168 * information with doorbell drop recovery mechanism.
/linux/fs/ocfs2/dlm/
H A Ddlmlock.c132 /* for the recovery lock, we can't allow the ast in dlmlock_master()
134 * frozen. but the recovery lock is always locked in dlmlock_master()
237 /* recovery lock was mastered by dead node. in dlmlock_remote()
240 mlog(0, "%s: recovery lock was owned by " in dlmlock_remote()
257 /* special case for the $RECOVERY lock. in dlmlock_remote()
261 mlog(0, "%s: $RECOVERY lock for this node (%u) is " in dlmlock_remote()
548 int convert = 0, recovery = 0; in dlmlock() local
570 recovery = (flags & LKM_RECOVERY); in dlmlock()
572 if (recovery && in dlmlock()
629 mlog(0, "retrying convert with migration/recovery/" in dlmlock()
[all …]
/linux/drivers/i2c/busses/
H A Di2c-uniphier.c159 bool recovery = false; in uniphier_i2c_xfer_one() local
171 /* This error is fatal. Needs recovery. */ in uniphier_i2c_xfer_one()
173 recovery = true; in uniphier_i2c_xfer_one()
180 /* Failed to issue STOP. The bus needs recovery. */ in uniphier_i2c_xfer_one()
181 recovery = true; in uniphier_i2c_xfer_one()
186 if (recovery) in uniphier_i2c_xfer_one()
201 * in a wrong state. Try bus recovery. in uniphier_i2c_check_bus_busy()
/linux/include/ufs/
H A Dufs_quirks.h45 * - If there are fatal errors then SW does normal error recovery.
48 * - If NOP command times out, SW does normal error recovery
52 * enable this quirk to initiate quick error recovery and also silence related
84 * Gear switch can be issued by host controller as an error recovery and any
/linux/Documentation/devicetree/bindings/power/reset/
H A Dreboot-mode.yaml24 - recovery: Android Recovery mode, it is a mode to format the device or update a new image.
45 mode-recovery = <1>;
/linux/drivers/pci/hotplug/
H A Drpaphp_pci.c58 * get_adapter_status() can be called by the EEH handler during EEH recovery.
65 * operations. This sometimes causes EEH recovery to fail. To avoid this issue,
67 * recovery state and return -EBUSY error based on RTAS return status. This
69 * immediately and successfully proceed with EEH recovery steps.
85 * recovery. in __rpaphp_get_sensor_state()
/linux/Documentation/scsi/
H A Dscsi_eh.rst179 performs during recovery. This will be discussed in [2-2].
181 Once recovery is complete, SCSI EH resumes normal operation by
209 To achieve these goals, EH performs recovery actions with increasing
227 During recovery, the following rules are followed
229 - Recovery actions are performed on failed scmds on the to do list,
230 eh_work_q. If a recovery action succeeds for a scmd, recovered
233 Note that single recovery action on a scmd can recover multiple
240 - EH reuses failed scmds to issue commands for recovery. For
334 causes higher-severity recovery to be taken for the scmd.
427 scsi_unjam_host() and it is responsible for whole recovery process.

12345678910>>...38