#
303975 |
|
11-Aug-2016 |
gjb |
Copy stable/11@r303970 to releng/11.0 as part of the 11.0-RELEASE cycle.
Prune svn:mergeinfo from the new branch, and rename it to RC1.
Update __FreeBSD_version.
Use the quarterly branch for the default FreeBSD.conf pkg(8) repo and the dvd1.iso packages population.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
302408 |
|
08-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
260572 |
|
12-Jan-2014 |
jilles |
fts(3): Remove stray mentions of the obsolete fts_bignum.
|
#
250888 |
|
21-May-2013 |
ed |
Update manpages for r250887.
Remove the lists of unneeded header files.
Requested by: eadler
|
#
233648 |
|
29-Mar-2012 |
eadler |
Remove trailing whitespace per mdoc lint warning
Disussed with: gavin No objection from: doc Approved by: joel MFC after: 3 days
|
#
233132 |
|
18-Mar-2012 |
jilles |
fts(3): Mention that FTS_NOCHDIR imposes {PATH_MAX} limits on the returned 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
|
#
233130 |
|
18-Mar-2012 |
jilles |
fts(3): Document cases where FTS_NOCHDIR is set implicitly.
PR: docs/166091 Submitted by: Matthew Story MFC after: 1 week
|
#
199843 |
|
26-Nov-2009 |
jh |
Clarify that the value of the fts_info field is different in post-order.
Discussed with: das Approved by: trasz (mentor) MFC after: 1 week
|
#
197793 |
|
05-Oct-2009 |
delphij |
fts_open() requires that the list passed as argument to contain at least one path. When the list is empty (contain only a NULL pointer), return EINVAL instead of pretending to succeed, which will cause a NULL pointer deference in a later fts_read() call.
Noticed by: Christoph Mallon (via rdivacky@) MFC after: 2 weeks
|
#
175688 |
|
26-Jan-2008 |
yar |
Our fts(3) API, as inherited from 4.4BSD, suffers from integer fields in FTS and FTSENT structs being too narrow. In addition, the narrow types creep from there into fts.c. As a result, fts(3) consumers, e.g., find(1) or rm(1), can't handle file trees an ordinary user can create, which can have security implications.
To fix the historic implementation of fts(3), OpenBSD and NetBSD have already changed <fts.h> in somewhat incompatible ways, so we are free to do so, too. This change is a superset of changes from the other BSDs with a few more improvements. It doesn't touch fts(3) functionality; it just extends integer types used by it to match modern reality and the C standard.
Here are its points:
o For C object sizes, use size_t unless it's 100% certain that the object will be really small. (Note that fts(3) can construct pathnames _much_ longer than PATH_MAX for its consumers.)
o Avoid the short types because on modern platforms using them results in larger and slower code. Change shorts to ints as follows:
- For variables than count simple, limited things like states, use plain vanilla `int' as it's the type of choice in C.
- For a limited number of bit flags use `unsigned' because signed bit-wise operations are implementation-defined, i.e., unportable, in C.
o For things that should be at least 64 bits wide, use long long and not int64_t, as the latter is an optional type. See FTSENT.fts_number aka FTS.fts_bignum. Extending fts_number `to satisfy future needs' is pointless because there is fts_pointer, which can be used to link to arbitrary data from an FTSENT. However, there already are fts(3) consumers that require fts_number, or fts_bignum, have at least 64 bits in it, so we must allow for them.
o For the tree depth, use `long'. This is a trade-off between making this field too wide and allowing for 64-bit inode numbers and/or chain-mounted filesystems. On the one hand, `long' is almost enough for 32-bit filesystems on a 32-bit platform (our ino_t is uint32_t now). On the other hand, platforms with a 64-bit (or wider) `long' will be ready for 64-bit inode numbers, as well as for several 32-bit filesystems mounted one under another. Note that fts_level has to be signed because -1 is a magic value for it, FTS_ROOTPARENTLEVEL.
o For the `nlinks' local var in fts_build(), use `long'. The logic in fts_build() requires that `nlinks' be signed, but our nlink_t currently is uint16_t. Therefore let's make the signed var wide enough to be able to represent 2^16-1 in pure C99, and even 2^32-1 on a 64-bit platform. Perhaps the logic should be changed just to use nlink_t, but it can be done later w/o breaking fts(3) ABI any more because `nlinks' is just a local var.
This commit also inludes supporting stuff for the fts change:
o Preserve the old versions of fts(3) functions through libc symbol versioning because the old versions appeared in all our former releases.
o Bump __FreeBSD_version just in case. There is a small chance that some ill-written 3-rd party apps may fail to build or work correctly if compiled after this change.
o Update the fts(3) manpage accordingly. In particular, remove references to fts_bignum, which was a FreeBSD-specific hack to work around the too narrow types of FTSENT members. Now fts_number is at least 64 bits wide (long long) and fts_bignum is an undocumented alias for fts_number kept around for compatibility reasons. According to Google Code Search, the only big consumers of fts_bignum are in our own source tree, so they can be fixed easily to use fts_number.
o Mention the change in src/UPDATING.
PR: bin/104458 Approved by: re (quite a while ago) Discussed with: deischen (the symbol versioning part) Reviewed by: -arch (mostly silence); das (generally OK, but we didn't agree on some types used; assuming that no objections on -arch let me to stick to my opinion)
|
#
165903 |
|
09-Jan-2007 |
imp |
Per Regents of the University of Calfornia letter, remove advertising clause.
# If I've done so improperly on a file, please let me know.
|
#
139838 |
|
07-Jan-2005 |
pjd |
Update manual page after adding 'fts_bignum' field.
Submitted by: Peter Jeremy <PeterJeremy@optushome.com.au> MFC after: 5 days
|
#
134473 |
|
29-Aug-2004 |
tjr |
Add cross-reference to ftw(3).
|
#
131504 |
|
02-Jul-2004 |
ru |
Mechanically kill hard sentence breaks.
|
#
119893 |
|
08-Sep-2003 |
ru |
mdoc(7): Use the new feature of the .In macro.
|
#
115641 |
|
01-Jun-2003 |
jmallett |
Match style of source and headers.
Submitted by: bde
|
#
115604 |
|
01-Jun-2003 |
jmallett |
Make prototype match code with regard to constness of args to the function pointer passed in.
|
#
108087 |
|
19-Dec-2002 |
ru |
mdoc(7) police: "The .Fa argument.".
|
#
107387 |
|
29-Nov-2002 |
ru |
mdoc(7) police: formatting nits.
Approved by: re
|
#
103726 |
|
21-Sep-2002 |
wollman |
Make the threatened fts(3) ABI fix. FTSENT now avoids the use of the struct hack, thereby allowing future extensions to the structure (e.g., for extended attributes) without rebreaking the ABI. FTSENT now contains a pointer to the parent stream, which fts_compar() can then take advantage of, avoiding the undefined behavior previously warned about. As a consequence of this change, the prototype of the comparison function passed to fts_open() has changed to reflect the required amount of constness for its use. All callers in the tree are updated to use the correct prototype.
Comparison functions can now make use of the new parent pointer to access the new stream-specific private data pointer, which is intended to assist creation of reentrant library routines which use fts(3) internally.
Not objected to in spirit by: -arch
|
#
83722 |
|
20-Sep-2001 |
ru |
Document the FTS_ROOTPARENTLEVEL and FTS_ROOTLEVEL constants.
|
#
71895 |
|
01-Feb-2001 |
ru |
mdoc(7) police: split punctuation characters + misc fixes.
|
#
70481 |
|
29-Dec-2000 |
ru |
Prepare for mdoc(7)NG.
|
#
68945 |
|
20-Nov-2000 |
ru |
mdoc(7) police: use the new features of the Nm macro.
|
#
67967 |
|
30-Oct-2000 |
asmodai |
Whitespace only change: trim trailing whitespace.
|
#
59460 |
|
21-Apr-2000 |
phantom |
Introduce ".Lb" macro to libc manpages.
More libraries manpages updates following.
|
#
53169 |
|
15-Nov-1999 |
kris |
fts_pathlen and fts_namelen are u_short, not short
Obtained from: OpenBSD
|
#
52671 |
|
30-Oct-1999 |
phantom |
mdoc(7)'fy
|
#
50476 |
|
28-Aug-1999 |
peter |
$Id$ -> $FreeBSD$
|
#
33926 |
|
28-Feb-1998 |
jraynard |
Strings are terminated by NUL, not NULL.
|
#
23555 |
|
09-Mar-1997 |
mpp |
The first argument to fts_set was wrong. Part of PR# 2917.
|
#
14103 |
|
15-Feb-1996 |
jdp |
Corrected a couple of errors in the fts(3) manual page. The prototype for "fts_open" was wrong. Also, the "fts_info" field of the FTSENT structure was misleadingly described as containing "flags". Actually, it contains a single integer value.
|
#
1574 |
|
27-May-1994 |
rgrimes |
This commit was generated by cvs2svn to compensate for changes in r1573, which included commits to RCS files with non-trunk default branches.
|
#
1573 |
|
27-May-1994 |
rgrimes |
BSD 4.4 Lite Lib Sources
|