From owner-freebsd-current@freebsd.org Sun Nov 8 00:43:46 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 8099F2D7406 for ; Sun, 8 Nov 2020 00:43:46 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CTFjs2Yjmz4WM2 for ; Sun, 8 Nov 2020 00:43:44 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (115-38-187-204.shizuoka1.commufa.jp [115.38.187.204]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id 0A80hacW000838 for ; Sun, 8 Nov 2020 09:43:36 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sun, 8 Nov 2020 09:43:36 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: update UPDATING after malloc code change Message-Id: <20201108094336.4638ce33f22bf408cda31e52@dec.sakura.ne.jp> In-Reply-To: References: <20201107162050.38fac464@ernst.home> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CTFjs2Yjmz4WM2 X-Spamd-Bar: + X-Spamd-Result: default: False [1.89 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[210.188.226.8:from]; ASN(0.00)[asn:9370, ipnet:210.188.224.0/19, country:JP]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[115.38.187.204:received]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.67)[-0.674]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(1.00)[0.997]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[210.188.226.8:from:127.0.2.255]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_LONG(0.16)[0.163]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; 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 00:43:46 -0000 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. IIRC, there's no official documentation for it. Adding new NOTE for it into UPDATING (before the first dated entry) would be a good idea, as someone encounterd problem would read it to confirm any cautions. > You should be surprised when the old kmods still work, not the other way > around. +1. > > -- > Guido Falsi > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Tomoaki AOKI