Home
last modified time | relevance | path

Searched refs:issues (Results 1 – 25 of 297) sorted by relevance

12345678910>>...12

/linux/Documentation/process/
H A Dembargoed-hardware-issues.rst3 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 Dcve.rst17 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 Dthreat-model.rst7 <../admin-guide/reporting-issues>`), and can complicate security enforcement
127 * issues triggered only when using features intended for development or
132 * issues affecting drivers exposed under CONFIG_STAGING, as well as features
172 * issues that can only be triggered by heavy attacks (e.g. brute force) whose
177 that do not exist on real systems at the time of reporting (issues
181 * as well as issues that can be triggered at a cost that is orders of
222 issues that are resolved, mitigated, or detected by running a filesystem
H A Dstable-api-nonsense.rst45 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
/linux/Documentation/translations/zh_CN/admin-guide/
H A Dreporting-regressions.rst31 #. 按照 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst 中
74 只需按照 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst 中
136 如 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst (简要)
/linux/Documentation/translations/zh_TW/admin-guide/
H A Dreporting-regressions.rst31 #. 按照 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst 中
74 只需按照 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst 中
136 如 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst (簡要)
H A Dsecurity-bugs.rst27 請查看“Documentation/translations/zh_CN/admin-guide/reporting-issues.rst”中
/linux/Documentation/process/debugging/
H A Ddriver_development_debugging_guide.rst13 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/Documentation/kbuild/
H A Dissues.rst2 Recursion issues
/linux/Documentation/translations/zh_CN/kbuild/
H A Dindex.rst28 - issues
/linux/Documentation/ABI/removed/
H A Dnet_dma7 coherency issues of the cpu potentially touching the buffers
H A Dvideo13948 performance issues in its first generation. Any video1394 user had
/linux/Documentation/admin-guide/
H A Dreporting-regressions.rst24 #. 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/arch/arm64/boot/dts/freescale/
H A Dimx8qm-apalis.dtsi321 * issues with certain SD cards, disable 1.8V signaling for now.
330 * issues with certain SD cards, disable 1.8V signaling for now.
/linux/Documentation/
H A Dindex.rst81 Reporting issues <admin-guide/reporting-issues.rst>
/linux/Documentation/userspace-api/media/dvb/
H A Dlegacy_dvb_apis.rst11 The DVBv3 frontend API has issues with new delivery systems, including
H A Dfrontend_legacy_api.rst24 kernel due to compatibility issues only. Their usage is strongly not
/linux/Documentation/translations/zh_CN/process/
H A Dsecurity-bugs.rst27 请查看“Documentation/translations/zh_CN/admin-guide/reporting-issues.rst”中
H A Dindex.rst50 embargoed-hardware-issues
/linux/Documentation/arch/riscv/
H A Dzicfilp.rst16 Memory corruption issues usually result in crashes. However, in the
18 security issues.
20 Some of those security issues can be code re-use attacks, where an
/linux/Documentation/devicetree/bindings/csky/
H A Dpmu.txt6 it could count cpu's events for helping analysis performance issues.
/linux/Documentation/usb/
H A Dehci.rst51 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/Documentation/admin-guide/hw-vuln/
H A Dvmscape.rst38 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/Documentation/filesystems/fuse/
H A Dfuse-passthrough.rst73 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/translations/zh_TW/
H A Dindex.rst81 admin-guide/reporting-issues.rst

12345678910>>...12