On Sun, Apr 24, 2016 at 03:34:53PM +0200, Joerg Sonnenberger wrote:
> > That wasn't the question -- the question is what the semantics of
> > sem_open() names are supposed to be.
>
> They don't really have any. They are an independent namespace and the
> ENAMETOOLONG error was actually added
On Sat, Apr 23, 2016 at 09:12:43PM +, David Holland wrote:
> On Sat, Apr 23, 2016 at 10:42:52PM +0200, Kamil Rytarowski wrote:
> > >> I read in the POSIX resources that the limit is defined by
> > >> PATH_MAX or its variation:
> > >>
> > >> ENAMETOOLONG The length of the name argument exce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.04.2016 23:52, David Holland wrote:
> On Sat, Apr 23, 2016 at 09:12:43PM +, David Holland wrote:
> Additionally I noted that SEM_VALUE_MAX is defined at least
> twice in the code-base, in and
> sys/kern/uipc_sem.c (thankfully w
On Sat, Apr 23, 2016 at 09:12:43PM +, David Holland wrote:
> > >> Additionally I noted that SEM_VALUE_MAX is defined at least twice
> > >> in the code-base, in and sys/kern/uipc_sem.c
> > >> (thankfully with the same value: ~0U).
> > >
> > > That would be a bug.
>
> namely: pleas
On Sat, Apr 23, 2016 at 10:42:52PM +0200, Kamil Rytarowski wrote:
> >> I read in the POSIX resources that the limit is defined by
> >> PATH_MAX or its variation:
> >>
> >> ENAMETOOLONG The length of the name argument exceeds {PATH_MAX}
> >> or a pathname component is longer than {NAME_MAX}.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 23.04.2016 20:55, David Holland wrote:
> On Sat, Apr 23, 2016 at 06:06:10PM +0200, Kamil Rytarowski wrote:
>> The sem_open(2) function call reports an error for a too long
>> name and sets errno:
>>
>> [ENAMETOOLONG] The name argument is too
On Sat, Apr 23, 2016 at 06:06:10PM +0200, Kamil Rytarowski wrote:
> The sem_open(2) function call reports an error for a too long name and
> sets errno:
>
> [ENAMETOOLONG] The name argument is too long.
...as it should.
> The limit is held privately in the kernel:
>
> sys/kern/uipc_s
