Date: Thu, 2 Jan 2025 18:15:39 +0800 From: Zhenlei Huang <zlei@FreeBSD.org> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Cc: Miroslav Lachman <000.fbsd@quip.cz>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Should kernel modules be executable? Message-ID: <1CF31C37-9177-4267-8387-2E5089DDC2F9@FreeBSD.org> In-Reply-To: <8634i1r3f9.fsf@ltc.des.dev> References: <5120eb91-86c1-4c60-8d73-cbc46689669a@quip.cz> <10B8CED2-104F-4047-AED0-2B270CECB258@FreeBSD.org> <8634i1r3f9.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
> On Jan 2, 2025, at 5:05 PM, Dag-Erling Smørgrav <des@FreeBSD.org> wrote: > > Zhenlei Huang <zlei@FreeBSD.org> writes: >> Miroslav Lachman <000.fbsd@quip.cz> writes: >>> Previously there were about 25 files with permission r-xr-xr-x and >>> 871 with other permissions (mainly -r--r--r--). >>> But on the FreeBSD 14.2 (upgraded by freebsd-update), there are 809 >>> files with r-xr-xr-x permission and only 66 with other permissions >>> (63 with r--r--r--) >> Yes, indeed. The permission of kernel modules was changed from 555 to >> KMODMODE ( NOBINMODE, 444 ). See https://reviews.freebsd.org/D42768 >> for more context. > > And yet the observed change is the opposite. > > Looking at a 14.2 kernel tarball, the modules are not executable, but on > a 14.2 system updated from an earlier release using freebsd-update, they > are. I also observed this. `freebsd-upgrade IDS` reported the issue and I manually fixed the *wrong* permissions. > > DES > -- > Dag-Erling Smørgrav - des@FreeBSD.orghome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1CF31C37-9177-4267-8387-2E5089DDC2F9>