Subject: Re: kern/25118: semop() fails with EINVAL even when SEMUME is increased
To: enami tsugutomo <email@example.com>
From: Simon Burge <firstname.lastname@example.org>
Date: 04/10/2004 14:20:20
enami tsugutomo wrote:
> > It appears that seminfo.semume isn't changable (unless you mean changing
> > it with say gdb --write). I think the original patch in the PR has the
> > right effect otherwise. That said, it looks like changing SEMU to use
> > seminfo.semume instead of SEMUME would be a good idea.
> Simply sysv_sem.c wasn't recompiled since it doesn't include
> opt_sysvparam.h, was it?
I thought about that too. I think technically param.c is meant to have
the changable parameters, and sysv_sem.c should just use what is in
seminfo and not look at predefined constants.
This gets back to the "do we want a somehow modified seminfo" to work
(with "gdb --write" or a newly introduced system call or possibly a
superuser-only semctl command)?
Simon Burge <email@example.com>
NetBSD Support and Service: http://www.wasabisystems.com/