> YAMAMOTO Takashi wrote:
> 
> > the lack of locking in fileassoc.  are you kidding?
> >
> > 
> > as you know, veriexec is not only user of fileassoc.
> > do you mean you have investigated all of users and know fileassoc
> > doesn't need to have locking on netbsd-4?  otherwise, why do you claim
> > it isn't a problem?  to me, these users seem to work basically independently,
> > so i think nothing serializes users and thus fileassoc itself needs to
> > have locking internally.
> > am i missing something obvious?  (i guess i am, given that you are
> > an author of all of these fileassoc users.)
> 
> (interesting use of the word "all". :)

?  sorry, i don't understand what you mean.

> besides veriexec there's only segvguard, for which the implementation
> needs to change - it's unsafe even if locking was in place. I pointed
> this out at least two times, and this is why it's disabled by default.
> 
> -e.

is there a PR?

does veriexec serialize calls to fileassoc?

YAMAMOTO Takashi