From: Rongguang Wei <clementwei90@163.com>
To: netdev@vger.kernel.org
Cc: willemdebruijn.kernel@gmail.com, jasowangio@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, kuba@kernel.org,
Rongguang Wei <weirongguang@kylinos.cn>
Subject: [PATCH net v7 0/2] tun: fix re-attaching the socket filter
Date: Fri, 23 Oct 2026 17:22:37 +0800 [thread overview]
Message-ID: <20261023092239.186665-1-clementwei90@163.com> (raw)
From: Rongguang Wei <weirongguang@kylinos.cn>
This is v7 of the series that fixes attaching a queue to a TAP device which
re-installs the socket filter of a persistent device.
Patch 1 keeps a copy of the program in the kernel when it is configured,
instead of reading tun->fprog from user space again on every later attach,
and fixes the inverted error check in tun_attach(). The two changes are
one patch on purpose: with only the kernel copy every re-attach returns 0
without publishing the queue, and with only the check fixed a re-attach
that used to succeed without a filter starts to fail. IFF_NOFILTER keeps
working and is no longer needed to work around the re-attach bug. The
program is verified with bpf_prog_validate_classic() when it is copied in,
so a program that no verifier accepts is rejected even when no queue is
attached.
Patch 2 adds selftests: it re-attaches a queue after the buffer the program
was copied from was made unreadable, attaches a second queue from a fresh
socket to check that the filter is rebuilt from the kernel copy, and checks
that a TUNATTACHFILTER with a bad length or bad instructions keeps the
saved program, plus the ways to attach a queue without a filter.
Thanks to Willem de Bruijn for the reviews, and to the CI reviews for
the comments they raised.
Rongguang Wei (2):
tun: keep a kernel copy of the socket filter program
selftests: net: add TAP socket filter attach tests
---
v7:
- validate the program with bpf_prog_validate_classic() in
tun_copy_filter(), so an invalid program is rejected even when no
queue is attached
- fix the kernel-doc of sk_attach_filter_kern(): drop a reference to a
function that does not exist and complete the Return section
- make bpf_prog_validate_classic() reject a program whose length is out
of range, like bpf_prog_create() does, and say so in its kernel-doc
- document why the filter is dropped when a later step of tun_attach()
fails, and why filter_accept[] has three instructions
- selftests: add a case for a rejected program with valid length and
bad instructions
v6:
- add description for return value of sk_attach_filter_kern(); no code
change is involved
- https://lore.kernel.org/netdev/aa6f8ef9-56d8-4edb-9ae2-d3f3b7dc1721@163.com/
v5:
- add kernel-doc for sk_attach_filter_kern() describing what the missing
original program means for SO_GET_FILTER and sock_diag
- mention in the message that a rejected header now leaves the installed
filter alone
- fix the wording of the mprotect() comment and note what the IFF_NOFILTER
and TUNGETFILTER checks in the re-attach test
- https://lore.kernel.org/netdev/20261012021113.45939-1-clementwei90@163.com/
v4:
- merge the kernel copy and the error check into one patch, so that no
step of the series turns a re-attach into a silent no-op or into a new
failure
- charge the kernel copy to the caller's memory cgroup
- selftests: check that the queue is attached again, and attach a new
queue to see that the filter was installed from the kernel copy
- https://lore.kernel.org/netdev/20261003063859.136895-1-clementwei90@163.com/
v3:
- reorder: the kernel copy of the program comes before the corrected
error check
- add sk_attach_filter_kern() in the patch that first uses it
- address the review of the selftests
- https://lore.kernel.org/netdev/20260930080746.135017-1-clementwei90@163.com/
v2:
- roll back the filter attach when a later step of tun_attach() fails
- keep a copy of the program in the kernel, so that a later attach does
not depend on the address space of the process that set the filter
- add selftests for the re-attach and for a rejected TUNATTACHFILTER
- https://lore.kernel.org/netdev/20260929093712.131096-1-clementwei90@163.com/
v1:
- https://lore.kernel.org/netdev/20260923025653.59348-1-clementwei90@163.com/
---
drivers/net/tun.c | 76 +++++++++-
include/linux/filter.h | 2 +
net/core/filter.c | 62 +++++++++
tools/testing/selftests/net/tun.c | 223 ++++++++++++++++++++++++++++++
4 files changed, 358 insertions(+), 5 deletions(-)
base-commit: 7be4bc52fd9e0e55dc9a2e0232b89427d2c4b614
--
2.43.0
No virus found
Checked by Hillstone Network AntiVirus
next reply other threads:[~2026-10-23 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 9:22 Rongguang Wei [this message]
2026-10-23 9:22 ` [PATCH net v7 1/2] tun: keep a kernel copy of the socket filter program Rongguang Wei
2026-10-23 22:21 ` Willem de Bruijn
2026-10-27 10:09 ` netdev-bot+sashiko
2026-10-27 14:05 ` Willem de Bruijn
2026-10-23 9:22 ` [PATCH net v7 2/2] selftests: net: add TAP socket filter attach tests Rongguang Wei
2026-10-23 22:22 ` Willem de Bruijn
2026-10-27 10:09 ` netdev-bot+sashiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261023092239.186665-1-clementwei90@163.com \
--to=clementwei90@163.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=weirongguang@kylinos.cn \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox