From: Z Lim <zlim.lnx@gmail.com>
To: "Shi, Yang" <yang.shi@linaro.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Alexei Starovoitov <ast@kernel.org>,
daniel@iogearbox.net, Xi Wang <xi.wang@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] arm64: bpf: fix JIT stack setup
Date: Tue, 10 Nov 2015 19:11:12 -0800 [thread overview]
Message-ID: <CABg9mct8EnLAZoc5YyM5DFhw1PhdyTysxwsHiq9H5pNXh8ChLw@mail.gmail.com> (raw)
In-Reply-To: <564249A2.1070903@linaro.org>
On Tue, Nov 10, 2015 at 11:46 AM, Shi, Yang <yang.shi@linaro.org> wrote:
> On 11/9/2015 12:00 PM, Z Lim wrote:
>>
>> How about splitting this into two patches? One for the BPF-related
>> bug, and another for A64 FP-handling.
>
> I'm not sure if this is a good approach or not. IMHO, they are kind of
> atomic. Without A64 FP-handling, that fix looks incomplete and introduces
> another problem (stack backtrace).
>
The first, even on its own, doesn't make things worse, only better.
The second, which we agree needs to be fixed also, addresses a different issue.
Either way, please also note that these patches fix the original
implementation. We do want -stable to pick these up.
Suggestions for the diagram:
- As an enhancement, would you mind showing the A64_FP also?
- Please revisit "+64:"
next prev parent reply other threads:[~2015-11-11 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 5:36 [PATCH] arm64: bpf: fix JIT stack setup Yang Shi
2015-11-08 2:27 ` Alexei Starovoitov
2015-11-08 22:29 ` Z Lim
2015-11-09 18:08 ` Shi, Yang
2015-11-09 20:00 ` Z Lim
2015-11-10 19:46 ` Shi, Yang
2015-11-11 3:11 ` Z Lim [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-07 5:34 Yang Shi
2015-11-07 5:55 ` Shi, Yang
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=CABg9mct8EnLAZoc5YyM5DFhw1PhdyTysxwsHiq9H5pNXh8ChLw@mail.gmail.com \
--to=zlim.lnx@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=xi.wang@gmail.com \
--cc=yang.shi@linaro.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).