Home
last modified time | relevance | path

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

12345678910>>...186

/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/Documentation/admin-guide/device-mapper/
Ddm-dust.rst4 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 …]
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-dust.rst4 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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/drivers/nvme/host/
Dfc.h110 "Bad CR_ASSOC Length",
111 "Bad CR_ASSOC Rqst Length",
113 "Bad CR_ASSOC Cmd Length",
114 "Bad Ersp Ratio",
117 "Bad CR_CONN Length",
118 "Bad CR_CONN Rqst Length",
120 "Bad Association ID Length",
123 "Bad Connection ID Length",
126 "Bad CR_CONN Cmd Length",
127 "Bad DISCONN Length",
[all …]
/kernel/linux/linux-6.6/drivers/nvme/host/
Dfc.h110 "Bad CR_ASSOC Length",
111 "Bad CR_ASSOC Rqst Length",
113 "Bad CR_ASSOC Cmd Length",
114 "Bad Ersp Ratio",
117 "Bad CR_CONN Length",
118 "Bad CR_CONN Rqst Length",
120 "Bad Association ID Length",
123 "Bad Connection ID Length",
126 "Bad CR_CONN Cmd Length",
127 "Bad DISCONN Length",
[all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 * @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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/fs/ceph/
Dmdsmap.c57 #define __decode_and_drop_type(p, end, type, bad) \ argument
60 goto bad; \
64 #define __decode_and_drop_set(p, end, type, bad) \ argument
68 ceph_decode_32_safe(p, end, n, bad); \
70 ceph_decode_need(p, end, need, bad); \
74 #define __decode_and_drop_map(p, end, ktype, vtype, bad) \ argument
78 ceph_decode_32_safe(p, end, n, bad); \
80 ceph_decode_need(p, end, need, bad); \
91 ceph_decode_need(p, end, sizeof(u64) + sizeof(u32), bad); in __decode_and_drop_compat_set()
99 bad); in __decode_and_drop_compat_set()
[all …]
/kernel/linux/linux-6.6/drivers/tee/optee/
Drpc.c20 goto bad; in handle_rpc_func_cmd_get_time()
23 goto bad; in handle_rpc_func_cmd_get_time()
31 bad: in handle_rpc_func_cmd_get_time()
66 goto bad; in handle_rpc_func_cmd_i2c_transfer()
70 goto bad; in handle_rpc_func_cmd_i2c_transfer()
75 goto bad; in handle_rpc_func_cmd_i2c_transfer()
81 goto bad; in handle_rpc_func_cmd_i2c_transfer()
99 goto bad; in handle_rpc_func_cmd_i2c_transfer()
118 bad: in handle_rpc_func_cmd_i2c_transfer()
134 goto bad; in handle_rpc_func_cmd_wq()
[all …]
/kernel/linux/linux-5.10/drivers/misc/lkdtm/
Dperms.c58 pr_info("attempting bad execution at %px\n", func); in execute_location()
77 pr_info("attempting bad execution at %px\n", func); in execute_user_location()
87 pr_info("attempting bad rodata write at %px\n", ptr); in lkdtm_WRITE_RO()
89 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_RO()
106 pr_info("attempting bad ro_after_init write at %px\n", ptr); in lkdtm_WRITE_RO_AFTER_INIT()
108 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_RO_AFTER_INIT()
119 pr_info("attempting bad %zu byte write at %px\n", size, ptr); in lkdtm_WRITE_KERN()
122 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_KERN()
198 pr_info("attempting bad read at %px\n", ptr); in lkdtm_ACCESS_USERSPACE()
201 pr_err("FAIL: survived bad read\n"); in lkdtm_ACCESS_USERSPACE()
[all …]
/kernel/linux/linux-5.10/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 */
/kernel/linux/linux-6.6/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 */
/kernel/linux/linux-6.6/drivers/misc/lkdtm/
Dperms.c84 pr_info("attempting bad execution at %px\n", dst); in execute_location()
106 pr_info("attempting bad execution at %px\n", dst); in execute_user_location()
117 pr_info("attempting bad rodata write at %px\n", ptr); in lkdtm_WRITE_RO()
119 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_RO()
136 pr_info("attempting bad ro_after_init write at %px\n", ptr); in lkdtm_WRITE_RO_AFTER_INIT()
138 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_RO_AFTER_INIT()
150 pr_info("attempting bad %zu byte write at %px\n", size, ptr); in lkdtm_WRITE_KERN()
153 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_KERN()
167 pr_info("attempting bad %zu bytes write at %px\n", size, do_nothing); in lkdtm_WRITE_OPD()
169 pr_err("FAIL: survived bad write\n"); in lkdtm_WRITE_OPD()
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/
Dmtdnand.rst424 use bad block tables on FLASH, because the ECC layout is interfering
425 with the bad block marker positions. See bad block table support for
428 Bad block table support
431 Most NAND chips mark the bad blocks at a defined position in the spare
432 area. Those blocks must not be erased under any circumstances as the bad
433 block information would be lost. It is possible to check the bad block
435 the first page in the block. This is time consuming so a bad block table
438 The nand driver supports various types of bad block tables.
442 The bad block table contains all bad block information of the device
447 A bad block table is used per chip and contains the bad block
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/
Dmtdnand.rst424 use bad block tables on FLASH, because the ECC layout is interfering
425 with the bad block marker positions. See bad block table support for
428 Bad block table support
431 Most NAND chips mark the bad blocks at a defined position in the spare
432 area. Those blocks must not be erased under any circumstances as the bad
433 block information would be lost. It is possible to check the bad block
435 the first page in the block. This is time consuming so a bad block table
438 The nand driver supports various types of bad block tables.
442 The bad block table contains all bad block information of the device
447 A bad block table is used per chip and contains the bad block
[all …]

12345678910>>...186