| /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.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.
|
| 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 …]
|
| /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/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 …]
|
| H A D | switch.c | 83 struct spu_problem __iomem *prob = spu->problem; in check_spu_isolate()
203 struct spu_problem __iomem *prob = spu->problem; in save_spu_runcntl()
222 struct spu_problem __iomem *prob = spu->problem; in save_spu_status()
296 struct spu_problem __iomem *prob = spu->problem; in do_mfc_mssync()
368 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querymask()
379 struct spu_problem __iomem *prob = spu->problem; in save_ppu_querytype()
390 struct spu_problem __iomem *prob = spu->problem; in save_ppu_tagstatus()
503 struct spu_problem __iomem *prob = spu->problem; in save_spu_npc()
587 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb_stat()
597 struct spu_problem __iomem *prob = spu->problem; in save_ppu_mb()
[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/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/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/arch/powerpc/platforms/cell/ |
| H A D | spu_manage.c | 65 iounmap(spu->problem); in spu_unmap()
148 spu->problem = spu_map_prop_old(spu, node, "problem"); in spu_map_device_old()
149 if (!spu->problem) in spu_map_device_old()
227 ret = spu_map_resource(spu, 1, (void __iomem**)&spu->problem, in spu_map_device()
252 spu->problem_phys, spu->problem); in spu_map_device()
334 spu->local_store, spu->problem, spu->priv1, in of_create_spu()
|
| /openbmc/openbmc/poky/meta/recipes-core/coreutils/coreutils/ |
| H A D | 0001-local.mk-fix-cross-compiling-problem.patch | 4 Subject: [PATCH] local.mk: fix cross compiling problem
8 This patch fixes this problem.
|
| /openbmc/webui-vue/.github/ISSUE_TEMPLATE/ |
| H A D | feature_request.md | 9 **Is your feature request related to a problem? Please describe.** A clear and
10 concise description of what the problem is. Ex. I'm always frustrated when [...]
|
| H A D | bug_report.md | 21 **Screenshots** If applicable, add screenshots to help explain your problem.
36 **Additional context** Add any other context about the problem here.
|
| /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/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()
230 (unsigned long)spu->problem, (unsigned long)spu->local_store, in setup_areas()
|
| /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/Documentation/translations/zh_TW/ |
| H A D | IRQ.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/nis/ |
| H A D | nis.inc | 18 # a security problem (and this fix to the build problem is *much*
|
| /openbmc/linux/Documentation/translations/zh_CN/arch/arm64/ |
| H A D | tagged-pointers.txt | 4 original document maintainer directly. However, if you have a problem
7 or if there is a problem with the translation.
|
| /openbmc/qemu/target/ppc/ |
| H A D | power8-pmu-regs.c.inc | 17 * PMCs) has problem state read access.
34 * PMCs) has problem state write access.
60 * MMCR2 problem state write functions.
149 * problem state programs read/write access to MMCR2,
151 * not changed when mtspr is executed in problem state, and
152 * all other bits return 0s when mfspr is executed in problem
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-01 | 29 # But that is a problem, because this means that in order to determine
37 # obvious that an easy to solution to this problem should just be the removal
43 # CORE also consist of a solution to this recursive problem.
|
| /openbmc/linux/Documentation/translations/zh_TW/arch/arm64/ |
| H A D | tagged-pointers.txt | 6 original document maintainer directly. However, if you have a problem
9 or if there is a problem with the translation.
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | bug_report.md | 30 If applicable, add screenshots to help explain your problem.
38 Add any other context about the problem here.
|
| /openbmc/openbmc/poky/meta/recipes-sato/webkit/webkitgtk/ |
| H A D | bmalloc-fix.patch | 4 Subject: [PATCH] bmalloc: Build problem in bmalloc when X11/X.h is in the same
7 This avoids a build problem when the X11/X.h is included,
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 31 In the Linux kernel, one possible solution to this problem is to employ the
45 well, is being used in more and more drivers, the same problem of altering the
48 An additional problem with the device tree in U-Boot is that it is read-only,
52 this problem, it is a non-negligible task to implement it, an a interim
53 solution is needed to address the problem at least in the medium-term.
55 Hence, we propose a solution to this problem by offering a board-specific
|