| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and writev() except that they take an additional offset argument and do
not change the current file position. In SAT speak:
preadv:readv::pread:read and pwritev:writev::pwrite:write.
- Try to reduce code duplication some by merging most of the old
kern_foov() and dofilefoo() functions into new dofilefoo() functions
that are called by kern_foov() and kern_pfoov(). The non-v functions
now all generate a simple uio on the stack from the passed in arguments
and then call kern_foov(). For example, read() now just builds a uio and
calls kern_readv() and pwrite() just builds a uio and calls kern_pwritev().
PR: kern/80362
Submitted by: Marc Olzheim marcolz at stack dot nl (1)
Approved by: re (scottl)
MFC after: 1 week
|
|
|
|
| |
Approved by: re (hrs)
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
|
|
|
|
| |
reflects the actual behavior of the API
for listing extended attributes.
PR: docs/79261
Submitted by: rodrigc
Reviewed by: rwatson, kan
Approved by: das (mentor)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
aio_write(2) completion through kevent(2). This method does not work on
64-bit architectures. It was deprecated in FreeBSD 4.4. See revisions
1.87 and 1.70.2.7.
Change aio_physwakeup() to call psignal(9) directly rather than indirectly
through a timeout(9). Discussed with: bde
Correct a bug introduced in revision 1.65 that could result in premature
delivery of a signal if an lio_listio(2) consisted of a mixture of
direct/raw and queued I/O operations. Observed by: tegge
Eliminate a field from struct kaioinfo that is now unused.
Reviewed by: tegge
|
|
|
|
|
|
|
|
| |
negative (in addition to returning EINVAL when called on a descriptor
that is not a socket).
Submitted by: Arne H Juul <arnej@europe.yahoo-inc.com>
PR: docs/80587
|
|
|
|
|
|
| |
Bump FreeBSD_version to note this change.
Reviewed by: sobomax
|
|
|
|
| |
Noticed by: ru, who else? :)
|
|
|
|
|
|
|
| |
page. They do not exist.
PR: 53303
Submitted by: Marc Silver <marcs@draenor.org> (original version)
|
|
|
|
|
|
|
|
| |
attribute does not exist on the file.
-bump document date
Reviewed by: rwatson,trhodes
MFC after: 1 week
|
|
|
|
|
|
| |
Note that unlink.2 can return EPERM if the immutable or append-only flags are set.
PR: 77043
|
| |
|
| |
|
| |
|
|
|
|
| |
for more than INT_MAX bytes.
|
| |
|
|
|
|
|
|
|
|
| |
destination address to a datagram socket that is already connected.
Submitted by: Rudolf Cejka <cejkar@fit.vutbr.cz>
PR: docs/76399
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
o Sticky bit is actually defined as S_ISTXT not S_ISVTX.
o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a "null pointer".''
Making good use of the excellent explanations sent to me by Ruslan
Ermilov, Garrett Wollman and Bruce Evans, correct the descriptions of
null pointers. They are just "null pointers", not nil, not NULL or
".Dv NULL".
Suggested by: ru, wollman, bde
Reviewed by: ru, wollman
Pointy hat: keramida
|
|
|
|
| |
Noticed by: ru
|
| |
|
|
|
|
| |
"initialization process".
|
| |
|
|
|
|
|
| |
Note to mdoc(7) police:
The document date has already been touched today.
|
| |
|
| |
|
|
|
|
| |
use .Va instead of .Li for struct stat fields.
|
|
|
|
| |
Bump the document date accordingly.
|
|
|
|
|
| |
PR: docs/73193
Submitted by: Jilles Tjoelker <jilles at stack.nl>
|
|
|
|
| |
Discussed with: bde
|
|
|
|
|
|
|
| |
which have no negative offsets, "negative" and
"invalid" are equivalent WRT the offset argument.
Suggested by: bde
|
|
|
|
| |
when transfering rights (file descriptors.)
|
|
|
|
|
|
|
| |
Now readers won't get an impression that pointing to beyond
the current end of file will result in EINVAL.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
| |
to sendfile(2) falls beyond the end of file.
Touch .Dd.
PR: bin/72649 (in the audit trail)
MFC after: 1 week
|
|
|
|
| |
MFC in: 1 week
|
|
|
|
|
|
|
|
|
| |
documenting the obsoleteness of the msync(2) syscall and its single
remaining purpose.
PR: 70916
Submitted by: Radim Kolar <hsn@netmag.cz>
MFC after: 3 days
|
|
|
|
|
|
|
| |
to mksnap_ffs(8).
PR: 70402
Submitted by: James Raftery <james@now.ie>
|
| |
|
|
|
|
|
| |
a case where ENOMEM could be returned by munlock(2), and add possible
system deadlock to the BUGS section.
|
|
|
|
|
|
| |
PR: 69428
Submitted by: Sascha Schneider <suntsu@suntsu.org>
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
file as an argument, it may still fail for the same reasons that
open(2) can.
Pointed out by: Jilles Tjoelker
Apporived by: bmilekic (mentor)
|
|
|
|
|
|
|
|
| |
for statfs(2). This is false, if the pathname specified
is a regular file, then the information for the file
system that the file lives on will be returned.
Approved by: bmilekic (mentor)
|
| |
|
|
|
|
|
|
|
|
|
| |
The getfsstat(2) function expects a buffer and a count, and returns a count.
The confusing part is that the count it takes is a byte count, while the
return value is a count of the number of structures it has filled out.
Spell this out.
|