issues (full) in projects: Linux-v6.1 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:issues (Results 1 – 25 of 1280) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...52

/Linux-v6.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 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 160 members object to the patch, bringing up issues that the maintainers and 165 issues, some patches may be modified or dropped or additional patches may 167 issues are found.`
D	handling-regressions.rst	76 Documentation/admin-guide/reporting-issues.rst. 151 other Linux kernel work, unless the latter concerns acute security issues or 178 includes mainline, as issues like compile errors otherwise might prevent many 195 regressions and other issues which are annoying, but don't prevent anyone 245 * what issues actually qualify as regression 334 What kind of issues are supposed to be tracked by regzbot? 338 regular issues. But it's okay for the Linux kernel's regression tracker if you 339 use regzbot to track severe issues, like reports about hangs, corrupted data, 653 And regressions get reverted, unless there are security issues or 665 issues that way. There aren't that many of them.
/Linux-v6.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-v6.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-v6.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-v6.1/Documentation/mm/
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-v6.1/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-v6.1/drivers/gpu/drm/panfrost/
D	panfrost_gpu.c	`157 u64 issues; member 160 u64 issues; member 169 .issues = hw_issues_##_name, \ 176 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \ 279 hw_issues \|= model->issues; in panfrost_gpu_init_features() 289 hw_issues \|= model->revs[best].issues; in panfrost_gpu_init_features() 299 dev_info(pfdev->dev, "features: %64pb, issues: %64pb", in panfrost_gpu_init_features()`
/Linux-v6.1/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-v6.1/Documentation/kbuild/
D	llvm.rst	109 will build or work without any issues. Below is a general summary of 113 it or there are known issues. Using the latest stable version of LLVM or 160 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_ 164 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
/Linux-v6.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-v6.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-v6.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 135 etc. Smatch also has tests against more serious issues such as integer`
/Linux-v6.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-v6.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-v6.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-v6.1/tools/perf/pmu-events/arch/x86/sandybridge/
D	snb-metrics.json	11 …on": "This metric represents fraction of slots the CPU was stalled due to Frontend latency issues", 15 …represents fraction of slots the CPU was stalled due to Frontend latency issues. For example; ins… 59 …": "This metric represents fraction of slots the CPU was stalled due to Frontend bandwidth issues", 63 …presents fraction of slots the CPU was stalled due to Frontend bandwidth issues. For example; ine… 155 …"BriefDescription": "This metric represents fraction of slots where Core non-memory issues were of… 159 …"PublicDescription": "This metric represents fraction of slots where Core non-memory issues were o… 171 …cles the CPU performance was potentially limited due to Core computation issues (non divider-relat… 175 …cles the CPU performance was potentially limited due to Core computation issues (non divider-relat…
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
D	jkt-metrics.json	11 …on": "This metric represents fraction of slots the CPU was stalled due to Frontend latency issues", 15 …represents fraction of slots the CPU was stalled due to Frontend latency issues. For example; ins… 59 …": "This metric represents fraction of slots the CPU was stalled due to Frontend bandwidth issues", 63 …presents fraction of slots the CPU was stalled due to Frontend bandwidth issues. For example; ine… 155 …"BriefDescription": "This metric represents fraction of slots where Core non-memory issues were of… 159 …"PublicDescription": "This metric represents fraction of slots where Core non-memory issues were o… 171 …cles the CPU performance was potentially limited due to Core computation issues (non divider-relat… 175 …cles the CPU performance was potentially limited due to Core computation issues (non divider-relat…
/Linux-v6.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-v6.1/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-v6.1/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`

12 3 4 5 6 7 8 9 10 >>...52