| /linux/Documentation/process/ |
| H A 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 …]
|
| H A 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
|
| H A 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
|
| H A 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/tools/testing/selftests/rseq/ |
| H A 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/Documentation/process/debugging/ |
| H A D | driver_development_debugging_guide.rst | 13 debugging issues and behavior.
47 - Can cause delays in the execution of the code (which can cause issues to be
60 delays into the code execution, causing issues to be flaky or hidden.)
62 If the processing of this still causes timing issues then you can try
182 behavior. It is designed to find a variety of issues, including signed integer
193 and other locking-related issues in the kernel.
|
| /linux/drivers/gpio/ |
| H A D | gpiolib-acpi-quirks.c | 252 * https://gitlab.freedesktop.org/drm/amd/-/issues/1722#note_1720627
265 * https://gitlab.freedesktop.org/drm/amd/-/issues/1722#note_1720627
310 * https://gitlab.freedesktop.org/drm/amd/-/issues/3073
336 * https://gitlab.freedesktop.org/drm/amd/-/issues/3954
349 * https://gitlab.freedesktop.org/drm/amd/-/issues/4169
363 * https://gitlab.freedesktop.org/drm/amd/-/issues/4482
|
| /linux/Documentation/admin-guide/ |
| H A 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/Documentation/usb/ |
| H A 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/drivers/gpu/drm/panfrost/ |
| H A D | panfrost_gpu.c | 181 u64 issues; member
184 u64 issues; member
193 .issues = hw_issues_##_name, \
200 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \
315 hw_issues |= model->issues; in panfrost_gpu_init_features()
325 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
335 dev_info(pfdev->dev, "features: %64pb, issues: %64pb", in panfrost_gpu_init_features()
|
| /linux/drivers/gpu/drm/amd/display/ |
| H A D | Kconfig | 14 # !CC_IS_CLANG: https://github.com/ClangBuiltLinux/linux/issues/1752
26 https://github.com/llvm/llvm-project/issues/41896.
|
| /linux/Documentation/dev-tools/ |
| H A 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/Documentation/filesystems/fuse/ |
| H A D | fuse-passthrough.rst | 73 This behavior leads to two main issues for unprivileged FUSE daemons:
81 debug issues related to open files (e.g., preventing unmounts).
91 The ``CAP_SYS_ADMIN`` requirement acts as a safeguard against these issues,
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| H A 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/fs/xfs/libxfs/ |
| H A D | xfs_health.h | 59 /* Observable health issues for metadata spanning the entire filesystem. */
69 /* Observable health issues for realtime group metadata. */
76 /* Observable health issues for AG metadata. */
89 /* Observable health issues for inode metadata. */
|
| /linux/security/ |
| H A D | Kconfig.hardening | 192 # https://github.com/ClangBuiltLinux/linux/issues/1766
193 # https://github.com/llvm/llvm-project/issues/59242
219 # https://github.com/llvm/llvm-project/issues/53645
283 # Clang 16 due to https://github.com/llvm/llvm-project/issues/60349
|
| /linux/Documentation/dev-tools/kunit/ |
| H A 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/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | fm10k.rst | 15 - Known Issues
85 each jumbo packet. This should help to avoid buffer starvation issues when
120 Known Issues/Troubleshooting
|
| H A D | ixgbevf.rst | 14 - Known Issues
41 Known Issues/Troubleshooting
|
| /linux/Documentation/driver-api/cxl/platform/ |
| H A D | acpi.rst | 49 Common Issues
74 All of these issues will appear to users as if the driver is failing to
|
| /linux/tools/perf/tests/shell/ |
| H A D | stat_all_metrics.sh | 73 echo "FP issues"
82 echo "Optane memory issues"
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | vmscape.rst | 38 Kernel tracks when a CPU has run a potentially malicious guest and issues an
86 run a potentially malicious guest and issues an IBPB before the first
|
| /linux/drivers/ras/amd/atl/ |
| H A D | system.c | 25 /* Do each step independently to avoid shift out-of-bounds issues. */ in determine_node_id()
36 /* Do each step independently to avoid shift out-of-bounds issues. */ in determine_node_id()
218 * Explicit support should be added for newer systems to avoid issues. in determine_df_rev()
|
| /linux/arch/arm/mm/ |
| H A D | fault-armv.c | 49 * fault (ie, is old), we can safely ignore any issues. in do_adjust_pte()
183 * an object, we need to deal with the cache aliasing issues.
219 * issues. If it has, we need to avoid them for the case where
|
| /linux/drivers/misc/cb710/ |
| H A D | sgbuf2.c | 79 * handling any alignment issues. Bytes past the buffer's end
124 * handling any alignment issues. Bytes which would be written
|