On Sun, Jul 17, 2022 at 4:17 PM stan via kernel
<kernel(a)lists.fedoraproject.org> wrote:
On Sun, 17 Jul 2022 11:40:14 -0700
stan <upaitag(a)zoho.com> wrote:
> I'll be building the rc6 kernel with the new option enabled to see if
> that fixes things, but the kernel should still run even if the
> automatic mitigation is turned off. Should I open a bugzilla for
> this?
I built a kernel with the automatic mitigation turned on, same behavior.
I then commented out all the rtla related code in the spec file, and
turned off the mitigation, and still the same behavior.
rtla is a binary for kernel-tools, it is a subpackage, and has no
bearing at all on the running kernel, it is a userspace binary built
separately. For Fedora, this part is built in the kernel-tools
package.
The only other change I see is removing cpufreq.h from the headers,
but
I don't think that would cause an error.
Also a bit that would have no bearing on building a kernel, it is only
used to build userspace utilities.
So, stumped.
There were unfortunately some corner cases with retbleed mitigation
that simply did not work. Most of those should have been worked out
over the past week, but due to the way the embargo was done, there was
a whole lot of testing that just couldn't happen before the code was
merged. As this is your rebuild, the first thing I would do is see if
the proper fedora build boots on this system, and I would not work
with anything pre rc7 at this point. Doing so ensures that you are
missing valid fixes. If the fedora build boots and your build does
not, that is an interesting case to investigate. If the fedora build
does not, that should be filed as a bug and figured out as 5.19 will
be the F37 kernel.
Justin