History log of /freebsd/sys/kern/sysv_sem.c (Results 226 – 250 of 293)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0
# f5925b74 19-Dec-2003 Tim J. Robbins <tjr@FreeBSD.org>

Reduce the overhead of semop() by using the kernel stack instead of
malloc'd memory to store the operations array if it is small enough
to fit.


# 4d93f53e 15-Nov-2003 Tim J. Robbins <tjr@FreeBSD.org>

Initialize sequence numbers to 0 in seminit() instead of using whatever
garbage happens to be in memory. This did not seem to cause any problems
except making semaphore ID's unpredictable (and ugly i

Initialize sequence numbers to 0 in seminit() instead of using whatever
garbage happens to be in memory. This did not seem to cause any problems
except making semaphore ID's unpredictable (and ugly in ipcs(1) output).

show more ...


# 541c3b66 10-Nov-2003 Tim J. Robbins <tjr@FreeBSD.org>

When there are no free sem_undo structs available in semu_alloc(), only
free one sem_undo with un_cnt == 0 instead of all of them. This is a
temporary workaround until the SLIST_FOREACH_PREVPTR loop

When there are no free sem_undo structs available in semu_alloc(), only
free one sem_undo with un_cnt == 0 instead of all of them. This is a
temporary workaround until the SLIST_FOREACH_PREVPTR loop gets fixed so
that it doesn't cause cycles in semu_list when removing multiple adjacent
items. It might be easier to just use (doubly-linked) LISTs here instead
of complicated SLIST code to achieve O(1) removals.

This bug manifested itself as a complete lockup under heavy semaphore use
by multiple processes with the SEM_UNDO flag set.

PR: 58984

show more ...


# a2f88a8b 07-Nov-2003 Robert Watson <rwatson@FreeBSD.org>

Slight whitespace consistency improvement:
Trim trailing whitespace.
Remove unmatched " " before ")".


Revision tags: release/4.9.0_cvs, release/4.9.0
# 184dcdc7 21-Oct-2003 Mike Silbersack <silby@FreeBSD.org>

Change all SYSCTLS which are readonly and have a related TUNABLE
from CTLFLAG_RD to CTLFLAG_RDTUN so that sysctl(8) can provide
more useful error messages.


# 01b9dc96 07-Aug-2003 Jacques Vidrine <nectar@FreeBSD.org>

Update some argument-documenting comments to match reality.

Add an explicit range check to those same arguments to reduce risk of
cardiac arrest in future code readers.


# 677b542e 11-Jun-2003 David E. O'Brien <obrien@FreeBSD.org>

Use __FBSDID().


Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0
# 75b8b3b2 24-Mar-2003 John Baldwin <jhb@FreeBSD.org>

Replace the at_fork, at_exec, and at_exit functions with the slightly more
flexible process_fork, process_exec, and process_exit eventhandlers. This
reduces code duplication and also means that I do

Replace the at_fork, at_exec, and at_exit functions with the slightly more
flexible process_fork, process_exec, and process_exit eventhandlers. This
reduces code duplication and also means that I don't have to go duplicate
the eventhandler locking three more times for each of at_fork, at_exec, and
at_exit.

Reviewed by: phk, jake, almost complete silence on arch@

show more ...


# a163d034 19-Feb-2003 Warner Losh <imp@FreeBSD.org>

Back out M_* changes, per decision of the TRB.

Approved by: trb


# af7cbce8 29-Jan-2003 Tim J. Robbins <tjr@FreeBSD.org>

Fix two fatal signedness errors introduced when i and j in semop()
were changed from int to size_t in the previous revision.

PR: 47625


# 3beb3270 25-Jan-2003 Alfred Perlstein <alfred@FreeBSD.org>

Bring semop() closer the the opengroup standards.

PR: 47471
Submitted by: Craig Rodrigues <rodrigc@attbi.com>


