Date: Fri, 13 Dec 2002 11:57:52 -0500 From: Mike Barcroft <mike@FreeBSD.org> To: Joe Kelsey <joek@mail.flyingcroc.net> Cc: freebsd-current@freebsd.org Subject: Re: Posix Semaphores in -CURRENT Message-ID: <20021213115752.B61753@espresso.q9media.com> In-Reply-To: <3DFA0DAC.2070801@mail.flyingcroc.net>; from joek@mail.flyingcroc.net on Fri, Dec 13, 2002 at 08:41:16AM -0800 References: <3DF8F08E.8050809@mail.flyingcroc.net> <3DFA0771.BDFC87A8@mindspring.com> <3DFA0DAC.2070801@mail.flyingcroc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Kelsey <joek@mail.flyingcroc.net> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021213115752.B61753>