| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
pointer, here we keep orignal %ebp, so we can see where signal handler
comes in and interrupt normal code.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
setting %ebp to zero, this avoids new gdb to dump a weird
backtrace.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pointer to the corresponding struct thread to the thread ID (lwpid_t)
assigned to that thread. The primary reason for this change is that
libthr now internally uses the same ID as the debugger and the kernel
when referencing to a kernel thread. This allows us to implement the
support for debugging without additional translations and/or mappings.
To preserve the ABI, the 1:1 threading syscalls, including the umtx
locking API have not been changed to work on a lwpid_t. Instead the
1:1 threading syscalls operate on long and the umtx locking API has
not been changed except for the contested bit. Previously this was
the least significant bit. Now it's the most significant bit. Since
the contested bit should not be tested by userland, this change is
not expected to be visible. Just to be sure, UMTX_CONTESTED has been
removed from <sys/umtx.h>.
Reviewed by: mtm@
ABI preservation tested on: i386, ia64
|
| |
|
|
|
|
|
| |
Fixed markup.
Fixed examples to match the new API.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
instead of asking the kernel to do it when we create the thread.
|
| |
| |
| |
| | |
Noticed by: Stoned Elipot
|
| | |
|
| |
| |
| |
| | |
chmod() and not lchmod() whenever we know we didn't extract a symlink.
|
| |
| |
| |
| |
| |
| | |
applied to their permissions. Just calculate the
default dir mode once and use it consistently, rather than
trying to remember to calculate it everywhere it's needed.
|
| |
| |
| |
| | |
is a defacto standard on other UNIX systems.
|
| |
| |
| |
| | |
(This is the converse of the "don't add an archive to itself".)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Rename some variables/functions/etc to try to make things clearer.
* Add separate flags to control fflag/acl restore
* Collect metadata restore into a single function for clarity
* Propagate errors in metadata restore back out to the client
* Fix some places where errors were being returned when they
shouldn't and vice-versa
* Modes are now always restored; ARCHIVE_EXTRACT_PERM just controls
whether or not umask is obeyed.
* Restore suid/sgid bits only if user/group matches archive
* Cache the last stat results to try to reduce the number of stat calls
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
archive_entry.
Update the Makefile MLINKS and manpage to bring it up-to-date with
the current status of archive_entry. At least the manpage actually
lists all of the functions now, even if it doesn't really yet explain
them all.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Mostly, these were being used correctly even though a lot of
variables and function names were mis-named.
In the process, I found and fixed a couple of latent bugs and
added a guard against adding an archive to itself.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a/././b/../b/../c/./../d/e/f now work correctly. And yes, a/b and a/c
both get created in this example; if you want, you can create an
entire dir heirarchy from a tar archive with only one entry.
More tweaks to umask support: umasks are now obeyed for all objects,
not just directories; the umask used is now the one in effect at the
corresponding call to archive_read_extract(), so clients that want to
tinker with umask during extract should get the expected behavior.
|
| |
| |
| |
| |
| |
| | |
work in libpthread.
Submitted by: Dan Nelson <dnelson@allantgroup.com>
|
| |
| |
| |
| |
| |
| | |
a fork, make sure that the current thread isn't detached and freed. As
a consequence the thread should be inserted into the head of the
active list only once (in the beginning).
|
| |
| |
| |
| |
| |
| |
| | |
umask in effect when the archive is closed
* Correct a typo that broke implicit dir creation for non-directories.
Thanks to: Garret A Wollman for pointing out my umask oversight
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
read_extract_dir (which creates directories in the archive). This
brings a number of advantages:
* FINALLY fix the problems creating dirs ending in "/." <sigh>
* Missing parent dirs now get created securely, just like explicit dirs.
(Created 0700 initially, then edited to 0755 at end of extraction.)
* Eliminate some duplicate code and some weird special cases.
While I'm cleaning, inline the regular-file creation code as well.
|
| |
| |
| |
| |
| |
| |
| | |
This change also pointed out one API deficiency: the
archive_read_data_into_XXX functions were originally defined to return
the total bytes read. This is, of course, ambiguous when dealing with
non-contiguous files. Change it to just return a status value.
|
| |
| |
| |
| | |
they break due to diferent alignment restrictions.
|
| | |
|
| |
| |
| |
| | |
for this now.
|
| | |
|
| |
| |
| |
| |
| |
| | |
with the user's environment.
Wondered why his cross-builds kept failing: marcel
|
| |
| |
| |
| | |
Submitted by: Cyrille Lefevre
|
| |
| |
| |
| | |
Submitted by: Cyrille Lefevre
|
| |
| |
| |
| |
| |
| | |
with ``__'' to avoid polluting the namespace. This doesn't change the
documented rune interface at all, but breaks applications that accessed
_RuneLocale directly.
|
| |
| |
| |
| |
| |
| | |
socket upon accept(2).
PR: docs/54995, kern/45733
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Submitted by: Chirstopger Nehren <apeiron@comcast.net>
|
| |
| |
| |
| |
| |
| | |
speed improvement to none at all over the MI version.
Submitted by: bde
|