| /openbmc/docs/security/ |
| H A D | how-to-report-a-security-vulnerability.md | 4 give the project time to address the problem before public disclosure.
8 - You have information about a security problem or vulnerability which is not
10 - You want the problem fixed before public disclosure and you are willing to
12 - You understand the problem will eventually be publicly disclosed.
20 not, the security response team will help route the problem.
21 - Include details about the security problem such as:
22 - The version and configuration of OpenBMC the problem appears in.
23 - How to reproduce the problem.
25 - As the problem reporter, you will be included in the problem response.
29 the security response team can help you route the problem.
[all …]
|
| H A D | obmc-security-response-team-guidelines.md | 19 1. Handle new problem reports.
24 problem is known.
26 2. Analyze the problem and engage collaborators as needed (upstream, downstream,
29 - Determine if the problem is new or known.
30 - Determine if the problem is in OpenBMC.
31 - If the problem is in a project that OpenBMC uses, re-route the problem to
33 - Note that the problem may be in a customized version of OpenBMC but not
35 - Determine which OpenBMC areas should address the problem.
39 - Please describe when the problem was introduced to help users learn if
42 problem in the original code through OpenBMC release 2.9, the affected
[all …]
|
| H A D | obmc-security-response-team.md | 16 1. A community member reports a problem privately to the security response team
19 maintainers, and the problem submitter) work to understand the problem.
21 explains the problem, its severity, and how to protect your systems that
37 communication vehicle between the person who reported the problem and the
44 working to fix the problem.
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 6 give the project time to address the problem before public disclosure.
10 - You have information about a security problem which is not yet publicly
12 - You want the problem fixed before public disclosure and you are willing to
14 - You understand the problem will eventually be publicly disclosed.
19 security problem such as:
20 - the version and configuration of OpenBMC the problem appears in
21 - how to reproduce the problem
23 - As the problem reporter, you will be included in the email thread for the
24 problem.
27 the problem. Activities may include:
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z10/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
62 "BriefDescription": "Problem-State Level-1 I-Cache Directory Write Count",
63 …level-1 instruction-cache or unified-cache directory writes while the CPU is in the problem state."
70 …nalty cycles for level-1 instruction cache or unified cache while the CPU is in the problem state."
76 "BriefDescription": "Problem-State Level-1 D-Cache Directory Write Count",
77 …nts the total number of level-1 data-cache directory writes while the CPU is in the problem state."
83 "BriefDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count",
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z13/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
62 "BriefDescription": "Problem-State Level-1 I-Cache Directory Write Count",
63 …level-1 instruction-cache or unified-cache directory writes while the CPU is in the problem state."
70 …nalty cycles for level-1 instruction cache or unified cache while the CPU is in the problem state."
76 "BriefDescription": "Problem-State Level-1 D-Cache Directory Write Count",
77 …nts the total number of level-1 data-cache directory writes while the CPU is in the problem state."
83 "BriefDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count",
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z196/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
62 "BriefDescription": "Problem-State Level-1 I-Cache Directory Write Count",
63 …level-1 instruction-cache or unified-cache directory writes while the CPU is in the problem state."
70 …nalty cycles for level-1 instruction cache or unified cache while the CPU is in the problem state."
76 "BriefDescription": "Problem-State Level-1 D-Cache Directory Write Count",
77 …nts the total number of level-1 data-cache directory writes while the CPU is in the problem state."
83 "BriefDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count",
[all …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_zec12/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
62 "BriefDescription": "Problem-State Level-1 I-Cache Directory Write Count",
63 …level-1 instruction-cache or unified-cache directory writes while the CPU is in the problem state."
70 …nalty cycles for level-1 instruction cache or unified cache while the CPU is in the problem state."
76 "BriefDescription": "Problem-State Level-1 D-Cache Directory Write Count",
77 …nts the total number of level-1 data-cache directory writes while the CPU is in the problem state."
83 "BriefDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count",
[all …]
|
| /openbmc/linux/arch/powerpc/platforms/cell/spufs/ |
| H A D | hw_ops.c | 27 struct spu_problem __iomem *prob = spu->problem; in spu_hw_mbox_read()
43 return in_be32(&ctx->spu->problem->mb_stat_R); in spu_hw_mbox_stat_read()
53 stat = in_be32(&spu->problem->mb_stat_R); in spu_hw_mbox_stat_poll()
85 struct spu_problem __iomem *prob = spu->problem; in spu_hw_ibox_read()
106 struct spu_problem __iomem *prob = spu->problem; in spu_hw_wbox_write()
126 out_be32(&ctx->spu->problem->signal_notify1, data); in spu_hw_signal1_write()
131 out_be32(&ctx->spu->problem->signal_notify2, data); in spu_hw_signal2_write()
178 return in_be32(&ctx->spu->problem->spu_npc_RW); in spu_hw_npc_read()
183 out_be32(&ctx->spu->problem->spu_npc_RW, val); in spu_hw_npc_write()
188 return in_be32(&ctx->spu->problem->spu_status_R); in spu_hw_status_read()
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 13 Specifying the problem
17 clear description of the problem to be solved. In some cases, this step is
19 example. In others, though, it is tempting to confuse the real problem
31 immediate problem. To the wider kernel community, though, it was seen as a
53 the right solution to the problem than they were with a specific module.
54 The moral of the story is to focus on the problem - not a specific solution
61 - What, exactly, is the problem which needs to be solved?
63 - Who are the users affected by this problem? Which use cases should the
66 - How does the kernel fall short in addressing that problem now?
78 - It may well be that the problem is addressed by the kernel in ways which
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 13 sysadmin, start recovery) when a file system problem is detected.
16 for a monitoring tool to know a problem in the file system has happened.
20 early file system problem detection and reporting recovery tools.
25 problem. For this reason, FAN_FS_ERROR tries to report only the first
53 agnostic tool to learn about a problem in the file system, without
54 providing any additional details about the problem. This record is
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | fabric_message_registry.hpp | 89 "Contact the network administrator for problem resolution.",
180 "Contact the network administrator for problem resolution.",
193 "Contact the network administrator for problem resolution.",
206 "Contact the network administrator for problem resolution.",
219 "Contact the network administrator for problem resolution.",
247 "Contact the network administrator for problem resolution.",
299 "Contact the network administrator for problem resolution.",
327 "Contact the network administrator for problem resolution.",
419 "Contact the network administrator for problem resolution.",
432 "Contact the network administrator for problem resolution.",
[all …]
|
| /openbmc/linux/scripts/tracing/ |
| H A D | ftrace-bisect.sh | 12 # (note, if this is a problem with function_graph tracing, then simply
75 # Eventually, if you did this correctly, you will get down to the problem
78 # The way to figure out if the problem function is bad, just do:
80 # # echo <problem-function> > set_ftrace_notrace
86 # If it does crash, do this again (there's more than one problem function)
87 # but you need to echo the problem function(s) into set_ftrace_notrace before
89 # kernel, annotate the problem functions with "notrace" and start again.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | debug-objects.rst | 78 problem before the real initialization of the object happens. E.g. it
101 problem before the real initialization of the object happens. E.g. it
125 problem before the real activation of the object happens. E.g. it can
164 provided by the caller. The fixup function can correct the problem
180 fixup function can correct the problem before the real free of the
196 fixup function can correct the problem by calling debug_object_init
213 This function is called from the debug code whenever a problem in
231 This function is called from the debug code whenever a problem in
259 This function is called from the debug code whenever a problem in
272 This function is called from the debug code whenever a problem in
[all …]
|
| /openbmc/linux/fs/afs/ |
| H A D | addr_list.c | 72 const char *problem; in afs_parse_text_addrs() local
90 problem = "nul"; in afs_parse_text_addrs()
99 problem = "brace1"; in afs_parse_text_addrs()
104 problem = "brace2"; in afs_parse_text_addrs()
160 problem = "family"; in afs_parse_text_addrs()
166 problem = "nostop"; in afs_parse_text_addrs()
179 problem = "port"; in afs_parse_text_addrs()
186 problem = "pval"; in afs_parse_text_addrs()
194 problem = "weird"; in afs_parse_text_addrs()
212 problem, p - text, (int)len, (int)len, text); in afs_parse_text_addrs()
[all …]
|
| /openbmc/docs/designs/ |
| H A D | design-template.md | 11 - The focus of the document is to define the problem we need to solve and
59 ## Problem Description
61 (1 paragraph) What are we doing and why? What problem are you trying to solve?
79 (2-5 paragraphs) What are the constraints for the problem you are trying to
82 the details you know about the problem space, so they can help review your
90 have alternative solutions to a problem, list them concisely in a bullet list.
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/3com/ |
| H A D | vortex.rst | 209 decision. If you think that Tx checksums are causing a problem, you
228 "Variables to work-around the Compaq PCI BIOS32 problem"....
331 On a side note, adding HAS_NWAY seems to share a problem with the
346 If autonegotiation is a problem, you may need to specify "speed
356 Maintainers find that accurate and complete problem reports are
359 the bottom of the problem.
361 If you believe you have a driver problem here are some of the
364 - Is it really a driver problem?
370 - OK, it's a driver problem.
377 problem. If it's a kernel crash then you should refer to
[all …]
|
| /openbmc/linux/Documentation/networking/device_drivers/fddi/ |
| H A D | skfp.rst | 90 Problem:
102 is not there, then you may have a hardware problem or PCI
110 Some COMPAQ machines have a problem with PCI under
115 Problem:
122 forwarding or there is a problem with the routing table
126 If your problem is not listed here, please contact our
252 document for details about this problem.
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z16/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z14/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
|
| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z15/ |
| H A D | basic.json | 48 "BriefDescription": "Problem-State Cycle Count",
49 …his counter counts the total number of CPU cycles when the CPU is in the problem state, excluding …
55 "BriefDescription": "Problem-State Instruction Count",
56 …is counter counts the total number of instructions executed by the CPU while in the problem state."
|
| /openbmc/qemu/.gitlab/issue_templates/ |
| H A D | bug.md | 5 to reproduce the problem with the latest qemu.git master built from
28 Give the smallest, complete command line that exhibits the problem.
43 ## Description of problem
44 <!-- Describe the problem, including any error/crash messages seen. -->
|
| /openbmc/linux/Documentation/power/ |
| H A D | basic-pm-debugging.rst | 112 that there is a problem with the tasks freezer subsystem that should be
128 make sure to report the problem with the driver.
136 If the "platform" test fails, there is a problem with the handling of the
142 work (of course, this only may be an issue on SMP systems) and the problem
149 the problem is most probably hardware-related and serious, so it should be
154 indicates a serious problem that very well may be related to the hardware, but
163 probably is a problem with a driver statically compiled into the kernel and you
165 individually. Otherwise, there is a problem with a modular driver and you can
175 before hibernation, and please report the problem with it(them).
209 techniques to find the problem. First, if there is a serial port in your box,
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/alsa-equal/alsa-equal/ |
| H A D | 0003-Fix-mixer.patch | 31 SNDERR("Problem with control file %s, %d.", controls, index);
41 SNDERR("Problem with control file %s.", controls);
48 SNDERR("Problem with control file %s.", controls);
81 SNDERR("Problem with control file %s.", controls);
88 SNDERR("Problem with control file %s.", controls);
|
| /openbmc/linux/arch/powerpc/platforms/ps3/ |
| H A D | spu.c | 124 unsigned long problem, unsigned long ls, unsigned long shadow, in _dump_areas() argument
129 pr_debug("%s:%d: problem: %lxh\n", func, line, problem); in _dump_areas()
178 iounmap(spu->problem); in spu_unmap()
210 spu->problem = ioremap(spu->problem_phys, in setup_areas()
213 if (!spu->problem) { in setup_areas()
214 pr_debug("%s:%d: ioremap problem failed\n", __func__, __LINE__); in setup_areas()
230 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
433 * for incorrect access to the spu problem state when the spu context is
435 * context that would inhibit mapping problem state pages, and a routine
436 * to unmap spu problem state pages. When the spu is enabled with
[all …]
|