linux-kernel - Re: [PATCH bpf-next 2/2] umd: Remove usermode driver framework

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: <20250722063328.GA15403@lst.de>
Date: Tue, 22 Jul 2025 08:33:28 +0200
From: Christoph Hellwig <hch@....de>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Alexei Starovoitov <ast@...nel.org>,
	Daniel Borkmann <daniel@...earbox.net>,
	Andrii Nakryiko <andrii@...nel.org>,
	Martin KaFai Lau <martin.lau@...ux.dev>,
	Eduard Zingerman <eddyz87@...il.com>, Song Liu <song@...nel.org>,
	Yonghong Song <yonghong.song@...ux.dev>,
	John Fastabend <john.fastabend@...il.com>,
	KP Singh <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>,
	Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Christoph Hellwig <hch@....de>,
	Linux-Fsdevel <linux-fsdevel@...r.kernel.org>,
	bpf <bpf@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH bpf-next 2/2] umd: Remove usermode driver framework

On Mon, Jul 21, 2025 at 08:51:22AM -0700, Alexei Starovoitov wrote:
> On Mon, Jul 21, 2025 at 2:05 AM Thomas Weißschuh
> <thomas.weissschuh@...utronix.de> wrote:
> >
> > The code is unused since commit 98e20e5e13d2 ("bpfilter: remove bpfilter"),
> > remove it.
> 
> Correct, but we have plans to use it.
> Since it's not causing any problems we prefer to keep it
> to avoid reverting the removal later.

Plans to eventually use something are no reason to keep code that's been
unused for almost 2 years around.  Unless the removal would conflict with
currently queued up in linux-next code it is always better to just drop
it and reinstate it when (or rather usually IFF) it is used again.