# 44956c98 21-Jan-2003 Alfred Perlstein <alfred@FreeBSD.org>

Remove M_TRYWAIT/M_WAITOK/M_WAIT. Callers should use 0.
Merge M_NOWAIT/M_DONTWAIT into a single flag M_NOWAIT.


Revision tags: release/5.0.0_cvs, release/5.0.0
# 871de19f 19-Oct-2002 Alfred Perlstein <alfred@FreeBSD.org>

Don't leak memory in semop(2). (Fix a bug I introduced in rev 1.55.)

Detective work by: jake


Revision tags: release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2
# 149004e9 13-Aug-2002 Alfred Perlstein <alfred@FreeBSD.org>

Make SYSVSEM mpsafe. Each semaphore set gets its own lock, however
there is a global lock over the undo structures because of the way
they are managed.

Switch to using SLIST instead of rolling our

Make SYSVSEM mpsafe. Each semaphore set gets its own lock, however
there is a global lock over the undo structures because of the way
they are managed.

Switch to using SLIST instead of rolling our own linked list.

Fix several races where a permission check was done before a
copyin/copyout, if the copy happened to fault it may have been
possible to race for access to a semaphore set that one shouldn't
have access to.

Requested by: rwatson
Tested by: NetBSD regression suite.

show more ...


# 4442e4a4 05-Aug-2002 Alfred Perlstein <alfred@FreeBSD.org>

Cleanup:
Fix line wrapping.
Remove 'register'.
malloc(9) with M_WAITOK can't fail, so remove checks for that.


# fd6d9be4 22-Jul-2002 Alfred Perlstein <alfred@FreeBSD.org>

Cleanup:
Define a debug printf macro rather than wrapping all calls to printf
with #ifdefs.


# 2cc593fd 22-Jul-2002 Alfred Perlstein <alfred@FreeBSD.org>

Remove caddr_t.


Revision tags: release/4.6.1, release/4.6.0_cvs
# 4d77a549 19-Mar-2002 Alfred Perlstein <alfred@FreeBSD.org>

Remove __P.


# 3ba30c18 19-Mar-2002 Peter Wemm <peter@FreeBSD.org>

Pacify gcc-3.1+, initialize two variables to avoid -Wuninitialized
warnings.


# cf11f482 06-Mar-2002 Maxim Konovalov <maxim@FreeBSD.org>

Fix a typo, unbreak the world.

Thanks to: mux
Approved by: ru


# 9dfd307b 06-Mar-2002 Maxim Konovalov <maxim@FreeBSD.org>

Maximum semid is seminfo.semmni not seminfo.semmsl.

PR: kern/34979
Submitted by: James Gritton <jamie@gritton.org>
Reviewed by: alfred, ru
Approved by: ru
MFC after: 1 week


# c6f55f33 05-Mar-2002 John Baldwin <jhb@FreeBSD.org>

- Use td_ucred for jail checks.
- Move jail checks and some other checks involving constants and stack
variables out from under Giant. This isn't perfectly safe atm because
jail_sysvipc_allowed

- Use td_ucred for jail checks.
- Move jail checks and some other checks involving constants and stack
variables out from under Giant. This isn't perfectly safe atm because
jail_sysvipc_allowed is read w/o a lock meaning that its value could be
stale. This global variable will soon become a per-jail flag, however,
at which time it will either not need a lock or will use the prison lock.

show more ...


# 4a7d6cd2 27-Feb-2002 John Baldwin <jhb@FreeBSD.org>

Fix Giant leakage in several error cases in __semctl().


# a854ed98 27-Feb-2002 John Baldwin <jhb@FreeBSD.org>

Simple p_ucred -> td_ucred changes to start using the per-thread ucred
reference.


# b541b65d 18-Feb-2002 Robert Watson <rwatson@FreeBSD.org>

Rehash of 1.43: simply remove the comment, since it's highly redundant
and only partially correct.


12345678910>>...12