| /linux/io_uring/ |
| H A D | opdef.c | 58 .issue = io_nop,
73 .issue = io_read,
88 .issue = io_write,
94 .issue = io_fsync,
107 .issue = io_read,
121 .issue = io_write,
128 .issue = io_poll_add,
133 .issue = io_poll_remove,
139 .issue = io_sync_file_range,
149 .issue = io_sendmsg,
[all …]
|
| H A D | opdef.h | 34 int (*issue)(struct io_kiocb *, unsigned int); member
|
| /linux/Documentation/kbuild/ |
| H A D | issues.rst | 5 issue #1
8 .. literalinclude:: Kconfig.recursion-issue-01
11 issue #2
14 .. literalinclude:: Kconfig.recursion-issue-02
|
| H A D | Kconfig.recursion-issue-01 | 1 # Simple Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
36 # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
41 # implications of this recursive issue where the solution is perhaps not so
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
|
| H A D | Kconfig.recursion-issue-02 | 1 # Cumulative Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
30 # other bells in the system cannot negate. The reason for this issue is
41 # For an example real world scenario issue refer to the attempt to remove
|
| H A D | Kconfig.select-break | 1 # Select broken dependency issue
13 # example of this issue is below.
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
22 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers
27 <https://kernel.org/>`_. If the issue is present there, send a report.
29 The issue was fixed there, but you would like to see it resolved in a still
38 before the issue occurs.
42 issue, like the kernel and the distro used. In case of a regression, CC the
64 early if an issue that looks like a Linux kernel problem is actually caused by
68 * Are you facing an issue with a Linux kernel a hardware or software vendor
70 document and reporting the issue to your vendor instead, unless you are
79 * See if the issue you are dealing with qualifies as regression, security
[all …]
|
| H A D | reporting-regressions.rst | 24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
31 Linux kernel regression tracking bot "regzbot" track the issue by specifying
52 the issue.
76 Just report the issue as outlined in
115 v5.14-rc1 was the first version where you encountered the issue. If you
161 time-consuming to reliably reproduce the issue, consider teaming up with other
169 issue might better be dealt with in private, feel free to omit the list.
222 running into the issue; nevertheless developers need to take enough time and
229 Is it a regression, if the issue can be avoided by updating some software?
268 developers of the affected code area should look into the issue to find a fix
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-usb-lvstest | 9 Write to this node to issue "Get Device Descriptor"
32 Write to this node to issue "Reset" for Link Layer Validation
39 Write to this node to issue "U3 entry" for Link Layer
46 Write to this node to issue "U3 exit" for Link Layer
58 Write to this node to issue "Warm Reset" for Link Layer Validation
|
| /linux/samples/bpf/ |
| H A D | xdp_sample.bpf.c | 146 NO_TEAR_INC(rec->issue); in BPF_PROG()
176 NO_TEAR_INC(rec->issue); in BPF_PROG()
232 NO_TEAR_INC(rec->issue); in BPF_PROG()
264 NO_TEAR_INC(rec->issue); in BPF_PROG()
|
| H A D | xdp_sample_shared.h | 8 size_t issue; member
|
| /linux/block/ |
| H A D | blk.h | 693 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument
695 return __bio_issue_time(issue->value); in bio_issue_time()
698 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument
700 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()
703 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument
707 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
|
| /linux/drivers/gpu/drm/panfrost/ |
| H A D | panfrost_issues.h | 269 enum panfrost_hw_issue issue) in panfrost_has_hw_issue() argument
271 return test_bit(issue, pfdev->features.hw_issues); in panfrost_has_hw_issue()
|
| H A D | TODO | 6 - Bifrost specific feature and issue handling
|
| /linux/Documentation/process/ |
| H A D | handling-regressions.rst | 26 #. Make the Linux kernel regression tracking bot "regzbot" track the issue (this
32 when the issue started to happen::
44 description pointing to all places where the issue was reported, as
47 only fixing part of the issue that caused the regression, you may use
82 "regzbot" immediately start tracking the issue:
90 This tells regzbot the version range in which the issue started to happen;
118 * Point to all places where the issue was reported using "Closes:" tags::
123 If you are only fixing part of the issue, you may use "Link:" instead as
134 into the issue weeks, months, or years later. These tags are also crucial for
152 should be less than two. And it ought to be just a few days, if the issue is
[all …]
|
| H A D | embargoed-hardware-issues.rst | 99 will form the initial response team for a particular issue. The initial
101 the issue in the best technical way.
105 immediate exclusion from the current issue and removal from all related
141 issue after confirming with the developers that they will adhere to this
144 issue after initial contact. The hardware security team is supporting the
154 entities who have already been, or should be, informed about the issue.
163 - If an expert who is required to handle an issue is employed by a listed
218 List participants may not communicate about the issue outside of the
286 disclosure of a particular issue, unless requested by a response team or by
|
| H A D | cve.rst | 49 feel you have found an unfixed security issue, please follow the
57 have a CVE assigned before an issue is resolved with a commit, please
61 No CVEs will be assigned for any issue found in a version of the kernel
82 If a security issue is found in a Linux kernel that is only supported by
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | igbvf.rst | 58 If an issue is identified with the released source code on a supported kernel
59 with a supported adapter, email the specific information related to the issue
|
| H A D | ixgbevf.rst | 60 If an issue is identified with the released source code on a supported kernel
61 with a supported adapter, email the specific information related to the issue
|
| H A D | idpf.rst | 76 enabling flow control may mitigate the issue.
150 If an issue is identified with the released source code on a supported kernel
151 with a supported adapter, email the specific information related to the issue
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | error_handling.rst | 25 indication of a bus allocation issue. The interrupt mechanism can also help
35 Slave or to a non-implemented register) or electrical issue, no response
39 solution. Alternatively some implementations might directly issue a bus
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | cross-thread-rsb.rst | 29 The following CVE entry is related to this issue:
75 Both mitigations are required to fully address this issue.
85 By default, the KVM hypervisor mitigates this issue by intercepting guest
|
| /linux/Documentation/hwmon/ |
| H A D | asus_wmi_sensors.rst | 71 getting stuck. This is not an issue with the driver, but the BIOS. The Prime
77 rectify the issue.
|
| /linux/drivers/virt/coco/pkvm-guest/ |
| H A D | Kconfig | 6 are isolated from the host and must issue hypercalls to enable
|
| /linux/arch/alpha/lib/ |
| H A D | strlen.S | 35 nop # helps dual issue last two insns
|