kernel May 2024

kernel@lists.fedoraproject.org

5 participants
25 discussions

[Testdays] Call for Fedora Linux 41 testing events
by Sumantro Mukherjee 13 May '24

13 May '24

Hi Fedora users, developers, and friends! It's time to start thinking about Test Days for Fedora 41. For anyone who isn't aware, a Test Day is an event usually focused around IRC for interaction and a Wiki page for instructions and results, with the aim being to get a bunch of interested users and developers together to test a specific feature or area of the distribution. You can run a Test Day on just about anything for which it would be useful to do some fairly focused testing in 'real time' with a group of testers; it doesn't have to be code, for instance, we often run Test Days for l10n/i18n topics. For more information on Test Days, see https://fedoraproject.org/wiki/QA/Test_Days . Anyone who wants to can host their own Test Day, or you can request that the QA group helps you out with organization or any combination of the two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's an example https://pagure.io/fedora-qa/issue/624 . For instructions on hosting a Test Day, see https://fedoraproject.org/wiki/QA/SOP_Test_Day_management . You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days . There are many slots open right now. Consider the development schedule, though, in deciding when you want to run your Test Day - for some topics you may want to avoid the time before the Beta release or the time after the feature freeze or the Final Freeze. We normally aim to schedule Test Days on Thursdays; however, if you want to run a series of related Test Days, it's often a good idea to do something like Tuesday / Wednesday / Thursday of the same week (this is how we usually run the X Test Week, for instance). If all the Thursday slots fill up but more people want to run Test Days, we will open up Tuesday slots as overflows. And finally, if you really want to run a Test Day in a specific time frame due to the development schedule, but the Thursday slot for that week is full, we can add a slot on another day. We're flexible! Just put in your ticket the date or time frame you'd like, and we'll figure it out from there. If you don't want to run your own Test Day, but you are willing to help with another, feel free to join one or more of already accepted Test Days: GNOME Test Day* i18n Test Day* Kernel Test Week(s)* Upgrade Test Day* IoT Test Week* Cloud Test Day* Fedora CoreOS Test Week* And don't be afraid, there are a lot of more slots available for your own Test Day! [*] These are the test days we run generally to make sure everything is working fine, the dates get announced as we move into the release cycle. If you have any questions about the Test Day process, please don't hesitate to contact me or any member of the Fedora QA team on test at lists.fedoraproject.org or in #fedora-qa on IRC. Thanks! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

[OS-BUILD PATCHv3 0/0] Add support for rh_flags to kernel-ark
by Ricardo Robaina (via Email Bridge) 13 May '24

13 May '24

From: Ricardo Robaina on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3070 NOTE: Truncated patchset due to missing public @redhat.com email address on your GitLab profile at https://gitlab.com/-/profile. Once that is fixed, close and reopen the merge request to retrigger sending the emails. JIRA: https://issues.redhat.com/browse/RHEL-32987 rh_flags is a mechanism that allows tracking usage of specific kernel features. The list of used features is accessible via procfs and is printed in panic messages. It's meant to provide better customer support making possible for support engineers to be able to see what specific features were used and steer the support accordingly. Ricardo Robaina (11): add support for rh_features add rh_features to /proc rh_features: convert to atomic allocation rh_features: move rh_features entry to sys/kernel kernel: rh_features: fix reading empty feature list from /proc rh_flags: Rename rh_features to rh_flags rh_flags: Replace strlcpy with strscpy rh_flags: Replace register_sysctl_table with register_sysctl rh_flags: Remove unused __read_mostly variable rh_flags: Hide rh_print_flags call behind CONFIG_RHEL_DIFFERENCES rh_flags: Move rh_flags.o to obj-$(CONFIG_RHEL_DIFFERENCES) line include/linux/rh_flags.h | 34 +++++++++++ kernel/Makefile | 2 +- kernel/module/main.c | 6 ++ kernel/rh_flags.c | 119 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 160 insertions(+), 1 deletion(-) create mode 100644 include/linux/rh_flags.h create mode 100644 kernel/rh_flags.c Signed-off-by: Ricardo Robaina <rrobaina(a)redhat.com>

