summaryrefslogtreecommitdiffstats
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* - Restore kse.h in this directory so other tools don't find it by mistake.jeff2008-03-233-1/+137
| | | | | | - Restore the ability to debug kse coredumps in 8.0. Suggested by: marcel
* Add POSIX pthread API pthread_getcpuclockid() to get a thread's cpudavidxu2008-03-223-0/+50
| | | | time clock id.
* Use linker set to collection all target operations.davidxu2008-03-224-13/+22
|
* Add MLINK for archive_write_close.kaiw2008-03-211-0/+1
| | | | Approved by: jkoshy(mentor), kientzle
* Resolve __error()'s PLT early so that it needs not to be resolved again,davidxu2008-03-211-0/+3
| | | | | otherwise rwlock is recursivly called when signal happens and the __error was never resolved before.
* pthread_mutexattr_destroy() was accidentally broken in last revision,ru2008-03-201-0/+1
| | | | unbreak it. We should really start compiling this with warnings.
* s/wait/delta/ to avoid namespace collision.des2008-03-201-16/+16
| | | | MFC after: 2 weeks
* Preserve application code's errno in rtld locking code, it attemps to keepdavidxu2008-03-201-2/+31
| | | | any case safe.
* Make pthread_mutexattr_settype to return error number directly anddavidxu2008-03-201-3/+1
| | | | | | conformant to POSIX specification. Bug reported by: modelnine at modelnine dt org
* don't reduce new thread's refcount if current thread can not set cpusetdavidxu2008-03-191-1/+1
| | | | for it, since the new thread will reduce it by itself.
* - Trim trailing spaces.davidxu2008-03-191-8/+8
| | | | - Use a different sigmask variable name to avoid confusing.
* if passed thread pointer is equal to current thread, pass -1 to kerneldavidxu2008-03-191-11/+19
| | | | to speed up searching.
* Ensure that the section header table is written out in an orderjkoshy2008-03-191-3/+2
| | | | | | | consistent with the section indices returned to the application by elf_ndxscn(). Submitted by: kaiw
* Clarify that the ELF library only sets the sh_entsize field of ajkoshy2008-03-191-4/+4
| | | | | | | | | section header entry if the application is not taking charge of ELF object layout. Update (c) years, and bump the manual page's date. Submitted by: kaiw
* Add mandatory "security description" SDP parameter to the PANU profileemax2008-03-191-0/+2
| | | | | Pointed-out by: Iain Hibbert < plunky at rya-online dot net > MFC after: 3 days
* Add PSM and Load Factor SDP parameters to the BNEP based profilesemax2008-03-181-9/+24
| | | | | | | | | | | (NAP, GN and PANU). No reason to not to support them. Separate SDP parameters data structures for the BNEP based profiles. Generalize Service Availability SDP parameter creation. Requested by: Iain Hibbert < plunky at rya-online dot net > MFC after: 3 days
* - Copy signal mask out before THR_UNLOCK(), because THR_UNLOCK() may calldavidxu2008-03-183-4/+17
| | | | | | | | _thr_suspend_check() which messes sigmask saved in thread structure. - Don't suspend a thread has force_exit set. - In pthread_exit(), if there is a suspension flag set, wake up waiting- thread after setting PS_DEAD, this causes waiting-thread to break loop in suspend_common().
* Don't allocate the constant array "props" on the stack in wctype.antoine2008-03-171-1/+1
| | | | | | | PR: 74743 Submitted by: knut st. osmundsen Approved by: rwatson (mentor) MFC after: 1 month
* scandir(3) previously used st_size to obtain an initial estimatedas2008-03-161-13/+3
| | | | | | | | | | | | | of the array length needed to store all the directory entries. Although BSD has historically guaranteed that st_size is the size of the directory file, POSIX does not, and more to the point, some recent filesystems such as ZFS use st_size to mean something else. The fix is to not stat the directory at all, set the initial array size to 32 entries, and realloc it in powers of 2 if that proves insufficient. PR: 113668
* Actually delete SIGCANCEL mask for suspended thread, so the signal will notdavidxu2008-03-161-3/+2
| | | | be masked when it is resumed.
* Update a comment: the format bid only runs once per archive; it nokientzle2008-03-151-9/+2
| | | | longer runs once per entry.
* Free up the entry objects allocated during this test.kientzle2008-03-151-0/+3
|
* Release the buffers used for exercising the compress code.kientzle2008-03-151-0/+3
|
* Remove the duplicate "archive_format" and "archive_format_name" fieldskientzle2008-03-157-29/+22
| | | | | | | from the private archive_write structure and fix up all writers to use the format fields in the base "archive" structure. This error made it impossible to query the format after setting up a writer because the write format was stored in an inaccessible place.
* Correct a sign mismatch that only showed up on 64-bit systems.kientzle2008-03-151-2/+2
| | | | Pointy hat: me
* Refactor the mtree code a bit to make the layering clearer: Eachkientzle2008-03-151-106/+172
| | | | | | "file" is described by multiple "lines" each possibly containing multiple "keywords." Incorporate some additions from Joerg Sonnenberger to handle linked files and correctly deal with backing files on disk.
* FreeBSD does have fstat().kientzle2008-03-152-1/+2
| | | | Correct the nasty typo this uncovers.
* Testability is more important than standards conformance.kientzle2008-03-151-3/+8
| | | | | | Disable the use of PaxHeader.<pid> for the fake pax extension pathname until I can make the name here settable. Otherwise, tests that try to compare output to static pre-generated reference files break.
* Ignore a few more common files.kientzle2008-03-151-1/+7
|
* Resolve a minor nit in SUS compliance by including the PID in thekientzle2008-03-152-12/+27
| | | | fake directory name used for pax extended headers.
* GC a reference to the defunct TESTFILES variable.kientzle2008-03-151-1/+1
|
* A subtle point: "pax interchange format" mandates that all stringskientzle2008-03-155-259/+538
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (including pathname, gname, uname) be stored in UTF-8. This usually doesn't cause problems on FreeBSD because the "C" locale on FreeBSD can convert any byte to Unicode/wchar_t and from there to UTF-8. In other locales (including the "C" locale on Linux which is really ASCII), you can get into trouble with pathnames that cannot be converted to UTF-8. Libarchive's pax writer truncated pathnames and other strings at the first nonconvertible character. (ouch!) Other archivers have worked around this by storing unconvertible pathnames as raw binary, a practice which has been sanctioned by the Austin group. However, libarchive's pax reader would segfault reading headers that weren't proper UTF-8. (ouch!) Since bsdtar defaults to pax format, this affects bsdtar rather heavily. To correctly support the new "hdrcharset" header that is going into SUS and to handle conversion failures in general, libarchive's pax reader and writer have been overhauled fairly extensively. They used to do most of the pax header processing using wchar_t (Unicode); they now do most of it using char so that common logic applies to either UTF-8 or "binary" strings. As a bonus, a number of extraneous conversions to/from wchar_t have been eliminated, which should speed things up just a tad. Thanks to: Bjoern Jacke for originally reporting this to me Thanks to: Joerg Sonnenberger for noting a bad typo in my first draft of this Thanks to: Gunnar Ritter for getting the standard fixed MFC after: 5 days
* Ignore some built files.kientzle2008-03-151-0/+4
|
* Don't lie. If a string can't be converted to a wide (Unicode) string,kientzle2008-03-142-1/+43
| | | | | return a NULL instead of an incomplete string. Expand the test coverage to verify the correct behavior here.
* Don't advertise the default block size as a constant; don'tkientzle2008-03-141-1/+6
| | | | | | | rely on a deprecated value to set the default. This is also related to a longer-term goal of setting the default block size based on format and possibly other factors, which makes it a bad idea to tie this to a published constant.
* New public functions archive_entry_copy_link() and archive_entry_copy_link_w()kientzle2008-03-145-1/+58
| | | | | override the currently set link value, whether that's a hardlink or a symlink. Plus documentation update and tests.
* Update some comments, comment out argument names to guard againstkientzle2008-03-141-16/+50
| | | | namespace problems.
* Since "length" computes the length of a string and is used as ankientzle2008-03-141-1/+1
| | | | argument to malloc(3), it should be size_t, not int.
* Let archive_entry_clear() accept a NULL pointer and simply do nothing.kientzle2008-03-141-0/+2
| | | | | In particular, this allows archive_entry_free() to work correctly for a NULL pointer, which makes it parallel with free(3).
* Rework the versioning implementation and test to match thekientzle2008-03-142-2/+58
| | | | | | | | | | new interface. Mark the functions that are going away in libarchive 3.0. In particular, archive_version_string() now computes the string rather than assuming that it will be created by the build infrastructure. Eventually, this will allow some simplification of the build infrastructure.
* Rework the versioning information, hopefully for the last time.kientzle2008-03-141-41/+37
| | | | | | | | | | | | | | | | | | * There are now only two public version identifiers: "number" is a single integer that combines Major/minor/release in a single value of the form Mmmmrrr. This is easy to compare against for checking feature support. "string" is a displayable text string of the form "libarchive M.mm.rr". * The number is present both as a macro (version of the installed header) and a function (version of the shared library). The string form is available only as a function. * Retain the older version definitions for now, but mark them all as deprecated, to disappear in libarchive 3.0 (whenever that happens). * Rework the various deprecation conditionals to use ARCHIVE_VERSION_NUMBER. An ancillary goal is to reduce the number of @...@ substitutions that are required. Someday, I might even be able to avoid build-time processing of archive.h entirely.
* Add a useful sprintf()-style wrapper aroundkientzle2008-03-142-0/+13
| | | | | | archive_string_vsprintf(). (Which is built on top of libarchive's internal resizable string support.)
* Support for writing 'compress' format, thanks to Joerg Sonnenberger.kientzle2008-03-145-0/+596
|
* A block in a tar file is 512 bytes. Period.kientzle2008-03-141-1/+1
| | | | | | | | | | Remove the entirely pointless symbolic constant and sizeof(unsigned char). (The constant here is doubly wrong, since not only does it obscure a basic format constant, it was never intended to be a tar-specific value, so could conceivably be changed at some point in the future.)
* - Document Pentium and Pentium MMX events.jkoshy2008-03-141-2/+338
| | | | - Update (c) years and the manual page's date.
* Fix bugs in previous revision (missing comma, misspelled syscall name).ru2008-03-131-3/+2
|
* Remove trailing whitespace.ru2008-03-131-1/+1
|
* Add missing section number.ru2008-03-131-1/+1
|
* In file sem_timewait.3, remove reference to SYSV semphore in SEE ALSOdavidxu2008-03-132-4/+3
| | | | section, sync it with sem_wait.3.
* Current 'ar' read support in libarchive can only handle a GNU/SVR4kaiw2008-03-123-42/+41
| | | | | | | | | | | | | | | | | | | | | | | | | filename table whose size is less than 65536 bytes. The original intention was to not consume the filename table, so the client will have a chance to look at it. To achieve that, the library call decompressor->read_ahead to read(look ahead) but do not call decompressor->consume to consume the data, thus a limit was raised since read_ahead call can only look ahead at most BUFFER_SIZE(65536) bytes at the moment, and you can not "look any further" before you consume what you already "saw". This commit will turn GNU/SVR4 filename table into "archive format data", i.e., filename table will be consumed by libarchive, so the 65536-bytes limit will be gone, but client can no longer have access to the content of filename table. 'ar' support test suite is changed accordingly. BSD ar(1) is not affected by this change since it doesn't look at the filename table. Reported by: erwin Discussed with: jkoshy, kientzle Reviewed by: jkoshy, kientzle Approved by: jkoshy(mentor), kientzle
OpenPOWER on IntegriCloud