Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Nov 2020 10:51:30 +0100
From:      Guido Falsi <mad@madpilot.net>
To:        junchoon@dec.sakura.ne.jp, freebsd-current@freebsd.org
Subject:   Re: update UPDATING after malloc code change
Message-ID:  <0b0bc9fd-7377-63a6-cc08-8498d43a3c51@madpilot.net>
In-Reply-To: <20201108094336.4638ce33f22bf408cda31e52@dec.sakura.ne.jp>
References:  <20201107162050.38fac464@ernst.home> <b4981e58-60e8-3f02-2bfe-a1cef8bc135e@madpilot.net> <20201108094336.4638ce33f22bf408cda31e52@dec.sakura.ne.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
On 08/11/20 01:43, Tomoaki AOKI wrote:
> On Sun, 8 Nov 2020 00:22:26 +0100
> Guido Falsi <mad@madpilot.net> 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.
> 

Sure that would be kind, I just wanted to point out that it's not a 
requirement or a mandatory thing.

Kernel ABI breakage also happens unknowingly sometimes!


-- 
Guido Falsi <mad@madpilot.net>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b0bc9fd-7377-63a6-cc08-8498d43a3c51>