From: Greg KH <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: elver@google.com, keescook@chromium.org, maskray@google.com,
ndesaulniers@google.com, stable-commits@vger.kernel.org,
stable@vger.kernel.org, sashal@kernel.org
Subject: Re: Patch "vmlinux.lds.h: Handle clang's module.{c,d}tor sections" has been added to the 5.13-stable tree
Date: Mon, 16 Aug 2021 10:52:17 +0200 [thread overview]
Message-ID: <YRonQXMxJWfuFXVZ@kroah.com> (raw)
In-Reply-To: <YRmbLz1ZivIMKgc5@archlinux-ax161>
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;a=summary
> >
> > 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
prev parent reply other threads:[~2021-08-16 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16290320662366@kroah.com>
2021-08-15 22:54 ` Patch "vmlinux.lds.h: Handle clang's module.{c,d}tor sections" has been added to the 5.13-stable tree Nathan Chancellor
2021-08-16 8:52 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YRonQXMxJWfuFXVZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=elver@google.com \
--cc=keescook@chromium.org \
--cc=maskray@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox