| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
is seems to be a problem for SUID applications, which we like to
prevent as much as possible.
PR: docs/39530
Submitted by: Soren Spies <sspies at apple dot com>
MFC After: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
a module was loaded might make the pathname inaccurate.
I wonder if an inode reference should be stored with the pathname
to allow a validity check?
Suggested by: rwatson@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for kldstat(2).
This allows libdtrace to determine the exact file from which
a kernel module was loaded without having to guess.
The kldstat(2) API is versioned with the size of the
kld_file_stat structure, so this change creates version 2.
Add the pathname to the verbose output of kldstat(8) too.
MFC: 3 days
|
|
|
|
| |
Approved by: re(ken)
|
|
|
|
|
|
|
| |
the netbsd versions, and tweaked by me with suggestions from phk.
Reviewed by: phk
Approved by: re@
|
|
|
|
|
|
|
|
| |
file systems since 2005.
Submitted by: Igor Sysoev
Approved by: re (bmah)
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Tijl Coosemans tijl at ulyssis dot org
Approved by: re (kensmith)
|
|
|
|
|
| |
Approved by: re (blanket)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
call the pad-less versions of the corresponding syscalls if the running
kernel supports it. Check kern.osreldate once per program and cache the
result to select the appropriate syscall. This maintains userland
compatability with kernel.old's from quite a while back.
Approved by: re (kensmith)
|
|
|
|
|
|
|
|
|
|
| |
syscalls, unless WITHOUT_SYSCALL_COMPAT is defined. The default case
will have the .c wrappers still. If you define WITHOUT_SYSCALL_COMPAT,
the .c wrappers will go away and libc will make direct syscalls.
After 7-stable starts, the direct syscall method will be default.
Approved by: re (kensmith)
|
| |
|
|
|
|
| |
Submitted by: peter
|
| |
|
| |
|
|
|
|
|
| |
SSP functions into FreeBSD libc. Use the same file name and location
for consistency with other projects.
|
|
|
|
|
|
| |
PR: docs/78915
Submitted by: Marc Olzheim <marcolz@stack.nl>
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
it is only relevant to receiving data from sockets, not to sending.
PR: 109667
Submitted by: Jari Kirma <kirma@cs.hut.fi>
Approved by: wollman
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
OpenSolaris. For more information please refer to:
http://blogs.sun.com/bonwick/entry/seek_hole_and_seek_data
|
|
|
|
| |
Pointed out by: ru
|
|
|
|
|
| |
Submitted by: Vlad GALU (with changes)
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: rwatson
Pointy hat to: bms
|
|
|
|
| |
use wording of FreeBSD License.
|
| |
|
|
|
|
|
| |
Submitted by: ru
MFC after: 2 days
|
|
|
|
| |
Submitted by: brueffer
|
|
|
|
|
|
|
|
| |
Add IMPLEMENTATION NOTES section explaining in detail the effect this
system call has in common use cases involving PF_INET and PF_INET6 sockets.
PR: kern/84761
MFC after: 2 days
|
|
|
|
| |
reported by pluknet@gmail.com.
|
| |
|
|
|
|
| |
Noticed by: Harlan Stenn <stenn@ntp.isc.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
effective group ID (and any of our group) doesn't match the group ID of the
file, we get EPERM. This doesn't conform POSIX. POSIX requires that we should
return 0, but silently clear the set-gid bit.
|
| |
|
|
|
|
|
|
|
|
| |
PR: docs/107696
Submitted by: Rob Robertson
Reviewed by: ru
Obtained from: NetBSD (mostly)
MFC after: 1 week
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
|
|
|
|
|
|
| |
- O_NONBLOCK flag has to be set, if it is not set, open(2) will wait for
another process opening the fifo for reading,
- Use O_WRONLY which implies that the file has to be opened _only_ for write.
|
|
|
|
| |
reside on a read-only file system.
|
|
|
|
|
| |
separately. Do the same.
- Document when EPERM can be returned.
|
|
|
|
|
|
|
|
|
|
| |
This is quite tricky situation, because we allow to open a file with
O_RDONLY|O_TRUNC. O_TRUNC modifies a file, but we actually don't open
it for writing. EISDIR is also returned when we try to open a directory
O_RDONLY|O_TRUNC, which is correct.
POSIX says that "The result of using O_TRUNC with O_RDONLY is undefined.",
we choose to accept it (Solaris did the same), that's why "to be modified"
seems more accurate to me.
|