| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
outside the range of valid file descriptors
PR: kern/164970
Submitted by: Peter Jeremy <peterjeremy@acm.org>
Reviewed by: jilles
Approved by: cperciva
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
usermode context switches (long jumps and ucontext operations). If these
are used across threads, multiple threads can end up with the same TLS base.
Madness will then result.
This makes behavior on PPC match that on x86 systems and on Linux.
MFC after: 10 days
|
|
|
|
|
|
|
|
|
| |
privilege attempts to toggle SF_SETTABLE flags.
- Use the '^' operator in the SF_SNAPSHOT anti-toggling check.
Flags are now stored to ip->i_flags in one place after all checks.
Submitted by: bde
|
|
|
|
|
|
|
|
|
|
|
|
| |
is already open in this process.
If the named semaphore is already open, sem_open() only increments a
reference count and did not take the flags into account (which otherwise
happens by passing them to open()). Add an extra check for O_CREAT|O_EXCL.
PR: kern/166706
Reviewed by: davidxu
MFC after: 10 days
|
|
|
|
|
|
|
| |
currently generated code clobbers r3. Fix this by loading ARM_TP_ADDRESS
using inline assembly.
Approved by: imp (mentor)
|
|
|
|
| |
Sorry! :(
|
| |
|
|
|
|
|
|
|
| |
is a descriptor, not a code address), which prevents crashes when starting
a context. This fixes QEMU on powerpc64.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
quotation. Also make sure we have the same amount of columns in each row as
the number of columns we specify in the head arguments.
Reviewed by: brueffer
|
|
|
|
|
|
|
| |
application destroys semaphore after sem_wait returns. Just enter
kernel to wake up sleeping threads, only update _has_waiters if
it is safe. While here, check if the value exceed SEM_VALUE_MAX and
return EOVERFLOW if this is true.
|
|
|
|
|
|
|
|
| |
by the current code, and the results would get overwritten anyway
by subsequent memset().
Reviewed by: ume
MFC after: 1 month
|
|
|
|
| |
Reviewed by: brueffer
|
| |
|
|
|
|
|
| |
this syntax violation and while I'm here also convert <TAB> to Ta and adjust
quotation marks in order to prevent this problem in the future.
|
|
|
|
|
|
|
| |
Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days
|
|
|
|
|
| |
Reviewed by: gjb
Approved by: sbruno
|
|
|
|
| |
Reviewed by: gabor
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: brueffer
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: brueffer
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Because the utmpx interface is generally not required to be thread-safe,
but it is nice to have, if easy to do so. Therefore don't make a mess
out of the code and only use it if __NO_TLS is not defined.
|
|
|
|
| |
Pointed out by: stefanf
|
|
|
|
|
|
| |
when passing damaged user-supplied fstab file data.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
no waiters, we still increase and decrease count in user mode without
entering kernel, once there is a waiter, sem_post will enter kernel to
increase count and wake thread up, this is atomicy and allow us to
gracefully destroy semaphore after sem_wait returned.
|
|
|
|
|
|
| |
debug mode (without optimisations) it doesn't generate a linker failure.
Approved by: dim (mentor)
|
|
|
|
| |
Approved by: hrs (mentor)
|
|
|
|
|
|
|
|
| |
how it may be set, and current limitations on the value.
Approved by: hrs (mentor)
PR: docs/157453
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
PR: docs/163771
Submitted by: phk
Reviewed by: If someone else reviewed your modification.
Approved by: cperciva
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
pathnames.
With the current API (no *at functions), FTS_NOCHDIR requires that the
fts_accpath start with the original path passed to fts_open(); therefore,
the depth that can be reached is limited by the {PATH_MAX} constraint on
this pathname.
MFC after: 1 week
|
|
|
|
|
|
| |
PR: docs/166091
Submitted by: Matthew Story
MFC after: 1 week
|
| |
|
|
|
|
| |
Approved by: cognet
|
|
|
|
|
|
|
|
| |
Document EIO from msync(2).
Inspired by PR: docs/165929 [1]
Reviewed by: jilles
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
Just like kill(2), it is impossible for killpg(0, ...) to fail with
ESRCH, as a process always has a process group.
Discussed on: arch@
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
This errno can also be returned if the passed process identifier doesn't
correspond with a process group.
Discussed on: arch@
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
On FreeBSD, all processes have a process group, so it is impossible for
kill(2) to fail this way. POSIX also doesn't mention this error
condition.
Discussed on: arch@
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Approved by: dim (mentor)
|
|
|
|
| |
Approved by: dim (mentor)
|