CentOS - Sep 2020 - Tracking or checking backported kernel patches from upstream

Hi!

I'm interested in finding out if a couple of upstream kernel patches were
backported into CentOS (RHEL), in particular this one
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=512ac999d27>
and this one
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=763a9ec06c4>
.

What's the procedure? After reading an article
<https://www.redhat.com/en/blog/what-backporting-and-how-does-it-apply-rhel-and-other-red-hat-products>,
I went into Red Hat's bugzilla, and tried several search terms (including
the kernel's commit ID) but found nothing.

Thanks!

On 9/2/20 9:46 AM, Carlos A. Carnero Delgado wrote:
> Hi!
> 
> I'm interested in finding out if a couple of upstream kernel patches
were
> backported into CentOS (RHEL), in particular this one
>
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=512ac999d27>
> and this one
>
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=763a9ec06c4>
> .
> 
> What's the procedure? After reading an article
>
<https://www.redhat.com/en/blog/what-backporting-and-how-does-it-apply-rhel-and-other-red-hat-products>,
> I went into Red Hat's bugzilla, and tried several search terms
(including
> the kernel's commit ID) but found nothing.
> 
There is not really a 'procedure' to do that . certianly not in CentOS.

The RHEL team currently only publishes the linux-*.tar.gz file in the
SOURCES .. they do not publish individual patches, just the tarball with
the patches already applied.

I see no public way .. other than the changelog of the SRPM, to figure
out what is different.

There may be a way for RHEL customers to see individual patches at
access.redhat.com .. but that is not really a CentOS question.

You CAN do a diff on the exploded tarball from the SRPM and either the
last kernel released (to see what is in this update) .. or the
kernel.org reference kernel .. to see what is different from the
kernel.org release.

If there is a public way to actually see the RHEL patches, I'm sure
someone will post it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20200902/50e8a97e/attachment-0002.sig>

El mi?., 2 de sep. de 2020 a la(s) 11:17, Johnny Hughes (johnny at centos.org)
escribi?:
> There is not really a 'procedure' to do that . certianly not in
CentOS.
>
Eh... poor wording from my part. I meant procedure *for me* to check.

You CAN do a diff on the exploded tarball from the SRPM and either
the
> last kernel released (to see what is in this update) .. or the
> kernel.org reference kernel .. to see what is different from the
> kernel.org release.
>
Yes, that's actually easy in this case.

Thanks a lot!

On 9/2/20 8:17 AM, Johnny Hughes wrote:
> You CAN do a diff on the exploded tarball from the SRPM and either the
> last kernel released (to see what is in this update) .. or the
> kernel.org reference kernel .. to see what is different from the
> kernel.org release.

You can, but expanding two kernels and diffing them consumes a lot of 
disk space and time.

To determine if a specific patch is present, it's a little more 
efficient to use only the CentOS kernel source 
(https://wiki.centos.org/HowTos/I_need_the_Kernel_Source#If_you_really_need_the_full_kernel_source),
and then attempt to apply the patch in question (patch -p1 < 
git-patchfile).? The "patch" application will tell you if it is
already
applied and ask if you want to reverse it, if the patch is already 
present.? If it applies the patch, then it wasn't there already.