Home
last modified time | relevance | path

Searched full:bad (Results 1 – 25 of 2764) sorted by relevance

12345678910>>...111

/Linux-v5.4/include/linux/ceph/
Ddecode.h57 #define ceph_decode_need(p, end, n, bad) \ argument
60 goto bad; \
63 #define ceph_decode_64_safe(p, end, v, bad) \ argument
65 ceph_decode_need(p, end, sizeof(u64), bad); \
68 #define ceph_decode_32_safe(p, end, v, bad) \ argument
70 ceph_decode_need(p, end, sizeof(u32), bad); \
73 #define ceph_decode_16_safe(p, end, v, bad) \ argument
75 ceph_decode_need(p, end, sizeof(u16), bad); \
78 #define ceph_decode_8_safe(p, end, v, bad) \ argument
80 ceph_decode_need(p, end, sizeof(u8), bad); \
[all …]
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-dust.txt4 This target emulates the behavior of bad sectors at arbitrary
11 drive with bad sectors).
15 in the "bad block list" will fail with EIO ("Input/output error").
17 Writes of blocks in the "bad block list will result in the following:
19 1. Remove the block from the "bad block list".
22 This emulates the "remapped sector" behavior of a drive with bad
25 Normally, a drive that is encountering bad sectors will most likely
26 encounter more bad sectors, at an unknown time or location.
28 messages to add arbitrary bad blocks at new locations, and the
30 configured "bad blocks" will be treated as bad, or bypassed.
[all …]
/Linux-v5.4/tools/testing/ktest/
Dconfig-bisect.pl9 # config-bisect.pl [options] good-config bad-config [good|bad]
12 # Compares a good config to a bad config, then takes half of the diffs
14 # the bad config. That is, the resulting config will start with the
16 # the good and bad configs match the bad config. It tries because of
24 # $ config-bisect.pl /path/to/good/config /path/to/bad/config
27 # so do not make that be one of the good or bad configs), and then
30 # the good config. It does the same for the bad config as well.
35 # and the bad config to /path/to/bad/config.tmp (just appends ".tmp" to the
39 # After the first run, determine if the result is good or bad then
43 # $ config-bisect.pl /path/to/good/config /path/to/bad/config good
[all …]
/Linux-v5.4/drivers/mtd/nand/onenand/
Donenand_bbt.c3 * Bad Block Table support for the OneNAND driver
26 * Check for a pattern at the given place. Used to search bad block
27 * tables and good / bad block identifiers. Same as check_pattern, but
46 * create_bbt - [GENERIC] Create a bad block table by scanning the device
49 * @param bd descriptor for the good/bad block search pattern
53 * Create a bad block table by scanning the device
54 * for the given good/bad block identify pattern
67 printk(KERN_INFO "Scanning device for bad blocks\n"); in create_bbt()
97 /* If it is a initial bad block, just ignore it */ in create_bbt()
105 "initial bad block\n", i >> 1); in create_bbt()
[all …]
/Linux-v5.4/include/linux/mtd/
Dbbm.h3 * NAND family Bad Block Management (BBM) header file
4 * - Bad Block Table (BBT) implementation
19 * struct nand_bbt_descr - bad block table descriptor
32 * bad) block in the stored bbt
33 * @pattern: pattern to identify bad block table or factory marked good /
34 * bad blocks, can be NULL, if len = 0
36 * Descriptor for the bad block table marker and the descriptor for the
37 * pattern which identifies good and bad blocks. The assumption is made
53 /* Options for the bad block table descriptors */
61 /* The bad block table is in the last good block of the device */
[all …]
/Linux-v5.4/net/ceph/
Ddecode.c17 goto bad; in ceph_decode_entity_addr_versioned()
22 ceph_decode_copy_safe(p, end, &addr->type, sizeof(addr->type), bad); in ceph_decode_entity_addr_versioned()
24 ceph_decode_copy_safe(p, end, &addr->nonce, sizeof(addr->nonce), bad); in ceph_decode_entity_addr_versioned()
26 ceph_decode_32_safe(p, end, addr_len, bad); in ceph_decode_entity_addr_versioned()
28 goto bad; in ceph_decode_entity_addr_versioned()
32 ceph_decode_copy_safe(p, end, &addr->in_addr, addr_len, bad); in ceph_decode_entity_addr_versioned()
41 bad: in ceph_decode_entity_addr_versioned()
52 ceph_decode_skip_n(p, end, 3, bad); in ceph_decode_entity_addr_legacy()
59 ceph_decode_copy_safe(p, end, &addr->nonce, sizeof(addr->nonce), bad); in ceph_decode_entity_addr_legacy()
62 sizeof(addr->in_addr), bad); in ceph_decode_entity_addr_legacy()
[all …]
/Linux-v5.4/drivers/mtd/nand/raw/
Dnand_bbt.c4 * Bad block table support for the NAND driver
10 * When nand_scan_bbt is called, then it tries to find the bad block table
13 * marked good / bad blocks. This information is used to create a memory BBT.
14 * Once a new bad block is discovered then the "factory" information is updated
21 * If the tables are not versioned, then we "or" the bad block information.
24 * good / bad blocks and the bad block tables are created.
29 * The auto generated bad block table is located in the last good blocks
40 * 00b: block is factory marked bad
41 * 01b, 10b: block is marked bad due to wear
43 * The memory bad block table uses the following scheme:
[all …]
/Linux-v5.4/tools/testing/ktest/examples/include/
Dbisect.conf23 # You must set the commit that was considered bad (git bisect bad)
28 # that requires to run a test to know if the bisect was good or bad.
29 # The test should exit with 0 on good, non-zero for bad. But see
33 # It is usually a good idea to confirm that the GOOD and the BAD
34 # commits are truly good and bad respectively. Having BISECT_CHECK
35 # set to 1 will check both that the good commit works and the bad
37 # set BISECT_CHECK to 'good' or to 'bad'.
40 #BISECT_CHECK = bad
66 # if the commit was good or bad. Instead, it will ask you to tell
76 # Currently (which hopefully will be fixed soon), the bad config
[all …]
/Linux-v5.4/fs/ceph/
Dmdsmap.c45 #define __decode_and_drop_type(p, end, type, bad) \ argument
48 goto bad; \
52 #define __decode_and_drop_set(p, end, type, bad) \ argument
56 ceph_decode_32_safe(p, end, n, bad); \
58 ceph_decode_need(p, end, need, bad); \
62 #define __decode_and_drop_map(p, end, ktype, vtype, bad) \ argument
66 ceph_decode_32_safe(p, end, n, bad); \
68 ceph_decode_need(p, end, need, bad); \
79 ceph_decode_need(p, end, sizeof(u64) + sizeof(u32), bad); in __decode_and_drop_compat_set()
87 bad); in __decode_and_drop_compat_set()
[all …]
/Linux-v5.4/arch/mips/include/asm/sn/
Dfru.h20 confidence_t km_confidence; /* confidence level that the memory is bad
24 /* confidence level that dimm[i] is bad
31 confidence_t kc_confidence; /* confidence level that cpu is bad */
32 confidence_t kc_icache; /* confidence level that instr. cache is bad */
33 confidence_t kc_dcache; /* confidence level that data cache is bad */
34 confidence_t kc_scache; /* confidence level that sec. cache is bad */
35 confidence_t kc_sysbus; /* confidence level that sysad/cmd/state bus is bad */
39 confidence_t kpb_belief; /* confidence level that the pci bus is bad */
41 /* confidence level that the pci dev is bad */
/Linux-v5.4/Documentation/driver-api/
Dmtdnand.rst422 use bad block tables on FLASH, because the ECC layout is interfering
423 with the bad block marker positions. See bad block table support for
426 Bad block table support
429 Most NAND chips mark the bad blocks at a defined position in the spare
430 area. Those blocks must not be erased under any circumstances as the bad
431 block information would be lost. It is possible to check the bad block
433 the first page in the block. This is time consuming so a bad block table
436 The nand driver supports various types of bad block tables.
440 The bad block table contains all bad block information of the device
445 A bad block table is used per chip and contains the bad block
[all …]
/Linux-v5.4/drivers/mtd/ubi/
Dio.c106 * that this eraseblock may become bad soon (but do not have to);
217 * bad.
305 * %-EIO is returned, the physical eraseblock most probably went bad.
355 * torture_peb - test a supposedly bad physical eraseblock.
412 ubi_msg(ubi, "PEB %d passed torture test, do not mark it as bad", pnum); in torture_peb()
422 ubi_err(ubi, "read problems on freshly erased PEB %d, must be bad", in torture_peb()
521 * eraseblock is bad.
558 * ubi_io_is_bad - check if a physical eraseblock is bad.
562 * This function returns a positive number if the physical eraseblock is bad,
576 ubi_err(ubi, "error %d while checking if PEB %d is bad", in ubi_io_is_bad()
[all …]
DKconfig8 flash chips like wear and bad blocks and provides some other useful
32 int "Maximum expected bad eraseblock count per 1024 eraseblocks"
36 This option specifies the maximum bad physical eraseblocks UBI
38 flash does not admit of bad eraseblocks (e.g. NOR flash), this value
43 expected bad eraseblocks per 1024 eraseblocks then can be calculated
48 about 1.9% of physical eraseblocks for bad blocks handling. And that
51 flash chip admits maximum 40 bad eraseblocks, and it is split on two
98 UBI driver will transparently handle things like bad eraseblocks and
/Linux-v5.4/tools/testing/selftests/x86/
Dtest_FCOMI.c75 printf("[BAD]\tfcomi_1_pi with flags:%lx\n", flags); in test()
79 printf("[BAD]\tfcomi_pi_1 with flags:%lx->%lx\n", flags, res_fcomi_pi_1 & ARITH); in test()
83 printf("[BAD]\tfcomi_1_1 with flags:%lx\n", flags); in test()
87 printf("[BAD]\tFE_INVALID is set in %s\n", __func__); in test()
112 printf("[BAD]\tfcomi_qnan_1 with flags:%lx\n", flags); in test_qnan()
116 printf("[BAD]\tFE_INVALID is not set in %s\n", __func__); in test_qnan()
141 printf("[BAD]\tfcomi_qnan_1 with flags:%lx\n", flags); in testu_qnan()
145 printf("[BAD]\tFE_INVALID is set in %s\n", __func__); in testu_qnan()
172 printf("[BAD]\tfcomi_qnan_1 with flags:%lx\n", flags); in testu_snan()
177 printf("[BAD]\tFE_INVALID is not set in %s\n", __func__); in testu_snan()
[all …]
Dtest_FISTTP.c36 printf("[BAD]\tfisttp 1\n"); in test()
41 printf("[BAD]\tfisttp 1: wrong exception state\n"); in test()
56 printf("[BAD]\tfisttp pi\n"); in test()
61 printf("[BAD]\tfisttp pi: wrong exception state\n"); in test()
79 printf("[BAD]\tfisttp -pi\n"); in test()
84 printf("[BAD]\tfisttp -pi: wrong exception state\n"); in test()
100 printf("[BAD]\tfisttp ln2\n"); in test()
105 printf("[BAD]\tfisttp ln2: wrong exception state\n"); in test()
/Linux-v5.4/drivers/misc/lkdtm/
Drefcount.c43 pr_info("attempting bad refcount_inc() overflow\n"); in lkdtm_REFCOUNT_INC_OVERFLOW()
62 pr_info("attempting bad refcount_add() overflow\n"); in lkdtm_REFCOUNT_ADD_OVERFLOW()
73 pr_info("attempting bad refcount_inc_not_zero() overflow\n"); in lkdtm_REFCOUNT_INC_NOT_ZERO_OVERFLOW()
85 pr_info("attempting bad refcount_add_not_zero() overflow\n"); in lkdtm_REFCOUNT_ADD_NOT_ZERO_OVERFLOW()
121 pr_info("attempting bad refcount_dec() to zero\n"); in lkdtm_REFCOUNT_DEC_ZERO()
157 pr_info("attempting bad refcount_dec() below zero\n"); in lkdtm_REFCOUNT_DEC_NEGATIVE()
171 pr_info("attempting bad refcount_dec_and_test() below zero\n"); in lkdtm_REFCOUNT_DEC_AND_TEST_NEGATIVE()
186 pr_info("attempting bad refcount_sub_and_test() below zero\n"); in lkdtm_REFCOUNT_SUB_AND_TEST_NEGATIVE()
230 pr_info("attempting bad refcount_inc() from zero\n"); in lkdtm_REFCOUNT_INC_ZERO()
255 pr_info("attempting bad refcount_add() from zero\n"); in lkdtm_REFCOUNT_ADD_ZERO()
[all …]
Dperms.c58 pr_info("attempting bad execution at %px\n", func); in execute_location()
76 pr_info("attempting bad execution at %px\n", func); in execute_user_location()
85 pr_info("attempting bad rodata write at %px\n", ptr); in lkdtm_WRITE_RO()
103 pr_info("attempting bad ro_after_init write at %px\n", ptr); in lkdtm_WRITE_RO_AFTER_INIT()
115 pr_info("attempting bad %zu byte write at %px\n", size, ptr); in lkdtm_WRITE_KERN()
193 pr_info("attempting bad read at %px\n", ptr); in lkdtm_ACCESS_USERSPACE()
197 pr_info("attempting bad write at %px\n", ptr); in lkdtm_ACCESS_USERSPACE()
208 pr_info("attempting bad read at %px\n", ptr); in lkdtm_ACCESS_NULL()
212 pr_info("attempting bad write at %px\n", ptr); in lkdtm_ACCESS_NULL()
/Linux-v5.4/block/
Dbadblocks.c3 * Bad block management
20 * badblocks_check() - check a given range for bad sectors
27 * We can record which blocks on each device are 'bad' and so just
29 * Entries in the bad-block table are 64bits wide. This comprises:
30 * Length of bad-range, in sectors: 0-511 for lengths 1-512
31 * Start of bad-range, sector offset, 54 bits (allows 8 exbibytes)
36 * Locking of the bad-block table uses a seqlock so badblocks_check
38 * We will sometimes want to check for bad blocks in a bi_end_io function,
41 * When looking for a bad block we specify a range and want to
42 * know if any block in the range is bad. So we binary-search
[all …]
/Linux-v5.4/Documentation/admin-guide/
Dbug-bisect.rst41 $ git bisect bad [commit]
54 $ git bisect bad
60 - For example, if you know that the current version is bad, and version
64 $ git bisect bad # Current version is bad
68 .. [#f1] You can, optionally, provide both good and bad arguments at git
69 start with ``git bisect start [BAD] [GOOD]``
/Linux-v5.4/tools/testing/selftests/bpf/verifier/
Dxdp_direct_packet_access.c2 "XDP pkt read, pkt_end mangling, bad access 1",
20 "XDP pkt read, pkt_end mangling, bad access 2",
55 "XDP pkt read, pkt_data' > pkt_end, bad access 1",
73 "XDP pkt read, pkt_data' > pkt_end, bad access 2",
109 "XDP pkt read, pkt_end > pkt_data', bad access 1",
128 "XDP pkt read, pkt_end > pkt_data', bad access 2",
164 "XDP pkt read, pkt_data' < pkt_end, bad access 1",
183 "XDP pkt read, pkt_data' < pkt_end, bad access 2",
218 "XDP pkt read, pkt_end < pkt_data', bad access 1",
236 "XDP pkt read, pkt_end < pkt_data', bad access 2",
[all …]
/Linux-v5.4/drivers/gpu/drm/radeon/
Devergreen_cs.c1145 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1157 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1164 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1174 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1216 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1228 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1240 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1252 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1275 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
1313 dev_warn(p->dev, "bad SET_CONTEXT_REG " in evergreen_cs_handle_reg()
[all …]
Dr600_cs.c445 /* the initial DDX does bad things with the CB size occasionally */ in r600_cs_track_validate_cb()
447 /* r600c,g also seem to flush at bad times in some apps resulting in in r600_cs_track_validate_cb()
868 DRM_ERROR("vline WAIT_REG_MEM bad reg\n"); in r600_cs_common_vline_parse()
873 DRM_ERROR("vline WAIT_REG_MEM bad bit mask\n"); in r600_cs_common_vline_parse()
1019 dev_warn(p->dev, "bad SET_CONTEXT_REG " in r600_cs_check_reg()
1037 dev_warn(p->dev, "bad SET_CONTEXT_REG " in r600_cs_check_reg()
1079 dev_warn(p->dev, "bad SET_CONTEXT_REG " in r600_cs_check_reg()
1138 dev_err(p->dev, "bad SET_CONTEXT_REG 0x%04X\n", reg); in r600_cs_check_reg()
1210 dev_err(p->dev, "bad SET_CONTEXT_REG 0x%04X\n", reg); in r600_cs_check_reg()
1241 dev_err(p->dev, "bad SET_CONTEXT_REG 0x%04X\n", reg); in r600_cs_check_reg()
[all …]
/Linux-v5.4/tools/testing/selftests/kvm/s390x/
Dmemop.c86 /* Check error conditions - first bad size: */ in main()
107 /* Bad flags: */ in main()
117 /* Bad operation: */ in main()
125 TEST_ASSERT(rv == -1 && errno == EINVAL, "ioctl allows bad operations"); in main()
127 /* Bad guest address: */ in main()
135 TEST_ASSERT(rv > 0, "ioctl does not report bad guest memory access"); in main()
137 /* Bad host address: */ in main()
146 "ioctl does not report bad host memory address"); in main()
148 /* Bad access register: */ in main()
/Linux-v5.4/drivers/tee/optee/
Drpc.c37 goto bad; in handle_rpc_func_cmd_get_time()
40 goto bad; in handle_rpc_func_cmd_get_time()
48 bad: in handle_rpc_func_cmd_get_time()
98 goto bad; in handle_rpc_func_cmd_wq()
102 goto bad; in handle_rpc_func_cmd_wq()
112 goto bad; in handle_rpc_func_cmd_wq()
117 bad: in handle_rpc_func_cmd_wq()
126 goto bad; in handle_rpc_func_cmd_wait()
130 goto bad; in handle_rpc_func_cmd_wait()
139 bad: in handle_rpc_func_cmd_wait()
[all …]
/Linux-v5.4/drivers/mtd/tests/
Dmtd_test.c36 pr_info("block %d is bad\n", ebnum); in is_block_bad()
44 int i, bad = 0; in mtdtest_scan_for_bad_eraseblocks() local
49 pr_info("scanning for bad eraseblocks\n"); in mtdtest_scan_for_bad_eraseblocks()
53 bad += 1; in mtdtest_scan_for_bad_eraseblocks()
56 pr_info("scanned %d eraseblocks, %d are bad\n", i, bad); in mtdtest_scan_for_bad_eraseblocks()

12345678910>>...111