Hello, Christian!
Imagine my surprise to learn that "make allmodconfig" builds
of the kernel also build userspace components, including
samples/vfs/test-list-all-mounts.c. ;-)
On CentOS, "make allmodconfig" gives a zero exit code, but gets the
following warnings:
In file included from
samples/vfs/../../tools/testing/selftests/pidfd/../clone3/clone3_selftests.h:8,
from
samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:20,
from samples/vfs/test-list-all-mounts.c:11:
usr/include/linux/sched.h:114: warning: "SCHED_NORMAL" redefined
114 | #define SCHED_NORMAL 0
|
In file included from /usr/include/sched.h:43,
from samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:9,
from samples/vfs/test-list-all-mounts.c:11:
/usr/include/bits/sched.h:32: note: this is the location of the previous
definition
32 | # define SCHED_NORMAL SCHED_OTHER
|
In file included from
samples/vfs/../../tools/testing/selftests/pidfd/../clone3/clone3_selftests.h:8,
from
samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:20,
from samples/vfs/test-list-all-mounts.c:11:
usr/include/linux/sched.h:137: warning: "SCHED_FLAG_KEEP_ALL" redefined
137 | #define SCHED_FLAG_KEEP_ALL (SCHED_FLAG_KEEP_POLICY | \
|
In file included from /usr/include/sched.h:43,
from samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:9,
from samples/vfs/test-list-all-mounts.c:11:
/usr/include/bits/sched.h:51: note: this is the location of the previous
definition
51 | #define SCHED_FLAG_KEEP_ALL 0x18
|
In file included from
samples/vfs/../../tools/testing/selftests/pidfd/../clone3/clone3_selftests.h:8,
from
samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:20,
from samples/vfs/test-list-all-mounts.c:11:
usr/include/linux/sched.h:140: warning: "SCHED_FLAG_UTIL_CLAMP" redefined
140 | #define SCHED_FLAG_UTIL_CLAMP (SCHED_FLAG_UTIL_CLAMP_MIN | \
|
In file included from /usr/include/sched.h:43,
from samples/vfs/../../tools/testing/selftests/pidfd/pidfd.h:9,
from samples/vfs/test-list-all-mounts.c:11:
/usr/include/bits/sched.h:52: note: this is the location of the previous
definition
But on older Ubuntu, it builds without any warnings.
Is this the sort of problem you would like reported, or should we go
back to looking only at the build's exit code for allmodconfig builds?
Thanx, Paul
