| /kernel/linux/linux-6.6/Documentation/process/ |
| D | maintainer-soc-clean-dts.rst | 18 new ``make dtbs_check W=1`` warnings. Warnings in a new board DTS, which are
20 warnings. The platform maintainers have automation in place which should point
21 out any new warnings.
23 If a commit introducing new warnings gets accepted somehow, the resulting
|
| /kernel/linux/linux-6.6/scripts/ |
| D | Makefile.extrawarn | 9 # Default set of warnings, always enabled
50 # These warnings generated too much noise in a regular build.
61 # disable pointer signed / unsigned warnings in gcc 4.0
70 # warnings for bounds checks involving those possible values. While
73 # warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX
105 # W=1 - warnings which may be relevant and do not occur too often
164 # W=2 - warnings which occur quite often but may still be relevant
184 # The following turn off the warnings enabled by -Wextra
202 # W=3 - more obscure warnings, can most likely be ignored
222 # The following turn off the warnings enabled by -Wextra
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | stallwarn.rst | 13 What Causes RCU CPU Stall Warnings?
18 warnings:
77 RCU CPU stall warnings.
80 timeout down to just barely avoid RCU CPU stall warnings, and then
88 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
102 This resulted in a series of RCU CPU stall warnings, eventually
106 Note that SRCU does -not- have CPU stall warnings. Please note that
108 No grace period, no CPU stall warnings.
112 If you have a series of stall warnings from a single extended stall,
166 own warnings, as this often gives better-quality stack traces.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/doc-guide/ |
| D | contributing.rst | 30 Addressing warnings
34 warnings. When you have that many, you might as well have none at all;
36 ones. For this reason, eliminating warnings is one of the highest-priority
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
44 problem; making those warnings go away requires understanding the problem
46 warnings should probably not say "fix a warning" in the changelog title;
49 Another important point is that documentation warnings are often created by
51 maintainer appreciates being copied on fixes for these warnings, the
55 For example, in a documentation build I grabbed a pair of warnings nearly
[all …]
|
| /kernel/linux/linux-6.6/Documentation/doc-guide/ |
| D | contributing.rst | 30 Addressing warnings
34 warnings. When you have that many, you might as well have none at all;
36 ones. For this reason, eliminating warnings is one of the highest-priority
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
44 problem; making those warnings go away requires understanding the problem
46 warnings should probably not say "fix a warning" in the changelog title;
49 Another important point is that documentation warnings are often created by
51 maintainer appreciates being copied on fixes for these warnings, the
55 For example, in a documentation build I grabbed a pair of warnings nearly
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/rcutorture/bin/ |
| D | parse-build.sh | 38 grep warning: < $F > $T/warnings
39 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings
40 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings
41 grep "^ld: .*undefined reference to" $T/warnings | head -1 > $T/ldwarnings
|
| D | kvm-test-1-run-qemu.sh | 110 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
111 grep "^(qemu) qemu:" $resdir/kvm-test-1-run*.sh.out >> $resdir/Warnings 2>&1
112 …ed -n "s/^(qemu) qemu: terminating on signal [0-9]* from pid \([0-9]*\).*$/\1/p" $resdir/Warnings`"
115 echo "ps -fp $killpid" >> $resdir/Warnings 2>&1
116 ps -fp $killpid >> $resdir/Warnings 2>&1
139 echo "PID $qemu_pid killed due to run STOP.1 request `date`" >> $resdir/Warnings 2>&1
171 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds `date`" >> $resdir/Warnings 2>&1
|
| /kernel/linux/linux-6.6/tools/testing/selftests/kvm/x86_64/ |
| D | mmio_warning_test.c | 81 int warnings; in get_warnings_count() local
85 if (fscanf(f, "%d", &warnings) < 1) in get_warnings_count()
86 warnings = 0; in get_warnings_count()
89 return warnings; in get_warnings_count()
118 "Warnings found in kernel. Run 'dmesg' to inspect them."); in main()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kvm/x86_64/ |
| D | mmio_warning_test.c | 81 int warnings; in get_warnings_count() local
85 if (fscanf(f, "%d", &warnings) < 1) in get_warnings_count()
86 warnings = 0; in get_warnings_count()
89 return warnings; in get_warnings_count()
124 "Warnings found in kernel. Run 'dmesg' to inspect them."); in main()
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | dqblk_xfs.h | 68 __u16 d_iwarns; /* # warnings issued wrt num inodes */
69 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
78 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
108 * warnings are set/cleared by the administrators (or automatically by going
175 __u16 qs_bwarnlimit; /* limit for num warnings */
176 __u16 qs_iwarnlimit; /* limit for num warnings */
220 __u16 qs_bwarnlimit; /* limit for num warnings */
221 __u16 qs_iwarnlimit; /* limit for num warnings */
222 __u16 qs_rtbwarnlimit;/* limit for rt blks warnings */
|
| /kernel/linux/linux-6.6/tools/verification/rv/ |
| D | Makefile | 69 .PHONY: all warnings show_warnings
70 all: warnings rv
74 WARNINGS = show_warnings macro
82 WARNINGS = show_warnings macro
107 ifneq ("$(WARNINGS)", "")
110 warnings: $(WARNINGS) target
|
| /kernel/linux/linux-6.6/tools/testing/ktest/examples/include/ |
| D | patchcheck.conf | 56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches
|
| /kernel/linux/linux-5.10/tools/testing/ktest/examples/include/ |
| D | patchcheck.conf | 56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches
|
| /kernel/linux/linux-6.6/Documentation/RCU/ |
| D | stallwarn.rst | 13 What Causes RCU CPU Stall Warnings?
18 warnings:
77 RCU CPU stall warnings.
80 timeout down to just barely avoid RCU CPU stall warnings, and then
88 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
115 of RCU CPU stall warnings, eventually leading the realization
119 CPU stall warning. Note that SRCU does *not* have CPU stall warnings.
121 in progress. No grace period, no CPU stall warnings.
125 If you have a series of stall warnings from a single extended stall,
199 own warnings, as this often gives better-quality stack traces.
[all …]
|
| /kernel/linux/linux-6.6/tools/tracing/rtla/ |
| D | Makefile | 69 .PHONY: all warnings show_warnings
70 all: warnings rtla
74 WARNINGS = show_warnings macro
82 WARNINGS = show_warnings macro
107 ifneq ("$(WARNINGS)", "")
110 warnings: $(WARNINGS) target
|
| /kernel/linux/linux-5.10/drivers/base/test/ |
| D | test_async_driver_probe.c | 21 static atomic_t warnings, errors, timeout, async_completed; variable
51 atomic_inc(&warnings); in test_probe()
244 * Otherwise if they completed without errors or warnings then in test_async_probe_init()
251 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init()
271 * errors or warnings being reported by the probe routine. in test_async_probe_init()
278 pr_err("Test failed with %d errors and %d warnings\n", in test_async_probe_init()
279 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
|
| /kernel/linux/linux-6.6/drivers/base/test/ |
| D | test_async_driver_probe.c | 21 static atomic_t warnings, errors, timeout, async_completed; variable
51 atomic_inc(&warnings); in test_probe()
240 * Otherwise if they completed without errors or warnings then in test_async_probe_init()
247 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init()
267 * errors or warnings being reported by the probe routine. in test_async_probe_init()
274 pr_err("Test failed with %d errors and %d warnings\n", in test_async_probe_init()
275 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
|
| /kernel/linux/linux-6.6/lib/ |
| D | debugobjects.c | 1035 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
1163 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1189 if (warnings != debug_objects_warnings) { in check_results()
1190 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1191 warnings, debug_objects_warnings); in check_results()
1215 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1221 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1225 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1228 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1231 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | debugobjects.c | 1026 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
1154 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1180 if (warnings != debug_objects_warnings) { in check_results()
1181 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1182 warnings, debug_objects_warnings); in check_results()
1206 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1212 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1216 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1219 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1222 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | dqblk_xfs.h | 68 __u16 d_iwarns; /* # warnings issued wrt num inodes */
69 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
78 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
108 * warnings are set/cleared by the administrators (or automatically by going
175 __u16 qs_bwarnlimit; /* limit for num warnings */
176 __u16 qs_iwarnlimit; /* limit for num warnings */
220 __u16 qs_bwarnlimit; /* limit for num warnings */
221 __u16 qs_iwarnlimit; /* limit for num warnings */
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 140 echo CPU count limited from $cpu_count to $TORTURE_ALLOTED_CPUS | tee -a $resdir/Warnings
218 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
219 grep "^(qemu) qemu:" $resdir/kvm-test-1-run.sh.out >> $resdir/Warnings 2>&1
220 …ed -n "s/^(qemu) qemu: terminating on signal [0-9]* from pid \([0-9]*\).*$/\1/p" $resdir/Warnings`"
223 echo "ps -fp $killpid" >> $resdir/Warnings 2>&1
224 ps -fp $killpid >> $resdir/Warnings 2>&1
247 echo "PID $qemu_pid killed due to run STOP request" >> $resdir/Warnings 2>&1
275 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
|
| D | parse-build.sh | 39 grep warning: < $F > $T/warnings
40 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings
41 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings
|
| /kernel/linux/linux-5.10/tools/power/acpi/ |
| D | Makefile.config | 64 WARNINGS := -Wall
65 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
71 CFLAGS += $(WARNINGS)
|
| /kernel/linux/linux-6.6/tools/power/acpi/ |
| D | Makefile.config | 64 WARNINGS := -Wall
65 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
71 CFLAGS += $(WARNINGS)
|
| /kernel/linux/linux-5.10/scripts/ |
| D | Makefile.extrawarn | 21 # W=1 - warnings which may be relevant and do not occur too often
35 # The following turn off the warnings enabled by -Wextra
64 # W=2 - warnings which occur quite often but may still be relevant
82 # W=3 - more obscure warnings, can most likely be ignored
|