Joe Kelsey <[EMAIL PROTECTED]> writes:
> Yes, I realize this, but it seems that from my cursory inspection of 
> uipc_sem.c that the check for embedded '/' characters is unnecessary and 
> much too restrictive according to the posix standard.  The standard only 
> talks about whether or not the semaphore name begins with '/' and has 
> nothing to say about embedded slashes except that the name must conform 
> to filename requirements.  It seems to me that either you take the TRU64 
> approach and place a marker in the file system (special directory 
> entry?) or you allow all strings, only looking at the first character 
> and not caring about anything else, except for whatever maximum pathname 
> requirements you choose to impose.
> 
> Maybe I am missing something in the system call semantics?

Sounds like a bug to me.  Could you open a PR?

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to