From owner-freebsd-current@freebsd.org Sun Nov 8 09:46:59 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 522412EBFC2 for ; Sun, 8 Nov 2020 09:46:59 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CTTmf2Qyyz3DtZ for ; Sun, 8 Nov 2020 09:46:57 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4CTTmc3dqXz6dcf; Sun, 8 Nov 2020 10:46:56 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id r_cMdcWtSv9Q; Sun, 8 Nov 2020 10:46:54 +0100 (CET) Subject: Re: update UPDATING after malloc code change To: gljennjohn@gmail.com Cc: freebsd-current@freebsd.org References: <20201107162050.38fac464@ernst.home> <20201108054855.5006dbfe@ernst.home> From: Guido Falsi Message-ID: Date: Sun, 8 Nov 2020 10:46:53 +0100 In-Reply-To: <20201108054855.5006dbfe@ernst.home> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CTTmf2Qyyz3DtZ X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[159.69.1.99:from]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; MISSING_MIME_VERSION(2.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[159.69.1.99:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2020 09:46:59 -0000 On 08/11/20 06:48, Gary Jennejohn wrote: > On Sun, 8 Nov 2020 00:22:26 +0100 > Guido Falsi wrote: > >> On 07/11/20 17:20, Gary Jennejohn wrote: >>> It seems like an entry should be added to /usr/src/UPDATING, since the change made >>> to the malloc code causes panics with KMODs from ports if they haven't been >>> re-compiled. My nvidia-driver also caused a panic with a new kernel. >>> >>> A reminder/warning would be useful. >>> >> >> Why? Rebuilding kmods every time you update the kernel sources is >> already required by default. >> > > No, it's not. It's an option which can be used, not a requirement. > On head there is no rule about kernel ABI, so any code change could cause old kernel module to require recompiling. When it is known it is sometimes written in UPDATING but there's no requirement. ON stable branches we have a kernel ABI rule that this should not happen (but it happens anyway sometimes for many reasons. -- Guido Falsi