Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1200251pxb; Fri, 21 Jan 2022 12:06:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJx4aHBoA78IDhXHiIJSaA9ehDxndJ4Ef6IddSMGSCnC+nPPL7HavB1uwyYL47pTkHoRLbCR X-Received: by 2002:a17:90b:28d:: with SMTP id az13mr2258163pjb.7.1642795581270; Fri, 21 Jan 2022 12:06:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642795581; cv=none; d=google.com; s=arc-20160816; b=A1r0ULhi2uikyljJ4ivZB6AIGU2Oaaue9oypAb8tfNiC/g6TnzJ8dQNUc6+VOziBSP MZmDb2demjDDatscSyWZ6TE7vvJ37eiH+N7t/vkFTha/vw+IUl8a1fWNDqIJRY8ug0j5 ENiuPTGUSTP/s0OpQLSWfckHiEj6c/N/g6lNtllKu6yfLuVIhSBXFP/fBChMI6TUZI7N Pw+f3KE7W8WD3tJ356SvV8ilcXTuUSvvKZTf/vfXxP/XLAPbtfUDwPS2Sw3LahHs/kju tSxLakLA+i8OmJpZ9JhtoFY96ZEbszhFDz4PmvZq9d6M/Mlc4/jFbgDaRNmLbQrTcmA/ ODqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:to:from:cc:in-reply-to:subject:date:dkim-signature; bh=jZ6lVTSSFLFuFM/L+SjIupfkrZNssGv8z3Ianidrykk=; b=SGCygHstPnZDaYMaxvyENkiVu/cAHpb4X2/3kgUpTjBlPllfa9ZAVbiGLAkHBa7Qnp o5TX5sGtSKuWjXSfNA2zLZP1CrG2cJneMK2OXaOgpb7QraDXMf+hoI7AWIxv5VsYjS81 zkNEQB+rSLKWEwths7UpBLOUgXjox5brdlq+FL28LcpxDvcpqKsYv37ikpqaCpOFZKr7 UCoxRMNNOxVedjVceSZz6c3y/tr7NYZeo5UNv33cFXJ74YhvDt60LjmYaZGvKFSbVUpc dbtBdYNjLLjHcu/hrKojW6pbWR8Xklz3H6S5kSakWZKsGLmhqQYqxjoREZsZxAzldeMl cueg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dabbelt-com.20210112.gappssmtp.com header.s=20210112 header.b=T5Ut7gDp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e192si6700710pgc.43.2022.01.21.12.06.09; Fri, 21 Jan 2022 12:06:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@dabbelt-com.20210112.gappssmtp.com header.s=20210112 header.b=T5Ut7gDp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357443AbiASVqU (ORCPT + 99 others); Wed, 19 Jan 2022 16:46:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60638 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1357418AbiASVqT (ORCPT ); Wed, 19 Jan 2022 16:46:19 -0500 Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3BC37C06173E for ; Wed, 19 Jan 2022 13:46:19 -0800 (PST) Received: by mail-pl1-x634.google.com with SMTP id a7so3462334plh.1 for ; Wed, 19 Jan 2022 13:46:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20210112.gappssmtp.com; s=20210112; h=date:subject:in-reply-to:cc:from:to:message-id:mime-version :content-transfer-encoding; bh=jZ6lVTSSFLFuFM/L+SjIupfkrZNssGv8z3Ianidrykk=; b=T5Ut7gDpIfiZ5vSn4GajrcdCDWzj3ncSvpr6z6u/ZHn+J7ACma+MqlbYIBGh6deKu+ AGSqX//MqiJnhFlcxxPXGhsyfGy4OUZt5/o8LkpVe126EQuZ1otC9ZvfvCSyaq5xOigZ 5cNXaMKmqRIOE+fQIwzIpvPLiavpe7QZVSlv401/WOfqOnxY6I+NazU64BPtwtOsDxpj 3H0Hao4uRWffQHJ212dZlw4d92bI0U2aaqU8cd3Uwsx+gcdBJxwzsRw/pjJjrr+qXPez ixx7wBTUnNLEC1vtxF5KOL4CEnwnE3Jpirk2c7r96x4GdSWtrM5oroLNP+PoZb4BHjIP FSSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:subject:in-reply-to:cc:from:to:message-id :mime-version:content-transfer-encoding; bh=jZ6lVTSSFLFuFM/L+SjIupfkrZNssGv8z3Ianidrykk=; b=wM+S0a0k7HeWKLHQSydzA+zEZJ32un9t1uIiWeyv/EB/p9Wecw6geErZkHZbypzW4L fTe7fZGWACFa3rRqJAcQWeBlLF38VfWHsFPHXAJAsiPrIY+je9n5JtH6dvs3SAVjPtrQ DvV1RZkcZ0DU3MS9TVSKXYde4fJYPcSRyzB+PfwbnA6L2wwo4lNmKX30O3HqTl0lkwao XUDsVFxRbX+d9saTCgaRJ4FaifrJ5ZU000JHKRyAtEaqG0oB6Ou43Sbqf2xWFRTgpUb5 JIVes3dDuAkNPIeTdgfhtqVsgDb35YEOcOT8jGtuz0UbfobwYVjAwIi1iDmh7Z7bU7W1 GcIg== X-Gm-Message-State: AOAM53188p8fXJsUaz+N0uTaTqWLQXPXaEoduj6x0P0K1+RDyngn7u1P BPe2cmr9On++/SUH602xue4tvdzSJKtxRA== X-Received: by 2002:a17:90b:1bcc:: with SMTP id oa12mr6853102pjb.4.1642628778470; Wed, 19 Jan 2022 13:46:18 -0800 (PST) Received: from localhost ([12.3.194.138]) by smtp.gmail.com with ESMTPSA id j4sm635045pfc.125.2022.01.19.13.46.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Jan 2022 13:46:17 -0800 (PST) Date: Wed, 19 Jan 2022 13:46:17 -0800 (PST) X-Google-Original-Date: Wed, 19 Jan 2022 13:45:49 PST (-0800) Subject: Re: [PATCH riscv-next] riscv: bpf: Fix eBPF's exception tables In-Reply-To: CC: Bjorn Topel , jszhang@kernel.org, Paul Walmsley , aou@eecs.berkeley.edu, ast@kernel.org, andrii@kernel.org, kafai@fb.com, songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, tongtiangen@huawei.com From: Palmer Dabbelt To: daniel@iogearbox.net Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 19 Jan 2022 10:04:24 PST (-0800), Palmer Dabbelt wrote: > On Wed, 19 Jan 2022 07:59:40 PST (-0800), Bjorn Topel wrote: >> On Wed, 19 Jan 2022 at 16:42, Daniel Borkmann wrote: >>> >> [...] >>> > AFAIK, Jisheng's extable work is still in Palmer's for-next tree. >>> > >>> > Daniel/Alexei: This eBPF must follow commit 1f77ed9422cb ("riscv: >>> > switch to relative extable and other improvements"), which is in >>> > Palmer's tree. It cannot go via bpf-next. >>> >>> Thanks for letting us know, then lets route this fix via Palmer. Maybe he could >>> also add Fixes tags when applying, so stable can pick it up later on. >>> >> >> It shouldn't have a fixes-tag, since it's a new feature for RV. This >> was adapting to that new feature. It hasn't made it upstream yet (I >> hope!). > > That was actually just merged this morning into Linus' tree. I'm still > happy to take the fix via my tree, but you're welcome to take it via a > BPF tree as well. I'm juggling some other patches right now, just LMK > what works on your end. > > IMO it should have a fixes tag: it's a bit of a grey area, but one > something's in I generally try and put those tags on it. That way folks > who try and backport features at least have a shot at finding the fix > (or at least, finding the fix without chasing around the bug ;)). > > I also tried poking you guys on the BPF Slack, but I don't really use it > and I'm not sure if anyone else does either. As per the slack discussion with Daniel, I've put this into the RISC-V for-next tree. Thanks!