From owner-freebsd-hackers Sat Feb 16 15:40:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-228.dsl.lsan03.pacbell.net [63.207.60.228]) by hub.freebsd.org (Postfix) with ESMTP id CEEC937B400 for ; Sat, 16 Feb 2002 15:40:54 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CEA3866C76; Sat, 16 Feb 2002 15:40:43 -0800 (PST) Date: Sat, 16 Feb 2002 15:40:43 -0800 From: Kris Kennaway To: hackers@FreeBSD.org Subject: Module versioning and linux.ko Message-ID: <20020216154043.A44137@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Is there anything which can be done in -stable to prevent new kernels from accepting old linux.ko modules? At some point in the past 3 months something changed in the kernel causing the old module to panic at runtime in elf_linux_fixup(). Yes, people should be upgrading their old modules when they upgrade the kernel, but it's an obvious source of confusion if you forget or don't realise you're actually using the module. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8bu36Wry0BWjoQKURAqWPAJ0XnCIL3J0EzxWPjbKFqmmvYw/KjgCg28Zs vKCWOfFOBJm7XOcvumTmrD0= =siz5 -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message