[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=wjLWFa3i6+Tab67gnNumTYipj_HuheXr2RCq4zn0tCTzA@mail.gmail.com>
Date: Thu, 30 Jan 2025 08:35:13 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Christian Brauner <brauner@...nel.org>
Cc: Juntong Deng <juntong.deng@...look.com>, Alexander Viro <viro@...iv.linux.org.uk>, ast@...nel.org,
daniel@...earbox.net, john.fastabend@...il.com, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, memxor@...il.com, snorcht@...il.com,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH bpf-next v9 1/5] bpf: Introduce task_file open-coded
iterator kfuncs
On Thu, 30 Jan 2025 at 08:04, Christian Brauner <brauner@...nel.org> wrote:
>
> I deeply dislike that this allows bpf programs to iterate through
> another tasks files more than what is already possible with the
> task_file_seq_* bpf api.
Ack. This needs to just die.
There is no excuse for this, and no, CRIU is absolutely *not* that excuse.
In fact, CRIU is a huge red flag, and has caused endless issues before.
We should absolutely not add special BPF interfaces for CRIU. It only
leads to pain and misery.
Linus
Powered by blists - more mailing lists