Bug 1958250 - 6-month lookback for kpatch [NEEDINFO]
Summary: 6-month lookback for kpatch
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: doc-Release_Notes-8-en-US
Version: 8.5
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: beta
: 8.5
Assignee: Lucie Vařáková
QA Contact: RHEL DPM
Jana Heves
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-07 14:04 UTC by Jaroslav Klech
Modified: 2022-11-04 10:02 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Deprecated Functionality
Doc Text:
.Kernel live patching now covers all RHEL minor releases Since RHEL 8.1, kernel live patches have been provided for selected minor release streams of RHEL covered under the Extended Update Support (EUS) policy to remediate Critical and Important Common Vulnerabilities and Exposures (CVEs). To accommodate the maximum number of concurrently covered kernels and use cases, the support window for each live patch has been decreased from 12 to 6 months for every minor, major, and zStream version of the kernel. It means that on the day a kernel live patch is released, it will cover every minor release and scheduled errata kernel delivered in the past 6 months. For more information about this feature, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/applying-patches-with-kernel-live-patching_managing-monitoring-and-updating-the-kernel[Applying patches with kernel live patching]. For details about available kernel live patches, see link:https://access.redhat.com/articles/4499631[Kernel Live Patch life cycles].
Clone Of:
Environment:
Last Closed: 2021-12-09 13:22:24 UTC
Type: Bug
Target Upstream Version:
jsvarova: needinfo? (rhandlin)
jsvarova: needinfo? (rhandlin)


Attachments (Terms of Use)

Description Jaroslav Klech 2021-05-07 14:04:07 UTC
Change in kernel live patch lookback needs to be documented in RHEL kernel release notes.


Note You need to log in before you can comment on or make changes to this bug.