Date: Tue, 24 Jun 2025 10:32:14 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: Michael Tuexen <tuexen@freebsd.org> Cc: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: June 2025 stabilization week Message-ID: <aFrhHmxDOe5NqWq-@cell.glebi.us> In-Reply-To: <6E5A0C58-E096-4EA1-BBC2-E0A66AA13176@FreeBSD.org> References: <aFkJwZgyZXgZkXiX@cell.glebi.us> <6E5A0C58-E096-4EA1-BBC2-E0A66AA13176@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Tue, Jun 24, 2025 at 12:28:25PM +0200, Michael Tuexen wrote: M> I observed one issue when building world/kernel. M> M> In /etc/devfs.conf I have M> M> own bpf* root:network M> perm bpf* 0660 M> M> and this results in M> tuexen@epyc:~ % ls -l /dev/bpf* M> crw-rw---- 1 root network 0x27 Apr 26 20:13 /dev/bpf M> lrwxr-xr-x 1 root wheel 3 Apr 26 20:13 /dev/bpf0 -> bpf M> M> This allows members of the network group to capture traffic. M> M> However, with main-n278173-81e6c0168d46 I get M> tuexen@epyc:~ % ls -l /dev/bpf* M> crw------- 1 root wheel 0x27 Jun 24 12:25 /dev/bpf M> lrwxr-xr-x 1 root wheel 3 Jun 24 12:25 /dev/bpf0 -> bpf M> M> It looks like the devd did not what it did in the past. M> M> Any idea what is going wrong? No idea. Can you please try to downgrade just the devd binary and check that? -- Gleb Smirnoffhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aFrhHmxDOe5NqWq->