From: Nick Desaulniers <ndesaulniers@google.com>
To: Sasha Levin <sashal@kernel.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: Nathan Huckleberry <nhuck15@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"# 3.4.x" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/4] ARM: backtrace-clang: add fixup for lr dereference
Date: Mon, 3 Aug 2020 11:13:04 -0700 [thread overview]
Message-ID: <CAKwvOdnNud7L9YUmJYDOb71nq+v1+rjSMMbGwkcMZwt6Qr8OxA@mail.gmail.com> (raw)
In-Reply-To: <20200801231815.7817920829@mail.kernel.org>
On Sat, Aug 1, 2020 at 4:18 PM Sasha Levin <sashal@kernel.org> wrote:
>
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: 6dc5fd93b2f1 ("ARM: 8900/1: UNWINDER_FRAME_POINTER implementation for Clang").
>
> The bot has tested the following trees: v5.7.11, v5.4.54.
>
> v5.7.11: Failed to apply! Possible dependencies:
> 5489ab50c227 ("arm/asm: add loglvl to c_backtrace()")
> 99c56f602183 ("ARM: backtrace-clang: check for NULL lr")
>
> v5.4.54: Failed to apply! Possible dependencies:
> 40ff1ddb5570 ("ARM: 8948/1: Prevent OOB access in stacktrace")
> 5489ab50c227 ("arm/asm: add loglvl to c_backtrace()")
> 99c56f602183 ("ARM: backtrace-clang: check for NULL lr")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
Ah, ok, I'll provide manual backports then once this hits mainline.
In that case, should I drop the explicit `Cc: stable...` tag?
(I don't think the dependency on the loglvl should be backported,
which is the source of conflict)
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2020-08-03 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200730205112.2099429-1-ndesaulniers@google.com>
2020-07-30 20:51 ` [PATCH 1/4] ARM: backtrace-clang: check for NULL lr Nick Desaulniers
2020-08-07 18:07 ` Nathan Huckleberry
2020-07-30 20:51 ` [PATCH 2/4] ARM: backtrace-clang: add fixup for lr dereference Nick Desaulniers
2020-08-01 23:18 ` Sasha Levin
2020-08-03 18:13 ` Nick Desaulniers [this message]
2020-08-04 6:27 ` Greg KH
2020-08-06 1:24 ` Sasha Levin
2020-08-06 22:38 ` Nathan Huckleberry
2020-08-10 22:33 ` Nick Desaulniers
2020-08-20 0:13 ` Nick Desaulniers
2020-08-13 16:25 ` Sasha Levin
2020-08-19 23:56 ` Sasha Levin
2020-08-06 1:24 ` [PATCH 0/4] CONFIG_UNWINDER_FRAME_POINTER fixes+cleanups Sasha Levin
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=CAKwvOdnNud7L9YUmJYDOb71nq+v1+rjSMMbGwkcMZwt6Qr8OxA@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=nhuck15@gmail.com \
--cc=sashal@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;
as well as URLs for NNTP newsgroup(s).