[ remove core@ and source-changes@, add tech-kern@ ]

> YAMAMOTO Takashi wrote:
> >> YAMAMOTO Takashi wrote:
> >>>>> ok, then you mean not to fix it for netbsd-4?
> >>>>>
> >>>>> YAMAMOTO Takashi
> >>>> no, sorry. it's not a problem for netbsd-4.
> >>>>
> >>>> -e.
> >>> i don't understand why it isn't a problem.  can you explain?
> >>>
> >>> YAMAMOTO Takashi
> >> I think I already did.
> > 
> > sorry, where/when?
> > 
> >> can you tell me why it *is* a problem?
> > 
> > because, afaik, there is no difference wrt this problem between
> > netbsd-4 and current.
> > 
> > YAMAMOTO Takashi
> 
> are we talking about the pr itself or the null dereference commit?

i'm talking about the PR.

> whichever one it is, I'd like to see a scenario of where it can be
> a problem.

an example which i told you some time ago:
1. thread A calls fileassoc_file_add and sleeps in malloc.
2. thread B calls fileassoc_file_add and successfully allocates and inserts
   a new entry.
3. thread A wakes up and inserts a duplicated entry.

do you mean it isn't a problem?

YAMAMOTO Takashi