| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
(cherry picked from commit a682a1bf553b1efe4dbb03207fece5b719cec482)
|
|
(cherry picked from commit 0f622686af3ae5a8f03dae886b08c260b38bda16)
|
|
The pt_chown program is completely transparently called. It might
not be able to live with the various file descriptors the program
has open at the time of the call (e.g., under SELinux). Close all
but the needed descriptor and connect stdin, stdout, and stderr
with /dev/null. pt_chown shouldn't print anything when called to
do real work.
(cherry picked from commit 139ee080b6b428240bf49f3e6361f3ac729f891a)
|
|
|
|
|
|
(cherry picked from commit 0f622686af3ae5a8f03dae886b08c260b38bda16)
|
|
The pt_chown program is completely transparently called. It might
not be able to live with the various file descriptors the program
has open at the time of the call (e.g., under SELinux). Close all
but the needed descriptor and connect stdin, stdout, and stderr
with /dev/null. pt_chown shouldn't print anything when called to
do real work.
(cherry picked from commit 139ee080b6b428240bf49f3e6361f3ac729f891a)
|
|
(cherry picked from commit 66221417957963c1d2df8d79f43573e328df2275)
|
|
I've noticed that sync_file_range is a stub on ppc/ppc64.
The kernel on these arches provides sync_file_range2 syscall with swapped
parameters.
The following completely untested patch ought to fix this.
(cherry picked from commit 8ad81b316bc158746aee18aa7d7df44d3eb61871)
|
|
(cherry picked from commit 03ebadd9eaa4663f58bd3fa6fe8283f255925632)
|
|
(cherry picked from commit 2866eeb1b70c989591293d37ae292e71def16775)
|
|
Fix building on x86 when older linux headers lack __NR_fallocate define.
(cherry picked from commit f9a7bd536e0b1693db32e1330bbd96108ca63c42)
|
|
(cherry picked from commit 8964681064db9f13ee4ec7f46c53f04d66a04b99)
|
|
|
|
Due to alignment of 64bit parameters there is a dummy second argument.
But other than that the syscall arguments are directly mapped to the
function arguments.
|
|
I've just committed STT_GNU_IFUNC ppc/ppc64 support into prelink,
and this patch is needed on the glibc side. Without it ld.so segfaults,
as in dl-conflict.c sym_map is always NULL. While dl-machine.h could use
RESOLVE_CONFLICT_FIND_MAP macro to compute it, it doesn't make sense,
because with prelink we know it is already properly relocated (all relative
relocations are applied by prelink).
|
|
As reported in http://bugzilla.redhat.com/533063 , preadv/pwritev prototypes
are wrong on 32-bit arches with -D_FILE_OFFSET_BITS=64 and as I've just
found, fallocate is wrong too.
The problem is that only off_t is remapped to the 64-bit type transparently,
__off_t is not.
|
|
|
|
|
|
Due to alignment of 64bit parameters there is a dummy second argument.
But other than that the syscall arguments are directly mapped to the
function arguments.
|
|
|
|
f_owner_ex for Linux targets."
They depend on F_GETOWN_EX/F_SETOWN_EX.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When passed an empty string for the filename, the compat code
using /proc in all *at functions did the wrong thing.
|
|
Several bugs fixed when we needed to create a thread to work on AIO
requests but failed and there is not one running.
|
|
The implementation of posix_openpt on Linux can fail in a few extra
ways if the appropriate pseudo filesystems are not mounted etc. In
some of these cases we have to explicitly set errno.
|
|
If a second call to ttyname is not for the same type of device (e.g.,
serial vs ptty) the prefix of the buffer was wrong. Don't rely on
the previous content, always reinitialize it.
|
|
|
|
The syscall conventions on some Linux archs prevented F_GETOWN from working
correctly in some situations. This can be rectified when using the new
F_GETOWN_EX command.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tst-longjmp_chk passes, tst-longjmp_chk2 fails but that is because
of some limitations of kernel signal delivery on sparc that I need
to fix, it has nothing to do with the longjmp_chk implementation.
(The problem with tst-longjmp_chk2 is that it tries to do a stack
fault SIGSEGV within a stack fault SIGSEGV , and the Linux kernel
will refuse to setup the signal stack and deliver the signal if the
register windows can't be written out to the stack first)
|
|
The values of F_SETOWN_EX and F_GETOWN_EX conflict with F_GETLK64 and
F_SETLK64 and are not finalized yet.
|
|
|
|
definitions.
|
|
|
|
|
