Re: [PATCH riscv-next] riscv: bpf: Fix eBPF's exception tables

[Palmer Dabbelt]

On Wed, 19 Jan 2022 07:59:40 PST (-0800), Bjorn Topel wrote:
> On Wed, 19 Jan 2022 at 16:42, Daniel Borkmann <daniel@xxxxxxxxxxxxx> 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.