netdev - Re: [GIT PULL] BPF token for v6.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEf4BzYTZ0KZYc+zgwSdm6h9i0nQAfM_ne8cdMoPJ36c3yNC1A@mail.gmail.com>
Date: Sun, 21 Jan 2024 11:36:36 -0800
From: Andrii Nakryiko <andrii.nakryiko@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrii Nakryiko <andrii@...nel.org>, bpf@...r.kernel.org, netdev@...r.kernel.org, 
	paul@...l-moore.com, brauner@...nel.org, linux-fsdevel@...r.kernel.org, 
	linux-security-module@...r.kernel.org, kernel-team@...a.com
Subject: Re: [GIT PULL] BPF token for v6.8

On Sun, Jan 21, 2024 at 11:27 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Thu, 18 Jan 2024 at 21:00, Andrii Nakryiko <andrii@...nel.org> wrote:
> >
> > This time I'm sending them as a dedicated PR. Please let me know if you are OK
> > pull them directly now, or whether I should target it for the next merge
> > window. If the latter is decided, would it be OK to land these patches into
> > bpf-next tree and then include them in a usual bpf-next PR batch?
>
> So I was keeping this pending while I dealt with all the other pulls
> (and dealt with the weather-related fallout here too, of course).
>
> I've now looked through this again, and I'm ok with it, but notice
> that it has been rebased in the last couple of days, which doesn't
> make me all that happy doing a last-minute pull in this merge window.

Yes, I understand. BPF token patches change common (internal) parts of
libbpf, and so there were conflicts with other libbpf-side changes in
the bpf tree.

>
> End result: I think this might as well go through the bpf-next tree
> and come next merge window through the usual channels.

Sounds good, I'll route it through bpf-next, then. Thanks!

>
> I think Christian's concerns were sorted out too, but in case I'm
> mistaken, just holler.

I believe they were, yes.

>
>                   Linus