Greetings testers!
Please join us for upcoming Test Days [1] and help us improve Fedora’s quality and stability. Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users.
This time, we’ll focus on the kernel 6.17 in Fedora 42.
Test period: 2025-10-12 to 2025-10-18
Test instructions: https://fedoraproject.org/wiki/Test_Day:2025-10-12_Kernel_6.17_Test_Week
Thank you for your contributions!
Kamil Paral
Fedora Quality
Correction here. All F43 testing has been with kernel 6.17. The purpose of test week is to test F42 with the 6.17 kernel as a rebase candidate. Though the kernel is the same, it is possible that there is different userspace interaction with F42.
Thanks, I corrected the announcement and the wiki page.
koji list-builds --package=kernel --after="2025-10-01" --pattern "kernel-6.17*" gives me a:
Build Built by State
------------------------------------------------------- ---------------- ----------------
kernel-6.17.1-300.fc43 jforbes COMPLETE
Did I understand correct? Even if it is declared as .fc43 we can go for it on F42?
I wonder - this topic is currently unlisted, i.e. it should be invisible. How did both of you actually find it?
I am TL4 so i can see unlisted topics.
p.s. i checked the wiki you mentioned .. there it displays F42 for the kernel … and I get just the F43 one.
It’s not prepared yet. Justin will be creating the right builds in the next few days.
I don’t visit the website really at all, it showed up in my emai.
Hah, I see. That’s because I create it as a regular topic and then immediately hide it (unlist it). I’m not able to create it hidden right away. That’s fine, it’s a corner case I have no issue with 
Everything ready now 
:
koji list-builds --package=kernel --after="2025-10-01" --pattern "kernel-6.17*"
Build Built by State
------------------------------------------------------- ---------------- ----------------
kernel-6.17.1-300.fc43 jforbes COMPLETE
kernel-6.17.1-300.fc42 jforbes COMPLETE
I can see it too as TL3
6.17.1 is going great for me
Been using it over the weekend and seems to more stable for me than the 6.16 series so far.
I made tests as here:
sudo ./runtests.sh
Test suite called with default
./default/cachedrop PASS
./default/insert_leap_second PASS
./default/libhugetlbfs SKIP
./default/memfd SKIP
./default/modsign PASS
./default/mq-memory-corruption PASS
./default/paxtest SKIP
./default/posix_timers PASS
./default/selinux-dac-controls PASS
./default/stack-randomness PASS
./default/sysfs-perms PASS
./default/timer-overhead PASS
Test suite complete PASS
Then got error while transmitting the results (I changed to submit=authenticated in .config):
Running Firefox as root in a regular user's session is not supported
I guess there it needs some fix, avoid running firefox as sudo/root?
I tested my default hardware by installing on the daily machine (even if we should not, but I have a backup system).
It should provide a link for you to click on normally.
Changed back to submit=anonymous and got the result:
sudo ./runtests.sh
Test suite called with default
./default/cachedrop PASS
./default/insert_leap_second PASS
./default/libhugetlbfs SKIP
./default/memfd SKIP
./default/modsign PASS
./default/mq-memory-corruption PASS
./default/paxtest SKIP
./default/posix_timers PASS
./default/selinux-dac-controls PASS
./default/stack-randomness PASS
./default/sysfs-perms PASS
./default/timer-overhead PASS
Test suite complete PASS
Your log file is being submitted...
{"message":"Upload successful!"}
The following information is not submitted with your log;
it is for informational purposes only.
Vulnerability status:
/sys/devices/system/cpu/vulnerabilities/gather_data_sampling:Not affected
/sys/devices/system/cpu/vulnerabilities/ghostwrite:Not affected
/sys/devices/system/cpu/vulnerabilities/indirect_target_selection:Not affected
/sys/devices/system/cpu/vulnerabilities/itlb_multihit:KVM: Mitigation: Split huge pages
/sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
/sys/devices/system/cpu/vulnerabilities/mds:Mitigation: Clear CPU buffers; SMT vulnerable
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/mmio_stale_data:Not affected
/sys/devices/system/cpu/vulnerabilities/old_microcode:Not affected
/sys/devices/system/cpu/vulnerabilities/reg_file_data_sampling:Not affected
/sys/devices/system/cpu/vulnerabilities/retbleed:Not affected
/sys/devices/system/cpu/vulnerabilities/spec_rstack_overflow:Not affected
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
/sys/devices/system/cpu/vulnerabilities/srbds:Vulnerable: No microcode
/sys/devices/system/cpu/vulnerabilities/tsa:Not affected
/sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected
/sys/devices/system/cpu/vulnerabilities/vmscape:Mitigation: IBPB before exit to userspace