Home
last modified time | relevance | path

Searched full:faulty (Results 1 – 25 of 225) sorted by relevance

123456789

/kernel/linux/linux-6.6/drivers/md/
Dmd-faulty.c3 * faulty.c : Multiple Devices driver for Linux
12 * The "faulty" personality causes some requests to fail.
30 * persisting-faulty blocks. When a new fault is requested that would
338 .name = "faulty",
363 MODULE_ALIAS("md-personality-10"); /* faulty */
364 MODULE_ALIAS("md-faulty");
Dmd.h75 * Not working: faulty==1 in_sync==0
76 * Fully working: faulty==0 in_sync==1
79 * faulty==0 in_sync==0
81 * It can never have faulty==1, in_sync==1
141 Faulty, /* device is known to have a fault */ enumerator
193 * this device was known to be faulty,
632 /* error_handler must set ->faulty and clear ->in_sync
828 int faulty = test_bit(Faulty, &rdev->flags); in rdev_dec_pending() local
829 if (atomic_dec_and_test(&rdev->nr_pending) && faulty) { in rdev_dec_pending()
DMakefile34 faulty-y += md-faulty.o
47 obj-$(CONFIG_MD_FAULTY) += faulty.o
Draid10.c497 * When the device is faulty, it is not necessary to in raid10_end_write_request()
500 if (!test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
525 * rebuilding or Faulty. This is because we cannot use in raid10_end_write_request()
532 !test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
779 if (rdev == NULL || test_bit(Faulty, &rdev->flags) || in read_balance()
791 test_bit(Faulty, &rdev->flags)) in read_balance()
1485 if (rdev && (test_bit(Faulty, &rdev->flags))) in raid10_write_request()
1487 if (rrdev && (test_bit(Faulty, &rrdev->flags))) in raid10_write_request()
1796 if (rdev && (test_bit(Faulty, &rdev->flags))) in raid10_handle_discard()
1798 if (rrdev && (test_bit(Faulty, &rrdev->flags))) in raid10_handle_discard()
[all …]
Dmd-multipath.c39 !test_bit(Faulty, &rdev->flags)) { in multipath_map()
177 set_bit(Faulty, &rdev->flags); in multipath_error()
202 i,!test_bit(Faulty, &tmp->rdev->flags), in print_multipath_conf()
383 if (!test_bit(Faulty, &rdev->flags)) in multipath_run()
Draid1.c477 * When the device is faulty, it is not necessary to in raid1_end_write_request()
480 if (!test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
507 * rebuilding or Faulty. This is because we cannot use in raid1_end_write_request()
514 !test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
648 || test_bit(Faulty, &rdev->flags)) in read_balance()
1417 if (!rdev || test_bit(Faulty, &rdev->flags)) { in raid1_write_request()
1644 * @rdev is marked as &Faulty excluding case when array is failed and
1667 set_bit(Faulty, &rdev->flags); in raid1_error()
1699 !test_bit(Faulty, &rdev->flags), in print_conf()
1738 && !test_bit(Faulty, &repl->flags) in raid1_spare_active()
[all …]
Dmd.c518 !test_bit(Faulty, &rdev->flags)) { in submit_flushes()
913 if (!test_bit(Faulty, &rdev->flags) in super_written()
943 if (test_bit(Faulty, &rdev->flags)) in md_super_write()
1277 clear_bit(Faulty, &rdev->flags); in super_90_validate()
1372 set_bit(Faulty, &rdev->flags); in super_90_validate()
1485 test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1501 if (test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1519 /* now set the "removed" and "faulty" bits on any missing devices */ in super_90_sync()
1788 clear_bit(Faulty, &rdev->flags); in super_1_validate()
1911 * It could happen that our rdev was marked as Faulty, and all other in super_1_validate()
[all …]
/kernel/linux/linux-5.10/drivers/md/
Dmd-faulty.c3 * faulty.c : Multiple Devices driver for Linux
12 * The "faulty" personality causes some requests to fail.
30 * persisting-faulty blocks. When a new fault is requested that would
336 .name = "faulty",
361 MODULE_ALIAS("md-personality-10"); /* faulty */
362 MODULE_ALIAS("md-faulty");
DMakefile29 faulty-y += md-faulty.o
42 obj-$(CONFIG_MD_FAULTY) += faulty.o
Dmd.h75 * Not working: faulty==1 in_sync==0
76 * Fully working: faulty==0 in_sync==1
79 * faulty==0 in_sync==0
81 * It can never have faulty==1, in_sync==1
143 Faulty, /* device is known to have a fault */ enumerator
195 * this device was known to be faulty,
577 /* error_handler must set ->faulty and clear ->in_sync
772 int faulty = test_bit(Faulty, &rdev->flags); in rdev_dec_pending() local
773 if (atomic_dec_and_test(&rdev->nr_pending) && faulty) { in rdev_dec_pending()
Draid10.c471 * When the device is faulty, it is not necessary to in raid10_end_write_request()
474 if (!test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
499 * rebuilding or Faulty. This is because we cannot use in raid10_end_write_request()
506 !test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
753 if (rdev == NULL || test_bit(Faulty, &rdev->flags) || in read_balance()
765 test_bit(Faulty, &rdev->flags)) in read_balance()
896 if (test_bit(Faulty, &rdev->flags)) { in flush_pending_writes()
1090 if (test_bit(Faulty, &rdev->flags)) { in raid10_unplug()
1380 if (rdev && (test_bit(Faulty, &rdev->flags))) in raid10_write_request()
1382 if (rrdev && (test_bit(Faulty, &rrdev->flags))) in raid10_write_request()
[all …]
Dmd-multipath.c39 !test_bit(Faulty, &rdev->flags)) { in multipath_map()
181 set_bit(Faulty, &rdev->flags); in multipath_error()
207 i,!test_bit(Faulty, &tmp->rdev->flags), in print_multipath_conf()
389 if (!test_bit(Faulty, &rdev->flags)) in multipath_run()
Draid1.c473 * When the device is faulty, it is not necessary to in raid1_end_write_request()
476 if (!test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
503 * rebuilding or Faulty. This is because we cannot use in raid1_end_write_request()
510 !test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
644 || test_bit(Faulty, &rdev->flags)) in read_balance()
800 if (test_bit(Faulty, &rdev->flags)) { in flush_bio_list()
1385 if (!rdev || test_bit(Faulty, &rdev->flags)) { in raid1_write_request()
1622 set_bit(Faulty, &rdev->flags); in raid1_error()
1655 !test_bit(Faulty, &rdev->flags), in print_conf()
1694 && !test_bit(Faulty, &repl->flags) in raid1_spare_active()
[all …]
Dmd.c569 !test_bit(Faulty, &rdev->flags)) { in submit_flushes()
950 if (!test_bit(Faulty, &rdev->flags) in super_written()
981 if (test_bit(Faulty, &rdev->flags)) in md_super_write()
1316 clear_bit(Faulty, &rdev->flags); in super_90_validate()
1411 set_bit(Faulty, &rdev->flags); in super_90_validate()
1524 test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1540 if (test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1558 /* now set the "removed" and "faulty" bits on any missing devices */ in super_90_sync()
1830 clear_bit(Faulty, &rdev->flags); in super_1_validate()
1952 case MD_DISK_ROLE_FAULTY: /* faulty */ in super_1_validate()
[all …]
/kernel/linux/linux-6.6/drivers/staging/media/omap4iss/
Diss_ipipeif.h43 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
46 * @fpc: Faulty pixels correction configuration
/kernel/linux/linux-5.10/drivers/staging/media/omap4iss/
Diss_ipipeif.h43 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
46 * @fpc: Faulty pixels correction configuration
/kernel/linux/linux-5.10/drivers/media/platform/omap3isp/
Dispccdc.h110 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
113 * @fpc: Faulty pixels correction configuration
/kernel/linux/linux-6.6/drivers/media/platform/ti/omap3isp/
Dispccdc.h110 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
113 * @fpc: Faulty pixels correction configuration
/kernel/linux/linux-6.6/Documentation/admin-guide/
Dmd.rst195 raid5, linear, multipath, faulty.
254 For arrays with data redundancy (i.e. not raid0, linear, faulty,
455 faulty
474 it were not faulty are blocked.
499 Writing ``faulty`` simulates a failure on the device.
528 This file responds to select/poll. Any change to ``faulty``
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dmd.rst195 raid5, linear, multipath, faulty.
254 For arrays with data redundancy (i.e. not raid0, linear, faulty,
455 faulty
474 it were not faulty are blocked.
499 Writing ``faulty`` simulates a failure on the device.
528 This file responds to select/poll. Any change to ``faulty``
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/supply/
Drohm,bd99954.yaml103 # battery is expected to be faulty if battery voltage exceeds this limit.
104 # Charger will then enter to a "battery faulty" -state
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Drohm,bd99954.yaml102 # battery is expected to be faulty if battery voltage exceeds this limit.
103 # Charger will then enter to a "battery faulty" -state
/kernel/linux/linux-5.10/arch/arm/mm/
Dabort-ev6.S24 * Faulty SWP instruction on 1136 doesn't set bit 11 in DFSR.
/kernel/linux/linux-6.6/arch/arm/mm/
Dabort-ev6.S25 * Faulty SWP instruction on 1136 doesn't set bit 11 in DFSR.
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/netronome/
Dnfp.rst170 alignment errors. The cause is usually faulty cables or SFPs.
214 * An error on the MAC/physical layer. Usually due to faulty cables or

123456789