| /Linux-v5.15/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
16 hardware vendors and other parties. For some of the issues, software
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 hardware
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 | 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 | stable-kernel-rules.rst | 18 - Serious issues as reported by a user of a distribution kernel may also
25 - No "theoretical race condition" issues, unless an explanation of how the
152 members object to the patch, bringing up issues that the maintainers and
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | reporting-issues.rst | 5 …rg/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-issues.rst
13 Reporting issues
49 If you are facing multiple issues with the Linux kernel at once, report each
60 Step-by-step guide how to report issues to the kernel maintainers
63 The above TL;DR outlines roughly how to report issues to the Linux kernel
65 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For
81 will often be needed anyway to hunt down and fix issues.
89 issue, or a really severe problem: those are 'issues of high priority' that
105 issues at once, create separate notes for each of them and make sure they
116 time this won't be bugzilla.kernel.org, as issues typically need to be sent
[all …]
|
| /Linux-v5.15/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
304 dev_info(&pci_dev->dev, "Note: there are known video quality issues. For details\n"); in tw5864_initdev()
|
| /Linux-v5.15/Documentation/vm/ |
| D | zsmalloc.rst | 13 This was one of the major issues with its predecessor (xvmalloc).
15 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
31 issues on 32-bit systems where the VA region for kernel space mappings
|
| /Linux-v5.15/drivers/staging/media/atomisp/ |
| D | TODO | 5 V4L2 driver, there are still some issues preventing it to
8 Solving the related bugs and issues preventing it to work is
40 5. There are several issues related to memory management, causing
66 6. There is some issues at the frame receive logic, causing the
|
| /Linux-v5.15/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 46 performance but will catch some internal issues.
139 performance but will catch some internal issues.
151 performance but will catch some internal issues.
163 performance but will help resolve GuC related issues.
|
| /Linux-v5.15/Documentation/kbuild/ |
| D | llvm.rst | 90 will build or work without any issues. Below is a general summary of
94 it or there are known issues. Using the latest stable version of LLVM or
135 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_
139 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
|
| /Linux-v5.15/drivers/gpu/drm/panfrost/ |
| D | panfrost_gpu.c | 163 u64 issues; member
166 u64 issues; member
175 .issues = hw_issues_##_name, \
182 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \
282 hw_issues |= model->issues; in panfrost_gpu_init_features()
292 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
302 dev_info(pfdev->dev, "features: %64pb, issues: %64pb", in panfrost_gpu_init_features()
|
| /Linux-v5.15/drivers/staging/fwserial/ |
| D | TODO | 4 - I/O is handled asynchronously which presents some issues when error
11 -- Issues with firewire stack --
|
| /Linux-v5.15/fs/xfs/libxfs/ |
| D | xfs_health.h | 39 /* Observable health issues for metadata spanning the entire filesystem. */
45 /* Observable health issues for realtime volume metadata. */
49 /* Observable health issues for AG metadata. */
61 /* Observable health issues for inode metadata. */
|
| /Linux-v5.15/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-v5.15/include/asm-generic/ |
| D | bug.h | 70 * significant kernel issues that need prompt attention if they should ever
76 * These macros should be used for recoverable kernel issues only.
80 * conditions distinguishable from kernel issues.
224 * function address, and can be useful for catching issues with
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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-v5.15/drivers/platform/x86/ |
| D | i2c-multi-instantiate.c | 144 * issues. The most common problem seen is interrupt flood.
153 * Because of the issues with the interrupt, the device is disabled for now. If
154 * you wish to debug the issues, uncomment the below, and add an entry for the
|
| /Linux-v5.15/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-v5.15/Documentation/dev-tools/kunit/ |
| D | faq.rst | 78 3. Running the UML kernel directly can often reveal issues or error messages
82 mounted), and has had issues in the past when built statically and the host
102 If none of the above tricks help, you are always welcome to email any issues to
|
| /Linux-v5.15/arch/arm/mm/ |
| D | fault-armv.c | 49 * fault (ie, is old), we can safely ignore any issues. in do_adjust_pte()
177 * an object, we need to deal with the cache aliasing issues.
213 * issues. If it has, we need to avoid them for the case where
|
| /Linux-v5.15/drivers/misc/cb710/ |
| D | sgbuf2.c | 79 * handling any alignment issues. Bytes past the buffer's end
124 * handling any alignment issues. Bytes which would be written
|
| /Linux-v5.15/Documentation/i2c/busses/ |
| D | i2c-ali15x3.rst | 36 by a power cycle. Cause unknown (see Issues below).
109 Issues section in Kernel driver i2c-ali15x3
|
| /Linux-v5.15/tools/perf/pmu-events/arch/powerpc/power10/ |
| D | marked.json | 10 …e data gets issued to the VSU. Also, issues can sometimes get killed/cancelled and cause multiple …
|
| /Linux-v5.15/drivers/staging/wfx/Documentation/devicetree/bindings/net/wireless/ |
| D | silabs,wfx.yaml | 25 WFx. Without it, you may encounter issues with warm boot. The mmc-pwrseq
61 during probe. Without this property, you may encounter issues with warm
|
