Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649

Reply: David Wolfskill : "Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649"
In reply to: David Wolfskill : "Re: Panic: "knote ... was already on knlist..." after main-n284826-d9d7b5948649"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Kyle Evans <kevans_at_FreeBSD.org>
Date: Thu, 02 Apr 2026 14:25:55 UTC

On 4/2/26 08:20, David Wolfskill wrote:
> On Thu, Apr 02, 2026 at 04:01:42PM +0300, Konstantin Belousov wrote:
>> ...
>> Peter Holm already reported this or similar issue.  Try this please.
> 
> Ah.
> 
>> commit 5da1dcf8b88ffa3591a84405a8ab29ebd846f2e0
>> Author: Konstantin Belousov <kib@FreeBSD.org>
>> Date:   Thu Apr 2 14:02:14 2026 +0300
>>
>>      kqueue_fork_copy_knote(): zero kn_knlist for the copy before calling knlist_add()
>> ...
> 
> Change made; works -- thanks!
> 

I know it's not much consolation *after* I've blown up your machines, but I wrote a regression
test that covers this scenario:

https://reviews.freebsd.org/D56223

Thanks,

Kyle Evan