From: Coiby Xu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1442#note_721676840
Thanks for the reminding. The change has been rebased.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Coiby Xu
redhat/configs: enable KEXEC_SIG for aarch64 RHEL
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1994858
KEXEC_SIG needs to be enabled for aarch64 so the kernel image's signature
can be verified when loading a kernel image via kexec with secureboot
enabled. Since this
From: Coiby Xu
redhat/configs: enable KEXEC_IMAGE_VERIFY_SIG for RHEL
CONFIG_KEXEC_IMAGE_VERIFY_SIG is enabled so kernel image signature
verification support could be enabled for aarch64. This option has
already been enabled for Fedora.
Signed-off-by: Coiby Xu
diff --git
From: Coiby Xu on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1442
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1994858
KEXEC_SIG needs to be enabled for aarch64 so the kernel image's signature
can be verified when loading a kernel image via
From: Mark Salter on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1442#note_721266539
Acked-by: Mark Salter
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1442#note_721251288
This change needs to be rebased and force pushed. We rebase os-build with
every .0 release, and that was done yesterday.
___
kernel
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1382#note_721117226
That is really a RHEL call, it just seemed the natural thing to do given it
exists. Either way, it needs to be wrapped, because this driver is just as
supported as anything else we
From: Ken Cox on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1382#note_721057450
Justin,
Regarding mark_driver_unsupported, it looks like it only prints a warning.
Don't we need to also set the tainted flag? I was using other unsupported
drivers (mptsas) as a reference.