| /linux-6.12.1/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues
9 Hardware issues which result in security problems are a different category
13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
17 issues, software mitigations can depend on microcode or firmware updates,
29 issues. Reports of pure software security bugs in the Linux kernel are not
46 While hardware security issues are often handled by the affected silicon
79 is aware of the sensitive nature of such issues and offers a Memorandum of
87 keep hardware security issues under embargo for coordination between
91 issues in the past and has the necessary mechanisms in place to allow
95 initial contact, which oversees the process of handling such issues under
[all …]
|
| D | cve.rst | 17 potential Linux kernel security issues. This assignment is independent
31 potentially security issues are identified by the developers responsible
47 security issues should be sent to this alias, it is ONLY for assignment
53 No CVEs will be automatically assigned for unfixed security issues in
118 assigned to all fixes for all issues, but sometimes we will fail to
|
| D | stable-api-nonsense.rst | 45 First off, I'm not going to address **any** legal issues about closed
50 the technical issues here (not to make light of the legal issues, they
84 Now a number of these issues can be addressed by simply compiling your
120 issues:
146 Security issues are also very important for Linux. When a
|
| D | maintainer-soc-clean-dts.rst | 19 results of issues in an included DTSI file, are considered existing, not new
24 issues shall be fixed in reasonable time (e.g. within one release) or the
|
| D | stable-kernel-rules.rst | 21 - Serious issues as reported by a user of a distribution kernel may also
189 members object to the patch, bringing up issues that the maintainers and
194 issues, some patches may be modified or dropped or additional patches may
196 issues are found.
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | reporting-issues.rst | 4 Reporting issues
40 If you are facing multiple issues with the Linux kernel at once, report each
51 Step-by-step guide how to report issues to the kernel maintainers
54 The above TL;DR outlines roughly how to report issues to the Linux kernel
56 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For
72 will often be needed anyway to hunt down and fix issues.
80 issue, or a really severe problem: those are 'issues of high priority' that
96 issues at once, create separate notes for each of them and make sure they
107 time this won't be bugzilla.kernel.org, as issues typically need to be sent
129 up there, scroll down to the instructions for issues only happening with
[all …]
|
| D | reporting-regressions.rst | 24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
57 behavior with a newer kernel version; such issues can be caused by changes in
77 Documentation/admin-guide/reporting-issues.rst, it already describes the
146 a lot of issues only occur in a particular environment outside the developer's
158 Documentation/admin-guide/reporting-issues.rst and described in more detail by
184 issues, or other problematic aspects already fixed in later versions
254 In extremely rare situations security issues can't be fixed without causing
258 issues without causing regressions.
389 What kind of issues are supposed to be tracked by regzbot?
393 regular issues. But it's okay for the Linux kernel's regression tracker if you
[all …]
|
| /linux-6.12.1/Documentation/gpu/amdgpu/display/ |
| D | display-contributing.rst | 10 This page summarizes some of the issues you can help with; keep in mind that
16 Gitlab issues
19 Users can report issues associated with AMD GPUs at:
24 filter issues. If you can reproduce any problem, you could help by adding more
50 issues on the display side.
54 Fix compilation issues when using um architecture
59 from the test perspective. We currently have some compilation issues in this
|
| /linux-6.12.1/drivers/media/pci/tw5864/ |
| D | tw5864-core.c | 33 * BEWARE OF KNOWN ISSUES WITH VIDEO QUALITY
43 * There is a workaround for both issues: avoid P-frames by setting GOP size
48 * These issues are not decoding errors; all produced H.264 streams are decoded
50 * analog-to-digital conversion issues nor internal memory errors; we conclude
51 * it's internal H.264 encoder issues.
53 * worked properly at all in our development environment. So these issues may
299 dev_info(&pci_dev->dev, "Note: there are known video quality issues. For details\n"); in tw5864_initdev()
|
| /linux-6.12.1/tools/testing/selftests/rseq/ |
| D | compiler.h | 21 * https://github.com/llvm/llvm-project/issues/52735
23 * Work around these issues by adding a volatile inline asm with
26 * issues are found in the future.
|
| /linux-6.12.1/drivers/gpu/drm/xe/ |
| D | Kconfig.debug | 27 performance but will catch some internal issues.
81 Choose this option when debugging guc issues.
82 Buffer should be large enough for complex issues.
|
| /linux-6.12.1/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 67 performance but will catch some internal issues.
160 performance but will catch some internal issues.
172 performance but will catch some internal issues.
185 performance but will help resolve GuC related issues.
|
| /linux-6.12.1/Documentation/usb/ |
| D | ehci.rst | 51 used on PPC hardware so big/little endianness issues should be gone.
53 systems with interesting DMA mapping issues.
84 There are some issues with power management; suspend/resume doesn't
156 but aggregate throughput is also affected by issues like delays between
224 Interrupt and ISO transfer performance issues. Those periodic
|
| /linux-6.12.1/tools/perf/tests/shell/ |
| D | stat_all_metrics.sh | 33 echo "Skip, not fail, for FP issues"
36 echo "Skip, not fail, for Optane memory issues"
|
| /linux-6.12.1/drivers/gpu/drm/amd/display/ |
| D | Kconfig | 12 # !CC_IS_CLANG: https://github.com/ClangBuiltLinux/linux/issues/1752
23 has been resolved: https://github.com/llvm/llvm-project/issues/41896.
|
| /linux-6.12.1/drivers/gpu/drm/panfrost/ |
| D | panfrost_gpu.c | 182 u64 issues; member
185 u64 issues; member
194 .issues = hw_issues_##_name, \
201 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \
312 hw_issues |= model->issues; in panfrost_gpu_init_features()
322 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
332 dev_info(pfdev->dev, "features: %64pb, issues: %64pb", in panfrost_gpu_init_features()
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | testing-overview.rst | 89 detect classes of issues when they occur in a running kernel. These typically
91 concurrency issues such as data races, or other undefined behaviour like
103 * KFENCE is a low-overhead detector of memory issues, which is much faster than
137 etc. Smatch also has tests against more serious issues such as integer
|
| /linux-6.12.1/Documentation/kbuild/ |
| D | llvm.rst | 141 will build or work without any issues. Below is a general summary of
145 it or there are known issues. Using the latest stable version of LLVM or
195 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_
199 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
|
| /linux-6.12.1/Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 38 WDT0 is triggered it issues hard reset for SoC.
59 WDT0 or WDT2 is triggered it issues soft reset for SoC.
|
| /linux-6.12.1/fs/xfs/libxfs/ |
| D | xfs_health.h | 56 /* Observable health issues for metadata spanning the entire filesystem. */
64 /* Observable health issues for realtime volume metadata. */
68 /* Observable health issues for AG metadata. */
81 /* Observable health issues for inode metadata. */
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/intel/ |
| D | ixgbevf.rst | 14 - Known Issues
41 Known Issues/Troubleshooting
|
| D | fm10k.rst | 15 - Known Issues
85 each jumbo packet. This should help to avoid buffer starvation issues when
120 Known Issues/Troubleshooting
|
| /linux-6.12.1/Documentation/dev-tools/kunit/ |
| D | faq.rst | 80 3. Running the UML kernel directly can often reveal issues or error messages,
84 filesystem mounted), and has had issues in the past when built statically and
103 If none of the above tricks help, you are always welcome to email any issues to
|
| /linux-6.12.1/include/asm-generic/ |
| D | bug.h | 76 * significant kernel issues that need prompt attention if they should ever
82 * These macros should be used for recoverable kernel issues only.
86 * conditions distinguishable from kernel issues.
|
| /linux-6.12.1/arch/arm/mm/ |
| D | fault-armv.c | 49 * fault (ie, is old), we can safely ignore any issues. in do_adjust_pte()
179 * an object, we need to deal with the cache aliasing issues.
215 * issues. If it has, we need to avoid them for the case where
|