Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752070AbbKKDLO (ORCPT ); Tue, 10 Nov 2015 22:11:14 -0500 Received: from mail-io0-f169.google.com ([209.85.223.169]:36069 "EHLO mail-io0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751612AbbKKDLN (ORCPT ); Tue, 10 Nov 2015 22:11:13 -0500 MIME-Version: 1.0 In-Reply-To: <564249A2.1070903@linaro.org> References: <1446874577-14539-1-git-send-email-yang.shi@linaro.org> <20151108022726.GB39441@ast-mbp.thefacebook.com> <5640E135.2020007@linaro.org> <564249A2.1070903@linaro.org> Date: Tue, 10 Nov 2015 19:11:12 -0800 Message-ID: Subject: Re: [PATCH] arm64: bpf: fix JIT stack setup From: Z Lim To: "Shi, Yang" Cc: Alexei Starovoitov , Catalin Marinas , Will Deacon , Alexei Starovoitov , daniel@iogearbox.net, Xi Wang , LKML , Network Development , "linux-arm-kernel@lists.infradead.org" , linaro-kernel@lists.linaro.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1043 Lines: 25 On Tue, Nov 10, 2015 at 11:46 AM, Shi, Yang 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:" -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/