From: Rongguang Wei <clementwei90@163.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: jasowangio@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
kuba@kernel.org, Rongguang Wei <weirongguang@kylinos.cn>
Subject: Re: [PATCH net v3 1/3] tun: keep a kernel copy of the socket filter program
Date: Fri, 2 Oct 2026 11:25:08 +0800 [thread overview]
Message-ID: <1d0e6066-f6ca-48cf-8665-848167f3dea7@163.com> (raw)
In-Reply-To: <willemdebruijn.kernel.3adc274631629@gmail.com>
on 2026/10/1 02:33, Willem de Bruijn wrote:
> Rongguang Wei wrote:
>> From: Rongguang Wei <weirongguang@kylinos.cn>
>>
>> TUNATTACHFILTER copies only the sock_fprog header, so tun->fprog.filter
>> stays a pointer into the address space of the process that issued the
>> ioctl. tun_attach() reads it again whenever a queue is attached to the
>> persistent device later on: unmapped there, the attach fails with -EFAULT;
>> mapped, whatever bytes it holds become the filter of the new queue.
>>
>> Keep the program in the kernel instead. tun->fprog_kern holds the
>> instructions and each queue gets its own program, built with
>> sk_attach_filter_kern().
>>
>> sk_attach_filter_kern() reads no user buffer and attaches the program like
>> sk_attach_filter() does. The caller must hold the socket lock. Failing the
>> attach releases it; so does the socket when the filter is replaced,
>> detached or the socket goes away.
>>
>> The copy is freed when the filter is detached or replaced and with the
>> device, and tun->fprog is left untouched so TUNGETFILTER keeps its uapi
>> behaviour.
>>
>> Fixes: 54f968d6efdb ("tuntap: move socket to tun_file")
>> Link: https://lore.kernel.org/netdev/179027275318.2160803.4185895144088175048@kernel.org/
>> Signed-off-by: Rongguang Wei <weirongguang@kylinos.cn>
>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
>
>> +int sk_attach_filter_kern(struct sock_fprog_kern *fprog, struct sock *sk)
>> +{
>> + struct bpf_prog *prog;
>> + int err;
>> +
>> + if (sock_flag(sk, SOCK_FILTER_LOCKED))
>> + return -EPERM;
>> +
>> + err = bpf_prog_create(&prog, fprog);
>
> Interesting small issue, not new with this patch:
>
> The BPF program is not validated on copy_from_user, but on attach,
> possibly after the system call has already returned with success.
> Which results in a dev without filter, rather than a failed syscall.
>
Got it, a device with no queues still returns success. I will look at it separately.
Thanks for the review.
>> + if (err)
>> + return err;
>> +
>> + err = __sk_attach_prog(prog, sk);
>> + if (err < 0) {
>> + __bpf_prog_release(prog);
>> + return err;
>> + }
>> +
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(sk_attach_filter_kern);
>> +
>> int sk_reuseport_attach_filter(struct sock_fprog *fprog, struct sock *sk)
>> {
>> struct bpf_prog *prog = __get_filter(fprog, sk);
>> --
>> 2.25.1
>>
>>
>> No virus found
>> Checked by Hillstone Network AntiVirus
>>
>
next prev parent reply other threads:[~2026-10-02 3:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 8:07 [PATCH net v3 0/3] tun: fix re-attaching the socket filter Rongguang Wei
2026-09-30 8:07 ` [PATCH net v3 1/3] tun: keep a kernel copy of the socket filter program Rongguang Wei
2026-09-30 18:33 ` Willem de Bruijn
2026-10-02 3:25 ` Rongguang Wei [this message]
2026-10-01 14:10 ` netdev-bot+sashiko
2026-10-02 3:13 ` Rongguang Wei
2026-09-30 8:07 ` [PATCH net v3 2/3] tun: fix inverted error check when re-attaching the filter Rongguang Wei
2026-09-30 18:34 ` Willem de Bruijn
2026-10-01 14:10 ` netdev-bot+sashiko
2026-10-02 3:17 ` Rongguang Wei
2026-09-30 8:07 ` [PATCH net v3 3/3] selftests: net: add TAP socket filter attach tests Rongguang Wei
2026-09-30 19:20 ` Willem de Bruijn
2026-10-02 3:20 ` Rongguang Wei
2026-10-01 14:10 ` netdev-bot+sashiko
2026-09-30 8:13 ` [PATCH net v3 0/3] tun: fix re-attaching the socket filter netdev-bot+sinfo
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=1d0e6066-f6ca-48cf-8665-848167f3dea7@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