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
| ||
|
Message-ID: <CAHk-=whBBWGaQy=rtS2Ma6QPqbQ+jEUKUWfF2zS7gDXpim11bA@mail.gmail.com> Date: Mon, 18 Dec 2023 17:17:05 -0800 From: Linus Torvalds <torvalds@...uxfoundation.org> To: Jakub Kicinski <kuba@...nel.org> Cc: Alexei Starovoitov <alexei.starovoitov@...il.com>, davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, daniel@...earbox.net, andrii@...nel.org, peterz@...radead.org, brauner@...nel.org, netdev@...r.kernel.org, bpf@...r.kernel.org, kernel-team@...com, linux-kernel@...r.kernel.org Subject: Re: pull-request: bpf-next 2023-12-18 On Mon, 18 Dec 2023 at 16:55, Jakub Kicinski <kuba@...nel.org> wrote: > > LGTM, but what do I know about file systems.. Adding LKML to the CC > list, if anyone has any late comments on the BPF token come forward > now, petty please? See my crossed email reply. The file descriptor handling is FUNDAMENTALLY wrong. The first time that happened, we chalked it up to a mistake. Now it's something worse. Please don't pull until at least that part is fixed. I tried to review the token patches, but honestly, I got to that part and I just gave up. We had this whole discussion more than 6 months ago: https://lore.kernel.org/all/20230517-allabendlich-umgekehrt-8cc81f8313ac@brauner/ and I really thought the bpf people had *understood* they their special use of "fd == 0" was wrong. But it seems that they never did. Once is a mistake. Twice is a choice. And the bpf people have chosen insanity. Linus
Powered by blists - more mailing lists