Hi Greg,
On Sun, Aug 15, 2021 at 02:54:26PM +0200, gregkh@linuxfoundation.org wrote:
This is a note to let you know that I've just added the patch titled
vmlinux.lds.h: Handle clang's module.{c,d}tor sections
to the 5.13-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git%3Ba=su...
The filename of the patch is: vmlinux.lds.h-handle-clang-s-module.-c-d-tor-sections.patch and it can be found in the queue-5.13 subdirectory.
Attached are backports for 4.4 to 5.10. I am not sure if anyone is actually using KASAN with clang on 4.4 (ChromeOS maybe?) but it does not hurt to have it just in case.
I did not get any emails that the patch failed to apply on the older versions, I assume this is because I did just a "Cc: stable@vger.kernel.org" without any version or fixes tag. Is there any "official" way to notate that I want a particular patch applied to all supported kernel versions aside from adding "# v4.4+" to the Cc tag so that I can provide manual backports for those versions?
Cheers, Nathan
On Sun, Aug 15, 2021 at 03:54:39PM -0700, Nathan Chancellor wrote:
Hi Greg,
On Sun, Aug 15, 2021 at 02:54:26PM +0200, gregkh@linuxfoundation.org wrote:
This is a note to let you know that I've just added the patch titled
vmlinux.lds.h: Handle clang's module.{c,d}tor sections
to the 5.13-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git%3Ba=su...
The filename of the patch is: vmlinux.lds.h-handle-clang-s-module.-c-d-tor-sections.patch and it can be found in the queue-5.13 subdirectory.
Attached are backports for 4.4 to 5.10. I am not sure if anyone is actually using KASAN with clang on 4.4 (ChromeOS maybe?) but it does not hurt to have it just in case.
I did not get any emails that the patch failed to apply on the older versions, I assume this is because I did just a "Cc: stable@vger.kernel.org" without any version or fixes tag. Is there any "official" way to notate that I want a particular patch applied to all supported kernel versions aside from adding "# v4.4+" to the Cc tag so that I can provide manual backports for those versions?
That comment is exactly how you should ask for that, otherwise I do a "best effort" type of backport and just stop when it does not apply.
Or you can provide a "Fixes:" tag, which will show me exactly how far back to apply patches, and that usually works better as it will catch commits that get backported to older kernels.
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org