> On Sep 15, 2019, at 1:40 AM, [email protected] <[email protected]> wrote:
> 
> Please add a comment explaining that this is for pathnames we can't
> resolve in chroots.

Done. It is not for chroots though.... It is for when we can't resolve vnode to 
name.

> 
> segvguard and veriexec ony use the name for printing error messages.
> I don't think it's necessary to give up on them because of it.
> 
> segvguard even handles a NULL name already.
> 

Fixed.

thanks,

christos

Reply via email to