kernel

kernel@lists.fedoraproject.org

4833 discussions

Kernel 6.9 Test Week is underway
by Sumantro Mukherjee 29 May '24

29 May '24

Hey Folks, We are currently running the Kernel 6.9 Test Week[0] and this is an awesome opportunity to come and contribute to Fedora! If you are interested and have some spare time, feel free to join us and submit reports here[1] [0] http://fedoraproject.org/wiki/Test_Day:2024-05-26_Kernel_6.9_Test_Week [1] https://testdays.fedoraproject.org/events/187 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

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

27 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: 118124586 You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:koji-118124586 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

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

18 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: 117824283 You can find all the details about the test run at https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:koji-117824283 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

The kernel-ark os-build branch has been rebased
by Justin Forbes 13 May '24

13 May '24

Please rebase any pending MRs and repush. As we have done since 5.15, we have done this again for os-build, we expect to keep it up as a cadence with every upstream release. This means we will do it again when 6.10 releases, and again with 6.11... It is difficult to manage a regularly rebased tree, because any outstanding MR is invalidated and has to also be rebased. But not doing somewhat regular rebases can also be difficult in the spirit of the openness that Fedora is based upon. While there are plenty of ways to see which patches we carry compared to upstream, some of those patches are fairly old, and would not apply cleanly at all to a modern tree after several releases were merged in with them. As we have gotten into a flow of things with merge requests, we can get to the point of very few outstanding MRs towards the end of a release cycle, and that makes it an opportune time to rebase the tree. This also means that the patches we carry should be no more than 1 release out of date, making them easier to apply to various other trees. I do realize that this is a minor inconvenience every 2-3 months, but I believe the results are worth it. Thanks, Justin

1 0

[OS-BUILD PATCHv4 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 (6): 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 include/linux/rh_flags.h | 34 ++++++++++++ kernel/Makefile | 2 +- kernel/module/main.c | 6 ++ kernel/rh_features.c | 116 +++++++++++++++++++++++++++++++++++++++ kernel/rh_flags.c | 116 +++++++++++++++++++++++++++++++++++++++ 5 files changed, 273 insertions(+), 1 deletion(-) create mode 100644 include/linux/rh_flags.h create mode 100644 kernel/rh_features.c create mode 100644 kernel/rh_flags.c Signed-off-by: Ricardo Robaina <rrobaina(a)redhat.com>

1 0

[OS-BUILD PATCH] redhat/configs: remove CONFIG_DMA_PERNUMA_CMA and switch CONFIG_DMA_NUMA_CMA off
by Jerry Snitselaar (via Email Bridge) 13 May '24

13 May '24

From: Jerry Snitselaar <jsnitsel(a)redhat.com> redhat/configs: remove CONFIG_DMA_PERNUMA_CMA and switch CONFIG_DMA_NUMA_CMA off CONFIG_DMA_PERNUMA_CMA was replaced by CONFIG_DMA_NUMA_CMA, so remove the old, and continue to leave off with CONFIG_DMA_NUMA_CMA. Signed-off-by: Jerry Snitselaar <jsnitsel(a)redhat.com> diff --git a/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA b/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA index blahblah..blahblah 100644 --- a/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA +++ b/redhat/configs/common/generic/CONFIG_DMA_NUMA_CMA @@ -1 +1 @@ -CONFIG_DMA_NUMA_CMA=y +# CONFIG_DMA_NUMA_CMA is not set diff --git a/redhat/configs/common/generic/CONFIG_DMA_PERNUMA_CMA b/redhat/configs/common/generic/CONFIG_DMA_PERNUMA_CMA deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/common/generic/CONFIG_DMA_PERNUMA_CMA +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_DMA_PERNUMA_CMA is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3099

3 4

[OS-BUILD PATCH] redhat/configs: enable RTL8822BU for rhel
by José Ignacio Tornos Martínez (via Email Bridge) 13 May '24

13 May '24

From: Jose Ignacio Tornos Martinez <jtornosm(a)redhat.com> redhat/configs: enable RTL8822BU for rhel RTL8822BU Realtek WiFi USB device (CONFIG_RTW88_8822BU) has been requested to be enabled for rhel. Unify configuration with fedora (it was previously enabled). Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm(a)redhat.com> diff --git a/redhat/configs/fedora/generic/CONFIG_RTW88_8822BU b/redhat/configs/common/generic/CONFIG_RTW88_8822BU rename from redhat/configs/fedora/generic/CONFIG_RTW88_8822BU rename to redhat/configs/common/generic/CONFIG_RTW88_8822BU index blahblah..blahblah 100644 --- a/redhat/configs/fedora/generic/CONFIG_RTW88_8822BU +++ b/redhat/configs/common/generic/CONFIG_RTW88_8822BU diff --git a/redhat/configs/rhel/generic/CONFIG_RTW88_8822BU b/redhat/configs/rhel/generic/CONFIG_RTW88_8822BU deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/rhel/generic/CONFIG_RTW88_8822BU +++ /dev/null @@ -1 +0,0 @@ -# CONFIG_RTW88_8822BU is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3085

2 2

[OS-BUILD PATCHv3 0/2] configs: add CONFIG_BLK_SED_OPAL and CONFIG_BLK_DEV_UBLK
by Ming Lei (via Email Bridge) 13 May '24

13 May '24

From: Ming Lei on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3071 We plan to support both two in cs10. Signed-off-by: Ming Lei <ming.lei(a)redhat.com> --- redhat/configs/fedora/generic/CONFIG_BLKDEV_UBLK_LEGACY_OPCODES => redhat/configs/common/generic/CONFIG_BLKDEV_UBLK_LEGACY_OPCODES | 0 redhat/configs/fedora/generic/CONFIG_BLK_DEV_UBLK => redhat/configs/common/generic/CONFIG_BLK_DEV_UBLK | 0 redhat/configs/fedora/generic/CONFIG_BLK_SED_OPAL => redhat/configs/common/generic/CONFIG_BLK_SED_OPAL | 0 redhat/configs/rhel/generic/CONFIG_BLK_DEV_UBLK => redhat/configs/rhel/generic/s390x/zfcpdump/CONFIG_BLK_DEV_UBLK | 0 redhat/configs/rhel/generic/CONFIG_BLK_SED_OPAL | 1 - 5 files changed, 0 insertions(+), 1 deletions(-)

3 4

[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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel