netdev - [PATCH RFC net-next v1] net: Add maintainer entry for netmem & friends

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>] [day] [month] [year] [list]

Message-ID: <20250821025620.552728-1-almasrymina@google.com>
Date: Thu, 21 Aug 2025 02:56:16 +0000
From: Mina Almasry <almasrymina@...gle.com>
To: linux-kernel@...r.kernel.org
Cc: Mina Almasry <almasrymina@...gle.com>, kuba@...nel.org, asml.silence@...il.com, 
	sdf@...ichev.me, byungchul@...com, io-uring@...r.kernel.org, 
	netdev@...r.kernel.org
Subject: [PATCH RFC net-next v1] net: Add maintainer entry for netmem & friends

There is some needless friction with regards to whether netmem_ref,
net_iov, and memory provider patches being CC'd to netdev or not. Add
clear policy and put it in the MAINTAINERS file so get_maintainer.pl
does the right thing by default.

All changes to current and future memory providers should be CC'd to
netdev. The devmem memory provider happens to be under net so is
covered by 'NETWORKING [GENERAL]' as-is. The io_uring memory provider
happens to be outside of net/ though, so add an explicit file entry
for that.

Note that the memory provider changes need _not_ be merged through net
or net-next, but the changes should be CC'd to netdev. Target the
appropriate tree using the [PATCH ...] prefix.

All changes using or modifying netmem_ref or struct net_iov should also
be sent to netdev, so add a content regex for that. Patches modifying
the netmem_ref or net_iov infra should also target net or net-next
([PATCH net] or [PATCH net-next]). This is already the convention.

Note that no maintainers or reviewers are dedicated to this entry.
We don't presume to overburden existing maintainers or add new ones; let
the maintainers nominate folks whenever they feel appropriate. But make
sure changes are sent to the correct lists.

Tested by creating a couple of trivial changes in io_uring/zcrx.[h|c]
and adding netmem_ref and net_iov in other subsystems, and looking at
the get_maintainer.pl results.

Signed-off-by: Mina Almasry <almasrymina@...gle.com>

---

Cc: kuba@...nel.org
Cc: asml.silence@...il.com
Cc: sdf@...ichev.me
Cc: byungchul@...com
Cc: io-uring@...r.kernel.org
Cc: netdev@...r.kernel.org
---
 MAINTAINERS | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 4dcce7a5894b..22c50aeefaa5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17853,6 +17853,17 @@ F:	include/uapi/linux/unix_diag.h
 F:	net/unix/
 F:	tools/testing/selftests/net/af_unix/

+NETWORKING [NETMEM, NET_IOV & MEMORY PROVIDERS]
+L:	netdev@...r.kernel.org
+S:	Maintained
+Q:	https://patchwork.kernel.org/project/netdevbpf/list/
+B:	mailto:netdev@...r.kernel.org
+P:	Documentation/process/maintainer-netdev.rst
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
+F:	io_uring/zcrx.*
+K:	\bnet(mem_ref|_iov)\b
+
 NETXEN (1/10) GbE SUPPORT
 M:	Manish Chopra <manishc@...vell.com>
 M:	Rahul Verma <rahulv@...vell.com>

base-commit: 62a2b3502573091dc5de3f9acd9e47f4b5aac9a1
-- 
2.51.0.rc1.193.gad69d77794-goog