1 0

[OS-BUILD PATCHv2] redhat: make filtermods.py less verbose by default
by Jan Stancek (via Email Bridge) 09 May '24

09 May '24

From: Jan Stancek <jstancek(a)redhat.com> redhat: make filtermods.py less verbose by default Lower the default verbosity of filtermods.py, so it doesn't increase build logs too much. Debug messages are still captured to a file, but only printed out in case there's an error. Signed-off-by: Jan Stancek <jstancek(a)redhat.com> diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index blahblah..blahblah 100644 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -2634,8 +2634,12 @@ BuildKernel() { fi # this creates ../modules-*.list output, where each kmod path is as it # appears in modules.dep (relative to lib/modules/$KernelVer) - %{SOURCE22} sort -d $RPM_BUILD_ROOT/lib/modules/$KernelVer/modules.dep -c configs/def_variants.yaml $variants_param -o .. + %{SOURCE22} -l "../filtermods-$KernelVer.log" sort -d $RPM_BUILD_ROOT/lib/modules/$KernelVer/modules.dep -c configs/def_variants.yaml $variants_param -o .. if [ $? -ne 0 ]; then + echo "8< --- filtermods-$KernelVer.log ---" + cat "../filtermods-$KernelVer.log" + echo "--- filtermods-$KernelVer.log --- >8" + echo "8< --- modules.dep ---" cat $RPM_BUILD_ROOT/lib/modules/$KernelVer/modules.dep echo "--- modules.dep --- >8" diff --git a/redhat/scripts/filtermods.adoc b/redhat/scripts/filtermods.adoc index blahblah..blahblah 100644 --- a/redhat/scripts/filtermods.adoc +++ b/redhat/scripts/filtermods.adoc @@ -17,7 +17,15 @@ there are some best practices for configs used in kernel builds: * Write as few rules for modules package as possible * Keep the rule list alphabetical where possible -*usage:* filtermods.py [-h] [-v] [-q] {sort,rulemap,selftest,cmp2rpm} ... +*usage:* filtermods.py [-h] [-v] [-q] [-l LOG_FILENAME] {sort,rulemap,selftest,cmp2rpm} ... + +== Common command line options +These options apply to all subcommands. + +* -h / --help : display help +* -v / --verbose : increases stdout verbosity +* -q / --quiet : lowers stdout verbosity +* -l / --log-filename : name of the logfile which captures detailed logs (filtermods.log by default) == SUBCOMMANDS === sort diff --git a/redhat/scripts/filtermods.py b/redhat/scripts/filtermods.py index blahblah..blahblah 100755 --- a/redhat/scripts/filtermods.py +++ b/redhat/scripts/filtermods.py @@ -11,7 +11,7 @@ import sys import yaml import unittest -from logging import getLogger, DEBUG, INFO, WARN, ERROR, CRITICAL, NOTSET, StreamHandler, Formatter, Logger +from logging import getLogger, DEBUG, INFO, WARN, ERROR, CRITICAL, NOTSET, FileHandler, StreamHandler, Formatter, Logger from typing import Optional log = getLogger('filtermods') @@ -42,14 +42,25 @@ def safe_run_command(cmd, cwddir=None): return retcode, out, err -def setup_logging(): +def setup_logging(log_filename, stdout_log_level): log_format = '%(asctime)s %(levelname)7.7s %(funcName)20.20s:%(lineno)4s %(message)s' log = getLogger('filtermods') + log.setLevel(DEBUG) + handler = StreamHandler(sys.stdout) formatter = Formatter(log_format, '%H:%M:%S') handler.setFormatter(formatter) + handler.setLevel(stdout_log_level) log.addHandler(handler) - log.debug('Logging on') + log.debug('stdout logging on') + + if log_filename: + file_handler = FileHandler(log_filename, 'w') + file_handler.setFormatter(formatter) + file_handler.setLevel(DEBUG) + log.addHandler(file_handler) + log.info('file logging on: %s', log_filename) + return log @@ -342,7 +353,7 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) if init: kmod.allowed_list = init_allowed_list - log.info('%s: init to %s', kmod.name, [x.name for x in kmod.allowed_list]) + log.debug('%s: init to %s', kmod.name, [x.name for x in kmod.allowed_list]) kmod_allowed_list = kmod.allowed_list or set() # log.debug('%s: update to %s', kmod.name, [x.name for x in kmod_allowed_list]) @@ -354,8 +365,8 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) continue if not is_pkg_parent_to_any(pkg, kmod_dep.allowed_list): to_remove.add(pkg) - log.info('%s: remove %s from allowed, child: %s [%s]', - kmod.name, [pkg.name], kmod_dep.name, [x.name for x in kmod_dep.allowed_list]) + log.debug('%s: remove %s from allowed, child: %s [%s]', + kmod.name, [pkg.name], kmod_dep.name, [x.name for x in kmod_dep.allowed_list]) # each allowed is child to at least one parent allowed [for _all_ parents] for pkg in kmod_allowed_list: @@ -365,8 +376,8 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) if not is_pkg_child_to_any(pkg, kmod_par.allowed_list): to_remove.add(pkg) - log.info('%s: remove %s from allowed, parent: %s %s', - kmod.name, [pkg.name], kmod_par.name, [x.name for x in kmod_par.allowed_list]) + log.debug('%s: remove %s from allowed, parent: %s %s', + kmod.name, [pkg.name], kmod_par.name, [x.name for x in kmod_par.allowed_list]) for pkg in to_remove: kmod_allowed_list.remove(pkg) @@ -377,7 +388,7 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) if init or to_remove or update_linked: if to_remove: - log.info('%s: updated to %s', kmod.name, [x.name for x in kmod_allowed_list]) + log.debug('%s: updated to %s', kmod.name, [x.name for x in kmod_allowed_list]) for kmod_dep in kmod.depends_on: num_updated = num_updated + update_allowed(kmod_dep, visited) @@ -488,8 +499,8 @@ def propagate_labels_2(pkg_list: KModPackageList, kmod_list: KModList): if chosen_pkg is not None: kmod.allowed_list = set([chosen_pkg]) - log.info('%s: making to prefer %s (preffered is %s), allowed: %s', kmod.name, chosen_pkg.name, - kmod.preferred_pkg.name, [pkg.name for pkg in kmod.allowed_list]) + log.debug('%s: making to prefer %s (preffered is %s), allowed: %s', kmod.name, chosen_pkg.name, + kmod.preferred_pkg.name, [pkg.name for pkg in kmod.allowed_list]) update_linked = True visited: set[KMod] = set() @@ -551,7 +562,7 @@ def propagate_labels_3(pkg_list: KModPackageList, kmod_list: KModList): if chosen_pkg: kmod.allowed_list = set([chosen_pkg]) - log.info('%s: making to prefer %s (default: %s)', kmod.name, [chosen_pkg.name], default_name) + log.debug('%s: making to prefer %s (default: %s)', kmod.name, [chosen_pkg.name], default_name) update_linked = True visited: set[KMod] = set() @@ -1002,13 +1013,15 @@ def cmd_cmp2rpm(options): def main(): global log - log = setup_logging() parser = argparse.ArgumentParser() parser.add_argument('-v', '--verbose', dest='verbose', help='be more verbose', action='count', default=4) parser.add_argument('-q', '--quiet', dest='quiet', help='be more quiet', action='count', default=0) + parser.add_argument('-l', '--log-filename', dest='log_filename', + help='log filename', default='filtermods.log') + subparsers = parser.add_subparsers(dest='cmd') def add_graphviz_arg(p): @@ -1061,7 +1074,9 @@ def main(): options.verbose = options.verbose - 2 options.verbose = max(options.verbose - options.quiet, 0) levels = [NOTSET, CRITICAL, ERROR, WARN, INFO, DEBUG] - log.setLevel(levels[min(options.verbose, len(levels) - 1)]) + stdout_log_level = levels[min(options.verbose, len(levels) - 1)] + + log = setup_logging(options.log_filename, stdout_log_level) ret = 0 if options.cmd == "sort": -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3098

1 0

[OS-BUILD PATCH] redhat: make filtermods.py less verbose by default
by Jan Stancek (via Email Bridge) 09 May '24

09 May '24

From: Jan Stancek <jstancek(a)redhat.com> redhat: make filtermods.py less verbose by default Lower the default verbosity of filtermods.py, so it doesn't increase build logs too much. Debug messages are still captured to a file, but only printed out in case there's an error. Signed-off-by: Jan Stancek <jstancek(a)redhat.com> diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index blahblah..blahblah 100644 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -2634,8 +2634,12 @@ BuildKernel() { fi # this creates ../modules-*.list output, where each kmod path is as it # appears in modules.dep (relative to lib/modules/$KernelVer) - %{SOURCE22} sort -d $RPM_BUILD_ROOT/lib/modules/$KernelVer/modules.dep -c configs/def_variants.yaml $variants_param -o .. + %{SOURCE22} -l "../filtermods-$KernelVer.log" sort -d $RPM_BUILD_ROOT/lib/modules/$KernelVer/modules.dep -c configs/def_variants.yaml $variants_param -o .. if [ $? -ne 0 ]; then + echo "8< --- filtermods-$KernelVer.log ---" + cat "../filtermods-$KernelVer.log" + echo "--- filtermods-$KernelVer.log --- >8" + echo "8< --- modules.dep ---" cat $RPM_BUILD_ROOT/lib/modules/$KernelVer/modules.dep echo "--- modules.dep --- >8" diff --git a/redhat/scripts/filtermods.py b/redhat/scripts/filtermods.py index blahblah..blahblah 100755 --- a/redhat/scripts/filtermods.py +++ b/redhat/scripts/filtermods.py @@ -11,7 +11,7 @@ import sys import yaml import unittest -from logging import getLogger, DEBUG, INFO, WARN, ERROR, CRITICAL, NOTSET, StreamHandler, Formatter, Logger +from logging import getLogger, DEBUG, INFO, WARN, ERROR, CRITICAL, NOTSET, FileHandler, StreamHandler, Formatter, Logger from typing import Optional log = getLogger('filtermods') @@ -42,14 +42,25 @@ def safe_run_command(cmd, cwddir=None): return retcode, out, err -def setup_logging(): +def setup_logging(log_filename, stdout_log_level): log_format = '%(asctime)s %(levelname)7.7s %(funcName)20.20s:%(lineno)4s %(message)s' log = getLogger('filtermods') + log.setLevel(DEBUG) + handler = StreamHandler(sys.stdout) formatter = Formatter(log_format, '%H:%M:%S') handler.setFormatter(formatter) + handler.setLevel(stdout_log_level) log.addHandler(handler) - log.debug('Logging on') + log.debug('stdout logging on') + + if log_filename: + file_handler = FileHandler(log_filename, 'w') + file_handler.setFormatter(formatter) + file_handler.setLevel(DEBUG) + log.addHandler(file_handler) + log.info('file logging on: %s', log_filename) + return log @@ -342,7 +353,7 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) if init: kmod.allowed_list = init_allowed_list - log.info('%s: init to %s', kmod.name, [x.name for x in kmod.allowed_list]) + log.debug('%s: init to %s', kmod.name, [x.name for x in kmod.allowed_list]) kmod_allowed_list = kmod.allowed_list or set() # log.debug('%s: update to %s', kmod.name, [x.name for x in kmod_allowed_list]) @@ -354,8 +365,8 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) continue if not is_pkg_parent_to_any(pkg, kmod_dep.allowed_list): to_remove.add(pkg) - log.info('%s: remove %s from allowed, child: %s [%s]', - kmod.name, [pkg.name], kmod_dep.name, [x.name for x in kmod_dep.allowed_list]) + log.debug('%s: remove %s from allowed, child: %s [%s]', + kmod.name, [pkg.name], kmod_dep.name, [x.name for x in kmod_dep.allowed_list]) # each allowed is child to at least one parent allowed [for _all_ parents] for pkg in kmod_allowed_list: @@ -365,8 +376,8 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) if not is_pkg_child_to_any(pkg, kmod_par.allowed_list): to_remove.add(pkg) - log.info('%s: remove %s from allowed, parent: %s %s', - kmod.name, [pkg.name], kmod_par.name, [x.name for x in kmod_par.allowed_list]) + log.debug('%s: remove %s from allowed, parent: %s %s', + kmod.name, [pkg.name], kmod_par.name, [x.name for x in kmod_par.allowed_list]) for pkg in to_remove: kmod_allowed_list.remove(pkg) @@ -377,7 +388,7 @@ def update_allowed(kmod: KMod, visited: set[KMod], update_linked: bool = False) if init or to_remove or update_linked: if to_remove: - log.info('%s: updated to %s', kmod.name, [x.name for x in kmod_allowed_list]) + log.debug('%s: updated to %s', kmod.name, [x.name for x in kmod_allowed_list]) for kmod_dep in kmod.depends_on: num_updated = num_updated + update_allowed(kmod_dep, visited) @@ -488,8 +499,8 @@ def propagate_labels_2(pkg_list: KModPackageList, kmod_list: KModList): if chosen_pkg is not None: kmod.allowed_list = set([chosen_pkg]) - log.info('%s: making to prefer %s (preffered is %s), allowed: %s', kmod.name, chosen_pkg.name, - kmod.preferred_pkg.name, [pkg.name for pkg in kmod.allowed_list]) + log.debug('%s: making to prefer %s (preffered is %s), allowed: %s', kmod.name, chosen_pkg.name, + kmod.preferred_pkg.name, [pkg.name for pkg in kmod.allowed_list]) update_linked = True visited: set[KMod] = set() @@ -551,7 +562,7 @@ def propagate_labels_3(pkg_list: KModPackageList, kmod_list: KModList): if chosen_pkg: kmod.allowed_list = set([chosen_pkg]) - log.info('%s: making to prefer %s (default: %s)', kmod.name, [chosen_pkg.name], default_name) + log.debug('%s: making to prefer %s (default: %s)', kmod.name, [chosen_pkg.name], default_name) update_linked = True visited: set[KMod] = set() @@ -1002,13 +1013,15 @@ def cmd_cmp2rpm(options): def main(): global log - log = setup_logging() parser = argparse.ArgumentParser() parser.add_argument('-v', '--verbose', dest='verbose', help='be more verbose', action='count', default=4) parser.add_argument('-q', '--quiet', dest='quiet', help='be more quiet', action='count', default=0) + parser.add_argument('-l', '--log-filename', dest='log_filename', + help='log filename', default='filtermods.log') + subparsers = parser.add_subparsers(dest='cmd') def add_graphviz_arg(p): @@ -1061,7 +1074,9 @@ def main(): options.verbose = options.verbose - 2 options.verbose = max(options.verbose - options.quiet, 0) levels = [NOTSET, CRITICAL, ERROR, WARN, INFO, DEBUG] - log.setLevel(levels[min(options.verbose, len(levels) - 1)]) + stdout_log_level = levels[min(options.verbose, len(levels) - 1)] + + log = setup_logging(options.log_filename, stdout_log_level) ret = 0 if options.cmd == "sort": -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3098

2 2

[OS-BUILD PATCH 0/0] scsi: sd: remove unused sd_probe_types
by Eric Chanudet (via Email Bridge) 07 May '24

07 May '24

From: Eric Chanudet on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3055 NOTE: Truncated patchset due to missing public @redhat.com email address on your GitLab profile at https://gitlab.com/-/profile. Once that is fixed, close and reopen the merge request to retrigger sending the emails. Attend the following warning introduced by a downstream change: ``` drivers/scsi/sd.c:121:20: error: ‘sd_probe_types’ defined but not used [-Werror=unused-variable] 121 | static const char *sd_probe_types[] = { "async", "sync" }; | ^~~~~~~~~~~~~~ ``` Fixes: bc573390ad32 ("scsi: sd: Add "probe_type" module parameter to allow synchronous probing") Signed-off-by: Eric Chanudet <echanude(a)redhat.com> --- drivers/scsi/sd.c | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-)

2 2

[OS-BUILD PATCH] [redhat] rh_messages.h: mark mlx5 on Bluefield-3 as unmaintained
by Scott Weaver (via Email Bridge) 06 May '24

06 May '24

From: Scott Weaver <scweaver(a)redhat.com> [redhat] rh_messages.h: mark mlx5 on Bluefield-3 as unmaintained The mlx5 pci device 0x15B3:0xA2DC should no longer be marked as disabled. This brings the status of this device up-to-date with the hardware removal support project for RHEL-10. Signed-off-by: Scott Weaver <scweaver(a)redhat.com> diff --git a/kernel/rh_messages.h b/kernel/rh_messages.h index blahblah..blahblah 100644 --- a/kernel/rh_messages.h +++ b/kernel/rh_messages.h @@ -260,7 +260,6 @@ static const struct pci_device_id rh_disabled_pci_devices[] = { { 0x15B3, 0x100e, PCI_ANY_ID, PCI_ANY_ID }, { 0x15B3, 0x100f, PCI_ANY_ID, PCI_ANY_ID }, { 0x15B3, 0x1010, PCI_ANY_ID, PCI_ANY_ID }, - { 0x15B3, 0xA2DC, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0064, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0065, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0070, PCI_ANY_ID, PCI_ANY_ID }, @@ -296,6 +295,7 @@ static const struct pci_device_id rh_unmaintained_pci_devices[] = { { 0x1000, 0x0071, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0073, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0079, PCI_ANY_ID, PCI_ANY_ID }, + { 0x15B3, 0xA2DC, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x006E, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0080, PCI_ANY_ID, PCI_ANY_ID }, { 0x1000, 0x0081, PCI_ANY_ID, PCI_ANY_ID }, -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3097

1 0

[OS-BUILD PATCH] redhat/kernel.spec: _buildvars_variant
by Jan Stancek (via Email Bridge) 06 May '24

06 May '24

From: Jan Stancek <jstancek(a)redhat.com> redhat/kernel.spec: _buildvars_variant This introduces a new macro that allows to override variant/config to use for standalone tools/tests build. In SPEC, we support building standalone tools and selftests. Main user are CKI pipelines, which run a native build. Over time however, selftests introduced also kmods, so picking a correct config now matters as well. This patch allows CKI (or other users) to pick a variant when doing standalone tools/tests build. Nothing is changing for builds that include kernel build. Signed-off-by: Jan Stancek <jstancek(a)redhat.com> diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template index blahblah..blahblah 100644 --- a/redhat/kernel.spec.template +++ b/redhat/kernel.spec.template @@ -217,6 +217,12 @@ Summary: The Linux kernel # arm64_64k X X X # realtime X X X +# _buildvars_variant - kernel variant used to initialise build variables +# This variable allows to set variant (and config) that is used when building +# standalone tools and/or tests (with no kernel and no modules). +# See variant parameter to BuildKernel() function. +%define buildvars_variant %{?_buildvars_variant}%{nil} + # kernel-doc %define with_doc %{?_without_doc: 0} %{?!_without_doc: 1} # kernel-headers @@ -2809,10 +2815,11 @@ BuildKernel %make_target %kernel_image %{_use_vdso} %ifnarch noarch i686 %{nobuildarches} %if !%{with_debug} && !%{with_zfcpdump} && !%{with_up} && !%{with_arm64_16k} && !%{with_arm64_64k} && !%{with_realtime} -# If only building the user space tools, then initialize the build environment -# and some variables so that the various userspace tools can be built. +# If only building the user space tools or selftests, then initialize +# the build environment and some variables so that the various userspace +# tools can be built. %{log_msg "Initialize userspace tools build environment"} -InitBuildVars +InitBuildVars %{buildvars_variant} # Some tests build also modules, and need Module.symvers if ! [[ -e Module.symvers ]] && [[ -f $DevelDir/Module.symvers ]]; then %{log_msg "Found Module.symvers in DevelDir, copying to ."} -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3089

1 0

[OS-BUILD PATCH] redhat: move amd-pstate-ut.ko to modules-internal
by Jan Stancek (via Email Bridge) 06 May '24

06 May '24

From: Jan Stancek <jstancek(a)redhat.com> redhat: move amd-pstate-ut.ko to modules-internal amd-pstate-ut is useful for testing but should be limited to the interal rpm. Signed-off-by: David Arcari <darcari(a)redhat.com> Signed-off-by: Jan Stancek <jstancek(a)redhat.com> diff --git a/redhat/rhel_files/def_variants.yaml.rhel b/redhat/rhel_files/def_variants.yaml.rhel index blahblah..blahblah 100644 --- a/redhat/rhel_files/def_variants.yaml.rhel +++ b/redhat/rhel_files/def_variants.yaml.rhel @@ -50,6 +50,7 @@ rules: - drivers/clk/.*test.*: modules-internal - drivers/clk/.*: modules-core - drivers/counter/.*: modules-core + - drivers/cpufreq/amd-pstate-ut.ko: modules-internal - drivers/cpufreq/.*: modules-core - drivers/crypto/caam/.*: modules - drivers/crypto/cavium/.*: modules -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3095

1 0

✅ PASS: Test report for 6.8.9-200.fc39 (fedora-latest)
by cki-project＠redhat.com 04 May '24

04 May '24

Hi, we tested your kernel and here are the results: Overall result: PASSED Merge: OK Compile: OK Test: OK Tested-by: CKI Project <cki-project(a)redhat.com> Kernel information: Brew / Koji Task ID: 117162762 You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:koji-117162762 One or more kernel tests failed: We also see the following known issues which are not related to your changes: Issue: NFS Connectathon: SELinux prevents rpcbind URL: https://bugzilla.redhat.com/1758147 Affected tests: Filesystem - NFS Connectathon [x86_64] If you find a failure unrelated to your changes, please ask the test maintainer to review it. This will prevent the failures from being incorrectly reported in the future. Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________

1 0

[OS-BUILD PATCH] redhat/rhel_files: move tipc.ko and tipc_diag.ko to modules-extra
by Xin Long (via Email Bridge) 03 May '24

03 May '24

From: Xin Long <lxin(a)redhat.com> redhat/rhel_files: move tipc.ko and tipc_diag.ko to modules-extra JIRA: https://issues.redhat.com/browse/RHEL-23931 Upstream Status: RHEL Specific There have been a few TIPC CVE bugs and we see no Red Hat customers using TIPC so far. Per Jianwen's request, move TIPC modules to modules-extra, and prevent auto-loading TIPC modules just because an user triggered it. The sysadmin will have to enable it. Signed-off-by: Xin Long <lxin(a)redhat.com> diff --git a/redhat/rhel_files/def_variants.yaml.rhel b/redhat/rhel_files/def_variants.yaml.rhel index blahblah..blahblah 100644 --- a/redhat/rhel_files/def_variants.yaml.rhel +++ b/redhat/rhel_files/def_variants.yaml.rhel @@ -505,7 +505,7 @@ rules: - net/sctp/.*: modules-extra - net/sunrpc/xprtrdma/rpcrdma.*: modules - net/sunrpc/.*: modules-core - - net/tipc/.*: modules-core + - net/tipc/.*: modules-extra - net/tls/.*: modules-core - net/vmw_vsock/.*: modules-core - net/xdp/.*: modules-core -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3096

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel May 2024