On Fri, Apr 05, 2024 at 09:21:15AM -0700, Andrii Nakryiko wrote:
> On Fri, Apr 5, 2024 at 9:15 AM Andrii Nakryiko
> <andrii.nakryiko@xxxxxxxxx> wrote:
> >
> > On Fri, Apr 5, 2024 at 2:50 AM <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > >
> > >
> > > The patch below does not apply to the 6.8-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@xxxxxxxxxxxxxxx>.
> > >
> >
> > This is strange, I get a clean auto-merged cherry-pick:
> >
> > $ git co linux-6.8.y
> > Updating files: 100% (10694/10694), done.
> > branch 'linux-6.8.y' set up to track 'stable/linux-6.8.y'.
> > Switched to a new branch 'linux-6.8.y'
> > $ git cp -x 1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce
> > Auto-merging include/linux/bpf.h
> > Auto-merging kernel/bpf/syscall.c
> > Auto-merging kernel/trace/bpf_trace.c
> > [linux-6.8.y fd74c60792f5] bpf: support deferring bpf_link dealloc to
> > after RCU grace period
> > Date: Wed Mar 27 22:24:26 2024 -0700
> > 3 files changed, 49 insertions(+), 6 deletions(-)
> >
> > Note that e9c856cabefb ("bpf: put uprobe link's path and task in
> > release callback") has to be backported at the same time. I'll
> > cherry-pick both and will send it just in case.
> >
>
> Ah, so it doesn't build (trivial link->prog->sleepable ->
> link->prog->aux->sleepable change, will fix up). Not sure if possible,
> but it would be nice to distinguish between patch not applying vs it
> causing build (or test) failures, but no big deal.
I only have 1 script, sorry :)
thanks,
greg k-h
