tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

re: if_bge.c callout freed before allocation

To: Emmanuel Dreyfus <manu%netbsd.org@localhost>
Subject: re: if_bge.c callout freed before allocation
From: matthew green <mrg%eterna23.net@localhost>
Date: Tue, 06 May 2025 15:12:33 +1000

seems like it would be simpler to simply move the callout_init earlier.
bge_flags also seems like h/w features, putting this in there seems
like, while it uses a spare bit, is the wrong place anyway, but i think
we can simply avoid it by moving the callout_init() earlier.


.mrg.

Follow-Ups:
- Re: if_bge.c callout freed before allocation
  - From: Emmanuel Dreyfus

References:
- if_bge.c callout freed before allocation
  - From: Emmanuel Dreyfus

Prev by Date: xen dom0 using kern.timecounter.hardware=clockinterrupt sees "WARNING: hardclock jumped past timecounter max"
Next by Date: Re: if_bge.c callout freed before allocation
Previous by Thread: if_bge.c callout freed before allocation
Next by Thread: Re: if_bge.c callout freed before allocation
Indexes:

Home | Main Index | Thread Index | Old Index